
From dart@es.net  Tue Nov  1 13:38:16 2011
Return-Path: <dart@es.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B004111E81D1 for <ipv6@ietfa.amsl.com>; Tue,  1 Nov 2011 13:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pYEafUmT-dMw for <ipv6@ietfa.amsl.com>; Tue,  1 Nov 2011 13:38:16 -0700 (PDT)
Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3815C11E8091 for <ipv6@ietf.org>; Tue,  1 Nov 2011 13:38:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=es.net; h=message-id : date : from : reply-to : mime-version : to : subject : content-type : content-transfer-encoding; s=es.net; bh=xQ1BPHPEPjfK95rzOOPH/nVoRiHOhZEG8pWOv3EVxPo=; b=ctie4Z068SiCAvPKCk0iBwB/rLS1P+c7Y3HnjxeHp9ohzE0zPucg7p/NSQyQnU6wctie KE/fKfP7aHkSYMiYCpaiCMIICrLdJWFSmsWaZ9hEy7yv2YOLGn0bvJlcTULdKdN7Qjlr MPLqad2kvPkHO2NBrNZJjSWn8IbScAsBWrI= 
Received: from e4-ce-8f-6-ab-c8.dhcp.lbnl.us (e4-ce-8f-6-ab-c8.dhcp.lbnl.us [198.128.26.182]) (authenticated bits=0) by mailgw.es.net (8.14.5/8.14.5) with ESMTP id pA1Kc0tL002307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ipv6@ietf.org>; Tue, 1 Nov 2011 13:38:00 -0700
Message-ID: <4EB058A6.4010607@es.net>
Date: Tue, 01 Nov 2011 13:37:58 -0700
From: Eli Dart <dart@es.net>
Organization: Energy Sciences Network
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: IETF IPv6 List <ipv6@ietf.org>
Subject: draft-hsingh-6man-enhanced-dad-02.txt - loopback text
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-11-01_06:2011-11-01, 2011-11-01, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1111010206
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dart@es.net
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 20:38:16 -0000

Hi all,

In the terminology section, there is the following text describing Loopback:

    o  Loopback - A function in which the router's interface to the
       network is looped back, resulting in interface unavailability for
       regular data traffic forwarding.  See more details in section 9.1
       of [RFC1247].  Loopback function is commonly used to gain
       information on the quality of this interface, by employing
       mechanisms such as ICMPv6 pings, bit-error test etc.  Loopback
       function may be done locally or remotely.


I suggest the replacement of the above text with the following text:

Loopback - A function in which the router's interface (or the circuit to 
which the router's interface is connected) is looped back or connected 
to itself.  Loopback causes packets sent by the interface to be received 
by the interface, and results in interface unavailability for regular 
data traffic forwarding.  See more details in section 9.1 of [RFC1247]. 
  The Loopback function is commonly used in an interface context to gain 
information on the quality of the interface, by employing mechanisms 
such as ICMPv6 pings, bit-error tests, etc.  In a circuit context, it is 
used in wide area environments including optical dense wave division 
multiplexing (DWDM) and SONET/SDH for fault isolation (e.g. by placing a 
loopback at different geographic locations along the path of a wide area 
circuit to help locate a circuit fault).  The Loopback function may be 
employed locally or remotely.




I have looked briefly for a reference in standards for Loopback in a 
circuit context, and haven't found one yet.  However, I like the new 
text because it captures the notion that a circuit might be in loopback 
and therefore cause the interface to receive traffic it sent, where the 
current text (as well as its reference) covers only the interface case.

Comments welcome.

Thanks,

		--eli

-- 
Eli Dart                                            NOC: (510) 486-7600
ESnet Network Engineering Group (AS293)                  (800) 333-7638
Lawrence Berkeley National Laboratory
PGP Key fingerprint = C970 F8D3 CFDD 8FFF 5486 343A 2D31 4478 5F82 B2B3

From wwwrun@rfc-editor.org  Tue Nov  1 16:18:43 2011
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A2BB21F9D3E; Tue,  1 Nov 2011 16:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.186
X-Spam-Level: 
X-Spam-Status: No, score=-102.186 tagged_above=-999 required=5 tests=[AWL=0.414, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFymnB+QSBWg; Tue,  1 Nov 2011 16:18:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 72C6C21F9CBB; Tue,  1 Nov 2011 16:18:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7B777B1E012; Tue,  1 Nov 2011 16:14:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6436 on Rationale for Update to the IPv6 Flow Label Specification
From: rfc-editor@rfc-editor.org
Message-Id: <20111101231420.7B777B1E012@rfc-editor.org>
Date: Tue,  1 Nov 2011 16:14:20 -0700 (PDT)
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 23:18:43 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6436

        Title:      Rationale for Update to the 
                    IPv6 Flow Label Specification 
        Author:     S. Amante, B. Carpenter,
                    S. Jiang
        Status:     Informational
        Stream:     IETF
        Date:       November 2011
        Mailbox:    shane@level3.net, 
                    brian.e.carpenter@gmail.com, 
                    shengjiang@huawei.com
        Pages:      13
        Characters: 28062
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-flow-update-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6436.txt

Various published proposals for use of the IPv6 flow label are
incompatible with its original specification in RFC 3697.
Furthermore, very little practical use is made of the flow label,
partly due to some uncertainties about the correct interpretation of
the specification.  This document discusses and motivates changes to
the specification in order to clarify it and to introduce some
additional flexibility.  This document is not an Internet Standards 
Track specification; it is published for informational purposes.

This document is a product of the IPv6 Maintenance Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Tue Nov  1 16:18:55 2011
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D452C21F9D90; Tue,  1 Nov 2011 16:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.055
X-Spam-Level: 
X-Spam-Status: No, score=-104.055 tagged_above=-999 required=5 tests=[AWL=1.022, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5DlsXWG7lJyY; Tue,  1 Nov 2011 16:18:55 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1C221F9D89; Tue,  1 Nov 2011 16:18:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 680ABB1E016; Tue,  1 Nov 2011 16:14:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6437 on IPv6 Flow Label Specification
From: rfc-editor@rfc-editor.org
Message-Id: <20111101231434.680ABB1E016@rfc-editor.org>
Date: Tue,  1 Nov 2011 16:14:34 -0700 (PDT)
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 23:18:55 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6437

        Title:      IPv6 Flow Label Specification 
        Author:     S. Amante, B. Carpenter,
                    S. Jiang, J. Rajahalme
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2011
        Mailbox:    shane@level3.net, 
                    brian.e.carpenter@gmail.com, 
                    jiangsheng@huawei.com,
                    jarno.rajahalme@nsn.com
        Pages:      15
        Characters: 35269
        Obsoletes:  RFC3697
        Updates:    RFC2205, RFC2460

        I-D Tag:    draft-ietf-6man-flow-3697bis-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6437.txt

This document specifies the IPv6 Flow Label field and the minimum
requirements for IPv6 nodes labeling flows, IPv6 nodes forwarding
labeled packets, and flow state establishment methods.  Even when
mentioned as examples of possible uses of the flow labeling, more
detailed requirements for specific use cases are out of the scope for
this document.

The usage of the Flow Label field enables efficient IPv6 flow
classification based only on IPv6 main header fields in fixed
positions.  [STANDARDS-TRACK]

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Tue Nov  1 16:19:17 2011
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD2B11E80BA; Tue,  1 Nov 2011 16:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.183
X-Spam-Level: 
X-Spam-Status: No, score=-104.183 tagged_above=-999 required=5 tests=[AWL=0.894, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5sckourg3F-x; Tue,  1 Nov 2011 16:19:17 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1C711E8098; Tue,  1 Nov 2011 16:19:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D415B1E01D; Tue,  1 Nov 2011 16:14:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6438 on Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in Tunnels
From: rfc-editor@rfc-editor.org
Message-Id: <20111101231455.0D415B1E01D@rfc-editor.org>
Date: Tue,  1 Nov 2011 16:14:55 -0700 (PDT)
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 23:19:17 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6438

        Title:      Using the IPv6 Flow Label 
                    for Equal Cost Multipath Routing and 
                    Link Aggregation in Tunnels 
        Author:     B. Carpenter, S. Amante
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2011
        Mailbox:    brian.e.carpenter@gmail.com, 
                    shane@level3.net
        Pages:      9
        Characters: 20999
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-flow-ecmp-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6438.txt

The IPv6 flow label has certain restrictions on its use.  This
document describes how those restrictions apply when using the flow
label for load balancing by equal cost multipath routing and for link
aggregation, particularly for IP-in-IPv6 tunneled traffic.  
[STANDARDS-TRACK]

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From brian.e.carpenter@gmail.com  Tue Nov  1 19:02:55 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C12611E8096 for <ipv6@ietfa.amsl.com>; Tue,  1 Nov 2011 19:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.502
X-Spam-Level: 
X-Spam-Status: No, score=-103.502 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sN5vxvCiLlzu for <ipv6@ietfa.amsl.com>; Tue,  1 Nov 2011 19:02:54 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC9E11E8095 for <ipv6@ietf.org>; Tue,  1 Nov 2011 19:02:54 -0700 (PDT)
Received: by wyg30 with SMTP id 30so3163069wyg.31 for <ipv6@ietf.org>; Tue, 01 Nov 2011 19:02:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=nppwccj7IXD51xQ1HJQclFpb0PlPsde/bKbBsYYpEOk=; b=HY20l109987Yt47xN6rjryxWZhZLhPXORaEJ62S/18Y1lyMDi+nEYym+yQMcBF7ovZ lJlAazTXGgYqyfOHzR+LbTjlUFDEYcEhNwhTZwH3Pfq254jMETMTsKMW9ksX9PWxW4mU uaGex+aHBnlRr2EBeGXBxga8H5tt4wqeA6fPM=
Received: by 10.216.160.130 with SMTP id u2mr5691464wek.30.1320199373742; Tue, 01 Nov 2011 19:02:53 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id gd6sm1486444wbb.1.2011.11.01.19.02.50 (version=SSLv3 cipher=OTHER); Tue, 01 Nov 2011 19:02:52 -0700 (PDT)
Message-ID: <4EB0A4D3.1070002@gmail.com>
Date: Wed, 02 Nov 2011 15:02:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: RFC 6437 on IPv6 Flow Label Specification
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 02:02:55 -0000

Hi,

The new flow label proposed standard is here, as well as
the rationale document (RFC 6436) and the ECMP/LAG proposed
standard (RFC 6438).

This document formally updates RFC 2460 and says that every IPv6
source SHOULD set the flow label value accordingly.

Maybe we can include this in draft-ietf-6man-node-req-ter when
it comes.

   Brian


From stbryant@cisco.com  Wed Nov  2 05:17:59 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7967D1F0CAF; Wed,  2 Nov 2011 05:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.599
X-Spam-Level: 
X-Spam-Status: No, score=-107.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4X+M9mo+-y0; Wed,  2 Nov 2011 05:17:59 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id AB7A01F0C91; Wed,  2 Nov 2011 05:17:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=389; q=dns/txt; s=iport; t=1320236279; x=1321445879; h=message-id:date:from:reply-to:mime-version:to:cc:subject: content-transfer-encoding; bh=JbZtyUf1mkcXteZHDeSQ48c+/bAPLQVnOj5nZXNe8kw=; b=E4kok0sA9jsZM5l+JQqa0Wz9HeAuvkD+DLYOHfMoB28Xq8F5tbl6jcUu Ib9c0mioiDAeuXk0VcTtdZdRq8TnmAWWOZcVPKZo2GOnO1T1r5sUP6qaa ZmL/BUerAR5qfqK0Ut3QxXUk3jem8AuySr+m90iH+tdPbbNzbxGplAybM Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AioHALozsU6Q/khL/2dsb2JhbABDmjONd4EegQWCCwECASJAATwWGAMCAQIBWAEHAQEeh2iWQAGDKg8BmyCJEASUFJFl
X-IronPort-AV: E=Sophos;i="4.69,443,1315180800";  d="scan'208";a="2256358"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 02 Nov 2011 12:17:57 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pA2CHsu8026977; Wed, 2 Nov 2011 12:17:57 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-29.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id pA2CHr24009800; Wed, 2 Nov 2011 12:17:53 GMT
Message-ID: <4EB134F1.3070408@cisco.com>
Date: Wed, 02 Nov 2011 12:17:53 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: draft-ietf-l2vpn-arp-mediation review request
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 02 Nov 2011 05:37:58 -0700
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "l2vpn-chairs@tools.ietf.org" <l2vpn-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>, draft-ietf-l2vpn-arp-mediation@tools.ietf.org, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, int-ads@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 12:17:59 -0000

Resending to the correct 6-man WG list email address

6-man WG,

During the IESG review of draft-ietf-l2vpn-arp-mediation
it was noted that the IPv6 elements of this draft would
benefit from a review by the 6-man working group.

http://datatracker.ietf.org/doc/draft-ietf-l2vpn-arp-mediation/

Please can we have review comments by Monday 28th November.

Thank you

Stewart


From bob.hinden@gmail.com  Wed Nov  2 07:10:50 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A31D811E80D8 for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 07:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=1.027, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+FrdXP-+-Ji for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 07:10:50 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E470211E80CA for <ipv6@ietf.org>; Wed,  2 Nov 2011 07:10:49 -0700 (PDT)
Received: by vws5 with SMTP id 5so205541vws.31 for <ipv6@ietf.org>; Wed, 02 Nov 2011 07:10:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=/3ouEx0bBQSd+ridIqkOkOsySkpoPHo3vAkHJX29DxY=; b=D5YmUkU9wi8MgMAyX2+uu+3F8+2SeF3FjEdXVA4aloXufb18OBmm9uo6Q3LJwoR7W1 yMa7cdoCBdij7wid1zU24VlRA+wvvFU682DUZVpTlwZS6BofdOUNkJsES54L/mwTUJt2 tPZm/DWlsmRyU1CbkTIDIXKmuT+OKAKvVRrds=
Received: by 10.68.72.33 with SMTP id a1mr5133725pbv.44.1320243041400; Wed, 02 Nov 2011 07:10:41 -0700 (PDT)
Received: from [10.0.0.25] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id a4sm813719pbd.7.2011.11.02.07.10.39 (version=SSLv3 cipher=OTHER); Wed, 02 Nov 2011 07:10:40 -0700 (PDT)
Subject: Re: RFC 6437 on IPv6 Flow Label Specification
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4EB0A4D3.1070002@gmail.com>
Date: Wed, 2 Nov 2011 07:10:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <22A8860A-1055-483C-83C3-93556A75DDA8@gmail.com>
References: <4EB0A4D3.1070002@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: 6man <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 14:10:50 -0000

Brian,

I agree this is a good idea.  <draft-ietf-6man-node-req-bis-11.txt> is =
recently entered AUTH48 so this may be possible.  I doubt we are going =
to update node-requirements again for a while, so it would be good to do =
it now.

The first step is to see if anyone on the list disagrees with this =
approach.  Comments?

I have asked the authors to propose text to the ipv6 list.

Bob

On Nov 1, 2011, at 7:02 PM, Brian E Carpenter wrote:

> Hi,
>=20
> The new flow label proposed standard is here, as well as
> the rationale document (RFC 6436) and the ECMP/LAG proposed
> standard (RFC 6438).
>=20
> This document formally updates RFC 2460 and says that every IPv6
> source SHOULD set the flow label value accordingly.
>=20
> Maybe we can include this in draft-ietf-6man-node-req-ter when
> it comes.
>=20
>   Brian
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From john@jlc.net  Wed Nov  2 08:07:51 2011
Return-Path: <john@jlc.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BAC91F0C96 for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 08:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.524
X-Spam-Level: 
X-Spam-Status: No, score=-106.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Jvxme4UhN20 for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 08:07:50 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id A15E41F0C78 for <ipv6@ietf.org>; Wed,  2 Nov 2011 08:07:50 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 8166533C26; Wed,  2 Nov 2011 11:07:49 -0400 (EDT)
Date: Wed, 2 Nov 2011 11:07:49 -0400
From: John Leslie <john@jlc.net>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: RFC 6437 on IPv6 Flow Label Specification
Message-ID: <20111102150749.GH1872@verdi>
References: <4EB0A4D3.1070002@gmail.com> <22A8860A-1055-483C-83C3-93556A75DDA8@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <22A8860A-1055-483C-83C3-93556A75DDA8@gmail.com>
User-Agent: Mutt/1.4.1i
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 15:07:51 -0000

Bob Hinden <bob.hinden@gmail.com> wrote:
> On Nov 1, 2011, at 7:02 PM, Brian E Carpenter wrote:
> 
>> The new flow label proposed standard is here, as well as
>> the rationale document (RFC 6436) and the ECMP/LAG proposed
>> standard (RFC 6438).
>> 
>> This document formally updates RFC 2460 and says that every IPv6
>> source SHOULD set the flow label value accordingly.
>> 
>> Maybe we can include this in draft-ietf-6man-node-req-ter when
>> it comes.

   I entirely agree it deserves mention in a -ter.

> I agree this is a good idea.  <draft-ietf-6man-node-req-bis-11.txt>
> is recently entered AUTH48 so this may be possible.

   I'm doubtful adding this during AUTH48 would be a good idea.

   Were it merely changing a Normative Reference to the new document,
I'd support this. But node-req-bis has no mention of Flow Label beyond
referencing RFC2460; and at first blush I see no way to introduce
Flow Label without text that would deserve an IETF LastCall.

   That said, I don't oppose covering Flow Label, and certainly any
node-req RFC that covers Flow Label should reference this standard:
it's just that adding this at AUTH48 seems a bit much. If, OTOH, we
intended to back off to a new IETF LastCall, I'd support it.

> I doubt we are going to update node-requirements again for a while,

   Understandable... but I sincerely hope "a while" doesn't turn
into years.

> so it would be good to do it now.

   I'm quite willing to reserve judgment until I see proposed text.

--
John Leslie <john@jlc.net>

From john.loughney@nokia.com  Wed Nov  2 19:50:47 2011
Return-Path: <john.loughney@nokia.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 041B01F0C36 for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 19:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rA3+fMvwq0Ii for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 19:50:46 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 2889E1F0C45 for <ipv6@ietf.org>; Wed,  2 Nov 2011 19:50:44 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id pA32ofbQ003167 for <ipv6@ietf.org>; Thu, 3 Nov 2011 04:50:42 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.26]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Nov 2011 04:50:37 +0200
Received: from 008-AM1MPN1-015.mgdnok.nokia.com ([169.254.5.142]) by 008-AM1MMR1-010.mgdnok.nokia.com ([65.54.30.26]) with mapi id 14.01.0339.002; Thu, 3 Nov 2011 03:50:36 +0100
From: <john.loughney@nokia.com>
To: <ipv6@ietf.org>
Subject: Flow Label support in the Node Requirements bis document
Thread-Topic: Flow Label support in the Node Requirements bis document
Thread-Index: AcyZ0t2CsMUgnZ6KSxKK9aG/9V9Dow==
Date: Thu, 3 Nov 2011 02:50:35 +0000
Message-ID: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Company Confidential;Project=None;
x-titus-version: 3.3.8.1
x-tituslabs-classificationhash-30: NgLgUAGhIMVcmkVcu9QCAwieSazXqlfDnHOnX9/iWtJPlxl4KJJRFnKFlCbtR17Q69ZPywyeCRoS29EGR4UUj/1u4WCkAk7d6laFAeWHKeWE0Vh7jQhYGcl4vjBub8N4r/B+HOP544705mWX0x7OSVJu6dLVszLlcjNnKLKhZFJQ6ZtNZLXj9pumQG4R/P1yiamrCc4HWv0/xETUr7cVbMtpgFkJra2BBcWw1ZeYjBKRoY4iTLLXProj9R8M43lzPEkvnyS3uWUdpIxOeSE5vQ==
x-headerinfofordlp: None
x-originating-ip: [98.234.218.242]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Nov 2011 02:50:37.0295 (UTC) FILETIME=[5D837FF0:01CC99D3]
X-Nokia-AV: Clean
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 02:50:47 -0000

Hi all,

There has been some discussions whether or not we should add support for th=
e Flow Label in
Soon to be RFC 6434 <draft-ietf-6man-node-req-bis-11.txt> As a straw man pr=
oposal, if we add
Support, I would suggest the following text:

All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,=20
defines the IPv6 Flow Label.  Specifically:
=20
    "Forwarding nodes such as routers and load distributors MUST NOT
      depend only on Flow Label values being uniformly distributed. "
=20
    "It is therefore RECOMMENDED  that source hosts support the flow=20
      label by setting the flow label field for all packets of a given flow=
 to the=20
      same value chosen from  an approximation to a discrete uniform distri=
bution. "

I'd like to ask the wg the following:

1) Is the above text acceptable?
2) Do you support adding the text? If no, please suggest text, unless you d=
o not support adding
     Flow label support at all (please say so).

John

From brian.e.carpenter@gmail.com  Wed Nov  2 20:04:49 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51FFE11E8096 for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 20:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.486
X-Spam-Level: 
X-Spam-Status: No, score=-103.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAtdTm7oJ5NV for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 20:04:48 -0700 (PDT)
Received: from mail-vw0-f66.google.com (mail-vw0-f66.google.com [209.85.212.66]) by ietfa.amsl.com (Postfix) with ESMTP id 519C911E8081 for <ipv6@ietf.org>; Wed,  2 Nov 2011 20:04:48 -0700 (PDT)
Received: by vws3 with SMTP id 3so36530vws.1 for <ipv6@ietf.org>; Wed, 02 Nov 2011 20:04:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JIC6DHOoBB+dy7+ZpenwFPTdbARo1MPXY8kUzFAhtEs=; b=LOlHL6Hhj+aIZq9WcNo9qV0fMRgrw0hfOwMY0L/STqDqsUNhjFIoTGSq1sEhmIbeu/ i2FkKCoj7lCtVKUKtTscp7eSkjriRkJEXRzGsSNIaBAcXbzo45G0PG+Gvz7HCn1QT/cc qXxZIHRmPiUKj43rAryqP+Rq8e6pXIEODaVfc=
Received: by 10.52.70.98 with SMTP id l2mr7478493vdu.101.1320289487729; Wed, 02 Nov 2011 20:04:47 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id j4sm6049007vdk.5.2011.11.02.20.04.45 (version=SSLv3 cipher=OTHER); Wed, 02 Nov 2011 20:04:46 -0700 (PDT)
Message-ID: <4EB204BA.7040106@gmail.com>
Date: Thu, 03 Nov 2011 16:04:26 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: Flow Label support in the Node Requirements bis document
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
In-Reply-To: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 03:04:49 -0000

I support this (and the proposed text), as long as it doesn't cause
more than three or four weeks' delay.

Regards
   Brian Carpenter

On 2011-11-03 15:50, john.loughney@nokia.com wrote:
> Hi all,
> 
> There has been some discussions whether or not we should add support for the Flow Label in
> Soon to be RFC 6434 <draft-ietf-6man-node-req-bis-11.txt> As a straw man proposal, if we add
> Support, I would suggest the following text:
> 
> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification, 
> defines the IPv6 Flow Label.  Specifically:
>  
>     "Forwarding nodes such as routers and load distributors MUST NOT
>       depend only on Flow Label values being uniformly distributed. "
>  
>     "It is therefore RECOMMENDED  that source hosts support the flow 
>       label by setting the flow label field for all packets of a given flow to the 
>       same value chosen from  an approximation to a discrete uniform distribution. "
> 
> I'd like to ask the wg the following:
> 
> 1) Is the above text acceptable?
> 2) Do you support adding the text? If no, please suggest text, unless you do not support adding
>      Flow label support at all (please say so).
> 
> John
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

From jiangsheng@huawei.com  Wed Nov  2 20:54:23 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF7711E80A0 for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 20:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NGJAOoVppIOF for <ipv6@ietfa.amsl.com>; Wed,  2 Nov 2011 20:54:22 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 600F311E8080 for <ipv6@ietf.org>; Wed,  2 Nov 2011 20:54:22 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LU2005JCG5WIN@szxga05-in.huawei.com> for ipv6@ietf.org; Thu, 03 Nov 2011 11:53:56 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LU200C3MG5W62@szxga05-in.huawei.com> for ipv6@ietf.org; Thu, 03 Nov 2011 11:53:56 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AES51130; Thu, 03 Nov 2011 11:53:55 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 03 Nov 2011 11:53:49 +0800
Received: from SZXEML506-MBS.china.huawei.com ([169.254.3.202]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0270.001; Thu, 03 Nov 2011 11:53:46 +0800
Date: Thu, 03 Nov 2011 03:53:45 +0000
From: Sheng Jiang <jiangsheng@huawei.com>
Subject: RE: Flow Label support in the Node Requirements bis document
In-reply-to: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
X-Originating-IP: [10.108.4.60]
To: "john.loughney@nokia.com" <john.loughney@nokia.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B9218549694@SZXEML506-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: Flow Label support in the Node Requirements bis document
Thread-index: AcyZ0t2CsMUgnZ6KSxKK9aG/9V9DowACUU+A
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 03:54:23 -0000

I support this action and the proposed text.

Sheng

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> john.loughney@nokia.com
> Sent: Thursday, November 03, 2011 10:51 AM
> To: ipv6@ietf.org
> Subject: Flow Label support in the Node Requirements bis document
> 
> Hi all,
> 
> There has been some discussions whether or not we should add support
> for the Flow Label in
> Soon to be RFC 6434 <draft-ietf-6man-node-req-bis-11.txt> As a straw
> man proposal, if we add
> Support, I would suggest the following text:
> 
> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,
> defines the IPv6 Flow Label.  Specifically:
> 
>     "Forwarding nodes such as routers and load distributors MUST NOT
>       depend only on Flow Label values being uniformly distributed. "
> 
>     "It is therefore RECOMMENDED  that source hosts support the flow
>       label by setting the flow label field for all packets of a given
> flow to the
>       same value chosen from  an approximation to a discrete uniform
> distribution. "
> 
> I'd like to ask the wg the following:
> 
> 1) Is the above text acceptable?
> 2) Do you support adding the text? If no, please suggest text, unless
> you do not support adding
>      Flow label support at all (please say so).
> 
> John
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From bob.hinden@gmail.com  Thu Nov  3 06:52:30 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD3411E812D for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 06:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.82
X-Spam-Level: 
X-Spam-Status: No, score=-102.82 tagged_above=-999 required=5 tests=[AWL=0.779, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUYGJ-Ufrr8S for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 06:52:28 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1827B11E8087 for <ipv6@ietf.org>; Thu,  3 Nov 2011 06:52:28 -0700 (PDT)
Received: by ggnv1 with SMTP id v1so1533903ggn.31 for <ipv6@ietf.org>; Thu, 03 Nov 2011 06:52:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=F9H3HOWvR+fJCX3U5T7ypAfLzFEpNVTYnR8ZX5cdzb8=; b=j/Uv+gFWgA1NrSzYT7tHumOBj2d7SgSWOYodZefXH8Z+WbVvBcpu9TiuPKkoQxI3VZ Z4Dq71S2xdt/vyXxm2OtkO91h8SqQpPoyERYsHQwoakAMTeZWYTjCZ1dZ8E5QL1KNWzv XaMV3k6ZpRtCJD5jTdxAl0s5xdImV9Xu3sWi0=
Received: by 10.150.177.12 with SMTP id z12mr9393084ybe.14.1320328347609; Thu, 03 Nov 2011 06:52:27 -0700 (PDT)
Received: from [10.0.0.25] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id v5sm17420183anf.3.2011.11.03.06.52.26 (version=SSLv3 cipher=OTHER); Thu, 03 Nov 2011 06:52:27 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF82 6man Agenda
Date: Thu, 3 Nov 2011 06:52:25 -0700
Message-Id: <C7937CD8-14EA-4A62-B38F-59E111190D8D@gmail.com>
To: 6man List <ipv6@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 13:52:30 -0000

The current agenda for the 6man session can be found at:

  http://www.ietf.org/proceedings/82/agenda/6man.html

The session is on Monday, 09:00-11:30, November 14, 2011, in 3F Banquet.

Speakers need to get their slides (pdf preferred) to us by Sunday 5pm.  =
We also need a jabber scribe and minute taker.

Thanks,

Bob & Brian



From bob.hinden@gmail.com  Thu Nov  3 08:33:02 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05CF01F0C96 for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 08:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.846
X-Spam-Level: 
X-Spam-Status: No, score=-102.846 tagged_above=-999 required=5 tests=[AWL=0.753, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUi2+sNYuA5V for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 08:33:01 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD191F0C72 for <ipv6@ietf.org>; Thu,  3 Nov 2011 08:33:01 -0700 (PDT)
Received: by gye5 with SMTP id 5so1655224gye.31 for <ipv6@ietf.org>; Thu, 03 Nov 2011 08:33:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=mbc3b/YQs65rq4/RH9OwfP0H3g9/Bk2nvjjQcx3ghxE=; b=PcOClxGlEi+pdzuqYvtqL/31d0zBjhmuRPTSTtOFF42ZDIAMwUJu4SxyLVIhgur1uB bucEkWa5mKAAMJpumMpJ+VL3ndFX20sEcdoQYdXevygMe7Gw3VrIzazVuN+o6v6Yx5K2 7SlK5hYDd99rODHbeDb1bbIUZAx6MO9u3XM4M=
Received: by 10.236.174.105 with SMTP id w69mr14502934yhl.32.1320334380546; Thu, 03 Nov 2011 08:33:00 -0700 (PDT)
Received: from [10.0.0.25] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id k20sm18099088ann.15.2011.11.03.08.32.59 (version=SSLv3 cipher=OTHER); Thu, 03 Nov 2011 08:33:00 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Date: Thu, 3 Nov 2011 08:32:56 -0700
Message-Id: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 15:33:02 -0000

All,

This message starts a two week 6MAN Working Group Last Call on =
advancing:

	Title           : The Line Identification Destination Option
	Author(s)       : Suresh Krishnan
                          Alan Kavanagh
                          Balazs Varga
                          Sven Ooghe
                          Erik Nordmark
	Filename        : draft-ietf-6man-lineid-02.txt
	Pages           : 14
	Date            : 2011-10-31
=09
        http://tools.ietf.org/html/draft-ietf-6man-lineid-02.txt

as an Experimental RFC.  Substantive comments and statements of support =
for advancing this document should be directed to the mailing list.  =
Editorial suggestions can be sent to the authors.  This last call will =
end on 17 November 2011.

Regards,
Bob Hinden & Brian Haberman
6MAN Chairs


From jmh@joelhalpern.com  Thu Nov  3 09:10:56 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1C691F0CA5 for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 09:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z99gMfv-ZJbk for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 09:10:51 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id A6AAE1F0C7C for <ipv6@ietf.org>; Thu,  3 Nov 2011 09:10:51 -0700 (PDT)
Received: from c2.tigertech.net (c2.tigertech.net [208.80.4.146]) by morbo.tigertech.net (Postfix) with ESMTP id AA14FCD0B4 for <ipv6@ietf.org>; Thu,  3 Nov 2011 09:10:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c2.tigertech.net (Postfix) with ESMTP id 6129D1BD385C; Thu,  3 Nov 2011 09:10:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.154.180.187] (unknown [129.192.185.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by c2.tigertech.net (Postfix) with ESMTPSA id 9E76C1BD387A; Thu,  3 Nov 2011 09:10:23 -0700 (PDT)
Message-ID: <4EB2BCEE.6000205@joelhalpern.com>
Date: Thu, 03 Nov 2011 12:10:22 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com>
In-Reply-To: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 16:10:56 -0000

Support.

I have read this document.  It provides a useful function in practical 
fashion.  It is ready for publication.

Yours,
Joel M. Halpern

On 11/3/2011 11:32 AM, Bob Hinden wrote:
> All,
>
> This message starts a two week 6MAN Working Group Last Call on advancing:
>
> 	Title           : The Line Identification Destination Option
> 	Author(s)       : Suresh Krishnan
>                            Alan Kavanagh
>                            Balazs Varga
>                            Sven Ooghe
>                            Erik Nordmark
> 	Filename        : draft-ietf-6man-lineid-02.txt
> 	Pages           : 14
> 	Date            : 2011-10-31
> 	
>          http://tools.ietf.org/html/draft-ietf-6man-lineid-02.txt
>
> as an Experimental RFC.  Substantive comments and statements of support for advancing this document should be directed to the mailing list.  Editorial suggestions can be sent to the authors.  This last call will end on 17 November 2011.
>
> Regards,
> Bob Hinden&  Brian Haberman
> 6MAN Chairs
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

From david.i.allan@ericsson.com  Thu Nov  3 09:22:03 2011
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D13D1F0C81 for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 09:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DCTyzvUi-PsY for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 09:22:02 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id F31E81F0C7C for <ipv6@ietf.org>; Thu,  3 Nov 2011 09:22:01 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pA3GLxLv032266 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 3 Nov 2011 11:21:59 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.174]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Thu, 3 Nov 2011 12:21:57 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Bob Hinden <bob.hinden@gmail.com>
Date: Thu, 3 Nov 2011 12:21:56 -0400
Subject: RE: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Thread-Topic: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Thread-Index: AcyaQzvFErXH3ZPjSE6QkwkXzxjfGQAAR2og
Message-ID: <60C093A41B5E45409A19D42CF7786DFD522602F869@EUSAACMS0703.eamcs.ericsson.se>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com> <4EB2BCEE.6000205@joelhalpern.com>
In-Reply-To: <4EB2BCEE.6000205@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 16:22:03 -0000

Support!

This document addresses an important issue in introducing IPv6 dual stack i=
nto broadband access networks. N:1 VLAN as per TR-101 is a common deploymen=
t model...

Dave


On 11/3/2011 11:32 AM, Bob Hinden wrote:
> All,
>
> This message starts a two week 6MAN Working Group Last Call on advancing:
>
> 	Title           : The Line Identification Destination Option
> 	Author(s)       : Suresh Krishnan
>                            Alan Kavanagh
>                            Balazs Varga
>                            Sven Ooghe
>                            Erik Nordmark
> 	Filename        : draft-ietf-6man-lineid-02.txt
> 	Pages           : 14
> 	Date            : 2011-10-31
> =09
>          http://tools.ietf.org/html/draft-ietf-6man-lineid-02.txt
>
> as an Experimental RFC.  Substantive comments and statements of support f=
or advancing this document should be directed to the mailing list.  Editori=
al suggestions can be sent to the authors.  This last call will end on 17 N=
ovember 2011.
>
> Regards,
> Bob Hinden&  Brian Haberman
> 6MAN Chairs
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From john@jlc.net  Thu Nov  3 10:47:20 2011
Return-Path: <john@jlc.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7FB11E80AE for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 10:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.52
X-Spam-Level: 
X-Spam-Status: No, score=-106.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DImTPUymFSQa for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 10:47:19 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id A98D911E8161 for <ipv6@ietf.org>; Thu,  3 Nov 2011 10:47:19 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id C6D1333C23; Thu,  3 Nov 2011 13:47:19 -0400 (EDT)
Date: Thu, 3 Nov 2011 13:47:19 -0400
From: John Leslie <john@jlc.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Flow Label support in the Node Requirements bis document
Message-ID: <20111103174719.GD88646@verdi>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <4EB204BA.7040106@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4EB204BA.7040106@gmail.com>
User-Agent: Mutt/1.4.1i
Cc: john.loughney@nokia.com, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 17:47:20 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> On 2011-11-03 15:50, john.loughney@nokia.com wrote:
>>
>> ... I would suggest the following text:
>> 
>> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification, 
>> defines the IPv6 Flow Label.  Specifically:
>>  
>>  "Forwarding nodes such as routers and load distributors MUST NOT
>>   depend only on Flow Label values being uniformly distributed. "
>>  
>>  "It is therefore RECOMMENDED  that source hosts support the flow 
>>   label by setting the flow label field for all packets of a given
>>   flow to the same value chosen from an approximation to a discrete
>>   uniform distribution. "
> 
> I support this (and the proposed text), as long as it doesn't cause
> more than three or four weeks' delay.

   The language feels right for a de-novo -bis.

   OTOH, it strikes me as going well beyond an AUTH48 change.

   Given IETF week, I personally doubt this big a change can be
accomplished in four weeks -- but that's a question for Jari, not me.

   I'd also support a lesser change, merely an Informative ref, just
pointing out the new RFC (which I _would_ have the nerve to ask for
as an AUTH49 change).

   Either way, I hope that a -ter becomes a milestone not more than
12-18 months from now. (If done soon enough, it shouldn't be that
hard!)

--
John Leslie <john@jlc.net>

From narten@us.ibm.com  Thu Nov  3 11:01:37 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD2C711E80DA for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 11:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SH4oEqfoYaW4 for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 11:01:36 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id A186F11E80AE for <ipv6@ietf.org>; Thu,  3 Nov 2011 11:01:36 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ipv6@ietf.org> from <narten@us.ibm.com>; Thu, 3 Nov 2011 14:01:35 -0400
Received: from d01relay03.pok.ibm.com ([9.56.227.235]) by e9.ny.us.ibm.com ([192.168.1.109]) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 3 Nov 2011 14:01:32 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pA3I1Svc097522 for <ipv6@ietf.org>; Thu, 3 Nov 2011 14:01:28 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pA3I0pru017338 for <ipv6@ietf.org>; Thu, 3 Nov 2011 16:00:51 -0200
Received: from cichlid.raleigh.ibm.com (dyn9050017234.mts.ibm.com [9.50.17.234] (may be forged)) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id pA3I0Tcc014065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2011 16:00:30 -0200
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id pA3I0Gp9019580; Thu, 3 Nov 2011 14:00:21 -0400
Message-Id: <201111031800.pA3I0Gp9019580@cichlid.raleigh.ibm.com>
To: John Leslie <john@jlc.net>
Subject: Re: Flow Label support in the Node Requirements bis document
In-reply-to: <20111103174719.GD88646@verdi>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <4EB204BA.7040106@gmail.com> <20111103174719.GD88646@verdi>
Comments: In-reply-to John Leslie <john@jlc.net> message dated "Thu, 03 Nov 2011 13:47:19 -0400."
Date: Thu, 03 Nov 2011 14:00:16 -0400
From: Thomas Narten <narten@us.ibm.com>
x-cbid: 11110318-7182-0000-0000-0000001FC4DC
Cc: john.loughney@nokia.com, ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 18:01:37 -0000

John,

This should not be a surprising or controversial change to the
node-requirements document. The WG made the decision earlier that we'd
leave out a reference to the Flow Label work because we didn't want to
have node-requirements block waiting for it, but we would revisit if
that work finished in time.

It has.

We should just make this change. There was never any doubt that node
requirements would point to the updated Flow Label RFC.

If we say "do it later, when we rev the document again", we should be
realistic in that that probably won't happen for at least another year
and probably more like 2+ years.

Thomas


From gdt@gdt.id.au  Thu Nov  3 15:19:02 2011
Return-Path: <gdt@gdt.id.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33EAA1F0CB4 for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 15:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLzjjsTX1ctb for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 15:19:01 -0700 (PDT)
Received: from aix.gdt.id.au (eth6445.sa.adsl.internode.on.net [150.101.30.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD361F0C9F for <ipv6@ietf.org>; Thu,  3 Nov 2011 15:19:00 -0700 (PDT)
Received: from [192.168.253.186] (ilion.44ansell.gdt.id.au [192.168.253.186]) (authenticated bits=0) by aix.gdt.id.au (8.14.2/8.14.2) with ESMTP id pA3MIojT010280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2011 08:48:50 +1030
Message-ID: <1320358729.3032.24.camel@ilion>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
From: Glen Turner <gdt@gdt.id.au>
To: Bob Hinden <bob.hinden@gmail.com>
Date: Fri, 04 Nov 2011 08:48:49 +1030
In-Reply-To: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com>
Organization: http://www.gdt.id.au/~gdt/
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.0- 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
Cc: Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 22:19:02 -0000

The contents of the Line Identification Destination Option are
essentially opaque.

Although this may allow a wide range of router implementations, in
practice it leads to a situation where new implementers must
reverse-engineer the dominant implementation in order to be assured of
compatibility.

An opaque field allows a wide range of router implementation practice at
the cost of ease of use of the field in provisioning databases. An
implementation of a provisioning database which can configure a range of
routers has to ask for the Identification Destination in hexadecimal.

If the contents of the field are in practice a MAC address there may be
a repetition of the experience with the RADIUS's Calling-Station-Id
where a lack of definition of the content of the field leads to programs
with two or so pages of parsing code to extract a wireless device's MAC
address.

If the contents of the field are in practice an interface name then
perhaps ifIndex would be more suitable.

If the contents of the field are in practice a customer provisioning
identifier then perhaps the field could be specified as a string so that
programmers know that the field can be typed or printed rather than
hexdumped. Some care should be taken to identify the character set, as
it is unlikely to be UTF-8.

If the authors decide that opaque is desirable then they should define
the textual representation of the field. That way the contents of the
field are defined identically across different manufacturers' router
configuration languages, ISP provisioning databases, etc.

Best wishes, Glen


From john@jlc.net  Thu Nov  3 17:00:01 2011
Return-Path: <john@jlc.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B1AE1F0C8E for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 17:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.524
X-Spam-Level: 
X-Spam-Status: No, score=-106.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j0RN-qBc4Cp9 for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 17:00:00 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 040991F0C85 for <ipv6@ietf.org>; Thu,  3 Nov 2011 16:59:56 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id DFCB633C23; Thu,  3 Nov 2011 19:59:54 -0400 (EDT)
Date: Thu, 3 Nov 2011 19:59:54 -0400
From: John Leslie <john@jlc.net>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Flow Label support in the Node Requirements bis document
Message-ID: <20111103235954.GE88646@verdi>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <4EB204BA.7040106@gmail.com> <20111103174719.GD88646@verdi> <201111031800.pA3I0Gp9019580@cichlid.raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201111031800.pA3I0Gp9019580@cichlid.raleigh.ibm.com>
User-Agent: Mutt/1.4.1i
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 00:00:01 -0000

Thomas Narten <narten@us.ibm.com> wrote:
> 
> This should not be a surprising or controversial change to the
> node-requirements document. The WG made the decision earlier that we'd
> leave out a reference to the Flow Label work because we didn't want to
> have node-requirements block waiting for it, but we would revisit if
> that work finished in time.
> 
> It has.
> 
> We should just make this change. There was never any doubt that node
> requirements would point to the updated Flow Label RFC.

   Alas, there was no mention of this in the document.

   And, the document is no longer under our control. It has gone
through IETF LastCall, also with no mention of an intent to point to
an updated Flow Label RFC.

   And, I quite agree, it would be a better document if it did point
to an updated Flow Label RFC.

   I agree with most of what Thomas says: but I agree more with Brian
Carpenter: it's not worth holding up this document for two (or more)
months to add this.

   Beyond that (though I soft-pedaled it) I believe there's rather
little chance of the proposed text breezing through in less than
four weeks.

   And personally, I see more value in getting out the document as
it stands quickly than in adding much of anything about Flow Labels.

> If we say "do it later, when we rev the document again", we should be
> realistic in that that probably won't happen for at least another year
> and probably more like 2+ years.

   IMHO, we should commit to revising well within two years whether or
not we add language about Flow Labels. I wish we already had language
about Flow Labels in there; but I would still believe we shouldn't
let the next rev drag on for two or more years: now is the time folks
are working on implementing and deploying IPv6, and all indications
are that such work will continue for a few years, at the same time
details of the various pieces of protocols are evolving. IMHO, a
road-map document is critically important, while a many-year-old
road-map document can actually detract.

   Also IMHO, Flow Label remains mostly unused, and of the pieces,
it's perhaps best able to wait for inclusion in a road-map.

   Now, something about process...

   Thomas certainly knows that to add the text in question, an AD
is likely to tell us to recycle the document back to a WG LastCall.
I happen to believe that's _very_ likely. And I listen in on the
IESG telechats: I recommend to your perusal the Narrative Minutes

http://www.ietf.org/iesg/minutes/2011/narrative-minutes-2011-07-14.html

where this document was discussed. Recycling this doesn't feel like
a slam-dunk at the IESG to me.

   I'm sure either Ralph Droms or Jari Arkko would allow the document
to go back to the WG from AUTH48; I'm not sure either of them would
look forward to its next trip through IESG, and I frankly don't see
how either of them could say the proposed text doesn't deserve a
recycle. That's why I suggested a minimal change, merely an
Informational Reference to a document recently published, with no
claims about what it says. Please _read_ the Narrative Minutes
before you ridicule me for this belief.

  If it does recycle, IMHO, we'll be asked to respond to a raft of
comments by IESG members the first time around (and there were more
than are shown in the Narrative Minutes). Frankly, I believe we
could get a -ter document out about as fast as we could recycle
this one.

   Thus, though I'm supportive of the text in question, I believe
it's better tactics to schedule a milestone to include it in a -ter
document.

   I'm nearly certain that our responsible AD (Jari) would have to
rule on either the change in wording or a milestone update: I'm
more optimistic about a ruling in favor of adding a milestone.
(And even if Jari agreed such a change doesn't require recycling,
the RFC Editor would also have to agree, which is by no means a
sure thing.)

   We're facing two separate questions here:
- whether we like the wording for a road-map document; and
- how long we're willing to hold up this document to get the change.

   I'm perfectly happy to be in the rough here; but I'm not happy
holding up this document at all, nor do I believe four weeks to
be a reasonable expectation if we insist on changing this
document. If we really choose to insist on this late change even
if it takes two or three months, so be it!

--
John Leslie <john@jlc.net>

From shane@castlepoint.net  Thu Nov  3 17:37:28 2011
Return-Path: <shane@castlepoint.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA2F911E80C5 for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 17:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level: 
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.277,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cnb26YEXCWgc for <ipv6@ietfa.amsl.com>; Thu,  3 Nov 2011 17:37:28 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id 4BCF611E80BF for <ipv6@ietf.org>; Thu,  3 Nov 2011 17:37:28 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id CBA8B268063; Thu,  3 Nov 2011 18:37:22 -0600 (MDT)
Received: from mbpw.castlepoint.net (65-102-206-76.hlrn.qwest.net [65.102.206.76]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for ipv6@ietf.org; Thu, 03 Nov 2011 18:37:22 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=65.102.206.76; client-port=61530; syn-fingerprint=65535:54:1:64:M1452,N,W2,N,N,T,S; data-bytes=0
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: Flow Label support in the Node Requirements bis document
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <201111031800.pA3I0Gp9019580@cichlid.raleigh.ibm.com>
Date: Thu, 3 Nov 2011 18:37:07 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <34B62D9F-2462-4EFF-93A1-FE9FB65FFE87@castlepoint.net>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <4EB204BA.7040106@gmail.com> <20111103174719.GD88646@verdi> <201111031800.pA3I0Gp9019580@cichlid.raleigh.ibm.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 00:37:29 -0000

On Nov 3, 2011, at 12:00 PM, Thomas Narten wrote:
> John,
> 
> This should not be a surprising or controversial change to the
> node-requirements document. The WG made the decision earlier that we'd
> leave out a reference to the Flow Label work because we didn't want to
> have node-requirements block waiting for it, but we would revisit if
> that work finished in time.
> 
> It has.
> 
> We should just make this change. There was never any doubt that node
> requirements would point to the updated Flow Label RFC.

I completely agree.  We should make the change now.

-shane


> If we say "do it later, when we rev the document again", we should be
> realistic in that that probably won't happen for at least another year
> and probably more like 2+ years.
> 
> Thomas
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From secretariat@balwois.com  Fri Nov  4 03:38:20 2011
Return-Path: <secretariat@balwois.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81A2B21F8B80 for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 03:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.051
X-Spam-Level: ***
X-Spam-Status: No, score=3.051 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_50=0.001, DEAR_FRIEND=2.699, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oalzzxRSt7q2 for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 03:38:18 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp04.smtpout.orange.fr [80.12.242.126]) by ietfa.amsl.com (Postfix) with ESMTP id 9691A21F8B7A for <ipv6@ietf.org>; Fri,  4 Nov 2011 03:38:17 -0700 (PDT)
Received: from PCdeOlivija ([81.248.2.201]) by mwinf5d07 with ME id sy1Z1h0014LD1xd03yeFKF; Fri, 04 Nov 2011 11:38:16 +0100
From: "BALWOIS Secretariat" <secretariat@balwois.com>
To: <ipv6@ietf.org>
Subject: Abstract submission deadline is POSTPONED to 20 of November 2011
Date: Fri, 4 Nov 2011 07:33:05 -0300
Message-ID: <2E281FCB98F24820ABF5991C7A7134B5@PCdeOlivija>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0BEC_01CC9AC4.B4CBBBA0"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acya2XLE2WbU/uO7Qkej8A5nXkT2qA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463
X-Mailman-Approved-At: Fri, 04 Nov 2011 03:43:45 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 10:38:20 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0BEC_01CC9AC4.B4CBBBA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear friend,

We would like to inform you that DEADLINE for abstract submission for
BALWOIS 2012 Conference (Fifth International Scientific Conference on Water,
Climate and Environment, from 28 May to 02 June 2012, Ohrid, Macedonia) is
POSTPONED until 20th of November 2011 (information at www.balwois.com/2012).

 

We hope this extra time will encourage more of you to consider participating
and please submit your abstracts as soon as possible on the Conference
website.

 

Those authors who have already submitted abstracts will be notified as to
whether their abstracts have been accepted or not until 30 of November 2011.

 

Here are some instructions about the submission procedure.

BALWOIS 2012 is using online Conference management system, therefore you
have to :

I - register yourself at conference web site;

II - only after registration you can submit your abstracts via your account
(using your username and password).

 

NOTE: We cannot register and/or submit your abstract on behalf of you.
Please, have a look on the following instructions.

 

 

Instructions about REGISTRATION (opening user account) and SUBMISSION of the
abstracts

 

 <http://1.to/> 1.To REGISTER you have to:

. Go on the page  <http://ocs.balwois.com/> http://ocs.balwois.com ;

. Click at LOG IN ;

. Click at: >
<http://ocs.balwois.com/index.php?conference=BALWOIS&schedConf=BW2012&page=u
ser&op=account> Not a user? Create an account with this site ;

. Fill the FORM and do not forget to check the box "Author" at the bottom of
this 

FORM (to define your account as author) .

 

This registration must be done only one time.

 

2. To SUBMIT your abstract you have :

. to use your username and password at  <http://ocs.balwois.com/>
http://ocs.balwois.com to access your account ;

. to choose "New Submission" ;

. to fill the form ;

. to submit the form (abstract). 

 

3. To MAKE CHANGES (to add more authors, to change the Title or the Text of
abstract, etc.) you should:

. Use your username and password to access your account;

. Choose < Active submission > ;

. Click on the Title of the abstract that you want to change;

. Click on the button EDIT METADATA (somewhere in the middle of the page);

. After making corrections, click on the button SAVE METADATA."

 

If you have some problems do not hesitate to contact us.

 

Best Regards,

 

BALWOIS Secretariat

____________________________________

If this email has arrived by mistake please delete it and if you want to
unsubscribe for the further emails concerning BALWOIS 2012 Conference,
please send us an email with this subject : < UNSUBSCRIBE ME > .

 

Our apology if you receive this announcement from multiple sources !


------=_NextPart_000_0BEC_01CC9AC4.B4CBBBA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<title>Dear friend,</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:128087712;
	mso-list-type:hybrid;
	mso-list-template-ids:859863974 67895297 67895299 67895301 67895297 =
67895299 67895301 67895297 67895299 67895301;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3Dblack face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Verdana;color:black'>Dear =
friend,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>We would like =
to
inform you that <b><span style=3D'font-weight:bold'>DEADLINE for =
abstract
submission </span></b><b><span style=3D'font-weight:bold'>for BALWOIS =
2012</span>
Conference</b> </span></font><i><font size=3D2 face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>(Fifth
International Scientific Conference on Water, Climate and Environment, =
from 28
May to 02 June 2012, Ohrid, Macedonia)</span></font></i><font size=3D2
face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial'> </span></font><b><font
size=3D2 color=3Dblack face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Verdana;color:black;font-weight:bold'>is =
POSTPONED</span></font></b><font
size=3D2 color=3Dblack face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Verdana;color:black'> until <b><span =
style=3D'font-weight:bold'>20<sup>th</sup>
of November 2011 </span></b></span></font><i><font size=3D2 =
face=3DArial><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>(informati=
on
at <a href=3D"http://www.balwois.com/2012"
title=3D"blocked::http://www.balwois.com/2012">www.balwois.com/2012</a>).=
</span></font></i><i><font
size=3D2 color=3Dblack face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Verdana;color:black;font-style:italic'><o:p></o:p></span></fo=
nt></i></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>We hope this =
extra
time will encourage more of you to consider participating and please =
submit
your abstracts as soon as possible on the Conference =
website.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>Those authors =
who have
already submitted abstracts will be notified as to whether their =
abstracts have
been accepted or not until 30 of November =
2011.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>&nbsp;<o:p></o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>Here are some
instructions about the submission =
procedure.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>BALWOIS 2012 =
is using
online Conference management system, therefore you have to =
:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:18.0pt'><b><font size=3D2 =
color=3Dblack
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:black;font-weight:bold'>I -</span></font></b><font size=3D2 =
color=3Dblack
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:black'> register yourself at conference web =
site;<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:18.0pt'><b><font size=3D2 =
color=3Dblack
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:black;font-weight:bold'>II &#8211;</span></font></b><font size=3D2
color=3Dblack face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Verdana;color:black'> only after registration you can submit your =
abstracts via
your account (using your username and =
password).<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:18.0pt'><font size=3D2 =
color=3Dblack
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:black'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'>NOTE: We =
cannot
register and/or submit your abstract on behalf of you. Please, have a =
look on
the following instructions.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#3366ff" =
face=3DVerdana><span lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:#3366FF'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D1
color=3Dblue face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:
Verdana;color:blue'>Instructions about <b><span =
style=3D'font-weight:bold'>REGISTRATION</span></b>
(opening user account) and <b><span =
style=3D'font-weight:bold'>SUBMISSION</span></b>
of the abstracts<o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue;font-weight:bold'=
><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D1 color=3Dnavy face=3DVerdana><span
style=3D'font-size:9.0pt;font-family:Verdana;color:navy;font-weight:bold'=
><a
href=3D"http://1.to/" target=3D"_blank"><font color=3Dnavy><span =
lang=3DEN-GB
style=3D'color:navy'>1.To</span></font></a></span></font></b><b><font =
size=3D1
color=3Dnavy face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:
Verdana;color:navy;font-weight:bold'> REGISTER</span></font></b><font =
size=3D1
color=3Dnavy face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:
Verdana;color:navy'> </span></font><font size=3D1 color=3Dblue =
face=3DVerdana><span
lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>you have =
to:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; Go on =
the page </span></font><b><font
size=3D1 color=3Dblue face=3DVerdana><span =
style=3D'font-size:9.0pt;font-family:Verdana;
color:blue;font-weight:bold'><a href=3D"http://ocs.balwois.com/" =
target=3D"_blank"><span
lang=3DEN-GB>http://ocs.balwois.com</span></a></span></font></b><b><font =
size=3D1
color=3Dblue face=3DVerdana><span =
style=3D'font-size:9.0pt;font-family:Verdana;
color:blue;font-weight:bold'> </span></font></b><font size=3D1 =
color=3Dblue
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Verdana;
color:blue'>;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; Click =
at <b><span
style=3D'font-weight:bold'>LOG IN =
</span></b>;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; Click =
at: &raquo; </span></font><b><font
size=3D1 color=3Dblue face=3DVerdana><span =
style=3D'font-size:9.0pt;font-family:Verdana;
color:blue;font-weight:bold'><a
href=3D"http://ocs.balwois.com/index.php?conference=3DBALWOIS&amp;schedCo=
nf=3DBW2012&amp;page=3Duser&amp;op=3Daccount"
target=3D"_blank"><span lang=3DEN-GB>Not a user? Create an account with =
this site</span></a></span></font></b><b><font
size=3D1 color=3Dblue face=3DVerdana><span =
style=3D'font-size:9.0pt;font-family:Verdana;
color:blue;font-weight:bold'> </span></font></b><font size=3D1 =
color=3Dblue
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Verdana;
color:blue'>;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; Fill =
the FORM
and <b><span style=3D'font-weight:bold'>do not forget to check the box
&quot;Author</span></b>&quot; at the bottom of this =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>FORM (to define =
your
account as author) .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'><o:p>&nbsp;</o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>This =
registration must
be done <b><span style=3D'font-weight:bold'>only one =
time</span></b>.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue;font-weight:bold'=
><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D1 color=3Dnavy face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:navy;font-weight:bold'=
>2. To
SUBMIT</span></font></b><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'> your abstract =
you have
:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; to use =
your
username and password at </span></font><font size=3D1 color=3Dblue =
face=3DVerdana><span
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'><a
href=3D"http://ocs.balwois.com/" target=3D"_blank"><span =
lang=3DEN-GB>http://ocs.balwois.com</span></a></span></font><font
size=3D1 color=3Dblue face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:9.0pt;
font-family:Verdana;color:blue'> to access your account =
;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; to =
choose
&quot;New Submission&quot; ;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; to fill =
the form
;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; to =
submit the
form (abstract). <o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue;font-weight:bold'=
><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D1 color=3Dnavy face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:navy;font-weight:bold'=
>3. To
MAKE CHANGES</span></font></b><font size=3D1 color=3Dblue =
face=3DVerdana><span
lang=3DEN-GB style=3D'font-size:9.0pt;font-family:Verdana;color:blue'> =
(to add more
authors, to change the Title or the Text of abstract, etc.) you =
should:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; Use =
your
username and password to access your =
account;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; Choose =
&laquo; <b><span
style=3D'font-weight:bold'>Active submission &raquo; =
</span></b>;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; Click =
on the <b><span
style=3D'font-weight:bold'>Title of the abstract</span></b> that you =
want to
change;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; Click =
on the
button <b><span style=3D'font-weight:bold'>EDIT METADATA =
</span></b>(somewhere in
the middle of the page);<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue'>&#8226; After =
making
corrections, click on the button <b><span =
style=3D'font-weight:bold'>SAVE
METADATA.&quot;<o:p></o:p></span></b></span></font></p>

<p class=3DMsoNormal><b><font size=3D1 color=3Dblue face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Verdana;color:blue;font-weight:bold'=
><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Verdana'>If you have some problems do not hesitate to
contact us.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Verdana'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Verdana'>Best Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Verdana'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Verdana'>BALWOIS =
Secretariat<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Verdana'>____________________________________<o:p></o:=
p></span></font></p>

<div =
style=3D'mso-element:para-border-div;border:none;border-bottom:solid =
windowtext 1.5pt;
padding:0cm 0cm 1.0pt 0cm'>

<p class=3DMsoNormal style=3D'border:none;padding:0cm'><span
class=3Dyiv1055745681apple-style-span><i><font size=3D1 color=3Dblack =
face=3DArial><span
lang=3DEN-GB =
style=3D'font-size:8.0pt;font-family:Arial;color:black;font-style:
italic'>If this email has arrived by mistake please delete it and if you =
want
to unsubscribe for the further emails concerning BALWOIS 2012 =
Conference,
please send us an email with this subject : &laquo; UNSUBSCRIBE ME =
&raquo; .</span></font></i></span><i><font
size=3D1 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:8.0pt;font-family:Verdana;
font-style:italic'><o:p></o:p></span></font></i></p>

</div>

<p class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center'><b><i><font size=3D2
face=3D"Times New Roman"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-weight:
bold;font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center'><b><i><font size=3D2
face=3D"Times New Roman"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-weight:
bold;font-style:italic'>Our apology if you receive this announcement =
from
multiple sources !<o:p></o:p></span></font></i></b></p>

</div>

</body>

</html>

------=_NextPart_000_0BEC_01CC9AC4.B4CBBBA0--


From ietfc@btconnect.com  Fri Nov  4 04:39:58 2011
Return-Path: <ietfc@btconnect.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4BDF21F8C5C for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 04:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSzGB4wLT2VD for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 04:39:58 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by ietfa.amsl.com (Postfix) with ESMTP id BC0BA21F8C5E for <ipv6@ietf.org>; Fri,  4 Nov 2011 04:39:56 -0700 (PDT)
Received: from host86-177-208-97.range86-177.btcentralplus.com (HELO pc6) ([86.177.208.97]) by c2beaomr08.btconnect.com with SMTP id EYU17814; Fri, 04 Nov 2011 11:37:25 +0000 (GMT)
Message-ID: <00b701cc9add$01fcdae0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com><4EB204BA.7040106@gmail.com> <20111103174719.GD88646@verdi><201111031800.pA3I0Gp9019580@cichlid.raleigh.ibm.com> <34B62D9F-2462-4EFF-93A1-FE9FB65FFE87@castlepoint.net>
Subject: Re: Flow Label support in the Node Requirements bis document
Date: Fri, 4 Nov 2011 11:32:04 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4EB3CE74.001A, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.11.4.105714:17:7.586, ip=86.177.208.97, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_PATH, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0208.4EB3CF0B.000F,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 11:39:58 -0000

----- Original Message -----
From: "Shane Amante" <shane@castlepoint.net>
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
Sent: Friday, November 04, 2011 1:37 AM
Subject: Re: Flow Label support in the Node Requirements bis document


>
> On Nov 3, 2011, at 12:00 PM, Thomas Narten wrote:
> > John,
> >
> > This should not be a surprising or controversial change to the
> > node-requirements document. The WG made the decision earlier that we'd
> > leave out a reference to the Flow Label work because we didn't want to
> > have node-requirements block waiting for it, but we would revisit if
> > that work finished in time.
> >
> > It has.
> >
> > We should just make this change. There was never any doubt that node
> > requirements would point to the updated Flow Label RFC.
>
> I completely agree.  We should make the change now.

Yes, make the change now.  Planning on yet another revision is just confirming
the impression that people get that IPv6 is not yet ready, will still be being
tinkered with in two years time, so don't invest in it yet.  Honest, I think
that the tinkeritis that has kept the IPv6 revision industry busy for 15 years
is a major bar to progress.  Sometime we must stop and say, just do it.

Tom Petch

>
> -shane
>
>
> > If we say "do it later, when we rev the document again", we should be
> > realistic in that that probably won't happen for at least another year
> > and probably more like 2+ years.
> >
> > Thomas
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>


From brian@innovationslab.net  Fri Nov  4 05:46:34 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50CBB21F8AFB; Fri,  4 Nov 2011 05:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2FCJyJAKPg2; Fri,  4 Nov 2011 05:46:33 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4622721F84C9; Fri,  4 Nov 2011 05:46:32 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 097B288151; Fri,  4 Nov 2011 05:46:32 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 0D1C8130005; Fri,  4 Nov 2011 05:46:30 -0700 (PDT)
Message-ID: <4EB3DEA4.5000207@innovationslab.net>
Date: Fri, 04 Nov 2011 08:46:28 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: 6man-ads@tools.ietf.org
Subject: Request To Advance: draft-ietf-6man-exthdr-05.txt
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: iesg-secretary@ietf.org, ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 12:46:34 -0000

Jari & Ralph,
     On behalf of the 6MAN Working Group, the chairs request the
advancement of:

     Title     : An uniform format for IPv6 extension headers
     Author(s) : Suresh Krishnan
                 James Woodyatt
                 Erik Kline
                 James Hoagland
                 Manav Bhatia
     Filename  : draft-ietf-6man-exthdr-05.txt
     Pages     : 8
     Date      : 2011-10-31

as a Proposed Standard.  The Working Group Last Call ended on July 14,
2011 and this version addresses all comments/issues raised.

Regards,
Brian Haberman & Bob Hinden

From brian@innovationslab.net  Fri Nov  4 07:16:59 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3925D21F8BDC for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 07:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZxwts1XafBu for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 07:16:58 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id B083321F8BEC for <ipv6@ietf.org>; Fri,  4 Nov 2011 07:16:58 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 381BF88090; Fri,  4 Nov 2011 07:16:58 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 3A45B13694EE; Fri,  4 Nov 2011 07:16:56 -0700 (PDT)
Message-ID: <4EB3F3D6.4090302@innovationslab.net>
Date: Fri, 04 Nov 2011 10:16:54 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 14:16:59 -0000

All,
     This message starts a two week 6MAN Working Group on advancing:

     Title     : Update to RFC 3484 Default Address Selection for IPv6
     Author(s) : Arifumi Matsumoto
                 Jun-ya Kato
                 Tomohiro Fujisaki
                 Tim Chown
     Filename  : draft-ietf-6man-rfc3484-revise-05.txt
     Pages     : 12
     Date      : 2011-10-31

as a Proposed Standard.  Substantive comments and statements of support
for advancing this document should be directed to the mailing list.
Editorial suggestions can be sent to the authors.  This last call will
end on November 18, 2011.

Regards,
Brian Haberman & Bob Hinden

From fx.lebail@yahoo.com  Fri Nov  4 10:08:32 2011
Return-Path: <fx.lebail@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA8B41F0C3E for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 10:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.451
X-Spam-Level: 
X-Spam-Status: No, score=0.451 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_50=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQ04zMpmxjA6 for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 10:08:32 -0700 (PDT)
Received: from nm38-vm3.bullet.mail.ne1.yahoo.com (nm38-vm3.bullet.mail.ne1.yahoo.com [98.138.229.147]) by ietfa.amsl.com (Postfix) with SMTP id 3D36421F8BD7 for <ipv6@ietf.org>; Fri,  4 Nov 2011 10:08:32 -0700 (PDT)
Received: from [98.138.90.48] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 04 Nov 2011 17:08:26 -0000
Received: from [98.138.89.167] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 04 Nov 2011 17:08:26 -0000
Received: from [127.0.0.1] by omp1023.mail.ne1.yahoo.com with NNFMP; 04 Nov 2011 17:08:26 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 501855.13480.bm@omp1023.mail.ne1.yahoo.com
Received: (qmail 36511 invoked by uid 60001); 4 Nov 2011 17:08:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1320426506; bh=hNJr/39CX4kg+IgTRFjdo6ZsJlZd0kdI36Ym9tEcNds=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=MtDmHXyUYIE2vZ5yvYLixae+NHi0qr5OWfZVz2kA+Gwrhmwaw6enU4cQx0r/T4aHevnYqYDvY2DIhEWLAJJslsr5R1ncu6vNsAEIfe00xixMVROnhcLi0ldGNVNkt3NY0P/DUy+wT/puVwGC1BD54seQcFXNp730CKPoGZpe45U=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=RrljiZT4XrJxkYe7/i6/q5kteNdST3DLZpxjs4AMyb/TzAllbhgdeouWeqoY1L53phdX2VdhtchR+yUTKWXvxiuKaURigsYEa+Jf4i2CQ1zpQ7cnhnoebwkfKQretpTPjKBPsbfwrbspJwiJadyapO+B53VOqNGEwseiQo307nU=;
X-YMail-OSG: LKIZkjgVM1lSFaYseMPXQy.PfaXKTCL.P71z5I8A7QowI1j d4Jt5JPrel7mcJM2AIwLrkLTS9J49DHkEUx2dUYjZw8W9qABUaWa0I5LYjzK yGa1.MRJ3poBkQSuLzzeHXSHrPZ7ba_3Pa5cGwyNojQhILgeH4w0nSss4GUT j9EXfndIs6ZWT0uADwY_hJM0m._HCbidutM6aM6btfGbvhVQjsFBEd5wvCa3 8.4G.Gw8crtulpiYC9skgTo.N2s1WwA3ZXSp1RVAx_m8iSju2Vak0mlUNxjO x6P8cbuREXExXREUacpbKWAw_FvFwFlSnJ0jsw.nfnvFPCB9xey9qLpGJwbd _dSLP5kyArrowJXa5tQc9AnVNPlFaAS_kOqhiOR9JSoRu.iJxG0S83YAwWRT ksqV42YE4MZYanwsEJfQN07aPzoaDadeO1syytRerjGnk7BuTLkjebLRLePY zD0DqVty40.om_toXxIezyc9eWqHaMgYPDveqzHEQQzhzJ7yq5olf_tOezQ- -
Received: from [193.49.124.107] by web126019.mail.ne1.yahoo.com via HTTP; Fri, 04 Nov 2011 10:08:26 PDT
X-Mailer: YahooMailWebService/0.8.115.325013
References: 
Message-ID: <1320426506.33305.YahooMailNeo@web126019.mail.ne1.yahoo.com>
Date: Fri, 4 Nov 2011 10:08:26 -0700 (PDT)
From: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
Subject: RFC 4443 versus RFC 4942
To: "ipv6@ietf.org" <ipv6@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 17:08:32 -0000

Hi,=0A=0AThe RFC 4443 (Internet Control Message Protocol (ICMPv6) for the=
=0AInternet Protocol Version 6 (IPv6) Specification) states :=0A(http://too=
ls.ietf.org/html/rfc4443#section-4.2)=0A[. . .]=0A"An Echo Reply SHOULD be =
sent in response to an Echo Request message=0Asent to an IPv6 multicast or =
anycast address.=A0 In this case, the=0Asource address of the reply MUST be=
 a unicast address belonging to=0Athe interface on which the Echo Request m=
essage was received." =0A=0AThe RFC 4942 (IPv6 Transition/Coexistence Secur=
ity Considerations) states :=0A(http://tools.ietf.org/html/rfc4942#section-=
2.1.6)=0A2.1.6. Anycast Traffic Identification and Security=0A[. . .]=0A"To=
 avoid exposing knowledge about the internal structure of the=0Anetwork, it=
 is recommended that anycast servers now take advantage of=0Athe ability to=
 return responses with the anycast address as the=0Asource address if possi=
ble."=0A=0AEven if it is "must" versus "recommended", It seems contradictor=
y=0Afor an anycast address.=0A=0APlease let me know your feedback.=0A=0ATha=
nks,=0AFrancois-Xavier Le Bail=0A

From rja.lists@gmail.com  Fri Nov  4 10:52:52 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35ECA21F8C45 for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 10:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.517
X-Spam-Level: 
X-Spam-Status: No, score=-3.517 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wN+AU5GXjG9U for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 10:52:51 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A357621F8BE7 for <ipv6@ietf.org>; Fri,  4 Nov 2011 10:52:51 -0700 (PDT)
Received: by vws5 with SMTP id 5so360165vws.31 for <ipv6@ietf.org>; Fri, 04 Nov 2011 10:52:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=sgo060hBeiomLQS3jqpr1d7/g0wKm+OgDydmi1PEm5U=; b=UIghotNMP0qIgxdHthnbpbiK75B83DubOTrpqd+8retEAAl7jOsUs6eL92jkgDD0Q3 nOTOAeQWC1ds3JUdma6WxSwI8v6So9NLqCkAmeQmbhixdCj7l2ttALcCMAHNymsNepQy VIzoN4jWEhkJAfdXJl5fHxupNvd/8XtyYMnFc=
Received: by 10.52.76.69 with SMTP id i5mr15880164vdw.4.1320429169480; Fri, 04 Nov 2011 10:52:49 -0700 (PDT)
Received: from [10.30.20.12] (pool-96-225-134-175.nrflva.fios.verizon.net. [96.225.134.175]) by mx.google.com with ESMTPS id id7sm14611600vdb.21.2011.11.04.10.52.47 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Nov 2011 10:52:48 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Date: Fri, 4 Nov 2011 13:52:46 -0400
Message-Id: <0E241F72-0529-47E2-AC56-32E2CB82E70E@gmail.com>
To: ipv6@ietf.org
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 17:52:52 -0000

While I support this document generally, I am very sympathetic 
to the specific operational issues raised by Glen Turner:

  <http://www.ietf.org/mail-archive/web/ipv6/current/msg14908.html>

After approval, this IPv6 Line ID destination option will need 
to be integrated with various provisioning systems and also
with various kinds of access equipment.  The past experience 
with certain under-specified RADIUS parameters is relevant,
if sad.  It would be best if we avoided repeating that 
particular operational difficulty. 

So I'd like to see a revised I-D that is edited 
such that it fully resolves Glen's concerns.

Yours,

Ran



From brian@innovationslab.net  Fri Nov  4 12:59:43 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A03211E80A1 for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 12:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level: 
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJxGi4DdFAg0 for <ipv6@ietfa.amsl.com>; Fri,  4 Nov 2011 12:59:42 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 54BD211E8098 for <ipv6@ietf.org>; Fri,  4 Nov 2011 12:59:42 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 247EE88122 for <ipv6@ietf.org>; Fri,  4 Nov 2011 12:59:42 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id F05831368160 for <ipv6@ietf.org>; Fri,  4 Nov 2011 12:59:40 -0700 (PDT)
Message-ID: <4EB4442A.2000403@innovationslab.net>
Date: Fri, 04 Nov 2011 15:59:38 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Consensus call on adopting: draft-george-6man-3627-historic
References: <4E94776D.5080908@innovationslab.net>
In-Reply-To: <4E94776D.5080908@innovationslab.net>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 19:59:43 -0000

All,
     Any dissenting opinions on the adoption of this draft?

Regards,
Brian

On 10/11/11 1:05 PM, Brian Haberman wrote:
> All,
>      This is a consensus call on adopting:
> 
>      Title     : RFC3627 to Historic status
>      Author(s) : Wesley George
>      Filename  : draft-george-6man-3627-historic-01.txt
>      Pages     : 4
>      Date      : 2011-10-10
> 
> as a 6MAN working group document.  Please state your opinion, positive
> or negative, on the mailing list or to the chairs.  This consensus call
> will end on October 25, 2011.
> 
> Regards,
> Brian & Bob
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From suresh.krishnan@ericsson.com  Sat Nov  5 06:38:40 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D577821F858C for <ipv6@ietfa.amsl.com>; Sat,  5 Nov 2011 06:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.474
X-Spam-Level: 
X-Spam-Status: No, score=-106.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k+jgmOYt3LHp for <ipv6@ietfa.amsl.com>; Sat,  5 Nov 2011 06:38:40 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id EA38221F8586 for <ipv6@ietf.org>; Sat,  5 Nov 2011 06:38:39 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pA5DcS5H001667; Sat, 5 Nov 2011 08:38:29 -0500
Received: from [142.133.10.44] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.137.0; Sat, 5 Nov 2011 09:38:27 -0400
Message-ID: <4EB53BCD.3090004@ericsson.com>
Date: Sat, 5 Nov 2011 09:36:13 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Glen Turner <gdt@gdt.id.au>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com> <1320358729.3032.24.camel@ilion>
In-Reply-To: <1320358729.3032.24.camel@ilion>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Nov 2011 13:38:40 -0000

Hi Glen,

Thanks for the comments. Please find responses inline.

On 11/03/2011 06:18 PM, Glen Turner wrote:
> The contents of the Line Identification Destination Option are
> essentially opaque.

Yes. They are.

>
> Although this may allow a wide range of router implementations, in
> practice it leads to a situation where new implementers must
> reverse-engineer the dominant implementation in order to be assured of
> compatibility.
>
> An opaque field allows a wide range of router implementation practice at
> the cost of ease of use of the field in provisioning databases. An
> implementation of a provisioning database which can configure a range of
> routers has to ask for the Identification Destination in hexadecimal.
>
> If the contents of the field are in practice a MAC address there may be
> a repetition of the experience with the RADIUS's Calling-Station-Id
> where a lack of definition of the content of the field leads to programs
> with two or so pages of parsing code to extract a wireless device's MAC
> address.
>
> If the contents of the field are in practice an interface name then
> perhaps ifIndex would be more suitable.
>
> If the contents of the field are in practice a customer provisioning
> identifier then perhaps the field could be specified as a string so that
> programmers know that the field can be typed or printed rather than
> hexdumped. Some care should be taken to identify the character set, as
> it is unlikely to be UTF-8.

This is the case in the deployments that we know about. The line-id is 
essentially a string that is matched with the provisioning databases 
(AAA) to determine a prefix to send out.

>
> If the authors decide that opaque is desirable then they should define
> the textual representation of the field. That way the contents of the
> field are defined identically across different manufacturers' router
> configuration languages, ISP provisioning databases, etc.

Will do. Would a simple statement e.g. that it is a null terminated text 
string be sufficient or did you want more details?

Thanks
Suresh


From nordmark@acm.org  Sat Nov  5 14:32:04 2011
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD68811E8080 for <ipv6@ietfa.amsl.com>; Sat,  5 Nov 2011 14:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7d9vMpUmsrD for <ipv6@ietfa.amsl.com>; Sat,  5 Nov 2011 14:32:04 -0700 (PDT)
Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by ietfa.amsl.com (Postfix) with ESMTP id 42E6811E807F for <ipv6@ietf.org>; Sat,  5 Nov 2011 14:32:04 -0700 (PDT)
Received: from [10.0.1.13] (128-107-239-233.cisco.com [128.107.239.233]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id pA5LVplg013193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Nov 2011 14:31:51 -0700
Message-ID: <4EB5AB4D.4050102@acm.org>
Date: Sat, 05 Nov 2011 14:31:57 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com> <1320358729.3032.24.camel@ilion> <4EB53BCD.3090004@ericsson.com>
In-Reply-To: <4EB53BCD.3090004@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Nov 2011 21:32:04 -0000

On 11/5/11 6:36 AM, Suresh Krishnan wrote:

>> If the authors decide that opaque is desirable then they should define
>> the textual representation of the field. That way the contents of the
>> field are defined identically across different manufacturers' router
>> configuration languages, ISP provisioning databases, etc.
>
> Will do. Would a simple statement e.g. that it is a null terminated text
> string be sufficient or did you want more details?

Or should we refer to the corresponding DHCPv4 relay option? I think the 
simple case is when operators reuse the syntax they use for line 
identification with DHCPv4. But I haven't look at exactly how that DHCP 
option is specified.

    Erik

From suresh.krishnan@ericsson.com  Sun Nov  6 17:24:56 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 867D821F886A for <ipv6@ietfa.amsl.com>; Sun,  6 Nov 2011 17:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.477
X-Spam-Level: 
X-Spam-Status: No, score=-106.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exJ-XeL7ZI4V for <ipv6@ietfa.amsl.com>; Sun,  6 Nov 2011 17:24:56 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 03FCA21F87C9 for <ipv6@ietf.org>; Sun,  6 Nov 2011 17:24:55 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pA71Ofcd026543 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 6 Nov 2011 19:24:41 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.174]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Sun, 6 Nov 2011 20:24:41 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Erik Nordmark <nordmark@acm.org>
Date: Sun, 6 Nov 2011 20:24:39 -0500
Subject: RE: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Thread-Topic: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Thread-Index: AcycAlpVACapm/ydQemYI49FYdmTcwA5uoiA
Message-ID: <4FD1E7CD248BF84F86BD4814EDDDBCC15142B1959E@EUSAACMS0703.eamcs.ericsson.se>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com> <1320358729.3032.24.camel@ilion> <4EB53BCD.3090004@ericsson.com> <4EB5AB4D.4050102@acm.org>
In-Reply-To: <4EB5AB4D.4050102@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2011 01:24:56 -0000

Hi Erik,
=20
> -----Original Message-----
> From: Erik Nordmark [mailto:nordmark@acm.org]=20
> Sent: Saturday, November 05, 2011 5:32 PM
> To: Suresh Krishnan
> Cc: Glen Turner; 6man Mailing List; Brian Haberman; Bob Hinden
> Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
>=20
> On 11/5/11 6:36 AM, Suresh Krishnan wrote:
>=20
> >> If the authors decide that opaque is desirable then they should=20
> >> define the textual representation of the field. That way=20
> the contents=20
> >> of the field are defined identically across different=20
> manufacturers'=20
> >> router configuration languages, ISP provisioning databases, etc.
> >
> > Will do. Would a simple statement e.g. that it is a null terminated=20
> > text string be sufficient or did you want more details?
>=20
> Or should we refer to the corresponding DHCPv4 relay option?=20
> I think the simple case is when operators reuse the syntax=20
> they use for line identification with DHCPv4. But I haven't=20
> look at exactly how that DHCP option is specified.

The corresponding DHCPv4 relay option (defined in RFC3046) and the
corresponding DHCPv6 relay option (defined in RFC4649) are both=20
defined as opaque with no character set information. That is what
makes definition more difficult.

Thanks
Suresh

From washam.fan@gmail.com  Sun Nov  6 20:39:28 2011
Return-Path: <washam.fan@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 067C61F0C36 for <ipv6@ietfa.amsl.com>; Sun,  6 Nov 2011 20:39:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.412
X-Spam-Level: 
X-Spam-Status: No, score=-3.412 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oZnvhzU2Ip3 for <ipv6@ietfa.amsl.com>; Sun,  6 Nov 2011 20:39:27 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 486B51F0C35 for <ipv6@ietf.org>; Sun,  6 Nov 2011 20:39:27 -0800 (PST)
Received: by wwi36 with SMTP id 36so4400560wwi.13 for <ipv6@ietf.org>; Sun, 06 Nov 2011 20:39:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WNKS/8Z0iaUzBtW98Ajr1Gwab3h9aaZin1JXBb7zAeg=; b=XdT9WsIyWhyXC+8mcPVIrOx/9kkE5PMB6FEZOCtCcvbthQS7MBT8W6LJdRB73lvNkh UUOsasxTGMQVTlbmxFGWopmOn4KhO4KWQEHP6+rUouwnCnveot3Vl55XildtfgCenvBU 1M4agtZBgB+GVJlS6s13Igd4UBX9GmUAcPA60=
MIME-Version: 1.0
Received: by 10.216.163.203 with SMTP id a53mr2727904wel.35.1320640766386; Sun, 06 Nov 2011 20:39:26 -0800 (PST)
Received: by 10.216.190.81 with HTTP; Sun, 6 Nov 2011 20:39:26 -0800 (PST)
In-Reply-To: <1320426506.33305.YahooMailNeo@web126019.mail.ne1.yahoo.com>
References: <1320426506.33305.YahooMailNeo@web126019.mail.ne1.yahoo.com>
Date: Mon, 7 Nov 2011 12:39:26 +0800
Message-ID: <CAAuHL_Apmfg2mfrYwit-Y5Z3rOQsR6fvYTX6zFQGUvxmE2j_Gw@mail.gmail.com>
Subject: Re: RFC 4443 versus RFC 4942
From: Washam Fan <washam.fan@gmail.com>
To: =?ISO-8859-1?Q?Fran=E7ois=2DXavier_Le_Bail?= <fx.lebail@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2011 04:39:28 -0000

Hi,

I think the statements apply to different scenarios.

The sequence number can be used to match an echo request and an echo
reply. But for UDP/TCP or any transport-layer communications,
addresses (regardless of the src or dest) change could lead to
communication interruption.

Thanks,
washam

2011/11/5 Fran=E7ois-Xavier Le Bail <fx.lebail@yahoo.com>:
> Hi,
>
> The RFC 4443 (Internet Control Message Protocol (ICMPv6) for the
> Internet Protocol Version 6 (IPv6) Specification) states :
> (http://tools.ietf.org/html/rfc4443#section-4.2)
> [. . .]
> "An Echo Reply SHOULD be sent in response to an Echo Request message
> sent to an IPv6 multicast or anycast address.=A0 In this case, the
> source address of the reply MUST be a unicast address belonging to
> the interface on which the Echo Request message was received."
>
> The RFC 4942 (IPv6 Transition/Coexistence Security Considerations) states=
 :
> (http://tools.ietf.org/html/rfc4942#section-2.1.6)
> 2.1.6. Anycast Traffic Identification and Security
> [. . .]
> "To avoid exposing knowledge about the internal structure of the
> network, it is recommended that anycast servers now take advantage of
> the ability to return responses with the anycast address as the
> source address if possible."
>
> Even if it is "must" versus "recommended", It seems contradictory
> for an anycast address.
>
> Please let me know your feedback.
>
> Thanks,
> Francois-Xavier Le Bail
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

From fx.lebail@yahoo.com  Mon Nov  7 01:28:43 2011
Return-Path: <fx.lebail@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C735421F8783 for <ipv6@ietfa.amsl.com>; Mon,  7 Nov 2011 01:28:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.899
X-Spam-Level: 
X-Spam-Status: No, score=-0.899 tagged_above=-999 required=5 tests=[AWL=1.400,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ujUNLdTqaeUS for <ipv6@ietfa.amsl.com>; Mon,  7 Nov 2011 01:28:43 -0800 (PST)
Received: from nm37.bullet.mail.ne1.yahoo.com (nm37.bullet.mail.ne1.yahoo.com [98.138.229.30]) by ietfa.amsl.com (Postfix) with SMTP id 44F3D21F8770 for <ipv6@ietf.org>; Mon,  7 Nov 2011 01:28:43 -0800 (PST)
Received: from [98.138.90.56] by nm37.bullet.mail.ne1.yahoo.com with NNFMP; 07 Nov 2011 09:28:37 -0000
Received: from [98.138.89.199] by tm9.bullet.mail.ne1.yahoo.com with NNFMP; 07 Nov 2011 09:28:37 -0000
Received: from [127.0.0.1] by omp1057.mail.ne1.yahoo.com with NNFMP; 07 Nov 2011 09:28:37 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 414187.82565.bm@omp1057.mail.ne1.yahoo.com
Received: (qmail 41539 invoked by uid 60001); 7 Nov 2011 09:28:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1320658117; bh=IquknWIKoSDcJXjTmZMOAFV34zGqTjNtYvQQG5pklM0=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=yuxDgSQd1q7UCOo8Q6LlAD/QokPff696nrwC0YmztN/amFfKbUv3aYph/1jhN5HlhxBs5lZ1+CuLE6jwIl3klp07hV4L6mVlbQa+z1BpIy89Ji2etoQ7UOUK4GejerRW0BryVjN+N7fE+MtNM/wOiKcV4V/T7Es+PwNKU//kCwc=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=MqCCHWnnh+dXtg5m2hWm+ueHREC4L4b/isM4gXSeU/cL8dJukvQd/TQLOd7QBC36Zn9ZDk+Ljsrqs5zM/j6jZjmy8mADgshLCz5tzp0vaVCdVw4nRACjTC1O9rnmDTrOY52YspdVKJz42m8ecu01twkFFel6s3Y/mzfqel+zkTE=;
X-YMail-OSG: hQfsZhgVM1m.Eg2tfltuM0rKUqLjYqAnqG66ESG33nYY140 1Y.hRPOYfjEiysyN15y.9Zt0qQcRXOqQDXwaSCTweqDcDylY6HXl2.BnVy7Q zzifWsmtUEEZJGUeT7jolyfkCJ0VclNXxaeFo3EY25S1rOpYxoMY_bA_W7fh 63QHj40_uzQ5qmpA5M5uRuaRo67Kl8di365tY_NNzfsMMMkYzU3wgt8qEs_k O1rM8kGJu_fbRpXmkobuhD1D45CyVjeXPqZFowVBFxs9e10dzVQw0xAcMuzZ MpGUR2IfRCymV09LqCLoDhpVw0SpVn6XLS4Hfj.KkY2RISpD1_1JLaEzZ3c2 1wndpAUn1ozxa9QKhUvhPiYJCdfo_aznrWWzDiOzAGHMoSqAmdf6aYPn_FbJ SiohlJZ_nvrJur9Tp6d9trtiA_jsMDRoKjcPSdCreFRrX5ps8BCuffIwUqr5 A.zM4HeuA
Received: from [193.49.124.107] by web126007.mail.ne1.yahoo.com via HTTP; Mon, 07 Nov 2011 01:28:37 PST
X-Mailer: YahooMailWebService/0.8.115.325013
References: <20111031235203.11203.64958.idtracker@ietfa.amsl.com>
Message-ID: <1320658117.39943.YahooMailNeo@web126007.mail.ne1.yahoo.com>
Date: Mon, 7 Nov 2011 01:28:37 -0800 (PST)
From: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
Subject: Re: I-D Action: draft-ietf-6man-rfc3484-revise-05.txt
To: "ipv6@ietf.org" <ipv6@ietf.org>
In-Reply-To: <20111031235203.11203.64958.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2011 09:28:43 -0000

=A0    =0AHi,=0A=0AThe draft has taken into account anycast addresses.=0Aht=
tp://tools.ietf.org/html/draft-ietf-6man-rfc3484-revise-05#section-2.6=0A=
=0AIt remains to handle the special case of Subnet-Router anycast address.=
=0A(http://tools.ietf.org/html/rfc4291#section-2.6.1)=0A"The Subnet-Router =
anycast address is intended to be used for=0Aapplications where a node need=
s to communicate with any one of the=0Aset of routers."=0A=0ASo, I think a =
SRaa must be excluded from the candidate set of source address=0Afor a new =
communication.=0AThe SRaa as source address must be reserved for a reply to=
 a packet sent to this SRaa.=0A=0AText proposal (to add section 2.6) :=0A"A=
s an exception, a Subnet-Router anycast address MUST NOT be included in the=
=0Acandidate set of source address when initiating communication.=0AThe Sub=
net-Router anycast address as source address MUST be used in a=0Areply to a=
 packet sent to this Subnet-Router anycast address".=0A=0AThanks,=0AFran=E7=
ois-Xavier=0A=0A=0A----- Original Message -----=0A> From: "internet-drafts@=
ietf.org" <internet-drafts@ietf.org>=0A> To: i-d-announce@ietf.org=0A> Cc: =
ipv6@ietf.org=0A> Sent: Tuesday, November 1, 2011 12:52 AM=0A> Subject: I-D=
 Action: draft-ietf-6man-rfc3484-revise-05.txt=0A> =0A> A New Internet-Draf=
t is available from the on-line Internet-Drafts directories. =0A> This draf=
t is a work item of the IPv6 Maintenance Working Group of the IETF.=0A> =0A=
> =A0=A0=A0 Title=A0 =A0 =A0 =A0 =A0  : Update to RFC 3484 Default Address =
Selection for IPv6=0A> =A0=A0=A0 Author(s)=A0 =A0 =A0  : Arifumi Matsumoto=
=0A> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Jun-ya Kato=0A> =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Tomohiro Fujisaki=0A> =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Tim Chown=0A> =A0=A0=A0=
 Filename=A0 =A0 =A0 =A0 : draft-ietf-6man-rfc3484-revise-05.txt=0A> =A0=A0=
=A0 Pages=A0 =A0 =A0 =A0 =A0  : 12=0A> =A0=A0=A0 Date=A0 =A0 =A0 =A0 =A0 =
=A0 : 2011-10-31=0A> =0A> =A0  RFC 3484 describes algorithms for source add=
ress selection and for=0A> =A0  destination address selection.=A0 The algor=
ithms specify default=0A> =A0  behavior for all Internet Protocol version 6=
 (IPv6) implementations.=0A> =A0  This document specifies a set of updates =
that modify the algorithms=0A> =A0  and fix the known defects.=0A> =0A> =0A=
> A URL for this Internet-Draft is:=0A> http://www.ietf.org/internet-drafts=
/draft-ietf-6man-rfc3484-revise-05.txt=0A> =0A> Internet-Drafts are also av=
ailable by anonymous FTP at:=0A> ftp://ftp.ietf.org/internet-drafts/=0A> =
=0A> This Internet-Draft can be retrieved at:=0A> ftp://ftp.ietf.org/intern=
et-drafts/draft-ietf-6man-rfc3484-revise-05.txt=0A> -----------------------=
---------------------------------------------=0A> IETF IPv6 working group m=
ailing list=0A> ipv6@ietf.org=0A> Administrative Requests: https://www.ietf=
.org/mailman/listinfo/ipv6=0A> --------------------------------------------=
------------------------=0A>

From Olaf.Bonness@telekom.de  Tue Nov  8 01:05:04 2011
Return-Path: <Olaf.Bonness@telekom.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C76AF21F8CBF for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 01:05:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U9wGRBKYqn7N for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 01:05:04 -0800 (PST)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 99BE321F8CBE for <ipv6@ietf.org>; Tue,  8 Nov 2011 01:05:03 -0800 (PST)
Received: from he113414.emea1.cds.t-internal.com ([10.125.65.80]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 08 Nov 2011 10:04:53 +0100
Received: from HE111541.emea1.cds.t-internal.com ([169.254.2.227]) by HE113414.emea1.cds.t-internal.com ([2002:7cd:4150::7cd:4150]) with mapi; Tue, 8 Nov 2011 10:04:52 +0100
From: <Olaf.Bonness@telekom.de>
To: <ipv6@ietf.org>
Date: Tue, 8 Nov 2011 10:04:51 +0100
Subject: AW: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Thread-Topic: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Thread-Index: AcyaQzvFErXH3ZPjSE6QkwkXzxjfGQAAR2ogAOw2sGA=
Message-ID: <CE8995AB5D178F44A2154F5C9A97CAF4024F25BDC4A6@HE111541.emea1.cds.t-internal.com>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com> <4EB2BCEE.6000205@joelhalpern.com> <60C093A41B5E45409A19D42CF7786DFD522602F869@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD522602F869@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: brian@innovationslab.net, bob.hinden@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2011 09:05:04 -0000

I support this I-D becoming an RFC. It's describing a solution that is need=
ed to deploy IPv6 in certain Broadband Access scenarios.

Regards
        Olaf


> On 11/3/2011 11:32 AM, Bob Hinden wrote:
> > All,
> >
> > This message starts a two week 6MAN Working Group Last Call
> on advancing:
> >
> >     Title           : The Line Identification Destination Option
> >     Author(s)       : Suresh Krishnan
> >                            Alan Kavanagh
> >                            Balazs Varga
> >                            Sven Ooghe
> >                            Erik Nordmark
> >     Filename        : draft-ietf-6man-lineid-02.txt
> >     Pages           : 14
> >     Date            : 2011-10-31
> >
> >          http://tools.ietf.org/html/draft-ietf-6man-lineid-02.txt
> >
> > as an Experimental RFC.  Substantive comments and
> statements of support for advancing this document should be
> directed to the mailing list.  Editorial suggestions can be
> sent to the authors.  This last call will end on 17 November 2011.
> >
> > Regards,
> > Bob Hinden&  Brian Haberman
> > 6MAN Chairs
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

From fx.lebail@yahoo.com  Tue Nov  8 06:11:17 2011
Return-Path: <fx.lebail@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A821A21F8C51 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 06:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.051
X-Spam-Level: 
X-Spam-Status: No, score=0.051 tagged_above=-999 required=5 tests=[AWL=-0.250,  BAYES_50=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32Oia3VYodU9 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 06:11:17 -0800 (PST)
Received: from nm40-vm6.bullet.mail.ne1.yahoo.com (nm40-vm6.bullet.mail.ne1.yahoo.com [98.138.229.182]) by ietfa.amsl.com (Postfix) with SMTP id 1B0A221F8B91 for <ipv6@ietf.org>; Tue,  8 Nov 2011 06:11:17 -0800 (PST)
Received: from [98.138.90.50] by nm40.bullet.mail.ne1.yahoo.com with NNFMP; 08 Nov 2011 14:11:16 -0000
Received: from [98.138.89.246] by tm3.bullet.mail.ne1.yahoo.com with NNFMP; 08 Nov 2011 14:11:16 -0000
Received: from [127.0.0.1] by omp1060.mail.ne1.yahoo.com with NNFMP; 08 Nov 2011 14:11:16 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 655202.32484.bm@omp1060.mail.ne1.yahoo.com
Received: (qmail 82391 invoked by uid 60001); 8 Nov 2011 14:11:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1320761476; bh=XQOXO668rQ1Nga2Ln/IsXmhH6if7G+y4v+T+M/aU50E=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=rqBgMMOQXydmVdMPIztp1p0vJmbosmCXQ31Uk0+3VC3boyWNVcwFXs9kY7Xm2ntY+RnEfkTS1MrS3ntnM6auB6q2gYBEaF1mnlgZi7+M5fXL29WoPHrFMNi046sPb2if/MYFqFh4JfGuZgVpDDo+F+3CTPdn3m2cNrp72JfTRqo=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=G0SnfTosg0ixFSYhZTKsVgpQ2CgK8/1ivdDu0AK9l6H1E2judsmcicGnwKDjZNwHBRtT8Cj5quYntq/IV8pzhbcofnvJGaH8kEAy+ma13z/ws25jbwujOk5vpA3V+xZv2FVvxs7DpEk/03pU9CsIo9TzgzWVM2nKTKsc6TAUD0k=;
X-YMail-OSG: jLjRTqcVM1kIw6dZbY9pwsEYhFAWSZmYxSP.yqpq0zfYpsL L7au2xemqE39rTAIBUyUNNzB6.MYu9TIcNUOxWx5.8xi.pQAoqyJXnTLzLwq iCqTRK0geExRKpO3Tq0vBgXZY0lB8gjx1KftqIgKWRHt549V3UfxYJCv6RqK UdyRDGi_8nTs5rxfeYRC2cfSMUl6gpjr7sTB0sFKmp.0QKb7CR0pWFWqCmpZ 3RX0.6Y7RGVtE.ZDbCL22pDdqEPTTrbb45okgU6os0uXOgHZZvMGBy0fITAU Kyq1q.7EVrIrg_CCLZXqUtL.oPBa.vmyToX3aIzGe7DA4rQUqYfeFjvaLIvA exFYQgiCX6K5NC2J1.U0wc.VYqShxfv9HUEewgwmSXngJdWSIWq.G_s5v1py TkvSsXDainM4bYseEOnVo3rqHh.FhtRFUaE4xoDRQDsZv7BC24ejatwAFfnK Qsu418O2L
Received: from [193.49.124.107] by web126020.mail.ne1.yahoo.com via HTTP; Tue, 08 Nov 2011 06:11:16 PST
X-Mailer: YahooMailWebService/0.8.115.325013
References: <1320426506.33305.YahooMailNeo@web126019.mail.ne1.yahoo.com> <CAAuHL_Apmfg2mfrYwit-Y5Z3rOQsR6fvYTX6zFQGUvxmE2j_Gw@mail.gmail.com>
Message-ID: <1320761476.78362.YahooMailNeo@web126020.mail.ne1.yahoo.com>
Date: Tue, 8 Nov 2011 06:11:16 -0800 (PST)
From: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
Subject: Re: RFC 4443 versus RFC 4942
To: Washam Fan <washam.fan@gmail.com>
In-Reply-To: <CAAuHL_Apmfg2mfrYwit-Y5Z3rOQsR6fvYTX6zFQGUvxmE2j_Gw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2011 14:11:17 -0000

----- Original Message -----=0A=0A> From: Washam Fan <washam.fan@gmail.com>=
=0A> To: Fran=E7ois-Xavier Le Bail <fx.lebail@yahoo.com>=0A> Cc: "ipv6@ietf=
.org" <ipv6@ietf.org>=0A> Sent: Monday, November 7, 2011 5:39 AM=0A> Subjec=
t: Re: RFC 4443 versus RFC 4942=0A> =0A> Hi,=0A> =0A> I think the statement=
s apply to different scenarios.=0A> =0A> The sequence number can be used to=
 match an echo request and an echo=0A> reply.=0A=0AIf the source address in=
 the reply don't match the destination address in=0Athe request, there are =
problems (firewall, etc.).=0A=0A> But for UDP/TCP or any transport-layer co=
mmunications,=0A> addresses (regardless of the src or dest) change could le=
ad to=0A> communication interruption.=0A=0AAgreed.=0A=0A> Thanks,=0A> washa=
m=0A=0AThanks,=0AFrancois-Xavier=0A=0A> 2011/11/5 Fran=E7ois-Xavier Le Bail=
 <fx.lebail@yahoo.com>:=0A>>  Hi,=0A>> =0A>>  The RFC 4443 (Internet Contro=
l Message Protocol (ICMPv6) for the=0A>>  Internet Protocol Version 6 (IPv6=
) Specification) states :=0A>>  (http://tools.ietf.org/html/rfc4443#section=
-4.2)=0A>>  [. . .]=0A>>  "An Echo Reply SHOULD be sent in response to an E=
cho Request message=0A>>  sent to an IPv6 multicast or anycast address.=A0 =
In this case, the=0A>>  source address of the reply MUST be a unicast addre=
ss belonging to=0A>>  the interface on which the Echo Request message was r=
eceived."=0A>> =0A>>  The RFC 4942 (IPv6 Transition/Coexistence Security Co=
nsiderations) states :=0A>>  (http://tools.ietf.org/html/rfc4942#section-2.=
1.6)=0A>>  2.1.6. Anycast Traffic Identification and Security=0A>>  [. . .]=
=0A>>  "To avoid exposing knowledge about the internal structure of the=0A>=
>  network, it is recommended that anycast servers now take advantage of=0A=
>>  the ability to return responses with the anycast address as the=0A>>  s=
ource address if possible."=0A>> =0A>>  Even if it is "must" versus "recomm=
ended", It seems =0A> contradictory=0A>>  for an anycast address.=0A>> =0A>=
>  Please let me know your feedback.=0A>> =0A>>  Thanks,=0A>>  Francois-Xav=
ier Le Bail

From nordmark@acm.org  Tue Nov  8 09:27:19 2011
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E343A21F8B89 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 09:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fDzarRKf5rW8 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 09:27:19 -0800 (PST)
Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by ietfa.amsl.com (Postfix) with ESMTP id 6E2C121F8B73 for <ipv6@ietf.org>; Tue,  8 Nov 2011 09:27:19 -0800 (PST)
Received: from [10.35.71.7] (128-107-239-233.cisco.com [128.107.239.233]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id pA8HRHQt016294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Nov 2011 09:27:17 -0800
Message-ID: <4EB96677.8080605@acm.org>
Date: Tue, 08 Nov 2011 09:27:19 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: IETF IPv6 <ipv6@ietf.org>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
References: <4EB95DE2.4070306@sonic.net>
In-Reply-To: <4EB95DE2.4070306@sonic.net>
X-Forwarded-Message-Id: <4EB95DE2.4070306@sonic.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2011 17:27:20 -0000

[This time it should make it to the list]

-------- Original Message --------
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Date: Tue, 08 Nov 2011 08:50:42 -0800
From: Erik Nordmark <nordmark@sonic.net>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
CC: Erik Nordmark <nordmark@acm.org>, Glen Turner <gdt@gdt.id.au>, 
   6man Mailing List <ipv6@ietf.org>,        Brian Haberman 
<brian@innovationslab.net>,        Bob Hinden <bob.hinden@gmail.com>

On 11/6/11 5:24 PM, Suresh Krishnan wrote:

>>> Will do. Would a simple statement e.g. that it is a null terminated
>>> text string be sufficient or did you want more details?
>>
>> Or should we refer to the corresponding DHCPv4 relay option?
>> I think the simple case is when operators reuse the syntax
>> they use for line identification with DHCPv4. But I haven't
>> look at exactly how that DHCP option is specified.
>
> The corresponding DHCPv4 relay option (defined in RFC3046) and the
> corresponding DHCPv6 relay option (defined in RFC4649) are both
> defined as opaque with no character set information. That is what
> makes definition more difficult.

I guess I don't understand why we would want to constrain it any more
than the DHCP relay options.
It would be helpful to put a sentence in section 7 providing the
motivation for it being just an opaque byte string. Something like
	The Line Identification is an opaque sequence of "Option Length"
	number of bytes (with no NULL termination etc). That matches
	the lack of constraints on the corresponding DHCPv4 and DHCPv6
	relay options.

    Erik


From nordmark@sonic.net  Tue Nov  8 09:07:59 2011
Return-Path: <nordmark@sonic.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD7721F8562 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 09:07:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOIV1T5fyQAi for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 09:07:58 -0800 (PST)
Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by ietfa.amsl.com (Postfix) with ESMTP id 89AE421F84BC for <ipv6@ietf.org>; Tue,  8 Nov 2011 09:07:58 -0800 (PST)
Received: from [10.35.71.7] (128-107-239-233.cisco.com [128.107.239.233]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id pA8H7iC7016469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Nov 2011 09:07:45 -0800
Message-ID: <4EB95DE2.4070306@sonic.net>
Date: Tue, 08 Nov 2011 08:50:42 -0800
From: Erik Nordmark <nordmark@sonic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com> <1320358729.3032.24.camel@ilion> <4EB53BCD.3090004@ericsson.com> <4EB5AB4D.4050102@acm.org> <4FD1E7CD248BF84F86BD4814EDDDBCC15142B1959E@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <4FD1E7CD248BF84F86BD4814EDDDBCC15142B1959E@EUSAACMS0703.eamcs.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 08 Nov 2011 11:49:04 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, Erik Nordmark <nordmark@acm.org>, Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2011 17:07:59 -0000

On 11/6/11 5:24 PM, Suresh Krishnan wrote:

>>> Will do. Would a simple statement e.g. that it is a null terminated
>>> text string be sufficient or did you want more details?
>>
>> Or should we refer to the corresponding DHCPv4 relay option?
>> I think the simple case is when operators reuse the syntax
>> they use for line identification with DHCPv4. But I haven't
>> look at exactly how that DHCP option is specified.
>
> The corresponding DHCPv4 relay option (defined in RFC3046) and the
> corresponding DHCPv6 relay option (defined in RFC4649) are both
> defined as opaque with no character set information. That is what
> makes definition more difficult.

I guess I don't understand why we would want to constrain it any more 
than the DHCP relay options.
It would be helpful to put a sentence in section 7 providing the 
motivation for it being just an opaque byte string. Something like
	The Line Identification is an opaque sequence of "Option Length"
	number of bytes (with no NULL termination etc). That matches
	the lack of constraints on the corresponding DHCPv4 and DHCPv6
	relay options.

    Erik

From gorry@erg.abdn.ac.uk  Tue Nov  8 10:07:10 2011
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4ABF21F8B11 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 10:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level: 
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pLXLE9D-RNQ2 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 10:07:10 -0800 (PST)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by ietfa.amsl.com (Postfix) with ESMTP id F3BCF21F84A1 for <6man@ietf.org>; Tue,  8 Nov 2011 10:07:06 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id pA8I71Wi013049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 8 Nov 2011 18:07:02 GMT
Message-ID: <4EB96FC6.5030003@erg.abdn.ac.uk>
Date: Tue, 08 Nov 2011 18:07:02 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: 6man@ietf.org
Subject: Some thoughts on draft-ietf-6man-udpchecksums-01
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-Mailman-Approved-At: Tue, 08 Nov 2011 11:49:04 -0800
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2011 18:07:10 -0000

Marshall, and others,

I've now read the new draft:
http://tools.ietf.org/html/draft-ietf-6man-udpchecksums-01

This looks much more like what I expected, thanks.

I've got some concerns with the following para in Section 5:

       Whenever originating a UDP packet, an IPv6 node SHOULD compute a
                                                       ^^^^^^ - (1)
       UDP checksum over the packet and the pseudo-header, and, if that
       computation yields a result of zero, it must be changed to hex
       FFFF for placement in the UDP header.  IPv6 receivers SHOULD
                                                             ^^^^^^ - (1)
       discard UDP packets containing a zero checksum, and SHOULD log the
       error.  However, some protocols, such as lightweight tunneling
       protocols that use UDP as a tunnel encapsulation, MAY omit
       computing the UDP checksum of the encapsulating UDP header and set
       it to zero, subject to the constraints described in
       [I-D.ietf-6man-udpzero].  In cases where the encapsulating
       protocol uses a zero checksum for UDP, the receiver of packets
       sent to a port enabled to receive zero-checksum packets MUST NOT
                                                               ^^^^^^^^ (2)
       discard packets solely for having a UDP checksum of zero.  Note
       that these constraints apply only to encapsulating protocols that
       omit calculating the UDP checksum and set it to zero.  An
       encapsulating protocol can always choose to compute the UDP
       checksum, in which case, its behavior should be as specified
       originally.
       ^^^^^^^^^^ - (3)

(1), I think they MUST do this unless the receiver has been explicitly
enabled to process zero checksums for a particular port.

I think this sentence could be misleading, in that it can be quoted out 
of context easily, better to say MUST unless the update specified later 
is used. After all, the update proposed is

(2) I don't think this is a requirement you can easily place as an update
to RFC 2460.

(3) I think this means the method defined in RFC 2460.

In addition, I do think we should clearly recommend the use of checksums 
when there are not specific reasons for disabling them.



I also see one minor NiT:

- The abstract should mention RFC 2460 in words, but not cite it as a
reference.

---

I look forward to your thoughts on this,

best wishes,

Gorry



From samita.chakrabarti@ericsson.com  Tue Nov  8 12:07:39 2011
Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 342A811E810B for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 12:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.939
X-Spam-Level: 
X-Spam-Status: No, score=-6.939 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qYxwQlQiDXR for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 12:07:38 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9C75911E80F6 for <ipv6@ietf.org>; Tue,  8 Nov 2011 12:07:38 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pA8K7bgi028142 for <ipv6@ietf.org>; Tue, 8 Nov 2011 14:07:38 -0600
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.18]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 8 Nov 2011 15:07:31 -0500
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Date: Tue, 8 Nov 2011 15:07:31 -0500
Subject: draft-chakrabarti-nordmark-energy-aware-nd-01.txt Published
Thread-Topic: draft-chakrabarti-nordmark-energy-aware-nd-01.txt Published
Thread-Index: AcyYGMVfoOfEHjihTVqopWAphXF+kAGOJj2A
Message-ID: <16D60F43CA0B724F8052D7E9323565D724413F3627@EUSAACMS0715.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2011 20:07:39 -0000

=20
Here is the revised version of the energy-aware-nd draft. The draft incorpo=
rates the comments from ipv6 working group at IETF81.

Comments are welcome.
-Samita
-----------------------------------



A URL for this Internet-Draft is:
 http://www.ietf.org/internet-drafts/draft-chakrabarti-nordmark-energy-awar=
e-nd-01.txt=20


Abstract:
   IPv6 Neighbor Discovery (RFC 4861) protocol has been designed for
   neighbor&#39;s address resolution, unreachability detection, address
   autoconfiguration, router advertisement and solicitation.  With the
   progress of Internet adoption on various industries including home,
   wireless and machine-to-machine communications, there is a desire for
   optimizing legacy IPv6 Neighbor Discovery protocol for energy-
   efficient networks and nodes.  Research indicates that often
   networked- nodes require more energy than stand-alone nodes because a
   node&#39;s energy usage depends on network messages it receives and
   responds.  While reducing energy consumption is essential for battery
   operated nodes in some machines, saving energy actually a cost factor
   in business in general as the explosion of more device usage is
   leading to usage of more servers and network infrastructure in all
   sectors of the society and business.  This document describes a
   method of optimizations by reducing periodic multicast messages,
   frequent Neighbor Solicitation messages and discusses
   interoperability with legacy IPv6 nodes.  This document also
   addresses the ND denial of service issues by introducing node
   Registration procedure.

                                                                           =
      =20




From a@arifumi.net  Tue Nov  8 15:56:15 2011
Return-Path: <a@arifumi.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F164411E8086 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 15:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6qz63Fes3Uc for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 15:56:14 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id D58BA11E8081 for <ipv6@ietf.org>; Tue,  8 Nov 2011 15:56:13 -0800 (PST)
Received: by faas12 with SMTP id s12so1336008faa.31 for <ipv6@ietf.org>; Tue, 08 Nov 2011 15:56:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.62.209 with SMTP id y17mr650306fah.7.1320796572884; Tue, 08 Nov 2011 15:56:12 -0800 (PST)
Received: by 10.223.71.205 with HTTP; Tue, 8 Nov 2011 15:56:12 -0800 (PST)
X-Originating-IP: [118.21.146.144]
In-Reply-To: <1320658117.39943.YahooMailNeo@web126007.mail.ne1.yahoo.com>
References: <20111031235203.11203.64958.idtracker@ietfa.amsl.com> <1320658117.39943.YahooMailNeo@web126007.mail.ne1.yahoo.com>
Date: Wed, 9 Nov 2011 08:56:12 +0900
Message-ID: <CAFtBC=-NW+up20rD8qPqpRrL9aGV-qg5cao9HYGhoYyf2+2buA@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-rfc3484-revise-05.txt
From: Arifumi Matsumoto <a@arifumi.net>
To: =?ISO-8859-1?Q?Fran=E7ois=2DXavier_Le_Bail?= <fx.lebail@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2011 23:56:15 -0000

Hi,

Thanks for your suggestion.

, and also we should also mention about Reserved IPv6 Subnet Anycast Addres=
ses ?
http://tools.ietf.org/html/rfc2526

2011/11/7 Fran=E7ois-Xavier Le Bail <fx.lebail@yahoo.com>:
>
> Hi,
>
> The draft has taken into account anycast addresses.
> http://tools.ietf.org/html/draft-ietf-6man-rfc3484-revise-05#section-2.6
>
> It remains to handle the special case of Subnet-Router anycast address.
> (http://tools.ietf.org/html/rfc4291#section-2.6.1)
> "The Subnet-Router anycast address is intended to be used for
> applications where a node needs to communicate with any one of the
> set of routers."
>
> So, I think a SRaa must be excluded from the candidate set of source addr=
ess
> for a new communication.
> The SRaa as source address must be reserved for a reply to a packet sent =
to this SRaa.
>
> Text proposal (to add section 2.6) :
> "As an exception, a Subnet-Router anycast address MUST NOT be included in=
 the
> candidate set of source address when initiating communication.
> The Subnet-Router anycast address as source address MUST be used in a
> reply to a packet sent to this Subnet-Router anycast address".
>
> Thanks,
> Fran=E7ois-Xavier
>
>
> ----- Original Message -----
>> From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>> To: i-d-announce@ietf.org
>> Cc: ipv6@ietf.org
>> Sent: Tuesday, November 1, 2011 12:52 AM
>> Subject: I-D Action: draft-ietf-6man-rfc3484-revise-05.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
>> This draft is a work item of the IPv6 Maintenance Working Group of the I=
ETF.
>>
>> =A0=A0=A0 Title=A0 =A0 =A0 =A0 =A0 =A0: Update to RFC 3484 Default Addre=
ss Selection for IPv6
>> =A0=A0=A0 Author(s)=A0 =A0 =A0 =A0: Arifumi Matsumoto
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Jun-ya Kato
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Tomohiro Fujisaki
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Tim Chown
>> =A0=A0=A0 Filename=A0 =A0 =A0 =A0 : draft-ietf-6man-rfc3484-revise-05.tx=
t
>> =A0=A0=A0 Pages=A0 =A0 =A0 =A0 =A0 =A0: 12
>> =A0=A0=A0 Date=A0 =A0 =A0 =A0 =A0 =A0 : 2011-10-31
>>
>> =A0 =A0RFC 3484 describes algorithms for source address selection and fo=
r
>> =A0 =A0destination address selection.=A0 The algorithms specify default
>> =A0 =A0behavior for all Internet Protocol version 6 (IPv6) implementatio=
ns.
>> =A0 =A0This document specifies a set of updates that modify the algorith=
ms
>> =A0 =A0and fix the known defects.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-6man-rfc3484-revise-05.tx=
t
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-rfc3484-revise-05.txt
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

From brian.e.carpenter@gmail.com  Tue Nov  8 17:11:03 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5A2F21F84F5 for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 17:11:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.485
X-Spam-Level: 
X-Spam-Status: No, score=-103.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1vXWu3qn5vjq for <ipv6@ietfa.amsl.com>; Tue,  8 Nov 2011 17:11:03 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 44DAB21F84ED for <ipv6@ietf.org>; Tue,  8 Nov 2011 17:11:03 -0800 (PST)
Received: by vws5 with SMTP id 5so1212645vws.31 for <ipv6@ietf.org>; Tue, 08 Nov 2011 17:11:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=OjjBgyh8SMdIk2qbzCtpOFfbXzPDTh3K8XA6TlH5+N8=; b=b2Kv+Pf+8RM1BZkqRuzu/bxuP7JQRYHt48M1IEqD0pJs6eXMRLJHRTuzMgMZZn8GjK UG2ZdzxxuaymncCPa687JBJ1xtRGEIoFa0wxfz6ZdTjL0wcFGphF6hp1wIyRMQQJ/nbT aKRm+j4oeeN6+zmcytRHZdtr30gUqGsBPials=
Received: by 10.52.27.236 with SMTP id w12mr437184vdg.63.1320801061669; Tue, 08 Nov 2011 17:11:01 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id eu4sm4998873vdc.8.2011.11.08.17.10.59 (version=SSLv3 cipher=OTHER); Tue, 08 Nov 2011 17:11:00 -0800 (PST)
Message-ID: <4EB9D332.1040003@gmail.com>
Date: Wed, 09 Nov 2011 14:11:14 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2011 01:11:03 -0000

Hi,

I think I'm going to make myself unpopular.

Reading this document as a proposed standard, I think it will confuse the reader.
I think that what we actually need is a 100% replacement of RFC 3484, that
can be read on its own.

(We've been here before - the same argument is why we ended up doing 3697bis.)

If that is not done, I would suggest reorganising the text so that (after
a short Introduction) the reader finds:

- firstly, a complete but concise statement of the normative changes made to 3484
  (such as section 2.1.5, and the new rules 5.1 and 9)

- secondly, the explanations (such as sections 2.1.1-2.1.4).

An implementer would only need to read the first part.

Trivia:

Needs a header: Updates: 3484 (if approved)

> 4.  IANA Considerations
> 
>    Address type number for the policy table may have to be assigned by
>    IANA.

You can't say "may", you have to tell IANA exactly what to do in which registry.

   Brian


From fx.lebail@yahoo.com  Thu Nov 10 05:59:31 2011
Return-Path: <fx.lebail@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 202E421F8AF4 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 05:59:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.455
X-Spam-Level: 
X-Spam-Status: No, score=-0.455 tagged_above=-999 required=5 tests=[AWL=0.356,  BAYES_05=-1.11, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fd4QunPgZUMV for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 05:59:30 -0800 (PST)
Received: from nm14-vm3.bullet.mail.ne1.yahoo.com (nm14-vm3.bullet.mail.ne1.yahoo.com [98.138.91.144]) by ietfa.amsl.com (Postfix) with SMTP id 5C62821F8AF2 for <ipv6@ietf.org>; Thu, 10 Nov 2011 05:59:30 -0800 (PST)
Received: from [98.138.90.57] by nm14.bullet.mail.ne1.yahoo.com with NNFMP; 10 Nov 2011 13:59:29 -0000
Received: from [98.138.89.232] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 10 Nov 2011 13:59:29 -0000
Received: from [127.0.0.1] by omp1047.mail.ne1.yahoo.com with NNFMP; 10 Nov 2011 13:59:29 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 854048.87806.bm@omp1047.mail.ne1.yahoo.com
Received: (qmail 75422 invoked by uid 60001); 10 Nov 2011 13:59:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1320933569; bh=nut/yVxg3vNRGysmPihhIg/gM4SQGLucri1OErHF0EY=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=QftL+Y0KS0bDMgvfKOjcBudbb74Aqowprx3LODrESFhqXmLpKbf11NC6KPh24uKDvp9ZMbi4IwXNAzGxdAhmFrtaUz+onNYX03GICzYP4l2pJrkWuPp1r/HiXAzD4cXCRnePW7W0WicTWnmefXjDF2M4/KgbsmSvo6MRG2iEJmI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=u6J4msmWtpxqe/v3qEeP8PqHmtH80F7MMxg0fTRos7gqWmww2O/5HOJ8337k4vAlmZtgbdAJPvqX6FH8c1S2XOf/H6ojfZWWda6qeJyrY1r2JfIMpJ3Nigoc7i4BVzpdki/c73oXCV/blplNz9aQSKas3/vOWUmMzNH59XPtJ78=;
X-YMail-OSG: oWXvAQ4VM1mat62TMqAuk.5jQmjyhvLrebotOG2lvOHaxMp UIlCcrdXsx0MjX4Bv33wmWLEvhFv.vG3Q_QRb6SYfx_3CuyKvPtZ.N41Pt8C lXheadse8UDNPreLBX71JoF9G2YbSiYevsjXDt1Id3UhT4bVyacr8y4FUD9R h81zRxNBycBAhRBdlyqggupmPnXV6t5ik2lawMJAriEgvgs3ekP_2H0FmC3m ykQyVbuHLki6KYaxNbQFnl8BACSzjKVlPMHlOzQGM_ZqHKvx1FjbqhxTye.L 7.B71HxSvSKQM1X2gS6LEtUmk6ded7._Z0boBbO_AkKGtSDnVWAzrDF_25l0 AmtAIURdtjQGb6_iQ6Vxmno_8o5L0MdkL4uHLvdz5Fp8RMVd1qrz09yUaaUf 52ZOJpnkhMgqI0HRtZNmnlixBZYGpBSDg.nrG1jTNeOkEFJnOnNXRad8uTVX spkD0_x57
Received: from [193.49.124.107] by web126003.mail.ne1.yahoo.com via HTTP; Thu, 10 Nov 2011 05:59:29 PST
X-Mailer: YahooMailWebService/0.8.115.325013
References: <20111031235203.11203.64958.idtracker@ietfa.amsl.com> <1320658117.39943.YahooMailNeo@web126007.mail.ne1.yahoo.com> <CAFtBC=-NW+up20rD8qPqpRrL9aGV-qg5cao9HYGhoYyf2+2buA@mail.gmail.com>
Message-ID: <1320933569.67232.YahooMailNeo@web126003.mail.ne1.yahoo.com>
Date: Thu, 10 Nov 2011 05:59:29 -0800 (PST)
From: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
Subject: Re: I-D Action: draft-ietf-6man-rfc3484-revise-05.txt
To: Arifumi Matsumoto <a@arifumi.net>
In-Reply-To: <CAFtBC=-NW+up20rD8qPqpRrL9aGV-qg5cao9HYGhoYyf2+2buA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 13:59:31 -0000

----- Original Message -----=0A=0A> From: Arifumi Matsumoto <a@arifumi.net>=
=0A> To: Fran=E7ois-Xavier Le Bail <fx.lebail@yahoo.com>=0A> Cc: "ipv6@ietf=
.org" <ipv6@ietf.org>=0A> Sent: Wednesday, November 9, 2011 12:56 AM=0A> Su=
bject: Re: I-D Action: draft-ietf-6man-rfc3484-revise-05.txt=0A> =0A> Hi,=
=0A> =0A> Thanks for your suggestion.=0A> =0A> , and also we should also me=
ntion about Reserved IPv6 Subnet Anycast Addresses ?=0A> http://tools.ietf.=
org/html/rfc2526=0A=0AHi,=0A=0AI had a look at RFC 2526.=0A=0AIt's seems it=
's the same case than SRaa, but I have no practical experience with such a =
reserved subnet anycast address.=0A=0Ahas someone an experience with these =
?=0A=0AFran=E7ois-Xavier=0A=0A> =0A> 2011/11/7 Fran=E7ois-Xavier Le Bail <f=
x.lebail@yahoo.com>:=0A>> =0A>>  Hi,=0A>> =0A>>  The draft has taken into a=
ccount anycast addresses.=0A>>  http://tools.ietf.org/html/draft-ietf-6man-=
rfc3484-revise-05#section-2.6=0A>> =0A>>  It remains to handle the special =
case of Subnet-Router anycast address.=0A>>  (http://tools.ietf.org/html/rf=
c4291#section-2.6.1)=0A>>  "The Subnet-Router anycast address is intended t=
o be used for=0A>>  applications where a node needs to communicate with any=
 one of the=0A>>  set of routers."=0A>> =0A>>  So, I think a SRaa must be e=
xcluded from the candidate set of source =0A> address=0A>>  for a new commu=
nication.=0A>>  The SRaa as source address must be reserved for a reply to =
a packet sent to =0A> this SRaa.=0A>> =0A>>  Text proposal (to add section =
2.6) :=0A>>  "As an exception, a Subnet-Router anycast address MUST NOT be =
included =0A> in the=0A>>  candidate set of source address when initiating =
communication.=0A>>  The Subnet-Router anycast address as source address MU=
ST be used in a=0A>>  reply to a packet sent to this Subnet-Router anycast =
address".=0A>> =0A>>  Thanks,=0A>>  Fran=E7ois-Xavier=0A>> =0A>> =0A>>  ---=
-- Original Message -----=0A>>>  From: "internet-drafts@ietf.org" =0A> <int=
ernet-drafts@ietf.org>=0A>>>  To: i-d-announce@ietf.org=0A>>>  Cc: ipv6@iet=
f.org=0A>>>  Sent: Tuesday, November 1, 2011 12:52 AM=0A>>>  Subject: I-D A=
ction: draft-ietf-6man-rfc3484-revise-05.txt=0A>>> =0A>>>  A New Internet-D=
raft is available from the on-line Internet-Drafts =0A> directories.=0A>>> =
 This draft is a work item of the IPv6 Maintenance Working Group of the =0A=
> IETF.=0A>>> =0A>>>  =A0=A0=A0 Title=A0 =A0 =A0 =A0 =A0 =A0: Update to RFC=
 3484 Default Address Selection for =0A> IPv6=0A>>>  =A0=A0=A0 Author(s)=A0=
 =A0 =A0 =A0: Arifumi Matsumoto=0A>>>  =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 Jun-ya Kato=0A>>>  =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 Tomohiro Fujisaki=0A>>>  =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 Tim Chown=0A>>>  =A0=A0=A0 Filename=A0 =A0 =A0 =A0 : draft-=
ietf-6man-rfc3484-revise-05.txt=0A>>>  =A0=A0=A0 Pages=A0 =A0 =A0 =A0 =A0 =
=A0: 12=0A>>>  =A0=A0=A0 Date=A0 =A0 =A0 =A0 =A0 =A0 : 2011-10-31=0A>>> =0A=
>>>  =A0 =A0RFC 3484 describes algorithms for source address selection and =
for=0A>>>  =A0 =A0destination address selection.=A0 The algorithms specify =
default=0A>>>  =A0 =A0behavior for all Internet Protocol version 6 (IPv6) i=
mplementations.=0A>>>  =A0 =A0This document specifies a set of updates that=
 modify the algorithms=0A>>>  =A0 =A0and fix the known defects.=0A>>> =0A>>=
> =0A>>>  A URL for this Internet-Draft is:=0A>>> =0A> http://www.ietf.org/=
internet-drafts/draft-ietf-6man-rfc3484-revise-05.txt=0A>>> =0A>>>  Interne=
t-Drafts are also available by anonymous FTP at:=0A>>>  ftp://ftp.ietf.org/=
internet-drafts/=0A>>> =0A>>>  This Internet-Draft can be retrieved at:=0A>=
>> =0A> ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-rfc3484-revise-0=
5.txt=0A>>>  --------------------------------------------------------------=
------=0A>>>  IETF IPv6 working group mailing list=0A>>>  ipv6@ietf.org=0A>=
>>  Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6=0A>=
>>  --------------------------------------------------------------------=0A=
>>> =0A>>  ----------------------------------------------------------------=
----=0A>>  IETF IPv6 working group mailing list=0A>>  ipv6@ietf.org=0A>>  A=
dministrative Requests: https://www.ietf.org/mailman/listinfo/ipv6=0A>>  --=
------------------------------------------------------------------=0A>> =0A=
>

From richard.kelsey@ember.com  Thu Nov 10 08:12:38 2011
Return-Path: <richard.kelsey@ember.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42D2C21F8B46 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 08:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G8ZFHXNZwS02 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 08:12:37 -0800 (PST)
Received: from p01c11o144.mxlogic.net (p01c11o144.mxlogic.net [208.65.144.67]) by ietfa.amsl.com (Postfix) with ESMTP id 9061321F86EE for <ipv6@ietf.org>; Thu, 10 Nov 2011 08:12:37 -0800 (PST)
Received: from unknown [216.236.254.3] (EHLO usmail.ember.com) by p01c11o144.mxlogic.net(mxl_mta-6.11.0-7) over TLS secured channel with ESMTP id fe7fbbe4.0.164325.00-353.289281.p01c11o144.mxlogic.net (envelope-from <richard.kelsey@ember.com>);  Thu, 10 Nov 2011 09:12:37 -0700 (MST)
X-MXL-Hash: 4ebbf7f52711881b-ed3710ffd78be6d4ce4a91f93a3a94c179a5eaf6
Received: from kelsey-ws.hq.ember.com (192.168.81.75) by usmail.ember.com (192.168.80.105) with Microsoft SMTP Server id 14.1.339.1; Thu, 10 Nov 2011 11:12:30 -0500
Date: Thu, 10 Nov 2011 11:14:29 -0500
Message-ID: <871utg9cpm.fsf@kelsey-ws.hq.ember.com>
To: <ipv6@ietf.org>
Subject: draft-ietf-6man-rpl-option questions
From: Richard Kelsey <richard.kelsey@ember.com>
MIME-Version: 1.0
Content-Type: text/plain
X-Originating-IP: [192.168.81.75]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <richard.kelsey@ember.com>
X-SOURCE-IP: [216.236.254.3]
X-AnalysisOut: [v=1.0 c=1 a=u0NvnAFnSA0A:10 a=4E5hXdYBtGMA:10 a=saA6nF2ZJa]
X-AnalysisOut: [AA:10 a=BLceEmwcHowA:10 a=MYqPJgym4Kx47q1P90kooQ==:17 a=5J]
X-AnalysisOut: [yROKRownvvOvnY_GgA:9 a=-hS6lM7cABEO1nTxVfYA:7]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 16:12:38 -0000

In section 4, "Router Behavior" draft-ietf-6man-rpl-option
says:

   Routers MUST use IPv6-in-IPv6 tunneling, as specified in
   [RFC2473] to include a new RPL Option in datagrams that
   are sourced by other nodes.

What destination should be used for the tunnel header?  The
router adding the RPL option may not know if the original
destination is inside or outside the RPL domain.  And if the
original destination is outside the RPL domain, the router
may not know the address of the border router that will
forward the datagram outside.

Also, there are normative statements which use the term "RPL
domain", such as

   Datagrams sent between nodes within a RPL domain MUST include
   a RPL Option or RPL Source Route Header (SRH) and MAY include
   both.

but "RPL domain" is not defined.  In particular, if a RPL
router has a non-RPL-aware host, is the host inside the RPL
domain?  Or is the router then a border router and messages
to the host need to be tunnelled to it?

                                    -Richard Kelsey

From bob.hinden@gmail.com  Thu Nov 10 08:37:23 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6CD321F8B2D for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 08:37:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.048
X-Spam-Level: 
X-Spam-Status: No, score=-103.048 tagged_above=-999 required=5 tests=[AWL=0.551, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GbuxHdnHpGc5 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 08:37:23 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 415C021F8B16 for <ipv6@ietf.org>; Thu, 10 Nov 2011 08:37:23 -0800 (PST)
Received: by ggnr4 with SMTP id r4so1904192ggn.31 for <ipv6@ietf.org>; Thu, 10 Nov 2011 08:37:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=CNo6JikxWBCkU22e+3RG+vTjoJOqYRmrA97Rt5yB9k0=; b=WFf3/ZfQw9nOqbt9Xx/hWs432aR+LG6b2Gd60UA/uodZ/fmnAIk1B+z30NkcbWgxBC a736oJIWt9J2xvEDPTyzUXGjopYMGBfk4pXPu6Kl55VZo+NgUMukMPKB9Bl2gi7aswFw Pq/jyVqxbyHrGL6jVXSwOiG0lyXqHhnsyu7ug=
Received: by 10.68.7.9 with SMTP id f9mr4235991pba.47.1320943042490; Thu, 10 Nov 2011 08:37:22 -0800 (PST)
Received: from [10.0.0.25] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id lk8sm22667846pbb.4.2011.11.10.08.37.21 (version=SSLv3 cipher=OTHER); Thu, 10 Nov 2011 08:37:21 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Need minute taker and Jabber scribe
Date: Thu, 10 Nov 2011 08:37:19 -0800
Message-Id: <343ECB43-DF0D-409A-81CD-6B4302A646C1@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 16:37:23 -0000

Hi,

We still need a minute taker and jabber scribe for the 6man session in =
Taipei.

Thanks,
Bob



From bob.hinden@gmail.com  Thu Nov 10 09:00:18 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 672F221F8B5C for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 09:00:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.061
X-Spam-Level: 
X-Spam-Status: No, score=-103.061 tagged_above=-999 required=5 tests=[AWL=0.538, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id duYoZfmazHiR for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 09:00:17 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 74A1D21F8B5E for <ipv6@ietf.org>; Thu, 10 Nov 2011 09:00:16 -0800 (PST)
Received: by eyg24 with SMTP id 24so3030592eyg.31 for <ipv6@ietf.org>; Thu, 10 Nov 2011 09:00:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=A1Qqyhk+1vxgBbcD7LPhDWR86jHNhe11jsWrHYnIj4g=; b=fYY8WWK4LTDQL2T3xNslPz8IXZsvfAWeLZzKWCbYuQKvKzZbVoofdqg8GzqPSxpt0v 24dW1sCzPaHXSxfyXcBzMcyRZBGiVCOBWibOiIcSUGsxvayKtLvtvwJCjcRmceeuhdN3 JUhddUhkYaNpK88ELjWJ2cdmgiovWK+7/YrhU=
Received: by 10.68.7.132 with SMTP id j4mr16518481pba.11.1320944414690; Thu, 10 Nov 2011 09:00:14 -0800 (PST)
Received: from [10.0.0.25] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id p10sm22759220pbd.15.2011.11.10.09.00.12 (version=SSLv3 cipher=OTHER); Thu, 10 Nov 2011 09:00:13 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Working Group last call for adding RFC6437 Flow Label support to Node Requirements bis document
From: Bob Hinden <bob.hinden@gmail.com>
Date: Thu, 10 Nov 2011 09:00:10 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
To: 6man Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 17:00:18 -0000

This email starts a one week 6MAN Working Group last call for adding =
text and a reference to RFC6437 "IPv6 Flow Label Specification" to the =
Node Requirements bis document current in AUTH48 state.  The document is =
currently on hold in the RFC Editor waiting for resolution of this =
issue. =20

The proposed text, first sent to the ipv6@ietf.org mailing list on =
November 2, 2011 (included below), is:

> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,=20
> defines the IPv6 Flow Label.  Specifically:
>=20
>    "Forwarding nodes such as routers and load distributors MUST NOT
>     depend only on Flow Label values being uniformly distributed. "
>=20
>    "It is therefore RECOMMENDED  that source hosts support the flow=20
>     label by setting the flow label field for all packets of a given =
flow to the=20
>     same value chosen from an approximation to a discrete uniform =
distribution. "

The chairs have discussed this with the Internet Area Directors and they =
recommended this course of action.  This topic is also on the agenda for =
the 6man session at the Taipei IETF.

Substantive comments and statements of support for taking this action =
should be sent to the mailing list.  This last call will end on November =
17, 2011.

Regards,
Bob Hinden & Brian Haberman


Begin forwarded message:

> From: <john.loughney@nokia.com>
> Date: November 2, 2011 7:50:35 PM PDT
> To: <ipv6@ietf.org>
> Subject: Flow Label support in the Node Requirements bis document
>=20
> Hi all,
>=20
> There has been some discussions whether or not we should add support =
for the Flow Label in
> Soon to be RFC 6434 <draft-ietf-6man-node-req-bis-11.txt> As a straw =
man proposal, if we add
> Support, I would suggest the following text:
>=20
> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,=20
> defines the IPv6 Flow Label.  Specifically:
>=20
>    "Forwarding nodes such as routers and load distributors MUST NOT
>      depend only on Flow Label values being uniformly distributed. "
>=20
>    "It is therefore RECOMMENDED  that source hosts support the flow=20
>      label by setting the flow label field for all packets of a given =
flow to the=20
>      same value chosen from  an approximation to a discrete uniform =
distribution. "
>=20
> I'd like to ask the wg the following:
>=20
> 1) Is the above text acceptable?
> 2) Do you support adding the text? If no, please suggest text, unless =
you do not support adding
>     Flow label support at all (please say so).
>=20
> John
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From jonhui@cisco.com  Thu Nov 10 09:03:00 2011
Return-Path: <jonhui@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5236721F8B42 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 09:03:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktDCBr0iUSC9 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 09:02:59 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 50C7C21F85AA for <ipv6@ietf.org>; Thu, 10 Nov 2011 09:02:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=4725; q=dns/txt; s=iport; t=1320944579; x=1322154179; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=OmM1HrdBntGoUIjb1sJGNmhm1z5L2niMSaE3JZHz8e4=; b=GKNAme5J3hfM/gVyiTy9MzUokpUR8SpnauFi51U1NdmV7K4YUkbaURCs 7e/WKJkva6kPemAm1vePOG6d0sJa0uYJ2G+Ed+vO2GNZdoOnYdKn8ICyS kOAVegIIJ1dZ62o8pNfWyJWS80JQyb/wS+OmVsnQo+2zY++7ad/dTLHLf E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPECvE6rRDoJ/2dsb2JhbABEqieBBYFyAQEBAwESASc/BQsLRlcGNYdgmWMBnmGJG2MEiA+MGZIW
X-IronPort-AV: E=Sophos;i="4.69,489,1315180800"; d="scan'208";a="13460352"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 10 Nov 2011 17:02:59 +0000
Received: from dhcp-128-107-155-203.cisco.com (dhcp-128-107-155-203.cisco.com [128.107.155.203]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAAH2wIO000516; Thu, 10 Nov 2011 17:02:58 GMT
Subject: Re: draft-ietf-6man-rpl-option questions
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <871utg9cpm.fsf@kelsey-ws.hq.ember.com>
Date: Thu, 10 Nov 2011 09:03:01 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <50A9F9C5-8C71-4F5E-B084-A127B7E982F4@cisco.com>
References: <871utg9cpm.fsf@kelsey-ws.hq.ember.com>
To: Richard Kelsey <richard.kelsey@ember.com>
X-Mailer: Apple Mail (2.1084)
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 17:03:00 -0000

Hi Richard,

On Nov 10, 2011, at 8:14 AM, Richard Kelsey wrote:

> In section 4, "Router Behavior" draft-ietf-6man-rpl-option
> says:
>=20
>   Routers MUST use IPv6-in-IPv6 tunneling, as specified in
>   [RFC2473] to include a new RPL Option in datagrams that
>   are sourced by other nodes.
>=20
> What destination should be used for the tunnel header?  The
> router adding the RPL option may not know if the original
> destination is inside or outside the RPL domain.  And if the
> original destination is outside the RPL domain, the router
> may not know the address of the border router that will
> forward the datagram outside.

The tunnel header's destination should be the next RPL router along the =
path towards the destination.  If, for example, a router only knows the =
next-hop destination (i.e. the DODAG Parent), then the tunnel header's =
destination will be the DODAG Parent itself.  Note that the original =
packet may traverse multiple such tunnels within the same RPL domain in =
order to reach its destination.  Let me propose the following update to =
Section 4:

4.  RPL Router Behavior

  To deliver an IPv6 datagram to its destination, a router may need to
  insert a new RPL Option.  Routers MUST use IPv6-in-IPv6 tunneling, as
  specified in [RFC2473] to include a new RPL Option in datagrams that
  are sourced by other nodes.  Using IPv6-in-IPv6 tunneling ensures
  that the delivered datagram remains unmodified and that ICMPv6 errors
  generated by inserting the RPL Option are sent back to the router
  that generated the routing header.

  A RPL router chooses the next RPL router that should process the
  original packet as the tunnel exit-point.  In some cases, the tunnel
  exit-point will be the final RPL router along a path towards the
  original packet's destination and the original packet will only
  traverse a single tunnel.  One example is when the final destination
  or the destination's attachment router is known to be within the same
  RPL domain.

  In other cases, the tunnel exit-point will not be the final RPL
  router along a path and the original packet may traverse multiple
  tunnels to reach the destination.  One example is when a RPL router
  is simply forwarding a packet to one of its DODAG Parents.  In this
  case, the RPL router sets the tunnel exit-point to a DODAG Parent.
  When forwarding the original packet hop-by-hop, the RPL router only
  makes a determination on the next hop towards the destination.

  A RPL router receiving an IPv6-in-IPv6 packet destined to it
  processes the tunnel packet as described in Section 3. of [RFC2473].
  Before IPv6 decapsulation, the RPL router MUST process the RPL Option
  if one exists.  If the router determines that it should forward the
  original packet to another RPL router, it MUST encapsulate the packet
  again using IPv6-in-IPv6 tunneling to include the RPL Option.  Note
  that fields within the RPL Option that do not change hop-by-hop MUST
  remain the same as those received from the prior tunnel.

  To avoid fragmentation, it is desirable to employ MTU sizes that
  allow for the header expansion (i.e. at least 1280 + 40 (outer IP
  header) + RPL_OPTION_MAX_SIZE), where RPL_OPTION_MAX_SIZE is the
  maximum RPL Option header size for a given RPL network.  To take
  advantage of this, however, the communicating endpoints need to be
  aware of the MTU along the path (i.e. through Path MTU Discovery).
  Unfortunately, the larger MTU size may not be available on all links
  (e.g. 1280 octets on 6LoWPAN links).  However, it is expected that
  much of the traffic on these types of networks consists of much
  smaller messages than the MTU, so performance degradation through
  fragmentation would be limited.

> Also, there are normative statements which use the term "RPL
> domain", such as
>=20
>   Datagrams sent between nodes within a RPL domain MUST include
>   a RPL Option or RPL Source Route Header (SRH) and MAY include
>   both.
>=20
> but "RPL domain" is not defined.  In particular, if a RPL
> router has a non-RPL-aware host, is the host inside the RPL
> domain?  Or is the router then a border router and messages
> to the host need to be tunnelled to it?

I agree that "RPL domain" is not well defined.  But after some thought, =
I think replacing with "RPL Instance" may be more appropriate.  In =
particular, we really want to limit the use of these RPL options/headers =
to a RPL Instance, not just a collection of routers that are all =
operating RPL.

If you agree to the above, I'll make the changes in my updates to =
address the LC comments.

Thanks.

--
Jonathan Hui


From marshall.eubanks@gmail.com  Thu Nov 10 09:17:31 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86F1221F8B36 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 09:17:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.478
X-Spam-Level: 
X-Spam-Status: No, score=-103.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63MvaeVwMPBC for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 09:17:31 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id DC73821F8AE6 for <ipv6@ietf.org>; Thu, 10 Nov 2011 09:17:30 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so3102491bkb.31 for <ipv6@ietf.org>; Thu, 10 Nov 2011 09:17:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EALFKpLCpBeK5OyRdtBWHJOXJkY78ivzsL1uAAxrSGY=; b=p01cz7jrzvB6ZBI2/HFc/7QvhVjZ14sRhlQwtVkjAcTjAEfxnXsn0lyBVlCo4sInau DNuILfFs8HixqYa4gCgersQ0oJBuCaQyF7j933q0sqM8iZCJN7FytIWo1TWDUKfWhDuh RofO+1zddlMRl8fgUQO0hZuvfZXxEnMmzIFqc=
MIME-Version: 1.0
Received: by 10.182.115.106 with SMTP id jn10mr2051575obb.54.1320945449722; Thu, 10 Nov 2011 09:17:29 -0800 (PST)
Received: by 10.182.159.73 with HTTP; Thu, 10 Nov 2011 09:17:29 -0800 (PST)
In-Reply-To: <343ECB43-DF0D-409A-81CD-6B4302A646C1@gmail.com>
References: <343ECB43-DF0D-409A-81CD-6B4302A646C1@gmail.com>
Date: Thu, 10 Nov 2011 12:17:29 -0500
Message-ID: <CAJNg7VJohQ2WW=8o9mGyu=3=zVBG6wuh=qR8u+ypV=ONT_vdLA@mail.gmail.com>
Subject: Re: Need minute taker and Jabber scribe
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 17:17:31 -0000

I will be glad to be jabber scribe, except during any presentation I might give

Marshall

On Thu, Nov 10, 2011 at 11:37 AM, Bob Hinden <bob.hinden@gmail.com> wrote:
> Hi,
>
> We still need a minute taker and jabber scribe for the 6man session in Taipei.
>
> Thanks,
> Bob
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

From jreddy@ti.com  Thu Nov 10 10:23:45 2011
Return-Path: <jreddy@ti.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E480D21F8B47 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 10:23:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7TXaT72ua6xz for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 10:23:45 -0800 (PST)
Received: from arroyo.ext.ti.com (arroyo.ext.ti.com [192.94.94.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1FBBA21F8B52 for <ipv6@ietf.org>; Thu, 10 Nov 2011 10:23:44 -0800 (PST)
Received: from dlep33.itg.ti.com ([157.170.170.112]) by arroyo.ext.ti.com (8.13.7/8.13.7) with ESMTP id pAAINeqU023443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ipv6@ietf.org>; Thu, 10 Nov 2011 12:23:40 -0600
Received: from dlep26.itg.ti.com (smtp-le.itg.ti.com [157.170.170.27]) by dlep33.itg.ti.com (8.13.7/8.13.8) with ESMTP id pAAINeeI000009 for <ipv6@ietf.org>; Thu, 10 Nov 2011 12:23:40 -0600 (CST)
Received: from DLEE74.ent.ti.com (localhost [127.0.0.1]) by dlep26.itg.ti.com (8.13.8/8.13.8) with ESMTP id pAAINeWM011039 for <ipv6@ietf.org>; Thu, 10 Nov 2011 12:23:40 -0600 (CST)
Received: from DLEE10.ent.ti.com ([fe80::843:a4aa:bf01:3f68]) by DLEE74.ent.ti.com ([fe80::a0f1:125b:e7e3:7ed8%20]) with mapi id 14.01.0323.003; Thu, 10 Nov 2011 12:23:40 -0600
From: "Reddy, Joseph" <jreddy@ti.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: draft-ietf-6man-rpl-option questions
Thread-Topic: draft-ietf-6man-rpl-option questions
Thread-Index: AQHMn9XeNLkNIIasV0qJj/9ZFtKXqA==
Date: Thu, 10 Nov 2011 18:23:39 +0000
Message-ID: <2AA5AC69E924D149A8D63EB676AF87DBEEBFBC@DLEE10.ent.ti.com>
References: <mailman.3414.1320945452.2955.ipv6@ietf.org>
In-Reply-To: <mailman.3414.1320945452.2955.ipv6@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.170.170.90]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 18:23:46 -0000

Hi Jonathan

Thanks for the clarifiction.=20

In your proposed new text, you state

"...Routers MUST use IPv6-in-IPv6 tunneling, as
  specified in [RFC2473] to include a new RPL Option in datagrams that
  are sourced by other nodes..."

Actually, isnt it true that this action ( use of tunnelling to include the =
RPL option ) is nececssary for all packets, even for those sourced on the r=
outer node itself ?=20
Basically, if the source router is not sure that the destination node is wi=
thin the RPL Instance, it musts use tunnelllig to include the RPL Option.


-Regards, Joseph


------------------------------

Message: 5
Date: Thu, 10 Nov 2011 09:03:01 -0800
From: Jonathan Hui <jonhui@cisco.com>
To: Richard Kelsey <richard.kelsey@ember.com>
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-6man-rpl-option questions
Message-ID: <50A9F9C5-8C71-4F5E-B084-A127B7E982F4@cisco.com>
Content-Type: text/plain; charset=3Dus-ascii


Hi Richard,

On Nov 10, 2011, at 8:14 AM, Richard Kelsey wrote:

> In section 4, "Router Behavior" draft-ietf-6man-rpl-option
> says:
>=20
>   Routers MUST use IPv6-in-IPv6 tunneling, as specified in
>   [RFC2473] to include a new RPL Option in datagrams that
>   are sourced by other nodes.
>=20
> What destination should be used for the tunnel header?  The
> router adding the RPL option may not know if the original
> destination is inside or outside the RPL domain.  And if the
> original destination is outside the RPL domain, the router
> may not know the address of the border router that will
> forward the datagram outside.

The tunnel header's destination should be the next RPL router along the pat=
h towards the destination.  If, for example, a router only knows the next-h=
op destination (i.e. the DODAG Parent), then the tunnel header's destinatio=
n will be the DODAG Parent itself.  Note that the original packet may trave=
rse multiple such tunnels within the same RPL domain in order to reach its =
destination.  Let me propose the following update to Section 4:

4.  RPL Router Behavior

  To deliver an IPv6 datagram to its destination, a router may need to
  insert a new RPL Option.  Routers MUST use IPv6-in-IPv6 tunneling, as
  specified in [RFC2473] to include a new RPL Option in datagrams that
  are sourced by other nodes.  Using IPv6-in-IPv6 tunneling ensures
  that the delivered datagram remains unmodified and that ICMPv6 errors
  generated by inserting the RPL Option are sent back to the router
  that generated the routing header.

  A RPL router chooses the next RPL router that should process the
  original packet as the tunnel exit-point.  In some cases, the tunnel
  exit-point will be the final RPL router along a path towards the
  original packet's destination and the original packet will only
  traverse a single tunnel.  One example is when the final destination
  or the destination's attachment router is known to be within the same
  RPL domain.

  In other cases, the tunnel exit-point will not be the final RPL
  router along a path and the original packet may traverse multiple
  tunnels to reach the destination.  One example is when a RPL router
  is simply forwarding a packet to one of its DODAG Parents.  In this
  case, the RPL router sets the tunnel exit-point to a DODAG Parent.
  When forwarding the original packet hop-by-hop, the RPL router only
  makes a determination on the next hop towards the destination.

  A RPL router receiving an IPv6-in-IPv6 packet destined to it
  processes the tunnel packet as described in Section 3. of [RFC2473].
  Before IPv6 decapsulation, the RPL router MUST process the RPL Option
  if one exists.  If the router determines that it should forward the
  original packet to another RPL router, it MUST encapsulate the packet
  again using IPv6-in-IPv6 tunneling to include the RPL Option.  Note
  that fields within the RPL Option that do not change hop-by-hop MUST
  remain the same as those received from the prior tunnel.

  To avoid fragmentation, it is desirable to employ MTU sizes that
  allow for the header expansion (i.e. at least 1280 + 40 (outer IP
  header) + RPL_OPTION_MAX_SIZE), where RPL_OPTION_MAX_SIZE is the
  maximum RPL Option header size for a given RPL network.  To take
  advantage of this, however, the communicating endpoints need to be
  aware of the MTU along the path (i.e. through Path MTU Discovery).
  Unfortunately, the larger MTU size may not be available on all links
  (e.g. 1280 octets on 6LoWPAN links).  However, it is expected that
  much of the traffic on these types of networks consists of much
  smaller messages than the MTU, so performance degradation through
  fragmentation would be limited.

> Also, there are normative statements which use the term "RPL
> domain", such as
>=20
>   Datagrams sent between nodes within a RPL domain MUST include
>   a RPL Option or RPL Source Route Header (SRH) and MAY include
>   both.
>=20
> but "RPL domain" is not defined.  In particular, if a RPL
> router has a non-RPL-aware host, is the host inside the RPL
> domain?  Or is the router then a border router and messages
> to the host need to be tunnelled to it?

I agree that "RPL domain" is not well defined.  But after some thought, I t=
hink replacing with "RPL Instance" may be more appropriate.  In particular,=
 we really want to limit the use of these RPL options/headers to a RPL Inst=
ance, not just a collection of routers that are all operating RPL.

If you agree to the above, I'll make the changes in my updates to address t=
he LC comments.

Thanks.

--
Jonathan Hui



From bob.hinden@gmail.com  Thu Nov 10 10:43:22 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACCA021F8AEC for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 10:43:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level: 
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l0L0Tnwjw2OB for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 10:43:22 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0A57B21F8B6E for <ipv6@ietf.org>; Thu, 10 Nov 2011 10:43:21 -0800 (PST)
Received: by ywt34 with SMTP id 34so1270393ywt.31 for <ipv6@ietf.org>; Thu, 10 Nov 2011 10:43:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=S6qdb8SBvvrJC99zKpjnQScfzXMoVsg4NML+Vm8LZgM=; b=Oap4ymPS2epDrNVG8qEAI587RBPDoNNAOpEDVYvw1o5PW3pnlb3815oA4iLXGIJioV t0uwDIwoaOiGmn6ccsFzKQ7NaQuy80WUOW7IzSTjLkb251/F160CMwPG3x/G0Hia7EGn SZE5oakySXZPTp2YMtoOZfCYiWsp+iCgxnZZw=
Received: by 10.68.28.3 with SMTP id x3mr16405768pbg.132.1320950596787; Thu, 10 Nov 2011 10:43:16 -0800 (PST)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id lk8sm23403434pbb.4.2011.11.10.10.43.15 (version=SSLv3 cipher=OTHER); Thu, 10 Nov 2011 10:43:16 -0800 (PST)
Subject: Re: Need minute taker and Jabber scribe
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAJNg7VJohQ2WW=8o9mGyu=3=zVBG6wuh=qR8u+ypV=ONT_vdLA@mail.gmail.com>
Date: Thu, 10 Nov 2011 10:43:15 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA6B13A6-2939-4A75-A6FB-1B7A8D4D48B3@gmail.com>
References: <343ECB43-DF0D-409A-81CD-6B4302A646C1@gmail.com> <CAJNg7VJohQ2WW=8o9mGyu=3=zVBG6wuh=qR8u+ypV=ONT_vdLA@mail.gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: 6man Mailing List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 18:43:22 -0000

Marshall,

Thanks very much.

Bob


On Nov 10, 2011, at 9:17 AM, Marshall Eubanks wrote:

> I will be glad to be jabber scribe, except during any presentation I =
might give
>=20
> Marshall
>=20
> On Thu, Nov 10, 2011 at 11:37 AM, Bob Hinden <bob.hinden@gmail.com> =
wrote:
>> Hi,
>>=20
>> We still need a minute taker and jabber scribe for the 6man session =
in Taipei.
>>=20
>> Thanks,
>> Bob
>>=20
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>=20


From jonhui@cisco.com  Thu Nov 10 10:57:33 2011
Return-Path: <jonhui@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64DF421F8484 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 10:57:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9Bzx3pyp2Lp for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 10:57:32 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 87D8A21F84AB for <ipv6@ietf.org>; Thu, 10 Nov 2011 10:57:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=7093; q=dns/txt; s=iport; t=1320951452; x=1322161052; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=s9fERPjE5z1kti2F30lig+S34rSCfg6UF6ogBic6pNI=; b=dBP9CySN/vAALhV27Bpc+4t1W35vStWdpynsi9WsH3A1xvB+sObv8Y07 /F91typasYPm8tIXLKLgdORYCXf9pUKbjJdsmy2c8Flhp4+rglIsVFHxZ RBSNjCM/e0fBMA7nAe02aPqqK5A87/U/S+Yj5BHa4kfzLincBpLlkxNlA 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAGsevE6rRDoJ/2dsb2JhbABEqiyBBYFyAQEBAwEBAQEPASc0CxALEQMBAgEuJygIBhMih2AImTsBnl4EiRtjBIgPjBmSFg
X-IronPort-AV: E=Sophos;i="4.69,489,1315180800"; d="scan'208";a="11916547"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 10 Nov 2011 18:57:32 +0000
Received: from dhcp-128-107-155-203.cisco.com (dhcp-128-107-155-203.cisco.com [128.107.155.203]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAAIvWTM019335; Thu, 10 Nov 2011 18:57:32 GMT
Subject: Re: draft-ietf-6man-rpl-option questions
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <2AA5AC69E924D149A8D63EB676AF87DBEEBFBC@DLEE10.ent.ti.com>
Date: Thu, 10 Nov 2011 10:57:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5CD1C48-84B4-4FDE-9484-7FA500411375@cisco.com>
References: <mailman.3414.1320945452.2955.ipv6@ietf.org> <2AA5AC69E924D149A8D63EB676AF87DBEEBFBC@DLEE10.ent.ti.com>
To: "Reddy, Joseph" <jreddy@ti.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 18:57:33 -0000

Hi Joseph,

It is not actually required to use tunneling if the RPL router knows =
that the destination is within the same RPL Instance.  But if the router =
does not know for sure, then it must use tunneling.  Just after sending =
my proposed text, I had modified the cited portion to the following:

   Datagrams sent between RPL routers MUST include a RPL Option or RPL
   Source Route Header (SRH) and MAY include both.  When the router is
   the source of the original packet and the destination is known to be
   within the same RPL Instance, the router SHOULD include the RPL =
Option
   directly within the original packet.  Otherwise, routers MUST use
   IPv6-in-IPv6 tunneling [RFC2473] to include a new RPL Option in
   datagrams that are sourced by other nodes.

Does this address your concern?

--
Jonathan Hui

On Nov 10, 2011, at 10:23 AM, Reddy, Joseph wrote:

>=20
>=20
> Hi Jonathan
>=20
> Thanks for the clarifiction.=20
>=20
> In your proposed new text, you state
>=20
> "...Routers MUST use IPv6-in-IPv6 tunneling, as
>  specified in [RFC2473] to include a new RPL Option in datagrams that
>  are sourced by other nodes..."
>=20
> Actually, isnt it true that this action ( use of tunnelling to include =
the RPL option ) is nececssary for all packets, even for those sourced =
on the router node itself ?=20
> Basically, if the source router is not sure that the destination node =
is within the RPL Instance, it musts use tunnelllig to include the RPL =
Option.
>=20
>=20
> -Regards, Joseph
>=20
>=20
> ------------------------------
>=20
> Message: 5
> Date: Thu, 10 Nov 2011 09:03:01 -0800
> From: Jonathan Hui <jonhui@cisco.com>
> To: Richard Kelsey <richard.kelsey@ember.com>
> Cc: ipv6@ietf.org
> Subject: Re: draft-ietf-6man-rpl-option questions
> Message-ID: <50A9F9C5-8C71-4F5E-B084-A127B7E982F4@cisco.com>
> Content-Type: text/plain; charset=3Dus-ascii
>=20
>=20
> Hi Richard,
>=20
> On Nov 10, 2011, at 8:14 AM, Richard Kelsey wrote:
>=20
>> In section 4, "Router Behavior" draft-ietf-6man-rpl-option
>> says:
>>=20
>>  Routers MUST use IPv6-in-IPv6 tunneling, as specified in
>>  [RFC2473] to include a new RPL Option in datagrams that
>>  are sourced by other nodes.
>>=20
>> What destination should be used for the tunnel header?  The
>> router adding the RPL option may not know if the original
>> destination is inside or outside the RPL domain.  And if the
>> original destination is outside the RPL domain, the router
>> may not know the address of the border router that will
>> forward the datagram outside.
>=20
> The tunnel header's destination should be the next RPL router along =
the path towards the destination.  If, for example, a router only knows =
the next-hop destination (i.e. the DODAG Parent), then the tunnel =
header's destination will be the DODAG Parent itself.  Note that the =
original packet may traverse multiple such tunnels within the same RPL =
domain in order to reach its destination.  Let me propose the following =
update to Section 4:
>=20
> 4.  RPL Router Behavior
>=20
>  To deliver an IPv6 datagram to its destination, a router may need to
>  insert a new RPL Option.  Routers MUST use IPv6-in-IPv6 tunneling, as
>  specified in [RFC2473] to include a new RPL Option in datagrams that
>  are sourced by other nodes.  Using IPv6-in-IPv6 tunneling ensures
>  that the delivered datagram remains unmodified and that ICMPv6 errors
>  generated by inserting the RPL Option are sent back to the router
>  that generated the routing header.
>=20
>  A RPL router chooses the next RPL router that should process the
>  original packet as the tunnel exit-point.  In some cases, the tunnel
>  exit-point will be the final RPL router along a path towards the
>  original packet's destination and the original packet will only
>  traverse a single tunnel.  One example is when the final destination
>  or the destination's attachment router is known to be within the same
>  RPL domain.
>=20
>  In other cases, the tunnel exit-point will not be the final RPL
>  router along a path and the original packet may traverse multiple
>  tunnels to reach the destination.  One example is when a RPL router
>  is simply forwarding a packet to one of its DODAG Parents.  In this
>  case, the RPL router sets the tunnel exit-point to a DODAG Parent.
>  When forwarding the original packet hop-by-hop, the RPL router only
>  makes a determination on the next hop towards the destination.
>=20
>  A RPL router receiving an IPv6-in-IPv6 packet destined to it
>  processes the tunnel packet as described in Section 3. of [RFC2473].
>  Before IPv6 decapsulation, the RPL router MUST process the RPL Option
>  if one exists.  If the router determines that it should forward the
>  original packet to another RPL router, it MUST encapsulate the packet
>  again using IPv6-in-IPv6 tunneling to include the RPL Option.  Note
>  that fields within the RPL Option that do not change hop-by-hop MUST
>  remain the same as those received from the prior tunnel.
>=20
>  To avoid fragmentation, it is desirable to employ MTU sizes that
>  allow for the header expansion (i.e. at least 1280 + 40 (outer IP
>  header) + RPL_OPTION_MAX_SIZE), where RPL_OPTION_MAX_SIZE is the
>  maximum RPL Option header size for a given RPL network.  To take
>  advantage of this, however, the communicating endpoints need to be
>  aware of the MTU along the path (i.e. through Path MTU Discovery).
>  Unfortunately, the larger MTU size may not be available on all links
>  (e.g. 1280 octets on 6LoWPAN links).  However, it is expected that
>  much of the traffic on these types of networks consists of much
>  smaller messages than the MTU, so performance degradation through
>  fragmentation would be limited.
>=20
>> Also, there are normative statements which use the term "RPL
>> domain", such as
>>=20
>>  Datagrams sent between nodes within a RPL domain MUST include
>>  a RPL Option or RPL Source Route Header (SRH) and MAY include
>>  both.
>>=20
>> but "RPL domain" is not defined.  In particular, if a RPL
>> router has a non-RPL-aware host, is the host inside the RPL
>> domain?  Or is the router then a border router and messages
>> to the host need to be tunnelled to it?
>=20
> I agree that "RPL domain" is not well defined.  But after some =
thought, I think replacing with "RPL Instance" may be more appropriate.  =
In particular, we really want to limit the use of these RPL =
options/headers to a RPL Instance, not just a collection of routers that =
are all operating RPL.
>=20
> If you agree to the above, I'll make the changes in my updates to =
address the LC comments.
>=20
> Thanks.
>=20
> --
> Jonathan Hui
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From brian.e.carpenter@gmail.com  Thu Nov 10 11:53:43 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 497AB21F8B0A for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 11:53:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.478
X-Spam-Level: 
X-Spam-Status: No, score=-103.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DK6w4OU-Rmy for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 11:53:42 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6F89E21F89BA for <ipv6@ietf.org>; Thu, 10 Nov 2011 11:53:42 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so3281913bkb.31 for <ipv6@ietf.org>; Thu, 10 Nov 2011 11:53:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ciQeWTg9ub3cCf5YWdp8/5lcYpp5L6solVEuGPRci4Y=; b=xzE9wHoyizcMfbijFCm3Xfz1+lvwimI0C8y+PIaHLvf0ArOHUwxe0wYt6CvZW8gYSZ 7QAClTQLRJmBktykxDwEuo33cQub7NILf/weQOih8y7I2tI3P7tRXdLKR/fAHtC3fb1O Ho47iQxCHrQtZnXfl5yyu+guyOZDn4iPlXI/w=
Received: by 10.204.7.144 with SMTP id d16mr5867234bkd.70.1320954821439; Thu, 10 Nov 2011 11:53:41 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id m4sm2678330fad.1.2011.11.10.11.53.37 (version=SSLv3 cipher=OTHER); Thu, 10 Nov 2011 11:53:40 -0800 (PST)
Message-ID: <4EBC2BB9.4030308@gmail.com>
Date: Fri, 11 Nov 2011 08:53:29 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Working Group last call for adding RFC6437 Flow Label support to Node Requirements bis document
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com>
In-Reply-To: <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 19:53:43 -0000

I support this change.

Regards
   Brian Carpenter

On 2011-11-11 06:00, Bob Hinden wrote:
> This email starts a one week 6MAN Working Group last call for adding text and a reference to RFC6437 "IPv6 Flow Label Specification" to the Node Requirements bis document current in AUTH48 state.  The document is currently on hold in the RFC Editor waiting for resolution of this issue.  
> 
> The proposed text, first sent to the ipv6@ietf.org mailing list on November 2, 2011 (included below), is:
> 
>> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification, 
>> defines the IPv6 Flow Label.  Specifically:
>>
>>    "Forwarding nodes such as routers and load distributors MUST NOT
>>     depend only on Flow Label values being uniformly distributed. "
>>
>>    "It is therefore RECOMMENDED  that source hosts support the flow 
>>     label by setting the flow label field for all packets of a given flow to the 
>>     same value chosen from an approximation to a discrete uniform distribution. "
> 
> The chairs have discussed this with the Internet Area Directors and they recommended this course of action.  This topic is also on the agenda for the 6man session at the Taipei IETF.
> 
> Substantive comments and statements of support for taking this action should be sent to the mailing list.  This last call will end on November 17, 2011.
> 
> Regards,
> Bob Hinden & Brian Haberman
> 
> 
> Begin forwarded message:
> 
>> From: <john.loughney@nokia.com>
>> Date: November 2, 2011 7:50:35 PM PDT
>> To: <ipv6@ietf.org>
>> Subject: Flow Label support in the Node Requirements bis document
>>
>> Hi all,
>>
>> There has been some discussions whether or not we should add support for the Flow Label in
>> Soon to be RFC 6434 <draft-ietf-6man-node-req-bis-11.txt> As a straw man proposal, if we add
>> Support, I would suggest the following text:
>>
>> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification, 
>> defines the IPv6 Flow Label.  Specifically:
>>
>>    "Forwarding nodes such as routers and load distributors MUST NOT
>>      depend only on Flow Label values being uniformly distributed. "
>>
>>    "It is therefore RECOMMENDED  that source hosts support the flow 
>>      label by setting the flow label field for all packets of a given flow to the 
>>      same value chosen from  an approximation to a discrete uniform distribution. "
>>
>> I'd like to ask the wg the following:
>>
>> 1) Is the above text acceptable?
>> 2) Do you support adding the text? If no, please suggest text, unless you do not support adding
>>     Flow label support at all (please say so).
>>
>> John
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

From brian@innovationslab.net  Thu Nov 10 13:25:50 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CBD221F8A35 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 13:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.932
X-Spam-Level: 
X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OTifc-X7ZTK for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 13:25:49 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 80DF421F8A58 for <ipv6@ietf.org>; Thu, 10 Nov 2011 13:25:49 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 017B788244 for <ipv6@ietf.org>; Thu, 10 Nov 2011 13:25:49 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 9CE391368145 for <ipv6@ietf.org>; Thu, 10 Nov 2011 13:25:48 -0800 (PST)
Message-ID: <4EBC415B.3080701@innovationslab.net>
Date: Thu, 10 Nov 2011 16:25:47 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Flow Label support in the Node Requirements bis document
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
In-Reply-To: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 21:25:50 -0000

I agree that an update should be done prior to publishing the Node 
Requirements draft, but I have some issues with the language (not the 
intent) proposed below...

On 11/2/11 10:50 PM, john.loughney@nokia.com wrote:
> Hi all,
>
> There has been some discussions whether or not we should add support for the Flow Label in
> Soon to be RFC 6434<draft-ietf-6man-node-req-bis-11.txt>  As a straw man proposal, if we add
> Support, I would suggest the following text:
>
> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,
> defines the IPv6 Flow Label.  Specifically:
>
>      "Forwarding nodes such as routers and load distributors MUST NOT
>        depend only on Flow Label values being uniformly distributed. "
>
>      "It is therefore RECOMMENDED  that source hosts support the flow
>        label by setting the flow label field for all packets of a given flow to the
>        same value chosen from  an approximation to a discrete uniform distribution. "

First, I propose that the text be added to section 5.1, which discusses 
the specifications that must be supported at the IPv6 layer.  Second, I 
would modify the text proposed to clean up the introductory component as 
follows:

      All nodes SHOULD support the setting and use of the IPv6 Flow
      Label field as defined in the IPv6 Flow Label specification
      [RFC6437].  Forwarding nodes such as routers and load distributors
      MUST NOT depend only on Flow Label values being uniformly
      distributed.  It is RECOMMENDED that source hosts support the flow
      label by setting the Flow Label field for all packets of a given
      flow to the same value chosen from an approximation to a discrete
      uniform distribution.

Regards,
Brian (who is not wearing any hats at this time)

From jreddy@ti.com  Thu Nov 10 16:12:40 2011
Return-Path: <jreddy@ti.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5CA21F84CC for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 16:12:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YTfe-bCt2Df3 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 16:12:40 -0800 (PST)
Received: from bear.ext.ti.com (bear.ext.ti.com [192.94.94.41]) by ietfa.amsl.com (Postfix) with ESMTP id DEA9F21F84B0 for <ipv6@ietf.org>; Thu, 10 Nov 2011 16:12:39 -0800 (PST)
Received: from dlep33.itg.ti.com ([157.170.170.112]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id pAB0CcNj010517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Nov 2011 18:12:39 -0600
Received: from dlep26.itg.ti.com (smtp-le.itg.ti.com [157.170.170.27]) by dlep33.itg.ti.com (8.13.7/8.13.8) with ESMTP id pAB0CcU6008543; Thu, 10 Nov 2011 18:12:38 -0600 (CST)
Received: from DFLE71.ent.ti.com (localhost [127.0.0.1]) by dlep26.itg.ti.com (8.13.8/8.13.8) with ESMTP id pAB0CcTu011293; Thu, 10 Nov 2011 18:12:38 -0600 (CST)
Received: from DLEE10.ent.ti.com ([fe80::843:a4aa:bf01:3f68]) by DFLE71.ent.ti.com ([fe80::29f6:72ad:a62e:2025%21]) with mapi id 14.01.0323.003; Thu, 10 Nov 2011 18:12:38 -0600
From: "Reddy, Joseph" <jreddy@ti.com>
To: Jonathan Hui <jonhui@cisco.com>
Subject: RE: draft-ietf-6man-rpl-option questions
Thread-Topic: draft-ietf-6man-rpl-option questions
Thread-Index: AQHMn9XeNLkNIIasV0qJj/9ZFtKXqJWm2h8A///zawA=
Date: Fri, 11 Nov 2011 00:12:37 +0000
Message-ID: <2AA5AC69E924D149A8D63EB676AF87DBEEC375@DLEE10.ent.ti.com>
References: <mailman.3414.1320945452.2955.ipv6@ietf.org> <2AA5AC69E924D149A8D63EB676AF87DBEEBFBC@DLEE10.ent.ti.com> <C5CD1C48-84B4-4FDE-9484-7FA500411375@cisco.com>
In-Reply-To: <C5CD1C48-84B4-4FDE-9484-7FA500411375@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.170.170.90]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Nov 2011 00:12:40 -0000

Yes, thanks !

-----Original Message-----
From: Jonathan Hui [mailto:jonhui@cisco.com]=20
Sent: Thursday, November 10, 2011 10:58 AM
To: Reddy, Joseph
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-6man-rpl-option questions


Hi Joseph,

It is not actually required to use tunneling if the RPL router knows that t=
he destination is within the same RPL Instance.  But if the router does not=
 know for sure, then it must use tunneling.  Just after sending my proposed=
 text, I had modified the cited portion to the following:

   Datagrams sent between RPL routers MUST include a RPL Option or RPL
   Source Route Header (SRH) and MAY include both.  When the router is
   the source of the original packet and the destination is known to be
   within the same RPL Instance, the router SHOULD include the RPL Option
   directly within the original packet.  Otherwise, routers MUST use
   IPv6-in-IPv6 tunneling [RFC2473] to include a new RPL Option in
   datagrams that are sourced by other nodes.

Does this address your concern?

--
Jonathan Hui

On Nov 10, 2011, at 10:23 AM, Reddy, Joseph wrote:

>=20
>=20
> Hi Jonathan
>=20
> Thanks for the clarifiction.=20
>=20
> In your proposed new text, you state
>=20
> "...Routers MUST use IPv6-in-IPv6 tunneling, as
>  specified in [RFC2473] to include a new RPL Option in datagrams that
>  are sourced by other nodes..."
>=20
> Actually, isnt it true that this action ( use of tunnelling to include th=
e RPL option ) is nececssary for all packets, even for those sourced on the=
 router node itself ?=20
> Basically, if the source router is not sure that the destination node is =
within the RPL Instance, it musts use tunnelllig to include the RPL Option.
>=20
>=20
> -Regards, Joseph
>=20
>=20
> ------------------------------
>=20
> Message: 5
> Date: Thu, 10 Nov 2011 09:03:01 -0800
> From: Jonathan Hui <jonhui@cisco.com>
> To: Richard Kelsey <richard.kelsey@ember.com>
> Cc: ipv6@ietf.org
> Subject: Re: draft-ietf-6man-rpl-option questions
> Message-ID: <50A9F9C5-8C71-4F5E-B084-A127B7E982F4@cisco.com>
> Content-Type: text/plain; charset=3Dus-ascii
>=20
>=20
> Hi Richard,
>=20
> On Nov 10, 2011, at 8:14 AM, Richard Kelsey wrote:
>=20
>> In section 4, "Router Behavior" draft-ietf-6man-rpl-option
>> says:
>>=20
>>  Routers MUST use IPv6-in-IPv6 tunneling, as specified in
>>  [RFC2473] to include a new RPL Option in datagrams that
>>  are sourced by other nodes.
>>=20
>> What destination should be used for the tunnel header?  The
>> router adding the RPL option may not know if the original
>> destination is inside or outside the RPL domain.  And if the
>> original destination is outside the RPL domain, the router
>> may not know the address of the border router that will
>> forward the datagram outside.
>=20
> The tunnel header's destination should be the next RPL router along the p=
ath towards the destination.  If, for example, a router only knows the next=
-hop destination (i.e. the DODAG Parent), then the tunnel header's destinat=
ion will be the DODAG Parent itself.  Note that the original packet may tra=
verse multiple such tunnels within the same RPL domain in order to reach it=
s destination.  Let me propose the following update to Section 4:
>=20
> 4.  RPL Router Behavior
>=20
>  To deliver an IPv6 datagram to its destination, a router may need to
>  insert a new RPL Option.  Routers MUST use IPv6-in-IPv6 tunneling, as
>  specified in [RFC2473] to include a new RPL Option in datagrams that
>  are sourced by other nodes.  Using IPv6-in-IPv6 tunneling ensures
>  that the delivered datagram remains unmodified and that ICMPv6 errors
>  generated by inserting the RPL Option are sent back to the router
>  that generated the routing header.
>=20
>  A RPL router chooses the next RPL router that should process the
>  original packet as the tunnel exit-point.  In some cases, the tunnel
>  exit-point will be the final RPL router along a path towards the
>  original packet's destination and the original packet will only
>  traverse a single tunnel.  One example is when the final destination
>  or the destination's attachment router is known to be within the same
>  RPL domain.
>=20
>  In other cases, the tunnel exit-point will not be the final RPL
>  router along a path and the original packet may traverse multiple
>  tunnels to reach the destination.  One example is when a RPL router
>  is simply forwarding a packet to one of its DODAG Parents.  In this
>  case, the RPL router sets the tunnel exit-point to a DODAG Parent.
>  When forwarding the original packet hop-by-hop, the RPL router only
>  makes a determination on the next hop towards the destination.
>=20
>  A RPL router receiving an IPv6-in-IPv6 packet destined to it
>  processes the tunnel packet as described in Section 3. of [RFC2473].
>  Before IPv6 decapsulation, the RPL router MUST process the RPL Option
>  if one exists.  If the router determines that it should forward the
>  original packet to another RPL router, it MUST encapsulate the packet
>  again using IPv6-in-IPv6 tunneling to include the RPL Option.  Note
>  that fields within the RPL Option that do not change hop-by-hop MUST
>  remain the same as those received from the prior tunnel.
>=20
>  To avoid fragmentation, it is desirable to employ MTU sizes that
>  allow for the header expansion (i.e. at least 1280 + 40 (outer IP
>  header) + RPL_OPTION_MAX_SIZE), where RPL_OPTION_MAX_SIZE is the
>  maximum RPL Option header size for a given RPL network.  To take
>  advantage of this, however, the communicating endpoints need to be
>  aware of the MTU along the path (i.e. through Path MTU Discovery).
>  Unfortunately, the larger MTU size may not be available on all links
>  (e.g. 1280 octets on 6LoWPAN links).  However, it is expected that
>  much of the traffic on these types of networks consists of much
>  smaller messages than the MTU, so performance degradation through
>  fragmentation would be limited.
>=20
>> Also, there are normative statements which use the term "RPL
>> domain", such as
>>=20
>>  Datagrams sent between nodes within a RPL domain MUST include
>>  a RPL Option or RPL Source Route Header (SRH) and MAY include
>>  both.
>>=20
>> but "RPL domain" is not defined.  In particular, if a RPL
>> router has a non-RPL-aware host, is the host inside the RPL
>> domain?  Or is the router then a border router and messages
>> to the host need to be tunnelled to it?
>=20
> I agree that "RPL domain" is not well defined.  But after some thought, I=
 think replacing with "RPL Instance" may be more appropriate.  In particula=
r, we really want to limit the use of these RPL options/headers to a RPL In=
stance, not just a collection of routers that are all operating RPL.
>=20
> If you agree to the above, I'll make the changes in my updates to address=
 the LC comments.
>=20
> Thanks.
>=20
> --
> Jonathan Hui
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From shane@castlepoint.net  Thu Nov 10 20:13:42 2011
Return-Path: <shane@castlepoint.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE951F0C54 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 20:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[AWL=0.251,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wNe7n9mg1Ddm for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 20:13:41 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id 765DA1F0C3D for <ipv6@ietf.org>; Thu, 10 Nov 2011 20:13:41 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0) id 15824268063; Thu, 10 Nov 2011 21:13:41 -0700 (MST)
Received: from mbpw.castlepoint.net (65-102-206-76.hlrn.qwest.net [65.102.206.76]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Thu, 10 Nov 2011 21:13:40 -0700 (MST) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=65.102.206.76; client-port=51532; syn-fingerprint=65535:54:1:64:M1452,N,W2,N,N,T,S; data-bytes=0
Subject: Re: Working Group last call for adding RFC6437 Flow Label support to Node Requirements bis document
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <4EBC2BB9.4030308@gmail.com>
Date: Thu, 10 Nov 2011 21:13:24 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CAA1335D-191B-4C55-A1B4-5D3F951C68F7@castlepoint.net>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com> <4EBC2BB9.4030308@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Cc: Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Nov 2011 04:13:42 -0000

On Nov 10, 2011, at 12:53 PM, Brian E Carpenter wrote:
> I support this change.

+1.

-shane



> Regards
>   Brian Carpenter
>=20
> On 2011-11-11 06:00, Bob Hinden wrote:
>> This email starts a one week 6MAN Working Group last call for adding =
text and a reference to RFC6437 "IPv6 Flow Label Specification" to the =
Node Requirements bis document current in AUTH48 state.  The document is =
currently on hold in the RFC Editor waiting for resolution of this =
issue. =20
>>=20
>> The proposed text, first sent to the ipv6@ietf.org mailing list on =
November 2, 2011 (included below), is:
>>=20
>>> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,=20
>>> defines the IPv6 Flow Label.  Specifically:
>>>=20
>>>   "Forwarding nodes such as routers and load distributors MUST NOT
>>>    depend only on Flow Label values being uniformly distributed. "
>>>=20
>>>   "It is therefore RECOMMENDED  that source hosts support the flow=20=

>>>    label by setting the flow label field for all packets of a given =
flow to the=20
>>>    same value chosen from an approximation to a discrete uniform =
distribution. "
>>=20
>> The chairs have discussed this with the Internet Area Directors and =
they recommended this course of action.  This topic is also on the =
agenda for the 6man session at the Taipei IETF.
>>=20
>> Substantive comments and statements of support for taking this action =
should be sent to the mailing list.  This last call will end on November =
17, 2011.
>>=20
>> Regards,
>> Bob Hinden & Brian Haberman
>>=20
>>=20
>> Begin forwarded message:
>>=20
>>> From: <john.loughney@nokia.com>
>>> Date: November 2, 2011 7:50:35 PM PDT
>>> To: <ipv6@ietf.org>
>>> Subject: Flow Label support in the Node Requirements bis document
>>>=20
>>> Hi all,
>>>=20
>>> There has been some discussions whether or not we should add support =
for the Flow Label in
>>> Soon to be RFC 6434 <draft-ietf-6man-node-req-bis-11.txt> As a straw =
man proposal, if we add
>>> Support, I would suggest the following text:
>>>=20
>>> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,=20
>>> defines the IPv6 Flow Label.  Specifically:
>>>=20
>>>   "Forwarding nodes such as routers and load distributors MUST NOT
>>>     depend only on Flow Label values being uniformly distributed. "
>>>=20
>>>   "It is therefore RECOMMENDED  that source hosts support the flow=20=

>>>     label by setting the flow label field for all packets of a given =
flow to the=20
>>>     same value chosen from  an approximation to a discrete uniform =
distribution. "
>>>=20
>>> I'd like to ask the wg the following:
>>>=20
>>> 1) Is the above text acceptable?
>>> 2) Do you support adding the text? If no, please suggest text, =
unless you do not support adding
>>>    Flow label support at all (please say so).
>>>=20
>>> John
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From gdt@gdt.id.au  Thu Nov 10 21:31:40 2011
Return-Path: <gdt@gdt.id.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A736E1F0C35 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 21:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r+--wIkBVnbU for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 21:31:38 -0800 (PST)
Received: from aix.gdt.id.au (eth6445.sa.adsl.internode.on.net [150.101.30.44]) by ietfa.amsl.com (Postfix) with ESMTP id 37F6221F844A for <ipv6@ietf.org>; Thu, 10 Nov 2011 21:31:38 -0800 (PST)
Received: from samarkand.adelaide.aarnet.edu.au (samarkand.adelaide.aarnet.edu.au [202.158.193.6]) (authenticated bits=0) by aix.gdt.id.au (8.14.2/8.14.2) with ESMTP id pAB5VOL3001534 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Nov 2011 16:01:25 +1030
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Glen Turner <gdt@gdt.id.au>
In-Reply-To: <4EB53BCD.3090004@ericsson.com>
Date: Fri, 11 Nov 2011 16:01:24 +1030
Content-Transfer-Encoding: quoted-printable
Message-Id: <9704B8E3-BFE2-4D70-BBB4-3F43DD260020@gdt.id.au>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com> <1320358729.3032.24.camel@ilion> <4EB53BCD.3090004@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1084)
Cc: 6man Mailing List <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Nov 2011 05:31:40 -0000

Hi Suresh,

> Will do. Would a simple statement e.g. that it is a null terminated =
text string be sufficient or did you want more details?

There's no need for it to be NUL-terminated. In fact that's asking for =
trouble because what do you do if the NUL and the field length don't =
match?

What application programmers need to know is:
- that the field can be printed
- what character set to use for the printing and input
- what to do if a non-compliant string is encountered (eg, non-printable =
chatacters, or a failed UTF-8 encoding). A reasonable action would be to =
never attempt to print the field, fail any comparisons, and generate a =
small number of log messages containing enough information for debugging =
but without allowing an attack vector on the logging device (ie, don't =
print the errorred string, hex dump it or escape non-printing =
characters).
- how to compare the field. Byte-by-byte makes sense; that is, the =
locale is irrelevant.

As you can see, there's a fair few issues avoided by that convenient =
word "opaque". It's a fine word to describe bytes on the wire: it says =
that middleboxes shouldn't tamper with the field. But it's a poor word =
for use at endpoints, as it amounts to underspecification of the field =
and thus divergent practices or reverse engineering.

For example, one compliant router could use a twos-complement counter, =
another could use ASCII, another could use a random nonce. Without =
further specification of the "opaque" field all that a compliant =
provisioning system can do is require the field to be input as hex. =
Ironically, only a non-compliant provisioning system could accept input =
as a string, which is the intended use of the field.


The contents of the DHCP Relay Agent Information Option fields in =
RFC3046 are said to be opaque but then it is immediately suggested that =
the contents are textual. For example,  "The Circuit ID SHOULD be =
considered an opaque value, with policies based on exact string match =
only". To my mind RFC3046 isn't a good specification because all it does =
is raise ambiguity in the implementer's mind and send them off to look =
at other implementations for guidance.


This is much more writing than the issue is worth. My apologies for =
taking up your time.

Best wishes, Glen

--=20
 Glen Turner <http://www.gdt.id.au/~gdt/>=

From gdt@gdt.id.au  Thu Nov 10 21:53:05 2011
Return-Path: <gdt@gdt.id.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 592E61F0C48 for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 21:53:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZ-zQgjIR-jc for <ipv6@ietfa.amsl.com>; Thu, 10 Nov 2011 21:53:04 -0800 (PST)
Received: from aix.gdt.id.au (eth6445.sa.adsl.internode.on.net [150.101.30.44]) by ietfa.amsl.com (Postfix) with ESMTP id DEF8D1F0C3D for <ipv6@ietf.org>; Thu, 10 Nov 2011 21:53:02 -0800 (PST)
Received: from samarkand.adelaide.aarnet.edu.au (samarkand.adelaide.aarnet.edu.au [202.158.193.6]) (authenticated bits=0) by aix.gdt.id.au (8.14.2/8.14.2) with ESMTP id pAB5qoBF003127 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Nov 2011 16:22:51 +1030
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-lineid-02.txt>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Glen Turner <gdt@gdt.id.au>
In-Reply-To: <4EB53BCD.3090004@ericsson.com>
Date: Fri, 11 Nov 2011 16:01:24 +1030
Content-Transfer-Encoding: quoted-printable
Message-Id: <9704B8E3-BFE2-4D70-BBB4-3F43DD260020@gdt.id.au>
References: <15766BFD-E312-4455-955F-AB74FA0B047C@gmail.com> <1320358729.3032.24.camel@ilion> <4EB53BCD.3090004@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1084)
Cc: 6man Mailing List <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Nov 2011 05:53:05 -0000

Hi Suresh,

> Will do. Would a simple statement e.g. that it is a null terminated =
text string be sufficient or did you want more details?

There's no need for it to be NUL-terminated. In fact that's asking for =
trouble because what do you do if the NUL and the field length don't =
match?

What application programmers need to know is:
- that the field can be printed
- what character set to use for the printing and input
- what to do if a non-compliant string is encountered (eg, non-printable =
chatacters, or a failed UTF-8 encoding). A reasonable action would be to =
never attempt to print the field, fail any comparisons, and generate a =
small number of log messages containing enough information for debugging =
but without allowing an attack vector on the logging device (ie, don't =
print the errorred string, hex dump it or escape non-printing =
characters).
- how to compare the field. Byte-by-byte makes sense; that is, the =
locale is irrelevant.

As you can see, there's a fair few issues avoided by that convenient =
word "opaque". It's a fine word to describe bytes on the wire: it says =
that middleboxes shouldn't tamper with the field. But it's a poor word =
for use at endpoints, as it amounts to underspecification of the field =
and thus divergent practices or reverse engineering.

For example, one compliant router could use a twos-complement counter, =
another could use ASCII, another could use a random nonce. Without =
further specification of the "opaque" field all that a compliant =
provisioning system can do is require the field to be input as hex. =
Ironically, only a non-compliant provisioning system could accept input =
as a string, which is the intended use of the field.


The contents of the DHCP Relay Agent Information Option fields in =
RFC3046 are said to be opaque but then it is immediately suggested that =
the contents are textual. For example,  "The Circuit ID SHOULD be =
considered an opaque value, with policies based on exact string match =
only". To my mind RFC3046 isn't a good specification because all it does =
is raise ambiguity in the implementer's mind and send them off to look =
at other implementations for guidance.


This is much more writing than the issue is worth. My apologies for =
taking up your time.

Best wishes, Glen

--=20
 Glen Turner <http://www.gdt.id.au/~gdt/>=

From tjc@ecs.soton.ac.uk  Fri Nov 11 12:07:34 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2479521F85DB for <ipv6@ietfa.amsl.com>; Fri, 11 Nov 2011 12:07:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IAmLrb1sGkbF for <ipv6@ietfa.amsl.com>; Fri, 11 Nov 2011 12:07:33 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id F237F21F87D3 for <ipv6@ietf.org>; Fri, 11 Nov 2011 12:07:32 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id pABK7Hs9014087;  Fri, 11 Nov 2011 20:07:17 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk pABK7Hs9014087
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1321042037; bh=gZANnrsEc4hMOSxaNw03aN5o/LI=; h=Subject:Mime-Version:From:In-Reply-To:Date:Cc:References:To; b=BO+rH6qIsc0rTveJSFgG0EPDpsLLVSigfHGFpNSshdJBnyvoqMxIfLM+PHUydhIj+ lEOW1WLXQmbzPAwa9KpymHxLZT8WP+VklA2c6Dae7w8dqbhQFi0HYfQVTpVihx2aPO aQvfwpEcFKf4zOyBCJc2klkvE6Su0MLZMZa8uR08=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id nAAK7H0543743651OX ret-id none; Fri, 11 Nov 2011 20:07:17 +0000
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id pABK698v002168 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Nov 2011 20:07:02 GMT
Subject: Re: Working Group last call for adding RFC6437 Flow Label support to Node Requirements bis document
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAA1335D-191B-4C55-A1B4-5D3F951C68F7@castlepoint.net>
Date: Fri, 11 Nov 2011 20:07:01 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|fb418a899c92787cccf76ebe9a1af9acnAAK7H03tjc|ecs.soton.ac.uk|3E19C111-2EAA-4A73-A602-75D6853A4777@ecs.soton.ac.uk>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com> <4EBC2BB9.4030308@gmail.com> <CAA1335D-191B-4C55-A1B4-5D3F951C68F7@castlepoint.net> <3E19C111-2EAA-4A73-A602-75D6853A4777@ecs.soton.ac.uk>
To: Shane Amante <shane@castlepoint.net>
X-Mailer: Apple Mail (2.1251.1)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=nAAK7H054374365100; tid=nAAK7H0543743651OX; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: pABK7Hs9014087
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Nov 2011 20:07:34 -0000

Agree.

On 11 Nov 2011, at 04:13, Shane Amante wrote:

>=20
> On Nov 10, 2011, at 12:53 PM, Brian E Carpenter wrote:
>> I support this change.
>=20
> +1.
>=20
> -shane
>=20
>=20
>=20
>> Regards
>>  Brian Carpenter
>>=20
>> On 2011-11-11 06:00, Bob Hinden wrote:
>>> This email starts a one week 6MAN Working Group last call for adding =
text and a reference to RFC6437 "IPv6 Flow Label Specification" to the =
Node Requirements bis document current in AUTH48 state.  The document is =
currently on hold in the RFC Editor waiting for resolution of this =
issue. =20
>>>=20
>>> The proposed text, first sent to the ipv6@ietf.org mailing list on =
November 2, 2011 (included below), is:
>>>=20
>>>> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,=20=

>>>> defines the IPv6 Flow Label.  Specifically:
>>>>=20
>>>>  "Forwarding nodes such as routers and load distributors MUST NOT
>>>>   depend only on Flow Label values being uniformly distributed. "
>>>>=20
>>>>  "It is therefore RECOMMENDED  that source hosts support the flow=20=

>>>>   label by setting the flow label field for all packets of a given =
flow to the=20
>>>>   same value chosen from an approximation to a discrete uniform =
distribution. "
>>>=20
>>> The chairs have discussed this with the Internet Area Directors and =
they recommended this course of action.  This topic is also on the =
agenda for the 6man session at the Taipei IETF.
>>>=20
>>> Substantive comments and statements of support for taking this =
action should be sent to the mailing list.  This last call will end on =
November 17, 2011.
>>>=20
>>> Regards,
>>> Bob Hinden & Brian Haberman
>>>=20
>>>=20
>>> Begin forwarded message:
>>>=20
>>>> From: <john.loughney@nokia.com>
>>>> Date: November 2, 2011 7:50:35 PM PDT
>>>> To: <ipv6@ietf.org>
>>>> Subject: Flow Label support in the Node Requirements bis document
>>>>=20
>>>> Hi all,
>>>>=20
>>>> There has been some discussions whether or not we should add =
support for the Flow Label in
>>>> Soon to be RFC 6434 <draft-ietf-6man-node-req-bis-11.txt> As a =
straw man proposal, if we add
>>>> Support, I would suggest the following text:
>>>>=20
>>>> All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,=20=

>>>> defines the IPv6 Flow Label.  Specifically:
>>>>=20
>>>>  "Forwarding nodes such as routers and load distributors MUST NOT
>>>>    depend only on Flow Label values being uniformly distributed. "
>>>>=20
>>>>  "It is therefore RECOMMENDED  that source hosts support the flow=20=

>>>>    label by setting the flow label field for all packets of a given =
flow to the=20
>>>>    same value chosen from  an approximation to a discrete uniform =
distribution. "
>>>>=20
>>>> I'd like to ask the wg the following:
>>>>=20
>>>> 1) Is the above text acceptable?
>>>> 2) Do you support adding the text? If no, please suggest text, =
unless you do not support adding
>>>>   Flow label support at all (please say so).
>>>>=20
>>>> John
>>>> =
--------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> =
--------------------------------------------------------------------
>>>=20
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From wesley.george@twcable.com  Fri Nov 11 20:49:17 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8CE91F0C3D for <ipv6@ietfa.amsl.com>; Fri, 11 Nov 2011 20:49:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.328
X-Spam-Level: 
X-Spam-Status: No, score=-0.328 tagged_above=-999 required=5 tests=[AWL=0.135,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OnfLoiQy2SmM for <ipv6@ietfa.amsl.com>; Fri, 11 Nov 2011 20:49:17 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 0B8231F0C3C for <ipv6@ietf.org>; Fri, 11 Nov 2011 20:49:16 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,498,1315195200"; d="scan'208";a="281294902"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 11 Nov 2011 23:44:28 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Fri, 11 Nov 2011 23:49:15 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Bob Hinden <bob.hinden@gmail.com>, 6man Mailing List <ipv6@ietf.org>
Date: Fri, 11 Nov 2011 23:49:36 -0500
Subject: RE: Working Group last call for adding RFC6437 Flow Label support to Node	Requirements bis document
Thread-Topic: Working Group last call for adding RFC6437 Flow Label support to Node	Requirements bis document
Thread-Index: AcyfyktEVkMj78BQQTKzvQoqfsFAJgBLCmsA
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791451B2CCD3@PRVPEXVS03.corp.twcable.com>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com>
In-Reply-To: <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Brian Haberman <brian@innovationslab.net>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Nov 2011 04:49:17 -0000

support

Thanks,

Wes

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Bob Hinden
> Sent: Thursday, November 10, 2011 12:00 PM
> To: 6man Mailing List
> Cc: Brian Haberman; Bob Hinden; Ralph Droms
> Subject: Working Group last call for adding RFC6437 Flow Label support
> to Node Requirements bis document
>
> This email starts a one week 6MAN Working Group last call for adding
> text and a reference to RFC6437 "IPv6 Flow Label Specification" to the
> Node Requirements bis document current in AUTH48 state.  The document
> is currently on hold in the RFC Editor waiting for resolution of this
> issue.
>
> The proposed text, first sent to the ipv6@ietf.org mailing list on
> November 2, 2011 (included below), is:
>
> > All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,
> > defines the IPv6 Flow Label.  Specifically:
> >
> >    "Forwarding nodes such as routers and load distributors MUST NOT
> >     depend only on Flow Label values being uniformly distributed. "
> >
> >    "It is therefore RECOMMENDED  that source hosts support the flow
> >     label by setting the flow label field for all packets of a given
> flow to the
> >     same value chosen from an approximation to a discrete uniform
> distribution. "
>
> The chairs have discussed this with the Internet Area Directors and
> they recommended this course of action.  This topic is also on the
> agenda for the 6man session at the Taipei IETF.
>
> Substantive comments and statements of support for taking this action
> should be sent to the mailing list.  This last call will end on
> November 17, 2011.
>
> Regards,
> Bob Hinden & Brian Haberman
>
>
> Begin forwarded message:
>
> > From: <john.loughney@nokia.com>
> > Date: November 2, 2011 7:50:35 PM PDT
> > To: <ipv6@ietf.org>
> > Subject: Flow Label support in the Node Requirements bis document
> >
> > Hi all,
> >
> > There has been some discussions whether or not we should add support
> > for the Flow Label in Soon to be RFC 6434
> > <draft-ietf-6man-node-req-bis-11.txt> As a straw man proposal, if we
> add Support, I would suggest the following text:
> >
> > All nodes SHOULD support RFC 6437, IPv6 Flow Label Specification,
> > defines the IPv6 Flow Label.  Specifically:
> >
> >    "Forwarding nodes such as routers and load distributors MUST NOT
> >      depend only on Flow Label values being uniformly distributed. "
> >
> >    "It is therefore RECOMMENDED  that source hosts support the flow
> >      label by setting the flow label field for all packets of a given
> flow to the
> >      same value chosen from  an approximation to a discrete uniform
> distribution. "
> >
> > I'd like to ask the wg the following:
> >
> > 1) Is the above text acceptable?
> > 2) Do you support adding the text? If no, please suggest text, unless
> you do not support adding
> >     Flow label support at all (please say so).
> >
> > John
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From arifumi@nttv6.net  Sun Nov 13 00:19:20 2011
Return-Path: <arifumi@nttv6.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E2DF21F8B0C for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 00:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.882
X-Spam-Level: 
X-Spam-Status: No, score=-102.882 tagged_above=-999 required=5 tests=[AWL=-0.283, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bn5FoE+4Z-J4 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 00:19:20 -0800 (PST)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by ietfa.amsl.com (Postfix) with ESMTP id BAF6B21F8B0B for <ipv6@ietf.org>; Sun, 13 Nov 2011 00:19:19 -0800 (PST)
Received: from [127.0.0.1] (localhost.nttv6.net [127.0.0.1]) by leo.nttv6.net (8.14.5/8.14.4) with ESMTP id pAD8HaXI038899; Sun, 13 Nov 2011 17:17:41 +0900 (JST) (envelope-from arifumi@nttv6.net)
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Arifumi Matsumoto <arifumi@nttv6.net>
In-Reply-To: <4EB9D332.1040003@gmail.com>
Date: Sun, 13 Nov 2011 17:19:13 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <81C461F1-C088-446A-892C-D8B233CF1EB7@nttv6.net>
References: <4EB9D332.1040003@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Nov 2011 08:19:20 -0000

Brian,

thank you for your comments.

On 2011/11/09, at 10:11, Brian E Carpenter wrote:

> Hi,
>=20
> I think I'm going to make myself unpopular.
>=20
> Reading this document as a proposed standard, I think it will confuse =
the reader.
> I think that what we actually need is a 100% replacement of RFC 3484, =
that
> can be read on its own.
>=20
> (We've been here before - the same argument is why we ended up doing =
3697bis.)
>=20
> If that is not done, I would suggest reorganising the text so that =
(after
> a short Introduction) the reader finds:
>=20
> - firstly, a complete but concise statement of the normative changes =
made to 3484
>  (such as section 2.1.5, and the new rules 5.1 and 9)
>=20
> - secondly, the explanations (such as sections 2.1.1-2.1.4).
>=20
> An implementer would only need to read the first part.

This document had started as an update, because there was not so many
things to update at first.

As the document gets older, it got a bit bigger than I had expected.

So, which of update or replace do you prefer ?

>=20
> Trivia:
>=20
> Needs a header: Updates: 3484 (if approved)
>=20
>> 4.  IANA Considerations
>>=20
>>   Address type number for the policy table may have to be assigned by
>>   IANA.
>=20
> You can't say "may", you have to tell IANA exactly what to do in which =
registry.

Thanks !=

From brian.e.carpenter@gmail.com  Sun Nov 13 14:48:07 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E539921F8AE6 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 14:48:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.038
X-Spam-Level: 
X-Spam-Status: No, score=-101.038 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RECV_IP_061228=0.895, SARE_RECV_SPAM_DOMN0b=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lp0YKh+U1P7a for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 14:48:07 -0800 (PST)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 65B7721F8ADC for <ipv6@ietf.org>; Sun, 13 Nov 2011 14:48:07 -0800 (PST)
Received: by pzk5 with SMTP id 5so7956767pzk.9 for <ipv6@ietf.org>; Sun, 13 Nov 2011 14:48:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dIGVdTaej/ilMSESWx8WkGUYGPV80JINAyiABtlxjk4=; b=oNnRrXaoZYYZBmWglryEUDxw/5HpX/UzXC91TO58WBaASfaaVutd1nbYnGZSqR0ch7 ZRDBXhUL+4yCQ62J+gYdXSGrrtbTI7vgXe4+ucjfvPmnKAa0MS+htdkIPZKBSAwzDRDv rQ7imf/bxAs3wAl1cjwLFz8gFrEBL8gSz233E=
Received: by 10.68.47.4 with SMTP id z4mr45028631pbm.39.1321224485398; Sun, 13 Nov 2011 14:48:05 -0800 (PST)
Received: from [192.168.0.217] (61-230-55-233.dynamic.hinet.net. [61.230.55.233]) by mx.google.com with ESMTPS id wn14sm51365722pbb.5.2011.11.13.14.48.00 (version=SSLv3 cipher=OTHER); Sun, 13 Nov 2011 14:48:04 -0800 (PST)
Message-ID: <4EC0491C.2050406@gmail.com>
Date: Mon, 14 Nov 2011 11:47:56 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
References: <4EB9D332.1040003@gmail.com> <81C461F1-C088-446A-892C-D8B233CF1EB7@nttv6.net>
In-Reply-To: <81C461F1-C088-446A-892C-D8B233CF1EB7@nttv6.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Nov 2011 22:48:08 -0000

> So, which of update or replace do you prefer ?

Hmm. If we want to go quickly, an update that makes it easy for
the implementer to find the changes is better.

Regards
   Brian

On 2011-11-13 21:19, Arifumi Matsumoto wrote:
> Brian,
> 
> thank you for your comments.
> 
> On 2011/11/09, at 10:11, Brian E Carpenter wrote:
> 
>> Hi,
>>
>> I think I'm going to make myself unpopular.
>>
>> Reading this document as a proposed standard, I think it will confuse the reader.
>> I think that what we actually need is a 100% replacement of RFC 3484, that
>> can be read on its own.
>>
>> (We've been here before - the same argument is why we ended up doing 3697bis.)
>>
>> If that is not done, I would suggest reorganising the text so that (after
>> a short Introduction) the reader finds:
>>
>> - firstly, a complete but concise statement of the normative changes made to 3484
>>  (such as section 2.1.5, and the new rules 5.1 and 9)
>>
>> - secondly, the explanations (such as sections 2.1.1-2.1.4).
>>
>> An implementer would only need to read the first part.
> 
> This document had started as an update, because there was not so many
> things to update at first.
> 
> As the document gets older, it got a bit bigger than I had expected.
> 
> So, which of update or replace do you prefer ?
> 
>> Trivia:
>>
>> Needs a header: Updates: 3484 (if approved)
>>
>>> 4.  IANA Considerations
>>>
>>>   Address type number for the policy table may have to be assigned by
>>>   IANA.
>> You can't say "may", you have to tell IANA exactly what to do in which registry.
> 
> Thanks !

From denghui02@gmail.com  Sun Nov 13 17:46:48 2011
Return-Path: <denghui02@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA2CF11E80EB; Sun, 13 Nov 2011 17:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oSgSO8jebU7y; Sun, 13 Nov 2011 17:46:48 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 02D7111E80D7; Sun, 13 Nov 2011 17:46:47 -0800 (PST)
Received: by yenq4 with SMTP id q4so2790660yen.31 for <multiple recipients>; Sun, 13 Nov 2011 17:46:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=riLXQ7m/yrNPXAPA6MiN9WsBqkItDrclgZJ7qm51WTg=; b=wyB81GAxHTRw+ZRYj+jPwpzwXUcJPmhSWWpsvSNhBHlt5RRsqHeLe+ALwspSHFjum0 myWIJ6Ai8hFR4NBVxzrsP8L2EwlLsZto0NwxgajEgv+RnK1Jymxx0SWPh9ZqL8PWderW Y7060hIZUgF0PPJmYr4ztEqDd2VVxvTOfrYLY=
MIME-Version: 1.0
Received: by 10.236.197.72 with SMTP id s48mr11227596yhn.81.1321235207615; Sun, 13 Nov 2011 17:46:47 -0800 (PST)
Received: by 10.146.84.10 with HTTP; Sun, 13 Nov 2011 17:46:47 -0800 (PST)
Date: Mon, 14 Nov 2011 09:46:47 +0800
Message-ID: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Subject: Conflict between RA and DHCP in MIF case
From: Hui Deng <denghui02@gmail.com>
To: ipv6@ietf.org, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=20cf303f6c8036f66204b1a80bca
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 01:46:48 -0000

--20cf303f6c8036f66204b1a80bca
Content-Type: text/plain; charset=ISO-8859-1

Hello 6MAN and DHCP,

Especially thanks *Wes Beebee*, Hemant Singh, Brian Carpenter, Alex and
Ted's discussion.

MIF is going to discuss the confliction between RA and DHCP on tuesday
afternoon MIF session (15:20-17:00)
the author Tomasz has propose below resolution:

The problem is about potential conflict between RA and DHCP. Our
proposed answer is as follows:

RA provides configuration to all hosts in a network. DHCP can provide
configuration on a per host basis. Therefore it may be useful to use
DHCP to "override" configuration for some hosts in a network (e.g.
engineering department has extra routes defined for a lab network). As
such, DHCP should be preferred.

However, there is also a matter of security. Both RA and DHCPv6 can be
secured. If SEND is deployed, RA is more trustworthy than DHCP, so it
should be preferred. Finally, there is such thing as secure DHCP, so if
both RA and DHCP are secure, prefer SEND. I must admit that I never
heard about any realistic deployments of secure DHCP, but it will change
over time.

This approach can be summed as: favor secure, favor DHCP. Or to be more
explicit, there's a complete list of all cases:
a) RA vs DHCP => prefer DHCP
b) RA(SEND) vs DHCP => prefer RA
c) RA vs secure DHCP => prefer DHCP
d) RA(SEND) vs secure DHCP => prefer DHCP

Does it sound reasonable?

This approach is very similar to what was described in DNS configuration
over RA and DHCP (except the part about both RA and DHCP being secure
that is not covered in RFC6106).

To summarize the discussion so far, Ted Lemon on MIF list agreed that
DHCP should be preferred. Herman Singh on 6MAN list suggested to go look
at what DNS over RA proposes and use the same approach. RFC6106, section
5.3.1covers cases a) and b). c) and d) are logical extension that takes
DHCPv6 security into consideration. My understanding is that proposed
solution will be satisfactory to everyone.

--20cf303f6c8036f66204b1a80bca
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello 6MAN and DHCP, </div>
<div>=A0</div>
<div>Especially=A0thanks <strong>Wes Beebee</strong>, Hemant Singh, Brian C=
arpenter, Alex and Ted&#39;s discussion.</div>
<div>=A0</div>
<div>MIF is going to discuss the confliction between RA and DHCP on tuesday=
 afternoon MIF session (15:20-17:00)=A0</div>
<div>the author Tomasz has propose below resolution:</div>
<div>=A0</div>
<div>The problem is about potential conflict between RA and DHCP. Our<br>pr=
oposed answer is as follows:<br><br>RA provides configuration to all hosts =
in a network. DHCP can provide<br>configuration on a per host basis. Theref=
ore it may be useful to use<br>
DHCP to &quot;override&quot; configuration for some hosts in a network (e.g=
.<br>engineering department has extra routes defined for a lab network). As=
<br>such, DHCP should be preferred.<br><br>However, there is also a matter =
of security. Both RA and DHCPv6 can be<br>
secured. If SEND is deployed, RA is more trustworthy than DHCP, so it<br>sh=
ould be preferred. Finally, there is such thing as secure DHCP, so if<br>bo=
th RA and DHCP are secure, prefer SEND. I must admit that I never<br>heard =
about any realistic deployments of secure DHCP, but it will change<br>
over time.<br><br>This approach can be summed as: favor secure, favor DHCP.=
 Or to be more<br>explicit, there&#39;s a complete list of all cases:<br>a)=
 RA vs DHCP =3D&gt; prefer DHCP<br>b) RA(SEND) vs DHCP =3D&gt; prefer RA<br=
>
c) RA vs secure DHCP =3D&gt; prefer DHCP<br>d) RA(SEND) vs secure DHCP =3D&=
gt; prefer DHCP<br><br>Does it sound reasonable?<br><br>This approach is ve=
ry similar to what was described in DNS configuration<br>over RA and DHCP (=
except the part about both RA and DHCP being secure<br>
that is not covered in RFC6106).<br><br>To summarize the discussion so far,=
 Ted Lemon on MIF list agreed that<br>DHCP should be preferred. Herman Sing=
h on 6MAN list suggested to go look<br>at what DNS over RA proposes and use=
 the same approach. RFC6106, section<br>
5.3.1covers cases a) and b). c) and d) are logical extension that takes<br>=
DHCPv6 security into consideration. My understanding is that proposed<br>so=
lution will be satisfactory to everyone.<br></div>

--20cf303f6c8036f66204b1a80bca--

From ichiroumakino@gmail.com  Sun Nov 13 17:59:49 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF55A11E8109; Sun, 13 Nov 2011 17:59:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SrWMA+93ObOo; Sun, 13 Nov 2011 17:59:49 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id EB03211E8091; Sun, 13 Nov 2011 17:59:48 -0800 (PST)
Received: by ggnr5 with SMTP id r5so433608ggn.31 for <multiple recipients>; Sun, 13 Nov 2011 17:59:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=WCUXB617eBHyCXPPmNzF+X0gl4DHSxdh2Aw1lleoVpA=; b=SlyqQ8NBV3Lfoiu+hSX3iA/diOaAm2CC3oaDDRlSbLvqbV8CfPfQ28QDrloky64S5H 1OKa0UEoM4yJw05bUGC+blJm8xERDVaJiMgMJw6KnBYUYuoTB4q5CAh1Om1CSjO7Av/q Mfvrjm2wDApRTCUaP4XHoukDnLnw34hRbCRPc=
Received: by 10.68.73.71 with SMTP id j7mr32010423pbv.116.1321235987294; Sun, 13 Nov 2011 17:59:47 -0800 (PST)
Received: from sjc-vpn4-250.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id p10sm52531607pbd.15.2011.11.13.17.59.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 17:59:45 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Date: Mon, 14 Nov 2011 09:59:40 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
To: Hui Deng <denghui02@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: MIF Mailing List <mif@ietf.org>, ipv6@ietf.org, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 01:59:49 -0000

Hui,

why not just merge all the information received?
e.g. if you get DNS server over DHCP and RA, use all.
if you get addresses via SLAAC and DHCP, you use all...

cheers,
Ole


On Nov 14, 2011, at 9:46 , Hui Deng wrote:

> Hello 6MAN and DHCP,
> =20
> Especially thanks Wes Beebee, Hemant Singh, Brian Carpenter, Alex and =
Ted's discussion.
> =20
> MIF is going to discuss the confliction between RA and DHCP on tuesday =
afternoon MIF session (15:20-17:00)=20
> the author Tomasz has propose below resolution:
> =20
> The problem is about potential conflict between RA and DHCP. Our
> proposed answer is as follows:
>=20
> RA provides configuration to all hosts in a network. DHCP can provide
> configuration on a per host basis. Therefore it may be useful to use
> DHCP to "override" configuration for some hosts in a network (e.g.
> engineering department has extra routes defined for a lab network). As
> such, DHCP should be preferred.
>=20
> However, there is also a matter of security. Both RA and DHCPv6 can be
> secured. If SEND is deployed, RA is more trustworthy than DHCP, so it
> should be preferred. Finally, there is such thing as secure DHCP, so =
if
> both RA and DHCP are secure, prefer SEND. I must admit that I never
> heard about any realistic deployments of secure DHCP, but it will =
change
> over time.
>=20
> This approach can be summed as: favor secure, favor DHCP. Or to be =
more
> explicit, there's a complete list of all cases:
> a) RA vs DHCP =3D> prefer DHCP
> b) RA(SEND) vs DHCP =3D> prefer RA
> c) RA vs secure DHCP =3D> prefer DHCP
> d) RA(SEND) vs secure DHCP =3D> prefer DHCP
>=20
> Does it sound reasonable?
>=20
> This approach is very similar to what was described in DNS =
configuration
> over RA and DHCP (except the part about both RA and DHCP being secure
> that is not covered in RFC6106).
>=20
> To summarize the discussion so far, Ted Lemon on MIF list agreed that
> DHCP should be preferred. Herman Singh on 6MAN list suggested to go =
look
> at what DNS over RA proposes and use the same approach. RFC6106, =
section
> 5.3.1covers cases a) and b). c) and d) are logical extension that =
takes
> DHCPv6 security into consideration. My understanding is that proposed
> solution will be satisfactory to everyone.
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From kauer@biplane.com.au  Sun Nov 13 18:11:12 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41E8821F8434 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:11:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G3C6Y8INoAiw for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:11:11 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by ietfa.amsl.com (Postfix) with ESMTP id 0077C21F8493 for <ipv6@ietf.org>; Sun, 13 Nov 2011 18:11:10 -0800 (PST)
Received: from eth4284.nsw.adsl.internode.on.net ([150.101.127.187] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1RPm0I-0006vP-4W for ipv6@ietf.org; Sun, 13 Nov 2011 21:10:34 -0500
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
In-Reply-To: <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-0NeX1f59UyFEK7PjrG+f"
Date: Mon, 14 Nov 2011 13:10:31 +1100
Message-ID: <1321236631.2514.48.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:11:12 -0000

--=-0NeX1f59UyFEK7PjrG+f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2011-11-14 at 09:59 +0800, Ole Troan wrote:
> why not just merge all the information received?
> e.g. if you get DNS server over DHCP and RA, use all.
> if you get addresses via SLAAC and DHCP, you use all...

It's about *conflict*, I think.

I.e., when  the information coming from RA and DHCP cannot be "merged" -
for example, differing domain search lists, or default routing
information.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-0NeX1f59UyFEK7PjrG+f
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk7AeJcACgkQMAcU7Vc29oduJQCfXdJCIy2KeEi5ImEoPzUYrwMT
/e0AnAnC3j/JdOdkfIQmgIYSBvsEWhha
=vnO9
-----END PGP SIGNATURE-----

--=-0NeX1f59UyFEK7PjrG+f--


From kawamucho@mesh.ad.jp  Sun Nov 13 18:19:43 2011
Return-Path: <kawamucho@mesh.ad.jp>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD32611E80E1 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVxsKeE8uajB for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:19:43 -0800 (PST)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD4A11E80DF for <ipv6@ietf.org>; Sun, 13 Nov 2011 18:19:42 -0800 (PST)
Received: from mailgate3.nec.co.jp ([10.7.69.195]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id pAE2JgOw019853 for <ipv6@ietf.org>; Mon, 14 Nov 2011 11:19:42 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id pAE2Jgn21959 for ipv6@ietf.org; Mon, 14 Nov 2011 11:19:42 +0900 (JST)
Received: from bgas200085.sys.biglobe.nec.co.jp (bgas200085.sys.biglobe.nec.co.jp [10.82.141.45]) by mailsv.nec.co.jp (8.13.8/8.13.4) with ESMTP id pAE2Jfu1014329 for <ipv6@ietf.org>; Mon, 14 Nov 2011 11:19:41 +0900 (JST)
Received: from mail.sys.biglobe.nec.co.jp (localhost [127.0.0.1]) by bgas200085.sys.biglobe.nec.co.jp (BINGO/BINGO/06101717) with ESMTP id pAE2JfJk010026; Mon, 14 Nov 2011 11:19:41 +0900
Received: from [127.0.0.1] ([10.65.91.161]) (authenticated bits=0) (envelope-from kawamucho@mesh.ad.jp)  by mail.sys.biglobe.nec.co.jp (BINGO/BINGO/10031711) with ESMTP id pAE2JWoM016251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2011 11:19:38 +0900
Message-ID: <4EC07AB1.3030807@mesh.ad.jp>
Date: Mon, 14 Nov 2011 11:19:29 +0900
From: Seiichi Kawamura <kawamucho@mesh.ad.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: draft-ietf-6man-addr-select-considerations-04
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:19:43 -0000

I think the first paragraph of the conclusion
should be noted in the introductory part of the draft
so that enterprise network managers know that this
document is important to them.

Seiichi

From kauer@biplane.com.au  Sun Nov 13 18:20:29 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00DF81F0C46 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:20:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwo3TvxVeRwI for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:20:28 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6A21F0C49 for <ipv6@ietf.org>; Sun, 13 Nov 2011 18:20:27 -0800 (PST)
Received: from eth4284.nsw.adsl.internode.on.net ([150.101.127.187] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1RPm9r-0000VW-6p for ipv6@ietf.org; Sun, 13 Nov 2011 21:20:27 -0500
Subject: Re: Conflict between RA and DHCP in MIF case
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-6F8TcP0GaLstTpM6SxSI"
Date: Mon, 14 Nov 2011 13:20:24 +1100
Message-ID: <1321237224.2514.58.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:20:29 -0000

--=-6F8TcP0GaLstTpM6SxSI
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2011-11-14 at 09:46 +0800, Hui Deng wrote:
> a) RA vs DHCP =3D> prefer DHCP
> b) RA(SEND) vs DHCP =3D> prefer RA
> c) RA vs secure DHCP =3D> prefer DHCP
> d) RA(SEND) vs secure DHCP =3D> prefer DHCP

Can this be summarised as "prefer DHCP except over RA+SEND"?

My apologies if this has already been dealt with, but it seems to me
that the behaviour SHOULD be configurable, with the above being the
default position if it is not configured or not configurable.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-6F8TcP0GaLstTpM6SxSI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk7AeugACgkQMAcU7Vc29oe1qACghkUYAicg5aBzzwzu5lR9Bn+M
bfQAoNQry+jJseFGRzpTEE3HUe+anWqZ
=bWw5
-----END PGP SIGNATURE-----

--=-6F8TcP0GaLstTpM6SxSI--


From brian.e.carpenter@gmail.com  Sun Nov 13 18:20:39 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2674A1F0C4E; Sun, 13 Nov 2011 18:20:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.442
X-Spam-Level: 
X-Spam-Status: No, score=-103.442 tagged_above=-999 required=5 tests=[AWL=0.158, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8O6yjVwzW8m2; Sun, 13 Nov 2011 18:20:38 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5B62B1F0C62; Sun, 13 Nov 2011 18:20:38 -0800 (PST)
Received: by yenq4 with SMTP id q4so2811608yen.31 for <multiple recipients>; Sun, 13 Nov 2011 18:20:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=x5SkQIePzE7xVG2xmaltQX4nChFg/4XxpaxQYVvRHRU=; b=SSn8S3vEnIdYmtNH2DuM8z0Y4zlsKS5ZbjjnnH3Gxj24i+nsClJLajEwkMgFsce45k qVgblvH/HRwDu6SBjXbd0YaHuD9HS+2K+t9w8pfkZ8aVn3rgWZQUFDKiW7JuhpfnIbuu HdssbrWBT9QnK0x4MZ6Z8BrPEkCMP2pgBusvU=
Received: by 10.236.116.98 with SMTP id f62mr11231472yhh.48.1321237237925; Sun, 13 Nov 2011 18:20:37 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id j25sm28619708yhm.12.2011.11.13.18.20.35 (version=SSLv3 cipher=OTHER); Sun, 13 Nov 2011 18:20:37 -0800 (PST)
Message-ID: <4EC07AEF.7070303@gmail.com>
Date: Mon, 14 Nov 2011 15:20:31 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hui Deng <denghui02@gmail.com>
Subject: Re: [mif] Conflict between RA and DHCP in MIF case
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: MIF Mailing List <mif@ietf.org>, ipv6@ietf.org, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:20:39 -0000

> MIF is going to discuss the confliction between RA and DHCP on tuesday
> afternoon MIF session (15:20-17:00)

This clashes with SOFTWIRE. Can you do it in the 17:10 session?

Regards
   Brian

On 2011-11-14 14:46, Hui Deng wrote:
> Hello 6MAN and DHCP,
> 
> Especially thanks *Wes Beebee*, Hemant Singh, Brian Carpenter, Alex and
> Ted's discussion.
> 
> MIF is going to discuss the confliction between RA and DHCP on tuesday
> afternoon MIF session (15:20-17:00)
> the author Tomasz has propose below resolution:
> 
> The problem is about potential conflict between RA and DHCP. Our
> proposed answer is as follows:
> 
> RA provides configuration to all hosts in a network. DHCP can provide
> configuration on a per host basis. Therefore it may be useful to use
> DHCP to "override" configuration for some hosts in a network (e.g.
> engineering department has extra routes defined for a lab network). As
> such, DHCP should be preferred.
> 
> However, there is also a matter of security. Both RA and DHCPv6 can be
> secured. If SEND is deployed, RA is more trustworthy than DHCP, so it
> should be preferred. Finally, there is such thing as secure DHCP, so if
> both RA and DHCP are secure, prefer SEND. I must admit that I never
> heard about any realistic deployments of secure DHCP, but it will change
> over time.
> 
> This approach can be summed as: favor secure, favor DHCP. Or to be more
> explicit, there's a complete list of all cases:
> a) RA vs DHCP => prefer DHCP
> b) RA(SEND) vs DHCP => prefer RA
> c) RA vs secure DHCP => prefer DHCP
> d) RA(SEND) vs secure DHCP => prefer DHCP
> 
> Does it sound reasonable?
> 
> This approach is very similar to what was described in DNS configuration
> over RA and DHCP (except the part about both RA and DHCP being secure
> that is not covered in RFC6106).
> 
> To summarize the discussion so far, Ted Lemon on MIF list agreed that
> DHCP should be preferred. Herman Singh on 6MAN list suggested to go look
> at what DNS over RA proposes and use the same approach. RFC6106, section
> 5.3.1covers cases a) and b). c) and d) are logical extension that takes
> DHCPv6 security into consideration. My understanding is that proposed
> solution will be satisfactory to everyone.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif

From Ted.Lemon@nominum.com  Sun Nov 13 18:22:59 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B43011E8115; Sun, 13 Nov 2011 18:22:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.551
X-Spam-Level: 
X-Spam-Status: No, score=-106.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HzyMtLcGYYFX; Sun, 13 Nov 2011 18:22:59 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD5D11E810E; Sun, 13 Nov 2011 18:22:55 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKTsB7fWhHzHSoYUKdTaD25od0/IRG6os3@postini.com; Sun, 13 Nov 2011 18:22:55 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0B8DB1B82B8; Sun, 13 Nov 2011 18:22:53 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EC26E190052; Sun, 13 Nov 2011 18:22:51 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sun, 13 Nov 2011 18:22:52 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Hui Deng <denghui02@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWro757
Date: Mon, 14 Nov 2011 02:22:51 +0000
Message-ID: <0AAC8A70-8D90-45EA-9EB7-14D9596BA99A@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: MIF Mailing List <mif@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:22:59 -0000

On Nov 14, 2011, at 9:46 AM, "Hui Deng" <denghui02@gmail.com> wrote:
> Finally, there is such thing as secure DHCP, so if
> both RA and DHCP are secure, prefer SEND. I must admit that I never
> heard about any realistic deployments of secure DHCP, but it will change
> over time.

This doesn't agree with the list of steps you gave subsequently.  I agree t=
o that list, but not to what is said here.  That is, if both DHCP and ND ar=
e secure, prefer DHCP. =

From Ted.Lemon@nominum.com  Sun Nov 13 18:24:43 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5081A11E812F; Sun, 13 Nov 2011 18:24:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.552
X-Spam-Level: 
X-Spam-Status: No, score=-106.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5wEhlOxK7Fef; Sun, 13 Nov 2011 18:24:39 -0800 (PST)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6071D11E812D; Sun, 13 Nov 2011 18:24:39 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKTsB75hyQMM1EIPgXAZI+xxzv48Q3CeCk@postini.com; Sun, 13 Nov 2011 18:24:39 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7B1421B82B5; Sun, 13 Nov 2011 18:24:38 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6DADC190052; Sun, 13 Nov 2011 18:24:38 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Sun, 13 Nov 2011 18:24:38 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3Mc=
Date: Mon, 14 Nov 2011 02:24:37 +0000
Message-ID: <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org>
In-Reply-To: <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:24:43 -0000

On Nov 14, 2011, at 9:59 AM, "Ole Troan" <otroan@employees.org> wrote:
> why not just merge all the information received?
> e.g. if you get DNS server over DHCP and RA, use all.
> if you get addresses via SLAAC and DHCP, you use all...

Because "just merge" is essentially equivalent to "just walk across the riv=
er without your feet getting wet.".  If you can write a spec that does this=
 correctly, you are probably the Messiah. =

From ichiroumakino@gmail.com  Sun Nov 13 18:27:11 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08C441F0C4E for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:27:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zy3G7BD9XmgD for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:27:10 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 780661F0C3C for <ipv6@ietf.org>; Sun, 13 Nov 2011 18:27:10 -0800 (PST)
Received: by ggnr5 with SMTP id r5so450356ggn.31 for <ipv6@ietf.org>; Sun, 13 Nov 2011 18:27:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=7jKQRok3NRL1H4tcfvOkvTIWOhEI8imWWHyf41HIe2c=; b=O6icECCf/RHqzTTrreg5EVNNB6b2OHFzT31C2iUVf1spwITaU4uKBKZulicyAwibTv M2jz/k3Tm0lc9zoskkuWjOXg1qyZvtH1fDsb9lyElBUW3qRhkTijTvPrhyLCMytI8tcO P4fxtB6aKuJ+S6+iIahBi1KHCNcGbgjM2t4xU=
Received: by 10.68.32.99 with SMTP id h3mr45718102pbi.38.1321237629835; Sun, 13 Nov 2011 18:27:09 -0800 (PST)
Received: from sjc-vpn4-250.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id b8sm52702432pba.16.2011.11.13.18.27.06 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 18:27:07 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1321236631.2514.48.camel@karl>
Date: Mon, 14 Nov 2011 10:27:02 +0800
Content-Transfer-Encoding: 7bit
Message-Id: <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl>
To: Karl Auer <kauer@biplane.com.au>
X-Mailer: Apple Mail (2.1084)
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:27:11 -0000

Karl,

>> why not just merge all the information received?
>> e.g. if you get DNS server over DHCP and RA, use all.
>> if you get addresses via SLAAC and DHCP, you use all...
> 
> It's about *conflict*, I think.
> 
> I.e., when  the information coming from RA and DHCP cannot be "merged" -
> for example, differing domain search lists, or default routing
> information.

can you give examples of what information cannot be merged?
certainly a default router list can be merged...

cheers,
Ole


From ichiroumakino@gmail.com  Sun Nov 13 18:30:09 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B409E11E814C; Sun, 13 Nov 2011 18:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18H+pg-0IfuY; Sun, 13 Nov 2011 18:30:09 -0800 (PST)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 2661F11E8146; Sun, 13 Nov 2011 18:30:09 -0800 (PST)
Received: by pzk5 with SMTP id 5so8385536pzk.9 for <multiple recipients>; Sun, 13 Nov 2011 18:30:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=OL/RTiy832CbrPkkX+uNSdoiKCy286kPwZVRx/C+bMg=; b=vu7hqD8xYWkgrJWZ8YpE7HfpC1NuwyqoX+B84qw4BYIfwoDR3w+s2s+yYFFKczW3DZ PaNQwushP99Bkcrl7qz8/yDfC92L90u8N+rvFK9CyOjWPBHyyflYxTKZytLuJG7BUkPj MfcSyyCzWbhiLMmlBxjtcH/nzm6KNo0Hc8kE4=
Received: by 10.68.7.9 with SMTP id f9mr34105931pba.47.1321237807839; Sun, 13 Nov 2011 18:30:07 -0800 (PST)
Received: from sjc-vpn4-250.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id b2sm52766995pbc.2.2011.11.13.18.30.04 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 18:30:06 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
Date: Mon, 14 Nov 2011 10:30:00 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:30:09 -0000

Ted,

>> why not just merge all the information received?
>> e.g. if you get DNS server over DHCP and RA, use all.
>> if you get addresses via SLAAC and DHCP, you use all...
>=20
> Because "just merge" is essentially equivalent to "just walk across =
the river without your feet getting wet.".  If you can write a spec that =
does this correctly, you are probably the Messiah.

isn't this what a host does anyway? if it has more than one router on =
the link?

cheers,
Ole


From Ted.Lemon@nominum.com  Sun Nov 13 18:32:44 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBED211E8156; Sun, 13 Nov 2011 18:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.553
X-Spam-Level: 
X-Spam-Status: No, score=-106.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsljRLCj2Ig8; Sun, 13 Nov 2011 18:32:44 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id D72E311E815D; Sun, 13 Nov 2011 18:32:42 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKTsB9ygQBkWaqH1t6aPuNOXtytBk/J6x4@postini.com; Sun, 13 Nov 2011 18:32:43 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 20CD61B82B4; Sun, 13 Nov 2011 18:32:42 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 140E2190052; Sun, 13 Nov 2011 18:32:42 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sun, 13 Nov 2011 18:32:42 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeAAIedAP//eqTG
Date: Mon, 14 Nov 2011 02:32:41 +0000
Message-ID: <BB7F1166-20DF-4ED3-A796-58453873FEA0@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org>
In-Reply-To: <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:32:44 -0000

On Nov 14, 2011, at 10:30 AM, "Ole Troan" <otroan@employees.org> wrote:
> isn't this what a host does anyway? if it has more than one router on the=
 link?

Yes, and they reliably do it wrong.  This is why we have a MIF working grou=
p!  :)=

From ichiroumakino@gmail.com  Sun Nov 13 18:35:49 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 077A81F0C84; Sun, 13 Nov 2011 18:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCnEjca8orum; Sun, 13 Nov 2011 18:35:48 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB751F0C82; Sun, 13 Nov 2011 18:35:48 -0800 (PST)
Received: by iaeo4 with SMTP id o4so8657083iae.31 for <multiple recipients>; Sun, 13 Nov 2011 18:35:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=CBVfHdjz0vFHC1HrrG60280fjyGcT2DWKjrPiHFihCY=; b=Pebfe+GChnxOhhhv6UWNRIjx3IPQaWwLqZPSTj7AFNrFWE/yriLs6jgPtWBbT6I0uX 4nOM6yATHVAOCdnZbUf7D5DKpDfiqJ9hGq8iHh7y/VxRLeWymCFBln1fzOHP1lC9V32H Bc5A6Uen9EaS8aPjJT294/RbgC0ESihaUO/us=
Received: by 10.42.154.194 with SMTP id r2mr20951585icw.50.1321238148016; Sun, 13 Nov 2011 18:35:48 -0800 (PST)
Received: from sjc-vpn4-250.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id n30sm28247533ibl.4.2011.11.13.18.35.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 18:35:46 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <BB7F1166-20DF-4ED3-A796-58453873FEA0@nominum.com>
Date: Mon, 14 Nov 2011 10:35:41 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DA6C509-3D10-4E56-A47C-2709030BE535@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org> <BB7F1166-20DF-4ED3-A796-58453873FEA0@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:35:49 -0000

>> isn't this what a host does anyway? if it has more than one router on =
the link?
>=20
> Yes, and they reliably do it wrong.  This is why we have a MIF working =
group!  :)

wouldn't they continue to do it wrong if we were to specify a default =
"policy"?
I'm in the camp of "use all the information you've got". the prefer one =
of the other by default, is heading down 3484 country, and that hasn't =
been a pleasant experience.

cheers,
Ole


From kauer@biplane.com.au  Sun Nov 13 18:47:44 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 440AC21F8546 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:47:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvRHA2qXgw0j for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 18:47:43 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6329E1F0C8B for <ipv6@ietf.org>; Sun, 13 Nov 2011 18:47:43 -0800 (PST)
Received: from eth4284.nsw.adsl.internode.on.net ([150.101.127.187] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1RPmaE-0006Lf-DA for ipv6@ietf.org; Sun, 13 Nov 2011 21:47:42 -0500
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
From: Karl Auer <kauer@biplane.com.au>
To: IETF IPv6 <ipv6@ietf.org>
In-Reply-To: <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl> <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-dBD+3PSBkGldJAphgaQ5"
Date: Mon, 14 Nov 2011 13:47:39 +1100
Message-ID: <1321238859.2514.73.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:47:44 -0000

--=-dBD+3PSBkGldJAphgaQ5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2011-11-14 at 10:27 +0800, Ole Troan wrote:
> can you give examples of what information cannot be merged?
> certainly a default router list can be merged...

If one source says that the domain search list is "a.com b.com c.com"
and another source says it is "c.com a.com b.com", how can you merge the
search lists?

Or if one source says that the default route is via IP address 1, and
the other source says that the default route is via IP address 2, which
IP address are you supposed to use as your default route? Sure, you can
set up two default routes - but when a packet turns up for which you
have no more specific route, which IP address will you send it to?
Something has to choose, using some criterion or other.

Some things cannot be merged - that's what "conflict" means.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-dBD+3PSBkGldJAphgaQ5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk7AgUsACgkQMAcU7Vc29od/4QCbBqCgnAOZiE0+zx3l0VFFGP+2
D0YAnjVCFgBd5WbgE1alnPfi/01lnfQm
=zTr6
-----END PGP SIGNATURE-----

--=-dBD+3PSBkGldJAphgaQ5--


From Ted.Lemon@nominum.com  Sun Nov 13 18:59:32 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0FBE11E819B; Sun, 13 Nov 2011 18:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rlbprWjbtrpR; Sun, 13 Nov 2011 18:59:32 -0800 (PST)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 02B9011E8198; Sun, 13 Nov 2011 18:59:31 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKTsCEE8kK+Vrx1n7JsE7t2C5d6O9FCj4k@postini.com; Sun, 13 Nov 2011 18:59:32 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 058C71B82B3; Sun, 13 Nov 2011 18:59:31 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 33506190052; Sun, 13 Nov 2011 18:59:27 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Sun, 13 Nov 2011 18:59:27 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeAAIedAP//eqTGgACG84D//4CHUQ==
Date: Mon, 14 Nov 2011 02:59:26 +0000
Message-ID: <8CF32B5B-3A57-46F7-AB16-A50B403F7595@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org> <BB7F1166-20DF-4ED3-A796-58453873FEA0@nominum.com>, <5DA6C509-3D10-4E56-A47C-2709030BE535@employees.org>
In-Reply-To: <5DA6C509-3D10-4E56-A47C-2709030BE535@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 02:59:33 -0000

On Nov 14, 2011, at 10:35 AM, "Ole Troan" <otroan@employees.org> wrote:
> wouldn't they continue to do it wrong if we were to specify a default "po=
licy"?
> I'm in the camp of "use all the information you've got". the prefer one o=
f the other by default, is heading down 3484 country, and that hasn't been =
a pleasant experience.

Great, then we can disband MIF and save everyone a lot of time!  All of the=
 various failure modes, DOS attacks and spoofing attacks that are possible =
in a MIF environment aren't all that important...  :)


From christopher.morrow@gmail.com  Sun Nov 13 19:06:53 2011
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59D441F0C94 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 19:06:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.54
X-Spam-Level: 
X-Spam-Status: No, score=-103.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8r+5nD1mULX8 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 19:06:52 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id C99AC1F0C43 for <ipv6@ietf.org>; Sun, 13 Nov 2011 19:06:52 -0800 (PST)
Received: by iaeo4 with SMTP id o4so8685745iae.31 for <ipv6@ietf.org>; Sun, 13 Nov 2011 19:06:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lfH5uf9NcnnpweCS31u7eoBkhj2AQcwbg8cSM+JWqLw=; b=t9489R2nD9CIXBPESfxC6v9eEQULw1RbXlvD4H/V8O+Orbn7ZGetCiJKhaB+J7B/3D g9/QoICV7VDvzodkZXzqO5qIUWiDe5Ld7CMwdppEh7aXgw8/vrSb+9TYuvNp12yzep5q O6NDSxja10ZkF8Ur4xrPB3tSGcXQ0xv3p7scw=
MIME-Version: 1.0
Received: by 10.50.202.100 with SMTP id kh4mr21307947igc.41.1321240012472; Sun, 13 Nov 2011 19:06:52 -0800 (PST)
Received: by 10.231.202.142 with HTTP; Sun, 13 Nov 2011 19:06:52 -0800 (PST)
In-Reply-To: <20110926220044.GJ2931@verdi>
References: <4E7FDEFA.6060808@gmail.com> <20110926143849.GH2931@verdi> <4E80DBCD.1040308@gmail.com> <20110926220044.GJ2931@verdi>
Date: Sun, 13 Nov 2011 22:06:52 -0500
Message-ID: <CAL9jLaa1nS7Dz5CQnpGKHVGoYdp6rNLR7AdXosYeF3EbpjiOuA@mail.gmail.com>
Subject: Re: Offset Indicating option
From: Christopher Morrow <christopher.morrow@gmail.com>
To: John Leslie <john@jlc.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 03:06:53 -0000

Just a question about this idea in general, if one of the reasons to
do it is to save middleboxes from doing 'lots of work' ... wouldn't a
smart attacker just not put this header in? and then choke the
middleboxes?

what's the incentive for a source to add this header? (it's not in
their interest to make things 'easier' is it?)

-chris
(interesting discussion at the meeting, thanks!)

From brian.e.carpenter@gmail.com  Sun Nov 13 19:15:48 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F12821F0CAD for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 19:15:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.52
X-Spam-Level: 
X-Spam-Status: No, score=-103.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gSiETrnLXeNz for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 19:15:48 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 763971F0CC2 for <ipv6@ietf.org>; Sun, 13 Nov 2011 19:15:48 -0800 (PST)
Received: by ywt34 with SMTP id 34so4240714ywt.31 for <ipv6@ietf.org>; Sun, 13 Nov 2011 19:15:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Froy3t59fe45N9VtWkiq5yu5Gx9SqvV/caL752jMOEc=; b=Z2UCLoF4PiN3fevXokds2/tx4dq9IXf8t6uL/WllkYqvJ6Zw6awXLqyBIdg6pCdJUd 2+gxlaFPi2A/yRiDHrbJd5cw1I/Iq2p0VENDHF0M2cQ5vmC52sowU47iRMBOBHEfNQz+ r8Zs2DMpp1aiCvQdkisJN1u1pWe/4iMQz8JEE=
Received: by 10.236.195.4 with SMTP id o4mr11791321yhn.6.1321240548043; Sun, 13 Nov 2011 19:15:48 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id 4sm57202896ano.9.2011.11.13.19.15.45 (version=SSLv3 cipher=OTHER); Sun, 13 Nov 2011 19:15:47 -0800 (PST)
Message-ID: <4EC087DE.8050204@gmail.com>
Date: Mon, 14 Nov 2011 16:15:42 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
Subject: Re: Offset Indicating option
References: <4E7FDEFA.6060808@gmail.com>	<20110926143849.GH2931@verdi>	<4E80DBCD.1040308@gmail.com>	<20110926220044.GJ2931@verdi> <CAL9jLaa1nS7Dz5CQnpGKHVGoYdp6rNLR7AdXosYeF3EbpjiOuA@mail.gmail.com>
In-Reply-To: <CAL9jLaa1nS7Dz5CQnpGKHVGoYdp6rNLR7AdXosYeF3EbpjiOuA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 03:15:49 -0000

Chris,

On 2011-11-14 16:06, Christopher Morrow wrote:
> Just a question about this idea in general, if one of the reasons to
> do it is to save middleboxes from doing 'lots of work' ... wouldn't a
> smart attacker just not put this header in? and then choke the
> middleboxes?

I could use that argument against *any* optimisation, couldn't I?
DoS is hard to defeat.

> 
> what's the incentive for a source to add this header? (it's not in
> their interest to make things 'easier' is it?)

Well, you can argue that it's a small price to get a small improvement
in response time from busy servers, but I agree, this would be a matter
of persuading stack vendors to do it because it's good to do it.

   Brian

> -chris
> (interesting discussion at the meeting, thanks!)
> 

From marka@isc.org  Sun Nov 13 19:28:07 2011
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B156C1F0CC4 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 19:28:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lYj69kRBAWfA for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 19:28:05 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 112131F0C47 for <ipv6@ietf.org>; Sun, 13 Nov 2011 19:28:04 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 54BCB5F9865; Mon, 14 Nov 2011 03:27:49 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 1A077216C6E; Mon, 14 Nov 2011 03:27:47 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id CFE7F1717457; Mon, 14 Nov 2011 14:27:44 +1100 (EST)
To: Karl Auer <kauer@biplane.com.au>
From: Mark Andrews <marka@isc.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl> <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org> <1321238859.2514.73.camel@karl>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
In-reply-to: Your message of "Mon, 14 Nov 2011 13:47:39 +1100." <1321238859.2514.73.camel@karl>
Date: Mon, 14 Nov 2011 14:27:44 +1100
Message-Id: <20111114032744.CFE7F1717457@drugs.dv.isc.org>
Cc: IETF IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 03:28:07 -0000

In message <1321238859.2514.73.camel@karl>, Karl Auer writes:
> 
> On Mon, 2011-11-14 at 10:27 +0800, Ole Troan wrote:
> > can you give examples of what information cannot be merged?
> > certainly a default router list can be merged...
> 
> If one source says that the domain search list is "a.com b.com c.com"
> and another source says it is "c.com a.com b.com", how can you merge the
> search lists?

Anyone depending apon search lists that they did not set already
has a broken configuration.  Anyone depending apon search lists in
RA's or DHCP messages being honoured by machines already has a
broken configuration.

Search lists are things that should be set by users for themselves.

ISP's SHOULD NOT be setting search lists in DHCP responses to
customers.  Hotspots's SHOULD NOT be setting search lists in DHCP
responses to customers.

Enterprises MAY advertise a search lists when configuring their own
machines.  Homes MAY advertise a search lists when configuring their
own machines.

Enterprises and homes SHOULD NOT set search lists when responding
to DHCP queries on guest networks.

Similarly for RA's.

> Or if one source says that the default route is via IP address 1, and
> the other source says that the default route is via IP address 2, which
> IP address are you supposed to use as your default route? Sure, you can
> set up two default routes - but when a packet turns up for which you
> have no more specific route, which IP address will you send it to?
> Something has to choose, using some criterion or other.

If they are both true "default routers" then it doesn't matter which
you send to.  If they are not then there is nothing a machine can
do automatically.

> Some things cannot be merged - that's what "conflict" means.
> 
> Regards, K.
> 
> --=20
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
> http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)
> 
> GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
> Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156
> 
> --=-dBD+3PSBkGldJAphgaQ5
> Content-Type: application/pgp-signature; name="signature.asc"
> Content-Description: This is a digitally signed message part
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> 
> iEYEABECAAYFAk7AgUsACgkQMAcU7Vc29od/4QCbBqCgnAOZiE0+zx3l0VFFGP+2
> D0YAnjVCFgBd5WbgE1alnPfi/01lnfQm
> =zTr6
> -----END PGP SIGNATURE-----
> 
> --=-dBD+3PSBkGldJAphgaQ5--
> 
> 
> --===============7419444934332968338==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> --===============7419444934332968338==--
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From christopher.morrow@gmail.com  Sun Nov 13 19:41:50 2011
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5674A21F8A91 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 19:41:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.547
X-Spam-Level: 
X-Spam-Status: No, score=-103.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id inJ4rfIz2S-J for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 19:41:49 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id CCA9F21F8A70 for <ipv6@ietf.org>; Sun, 13 Nov 2011 19:41:49 -0800 (PST)
Received: by iaeo4 with SMTP id o4so8716928iae.31 for <ipv6@ietf.org>; Sun, 13 Nov 2011 19:41:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YZ5SdDIRxRhmGl/gfDA2HXhR+3bWltIsHiAbcWpm11w=; b=w31V4IE/s4oIVcM6cCfgvSPClPAR3OMzZXZsiG9g7+W5ZWfJ7QXpKJAoQ3hof4AT7c xi+hg9Xgsy6pR7G+vH2hrQMILiEyjJm4fjO7THnLEjpGJkpIHdRafqmmKinoavq1XK91 5y3yEvJ54RNirZU0g6athBJEg+fMOfVcuR9zM=
MIME-Version: 1.0
Received: by 10.231.41.4 with SMTP id m4mr4831194ibe.44.1321242109417; Sun, 13 Nov 2011 19:41:49 -0800 (PST)
Received: by 10.231.202.142 with HTTP; Sun, 13 Nov 2011 19:41:49 -0800 (PST)
In-Reply-To: <4EC087DE.8050204@gmail.com>
References: <4E7FDEFA.6060808@gmail.com> <20110926143849.GH2931@verdi> <4E80DBCD.1040308@gmail.com> <20110926220044.GJ2931@verdi> <CAL9jLaa1nS7Dz5CQnpGKHVGoYdp6rNLR7AdXosYeF3EbpjiOuA@mail.gmail.com> <4EC087DE.8050204@gmail.com>
Date: Sun, 13 Nov 2011 22:41:49 -0500
Message-ID: <CAL9jLaaC+vdBSAn895Fz_8AC0FF3L9d=ijzUO3SNcb+X03hm9A@mail.gmail.com>
Subject: Re: Offset Indicating option
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 03:41:50 -0000

On Sun, Nov 13, 2011 at 10:15 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Chris,
>
> On 2011-11-14 16:06, Christopher Morrow wrote:
>> Just a question about this idea in general, if one of the reasons to
>> do it is to save middleboxes from doing 'lots of work' ... wouldn't a
>> smart attacker just not put this header in? and then choke the
>> middleboxes?
>
> I could use that argument against *any* optimisation, couldn't I?
> DoS is hard to defeat.

yes... it's not super hard :) but I get your point. The addition of an
assumption that middleboxes need/want/will-use this is part of my
weird feeling about this idea.

>
>>
>> what's the incentive for a source to add this header? (it's not in
>> their interest to make things 'easier' is it?)
>
> Well, you can argue that it's a small price to get a small improvement
> in response time from busy servers, but I agree, this would be a matter
> of persuading stack vendors to do it because it's good to do it.

ok. still seems odd to me :) but sure.

>> -chris
>> (interesting discussion at the meeting, thanks!)
>>
>

From kauer@biplane.com.au  Sun Nov 13 20:04:57 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9A211E81CD for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 20:04:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WG3QAtOgrkeK for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 20:04:56 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by ietfa.amsl.com (Postfix) with ESMTP id 29AFA11E81CC for <ipv6@ietf.org>; Sun, 13 Nov 2011 20:04:55 -0800 (PST)
Received: from eth4284.nsw.adsl.internode.on.net ([150.101.127.187] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1RPnmv-00049m-V2 for ipv6@ietf.org; Sun, 13 Nov 2011 23:04:54 -0500
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
From: Karl Auer <kauer@biplane.com.au>
To: IETF IPv6 <ipv6@ietf.org>
In-Reply-To: <20111114032744.CFE7F1717457@drugs.dv.isc.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl> <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org> <1321238859.2514.73.camel@karl> <20111114032744.CFE7F1717457@drugs.dv.isc.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-rLNcCq4ztG/I3Ipn7a3j"
Date: Mon, 14 Nov 2011 15:04:51 +1100
Message-ID: <1321243491.2514.99.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 04:04:57 -0000

--=-rLNcCq4ztG/I3Ipn7a3j
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2011-11-14 at 14:27 +1100, Mark Andrews wrote:
> Anyone depending apon search lists that they did not set already
> has a broken configuration.

I didn't say people should do these things, just that there are things
that *can be* delivered via RA and that *can be* delivered via DHCP, and
that *can conflict*.

If things do conflict, then something has to decide, on some criterion
or other, which to honour (or to honour neither of course).

My post was in answer to a question from someone about about how things
could conflict. That's all.

> Enterprises MAY advertise a search lists when configuring their own
> machines.  Homes MAY advertise a search lists when configuring their
> own machines.

Well - yes. And if their DHCP server says one thing and their RAs are
saying another, then there should be a sane default for deciding which
to use. That's all this is about.

Regards, K.
=20
--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-rLNcCq4ztG/I3Ipn7a3j
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk7Ak10ACgkQMAcU7Vc29oeojACggef6XicwBa2uA4EK0tUbGcXU
l5EAnRwFuPKOjLaOwj1Cy7Crk53HyRzy
=L6x4
-----END PGP SIGNATURE-----

--=-rLNcCq4ztG/I3Ipn7a3j--


From dougb@dougbarton.us  Sun Nov 13 20:10:15 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F3921F88AB for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 20:10:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.44
X-Spam-Level: 
X-Spam-Status: No, score=-3.44 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ag9LhoY8cwIA for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 20:10:14 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4F61421F863E for <ipv6@ietf.org>; Sun, 13 Nov 2011 20:10:07 -0800 (PST)
Received: (qmail 13580 invoked by uid 399); 14 Nov 2011 04:10:03 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 14 Nov 2011 04:10:03 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4EC09499.4020105@dougbarton.us>
Date: Sun, 13 Nov 2011 20:10:01 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111110 Thunderbird/8.0
MIME-Version: 1.0
To: Karl Auer <kauer@biplane.com.au>
Subject: Re: Conflict between RA and DHCP in MIF case
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl> <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org> <1321238859.2514.73.camel@karl> <20111114032744.CFE7F1717457@drugs.dv.isc.org> <1321243491.2514.99.camel@karl>
In-Reply-To: <1321243491.2514.99.camel@karl>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 04:10:15 -0000

On 11/13/2011 20:04, Karl Auer wrote:
> I didn't say people should do these things, just that there are things
> that *can be* delivered via RA and that *can be* delivered via DHCP, and
> that *can conflict*.

Given that this is a configuration error by definition, why can't we
just say that the behavior under these circumstances is undefined?


Doug

-- 

		"We could put the whole Internet into a book."
		"Too practical."

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From marka@isc.org  Sun Nov 13 20:55:01 2011
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD76D11E8192 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 20:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4h2vnQAWN58l for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 20:55:00 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 3E88911E8186 for <ipv6@ietf.org>; Sun, 13 Nov 2011 20:55:00 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 54F795F98A2; Mon, 14 Nov 2011 04:54:46 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 0E310216C6F; Mon, 14 Nov 2011 04:54:44 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 393AC1717E89; Mon, 14 Nov 2011 15:54:41 +1100 (EST)
To: Karl Auer <kauer@biplane.com.au>
From: Mark Andrews <marka@isc.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl> <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org> <1321238859.2514.73.camel@karl> <20111114032744.CFE7F1717457@drugs.dv.isc.org> <1321243491.2514.99.camel@karl>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
In-reply-to: Your message of "Mon, 14 Nov 2011 15:04:51 +1100." <1321243491.2514.99.camel@karl>
Date: Mon, 14 Nov 2011 15:54:41 +1100
Message-Id: <20111114045441.393AC1717E89@drugs.dv.isc.org>
Cc: IETF IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 04:55:02 -0000

In message <1321243491.2514.99.camel@karl>, Karl Auer writes:
> On Mon, 2011-11-14 at 14:27 +1100, Mark Andrews wrote:
> > Anyone depending apon search lists that they did not set already
> > has a broken configuration.
> 
> I didn't say people should do these things, just that there are things
> that *can be* delivered via RA and that *can be* delivered via DHCP, and
> that *can conflict*.
> 
> If things do conflict, then something has to decide, on some criterion
> or other, which to honour (or to honour neither of course).
> 
> My post was in answer to a question from someone about about how things
> could conflict. That's all.
> 
> > Enterprises MAY advertise a search lists when configuring their own
> > machines.  Homes MAY advertise a search lists when configuring their
> > own machines.
> 
> Well - yes. And if their DHCP server says one thing and their RAs are
> saying another, then there should be a sane default for deciding which
> to use. That's all this is about.

Just let implementations pick one and stick with it until it changes.
Difference *will* occur as a matter of operational practice whenever
the list is changed so this isn't a error condition unless it
continues for a long time.  If you update the DHCP server the RA
will be out of date.  If you update the RA first the DHCP server
will be out of date.

> Regards, K.
> =20
> --=20
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
> http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)
> 
> GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
> Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From Dmitry.Anipko@microsoft.com  Sun Nov 13 21:21:20 2011
Return-Path: <Dmitry.Anipko@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB0381F0C42 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 21:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f2vfipoQFbmx for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 21:21:17 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0D61F0C44 for <ipv6@ietf.org>; Sun, 13 Nov 2011 21:21:16 -0800 (PST)
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sun, 13 Nov 2011 21:21:11 -0800
Received: from TK5EX14MBXC266.redmond.corp.microsoft.com ([169.254.2.128]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.01.0355.003; Sun, 13 Nov 2011 21:21:11 -0800
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Thread-Topic: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Thread-Index: AcyijTWX59zcnPnKTYaF1gdIRytzuw==
Date: Mon, 14 Nov 2011 05:21:11 +0000
Message-ID: <03FE6A726D13284495EF1787D25F1DF9018D7907@TK5EX14MBXC266.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.71]
Content-Type: multipart/alternative; boundary="_000_03FE6A726D13284495EF1787D25F1DF9018D7907TK5EX14MBXC266r_"
MIME-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 05:21:22 -0000

--_000_03FE6A726D13284495EF1787D25F1DF9018D7907TK5EX14MBXC266r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

I have a question about this text the -01 revision:

>>A node MAY use OPTION_DASP in any of the following two cases:
                 1: The address selection option is delivered across a secu=
re, trusted
                    channel.

The OPTION_DASP is configured by a network administrator, presumably based =
on some knowledge they have about what makes more or less sense in the part=
icular network. How whether or not a secure channel has been used on one of=
 the networks relates to whether or not the admin of that network has knowl=
edge of a completely different network the host may simultaneously be conne=
cted to?

Thanks,
Dmitry



--_000_03FE6A726D13284495EF1787D25F1DF9018D7907TK5EX14MBXC266r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:q=3D"http://schema=
s.xmlsoap.org/soap/envelope/" xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig=
#" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xmlns:m=3D"http:=
//schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/=
REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal">Hello,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have a question about this text the -01 revision:<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&gt;&gt;A node MAY use OPTION_DASP in any of the fol=
lowing two cases:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; 1: The address selection option is =
delivered across a secure, trusted&nbsp;&nbsp;&nbsp;
<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; channel.&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The OPTION_DASP is configured by a network administr=
ator, presumably based on some knowledge they have about what makes more or=
 less sense in the particular network. How whether or not a secure channel =
has been used on one of the networks
 relates to whether or not the admin of that network has knowledge of a com=
pletely different network the host may simultaneously be connected to?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Dmitry<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_03FE6A726D13284495EF1787D25F1DF9018D7907TK5EX14MBXC266r_--

From shemant@cisco.com  Sun Nov 13 21:52:06 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E0E11E81E6 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 21:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.145
X-Spam-Level: 
X-Spam-Status: No, score=-6.145 tagged_above=-999 required=5 tests=[AWL=0.453,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPZ87qKi+YlB for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 21:52:04 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id A130311E81E4 for <ipv6@ietf.org>; Sun, 13 Nov 2011 21:52:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=11567; q=dns/txt; s=iport; t=1321249923; x=1322459523; h=mime-version:subject:date:message-id:from:to:cc; bh=cHVZjD6dBa9otJXn1pYiq0yPc4YwZvP9cjXzYWgAiNE=; b=WrjgBtW+wqRGu84Bwv/Z6CN5KKrjI+4zuUx/SzojBXxmZu+WqActxEjx zvKlVzsScEihpAbUp9rob0wdTCf6ilYCVQ8fOsy/UX8FhRERboIJ/WinI h0G/LLAIBhQ0NySqssj/7fOpkRdRzLus7s08dKF7NFiAlsFUhavooFzzh I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHmrwE6tJXHB/2dsb2JhbABCqX2BBYF0AQQSAQkRA0kSASoGGAdXAQQbGqElAZ1EiRxjBIgQkWKMVA
X-IronPort-AV: E=Sophos;i="4.69,506,1315180800"; d="scan'208,217";a="35609595"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-3.cisco.com with ESMTP; 14 Nov 2011 05:52:03 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id pAE5q3JI026929;  Mon, 14 Nov 2011 05:52:03 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 13 Nov 2011 23:52:03 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCA291.8849E8FE"
Subject: further responses for comments at the mic in 6man for draft-hsingh-6man-enhanced-dad-02.txt
Date: Sun, 13 Nov 2011 23:51:58 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303494B7C@XMB-RCD-109.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: further responses for comments at the mic in 6man for draft-hsingh-6man-enhanced-dad-02.txt
Thread-Index: AcyikYXqCmkayE20RKKfY9DN+0mBxw==
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 14 Nov 2011 05:52:03.0032 (UTC) FILETIME=[88766580:01CCA291]
Cc: cheshire@apple.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 05:52:06 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCA291.8849E8FE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

Thanks for the comments at the mic.  Here is the closure.

1.	Lee Howard - am not sure if the two examples presented (and
listed in the doc) are different examples showing two different problems
or two example showing the same problem.
	=09
		Both examples relate to reflected DAD probes received by
an interface on a router. However the problem space is different.  One
is a network Loopback test and the other is the setup in a home with two
broadband modems in served by the same SP.  The Cisco CMTS actually hit
this problem already in a CMTS IPv6 deployment.  I can talk to Lee and
see what text to edit to clarify.
	=09
2.	Stuart - can we do without the nonce for catching reflected DAD
probes? =20
	=09
		I talked to Stuart after the presentation and Stuart
understands why we need the nonce.  A reflected DAD probe or a DAD probe
sent by a genuine duplicate node are identical and the nonce separates
the two cases.
	=09
3.	Suresh - comments on the "Changes to RFC 4862" titled slide in
the presentation.  The text needs work for router vs. ...

	I already replied during the presentation the router in the text
is a router as specified in RFC 4861 vs. a host defined in the same
document.  Please suggest what change we can make to the text in the
document.  The text from section 4.5 is shown below.
	=09
   [4.5.  Changes to RFC 4862

   The following text is added to [RFC4862] at a yet to be determined
   location in [RFC4862].

   A router that supports IPv6 DAD MUST implement the detection of
   looped back NS messages during DAD operation as specified in this
   document.  A network interface on any other IPv6 node that is not a
   router SHOULD implement the detection of looped back NS messages
   during DAD operation as specified in this document.]

Thanks,

Hemant

------_=_NextPart_001_01CCA291.8849E8FE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7655.10">
<TITLE>further responses for comments at the mic in 6man for =
draft-hsingh-6man-enhanced-dad-02.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">Folks,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Thanks =
for</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
FACE=3D"Courier New">the</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> comments at the mic.&nbsp; =
Here is the closure.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">Lee Howard</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">&#8211;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> am</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">not sure if the two examples presented (and listed in the doc) are =
different examples showing two different problems or two example showing =
the same problem.</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Both =
examples relate to reflected DAD probes received by an =
inte</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">rface on a router. However the problem space is =
different</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New">.&nbsp; One is a network =
Loopback test and the other is the setup in a</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">home with two broadband modems in served by the same SP.&nbsp; The =
Cisco CMTS actually hit this problem already in a CMTS IPv6 =
deployment.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New">&nbsp; I can talk to Lee =
and</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
FACE=3D"Courier New">see what text to edit to =
clarify.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
</UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">Stuart</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">&#8211;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> can we do without the nonce =
for catching reflected DAD probes?&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> </SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">I</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT FACE=3D"Courier New">talked</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">to Stuart after the presentation and =
Stuart</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> =
understands</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> why we need the nonce.&nbsp; =
A reflected DAD probe or a DAD probe sent by a genuine duplicate node =
are identical and the nonce separates the two cases.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
</UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">Suresh - comments on the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">&#8220;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New">Changes to RFC =
4862</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">&#8221;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New"> =
titled slide in the presentation.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us">&nbsp;<FONT FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">The text needs work for router =
vs.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
FACE=3D"Courier New">&#8230;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>
<UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Courier New">I already replied</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">during</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> the =
presentation</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT FACE=3D"Courier New">the router in the text is =
a</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
FACE=3D"Courier New">router as specified in RFC 4861 vs. a host defined =
in the same document.&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT FACE=3D"Courier =
New">P</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New">lease =
suggest</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"> what change we can make to =
the text in the document.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New"></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us">&nbsp;<FONT FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT FACE=3D"Courier New">The text from section 4.5 is shown =
below.</FONT></SPAN></P>
<UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>
</UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Courier New">&nbsp;&nbsp; [</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">4.5.&nbsp; Changes to =
RFC 4862</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp; The following text is added to [RFC4862] at a yet to =
be determined</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp; location in [RFC4862].</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp; A router that supports IPv6 DAD MUST implement the =
detection of</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp; looped back NS messages during DAD operation as =
specified in this</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp; document.&nbsp; A network interface on any other IPv6 =
node that is not a</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp; router SHOULD implement the detection of looped back =
NS messages</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp; during DAD operation as specified in this =
document.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Courier New">]</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">Thanks,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier =
New">Hemant</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01CCA291.8849E8FE--

From shemant@cisco.com  Sun Nov 13 22:05:05 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1560C11E8200 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 22:05:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.152
X-Spam-Level: 
X-Spam-Status: No, score=-6.152 tagged_above=-999 required=5 tests=[AWL=0.448,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ah1X2CsMjSN0 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 22:05:03 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 1220C11E81F9 for <ipv6@ietf.org>; Sun, 13 Nov 2011 22:05:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2120; q=dns/txt; s=iport; t=1321250703; x=1322460303; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=BVJGbyw98T7hiG8tpGbh0xCEwvDGoBh13FBJfeDTeaw=; b=fPqlzXaFB5pAYLdqjq3YSz+9MbreW92SSVvtrkFKDpg5zmLWBrGIbOae hKv+fxLygLWHA19osmzTCOCnh2ulgTbdTc3awMYcEPzPyFUA5jwiFg6ru hde6Tty/YCOvXGmo5/r0GVtgsbcXlWnbmBW7NWzDnk2JiH+jgRknle+Up I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYAAEquwE6tJV2Y/2dsb2JhbABChQCUd48FgQGBBYFyAQEBAwESARANBEoHBAIBCA4DBAEBAQICBgYXAQICAgEBRAkIAQEEARIIGodgmVoBjFmQbIEwhzkzYwSIEJFihQiHTA
X-IronPort-AV: E=Sophos;i="4.69,506,1315180800"; d="scan'208";a="35626243"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-7.cisco.com with ESMTP; 14 Nov 2011 06:05:02 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAE652vx010141;  Mon, 14 Nov 2011 06:05:02 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Nov 2011 00:05:02 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Subject: RE: [dhcwg] Conflict between RA and DHCP in MIF case
Date: Mon, 14 Nov 2011 00:04:58 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303494B7D@XMB-RCD-109.cisco.com>
In-Reply-To: <1321243491.2514.99.camel@karl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AcyigpXThlFok+JqTQqwRlbuq638ewAELc4g
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com><402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org><1321236631.2514.48.camel@karl><AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org><1321238859.2514.73.camel@karl><20111114032744.CFE7F1717457@drugs.dv.isc.org> <1321243491.2514.99.camel@karl>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Karl Auer" <kauer@biplane.com.au>, "IETF IPv6" <ipv6@ietf.org>
X-OriginalArrivalTime: 14 Nov 2011 06:05:02.0479 (UTC) FILETIME=[590C91F0:01CCA293]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 06:05:05 -0000

KzEgdG8gS2FybCdzIGVtYWlscy4NCg0KSGVtYW50DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBpcHY2LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppcHY2LWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBLYXJsIEF1ZXINClNlbnQ6IE1vbmRheSwgTm92ZW1iZXIgMTQs
IDIwMTEgMTI6MDUgUE0NClRvOiBJRVRGIElQdjYNClN1YmplY3Q6IFJlOiBbZGhjd2ddIENvbmZs
aWN0IGJldHdlZW4gUkEgYW5kIERIQ1AgaW4gTUlGIGNhc2UNCg0KT24gTW9uLCAyMDExLTExLTE0
IGF0IDE0OjI3ICsxMTAwLCBNYXJrIEFuZHJld3Mgd3JvdGU6DQo+IEFueW9uZSBkZXBlbmRpbmcg
YXBvbiBzZWFyY2ggbGlzdHMgdGhhdCB0aGV5IGRpZCBub3Qgc2V0IGFscmVhZHkgaGFzIGEgDQo+
IGJyb2tlbiBjb25maWd1cmF0aW9uLg0KDQpJIGRpZG4ndCBzYXkgcGVvcGxlIHNob3VsZCBkbyB0
aGVzZSB0aGluZ3MsIGp1c3QgdGhhdCB0aGVyZSBhcmUgdGhpbmdzIHRoYXQgKmNhbiBiZSogZGVs
aXZlcmVkIHZpYSBSQSBhbmQgdGhhdCAqY2FuIGJlKiBkZWxpdmVyZWQgdmlhIERIQ1AsIGFuZCB0
aGF0ICpjYW4gY29uZmxpY3QqLg0KDQpJZiB0aGluZ3MgZG8gY29uZmxpY3QsIHRoZW4gc29tZXRo
aW5nIGhhcyB0byBkZWNpZGUsIG9uIHNvbWUgY3JpdGVyaW9uIG9yIG90aGVyLCB3aGljaCB0byBo
b25vdXIgKG9yIHRvIGhvbm91ciBuZWl0aGVyIG9mIGNvdXJzZSkuDQoNCk15IHBvc3Qgd2FzIGlu
IGFuc3dlciB0byBhIHF1ZXN0aW9uIGZyb20gc29tZW9uZSBhYm91dCBhYm91dCBob3cgdGhpbmdz
IGNvdWxkIGNvbmZsaWN0LiBUaGF0J3MgYWxsLg0KDQo+IEVudGVycHJpc2VzIE1BWSBhZHZlcnRp
c2UgYSBzZWFyY2ggbGlzdHMgd2hlbiBjb25maWd1cmluZyB0aGVpciBvd24gDQo+IG1hY2hpbmVz
LiAgSG9tZXMgTUFZIGFkdmVydGlzZSBhIHNlYXJjaCBsaXN0cyB3aGVuIGNvbmZpZ3VyaW5nIHRo
ZWlyIA0KPiBvd24gbWFjaGluZXMuDQoNCldlbGwgLSB5ZXMuIEFuZCBpZiB0aGVpciBESENQIHNl
cnZlciBzYXlzIG9uZSB0aGluZyBhbmQgdGhlaXIgUkFzIGFyZSBzYXlpbmcgYW5vdGhlciwgdGhl
biB0aGVyZSBzaG91bGQgYmUgYSBzYW5lIGRlZmF1bHQgZm9yIGRlY2lkaW5nIHdoaWNoIHRvIHVz
ZS4gVGhhdCdzIGFsbCB0aGlzIGlzIGFib3V0Lg0KDQpSZWdhcmRzLCBLLg0KIA0KLS0NCn5+fn5+
fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+
fn5+fn5+fn5+DQpLYXJsIEF1ZXIgKGthdWVyQGJpcGxhbmUuY29tLmF1KSAgICAgICAgICAgICAg
ICAgICArNjEtMi02NDk1NzE2MCAoaCkNCmh0dHA6Ly93d3cuYmlwbGFuZS5jb20uYXUva2F1ZXIv
ICAgICAgICAgICAgICAgICAgICs2MS00MjgtOTU3MTYwIChtb2IpDQoNCkdQRyBmaW5nZXJwcmlu
dDogREE0MSA1MUIxIDE0ODEgMTZFMSBGN0UyIEIyRTkgMzAwNyAxNEVEIDU3MzYgRjY4NyBPbGQg
ZmluZ2VycHJpbnQ6IEIzODYgNzgxOSBCMjI3IDI5NjEgODMwMSBDNUE5IDJFQkMgNzU0QiBDRDk3
IDAxNTYNCg==

From shemant@cisco.com  Sun Nov 13 22:13:10 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50C611E80AB for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 22:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.158
X-Spam-Level: 
X-Spam-Status: No, score=-6.158 tagged_above=-999 required=5 tests=[AWL=0.441,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jLu9y-VRfhzb for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 22:13:09 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id B3D3111E80A6 for <ipv6@ietf.org>; Sun, 13 Nov 2011 22:13:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2393; q=dns/txt; s=iport; t=1321251189; x=1322460789; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=se10v8415632WC6C0jzd3LbrcK6Vhwr8GDjz8gH6tTo=; b=B0YV5KtqeRfMYWzSVB9hBICVLkP9ODLD4iBUSIT5JkKCHxI1qB+bEkB1 mh5JFPGuuKSIwnYRIRTopyo8rcgf3Z4WJRjRA5BLIs54t1/YJWcya9Nu+ PDLsLhLf8o02P1RuPmDtUbn2UAve/vejIrUEIwO69OdeFP41Jj8MDHM9T 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYAAKWwwE6tJXHA/2dsb2JhbABCmXeQBoEFgXIBAQEDAQEBAQ8BHQo0EAcEAgEIEQQBAQEKBhcBBgEmHwkIAQEEARIIGodgCJlKAZ1FiRxjBIgQkWKFCIdM
X-IronPort-AV: E=Sophos;i="4.69,506,1315180800"; d="scan'208";a="35628715"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 14 Nov 2011 06:13:09 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id pAE6D9sv025726;  Mon, 14 Nov 2011 06:13:09 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Nov 2011 00:13:09 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Conflict between RA and DHCP in MIF case
Date: Mon, 14 Nov 2011 00:13:07 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303494B7E@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303494B7D@XMB-RCD-109.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AcyigpXThlFok+JqTQqwRlbuq638ewAELc4gAAAu4GA=
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com><402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org><1321236631.2514.48.camel@karl><AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org><1321238859.2514.73.camel@karl><20111114032744.CFE7F1717457@drugs.dv.isc.org><1321243491.2514.99.camel@karl> <5B6B2B64C9FE2A489045EEEADDAFF2C303494B7D@XMB-RCD-109.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, "Karl Auer" <kauer@biplane.com.au>, "IETF IPv6" <ipv6@ietf.org>
X-OriginalArrivalTime: 14 Nov 2011 06:13:09.0136 (UTC) FILETIME=[7B1E8900:01CCA294]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 06:13:10 -0000

If a correct source is not chosen the return path may not be symmetric
and cause issues to the subscriber.  For example native IPv6 and 6rd are
running concurrently in a home served by broadband access.

I can't see how can routing information from two sources be merged if
there is a conflict.

Hemant

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Hemant Singh (shemant)
Sent: Monday, November 14, 2011 2:05 PM
To: Karl Auer; IETF IPv6
Subject: RE: [dhcwg] Conflict between RA and DHCP in MIF case

+1 to Karl's emails.

Hemant

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Karl Auer
Sent: Monday, November 14, 2011 12:05 PM
To: IETF IPv6
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case

On Mon, 2011-11-14 at 14:27 +1100, Mark Andrews wrote:
> Anyone depending apon search lists that they did not set already has a

> broken configuration.

I didn't say people should do these things, just that there are things
that *can be* delivered via RA and that *can be* delivered via DHCP, and
that *can conflict*.

If things do conflict, then something has to decide, on some criterion
or other, which to honour (or to honour neither of course).

My post was in answer to a question from someone about about how things
could conflict. That's all.

> Enterprises MAY advertise a search lists when configuring their own=20
> machines.  Homes MAY advertise a search lists when configuring their=20
> own machines.

Well - yes. And if their DHCP server says one thing and their RAs are
saying another, then there should be a sane default for deciding which
to use. That's all this is about.

Regards, K.
=20
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687 Old
fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From mohacsi@niif.hu  Sun Nov 13 23:55:48 2011
Return-Path: <mohacsi@niif.hu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E35211E824C; Sun, 13 Nov 2011 23:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.004
X-Spam-Level: 
X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7SwRaSKTCd0y; Sun, 13 Nov 2011 23:55:47 -0800 (PST)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by ietfa.amsl.com (Postfix) with ESMTP id 2234011E8243; Sun, 13 Nov 2011 23:55:47 -0800 (PST)
Received: from bolha.lvs.iif.hu (bolha.lvs.iif.hu [193.225.14.181]) by mail.ki.iif.hu (Postfix) with ESMTP id 6CEB28782D; Mon, 14 Nov 2011 08:55:45 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at bolha.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by bolha.lvs.iif.hu (bolha.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id lIk6E--GN1y8; Mon, 14 Nov 2011 08:55:42 +0100 (CET)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id 11A3D8782C; Mon, 14 Nov 2011 08:55:42 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id 023F8877F5; Mon, 14 Nov 2011 08:55:41 +0100 (CET)
Date: Mon, 14 Nov 2011 08:55:41 +0100 (CET)
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Hui Deng <denghui02@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.1111140850130.66599@mignon.ki.iif.hu>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1307643040-1321257342=:66599"
Cc: MIF Mailing List <mif@ietf.org>, ipv6@ietf.org, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 07:55:48 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1307643040-1321257342=:66599
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT




On Mon, 14 Nov 2011, Hui Deng wrote:

> Hello 6MAN and DHCP,
>  
> Especially thanks Wes Beebee, Hemant Singh, Brian Carpenter, Alex and Ted's discussion.
>  
> MIF is going to discuss the confliction between RA and DHCP on tuesday afternoon MIF session (15:20-17:00) 
> the author Tomasz has propose below resolution:
>  
> The problem is about potential conflict between RA and DHCP. Our
> proposed answer is as follows:
> 
> RA provides configuration to all hosts in a network. DHCP can provide
> configuration on a per host basis. Therefore it may be useful to use
> DHCP to "override" configuration for some hosts in a network (e.g.
> engineering department has extra routes defined for a lab network). As
> such, DHCP should be preferred.
> 
> However, there is also a matter of security. Both RA and DHCPv6 can be
> secured. If SEND is deployed, RA is more trustworthy than DHCP, so it
> should be preferred. Finally, there is such thing as secure DHCP, so if
> both RA and DHCP are secure, prefer SEND. I must admit that I never
> heard about any realistic deployments of secure DHCP, but it will change
> over time.
> 
> This approach can be summed as: favor secure, favor DHCP. Or to be more
> explicit, there's a complete list of all cases:
> a) RA vs DHCP => prefer DHCP
> b) RA(SEND) vs DHCP => prefer RA
> c) RA vs secure DHCP => prefer DHCP
> d) RA(SEND) vs secure DHCP => prefer DHCP
> 
> Does it sound reasonable?
> 
> This approach is very similar to what was described in DNS configuration
> over RA and DHCP (except the part about both RA and DHCP being secure
> that is not covered in RFC6106).
> 
> To summarize the discussion so far, Ted Lemon on MIF list agreed that
> DHCP should be preferred. Herman Singh on 6MAN list suggested to go look
> at what DNS over RA proposes and use the same approach. RFC6106, section
> 5.3.1covers cases a) and b). c) and d) are logical extension that takes
> DHCPv6 security into consideration. My understanding is that proposed
> solution will be satisfactory to everyone.


I think in reality it will not be very easy to implement all these things. 
Some Operating System might implement RA(SEND), some the Secure DHCP, some 
none of above. . The operator should operate the network consistently: - 
same information all the relevant channel..... This preferential treatment 
can give  some protections against malicious activity or misconfiguration.



Best Regards,
 		Janos Mohacsi
--0-1307643040-1321257342=:66599--

From kerlyn2001@gmail.com  Sun Nov 13 21:41:15 2011
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CADA011E8184 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 21:41:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQM8NNmIcYZk for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 21:41:15 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id B78AA11E819D for <ipv6@ietf.org>; Sun, 13 Nov 2011 21:41:14 -0800 (PST)
Received: by eyg24 with SMTP id 24so5391591eyg.31 for <ipv6@ietf.org>; Sun, 13 Nov 2011 21:41:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=ovTexO8Q/Vnb8qc+61Q220VM+4bkYH23aSMqWDrTodw=; b=jsSJb8/7Xy32R9gRcpqb0/81AP0ilkTNL30g8hSJL6PBqo9guN8jWvoYpRnfNf92sz LCzjzxShxVK78NI3vCVgqNOmiDO3ZiSumGcRjiIf8JqOZ9lnDSMYQvt6X2tHPQgAcMP/ 2P+GWow7af2DJNMH6WY5QN//PzaxxX0P108Ug=
MIME-Version: 1.0
Received: by 10.14.9.218 with SMTP id 66mr1539689eet.98.1321249272608; Sun, 13 Nov 2011 21:41:12 -0800 (PST)
Received: by 10.14.96.68 with HTTP; Sun, 13 Nov 2011 21:41:12 -0800 (PST)
Date: Mon, 14 Nov 2011 00:41:12 -0500
Message-ID: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com>
Subject: Link-local IPv6 addresses in URIs
From: Kerry Lynn <kerlyn2001@gmail.com>
To: 6man <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=0016e646a4888db6ca04b1ab513a
X-Mailman-Approved-At: Mon, 14 Nov 2011 00:41:50 -0800
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 05:41:16 -0000

--0016e646a4888db6ca04b1ab513a
Content-Type: text/plain; charset=ISO-8859-1

Greetings,

I've noticed that a "bug" has re-appeared in Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=700999

In older versions of Firefox (e.g. 3.6.23) it is possible to enter URIs of
the form http://[fe80::206:98ff:fe00:232%tap0] in the
location bar and get a positive result.  This capability is quite handy in
simple testing scenarios and obviously requires the client and server
to be on a common link (so I don't necessarily see how it creates a
security risk.)

According to a note attached to the bug, the regression occurred as a
result of fixing a security bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=<https://bugzilla.mozilla.org/show_bug.cgi?id=700999>
504014 <https://bugzilla.mozilla.org/show_bug.cgi?id=504014>
I don't seem to have access to that bug, so I don't know the complete
rationale.  However, the note on 700999 says the title is "Enforce RFC
3986 syntax for IPv6 literals".  It goes on to say that RFC 3986
"disallows" interface specifiers (a.k.a. zone indices:
http://en.wikipedia.org/wiki/IPv6_address#Link-local_addresses_and_zone_indices
).

I don't see how a link-local address can be used in this context w/o
using a zone index.  Granted, RFC 3986 doesn't cover this case but
it also doesn't prohibit it.  This leads me to suspect it was an oversight,
so I'm wondering if RFC 3986 needs to be updated to cover it link-
local IPv6 literals?  If so, is there a reference that could be used to
derive the necessary ABNF?

Thanks, -K-

--0016e646a4888db6ca04b1ab513a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Greetings,<div><br></div><div>I&#39;ve noticed that a &quot;bug&quot; has r=
e-appeared in Firefox:</div><div><a href=3D"https://bugzilla.mozilla.org/sh=
ow_bug.cgi?id=3D700999" target=3D"_blank">https://bugzilla.mozilla.org/show=
_bug.cgi?id=3D700999</a></div>

<div><br></div><div>In older versions of Firefox (e.g. 3.6.23) it is possib=
le to enter URIs of</div><div>the form <span style=3D"font-family:monospace=
;white-space:pre-wrap;font-size:medium">http://[fe80::206:98ff:fe00:232%tap=
0] </span>in the</div>

<div>location bar and get a positive result. =A0This capability is quite ha=
ndy in</div><div>simple=A0testing=A0scenarios and obviously requires the cl=
ient and server</div><div>to be on a=A0common link (so I don&#39;t necessar=
ily see how it creates a</div>
<div>security risk.)</div><div><br></div><div>According to a note attached =
to=A0the bug, the regression occurred as a</div><div>result of fixing a sec=
urity bug:=A0<a href=3D"https://bugzilla.mozilla.org/show_bug.cgi?id=3D7009=
99" target=3D"_blank">https://bugzilla.mozilla.org/show_bug.cgi?id=3D</a><a=
 href=3D"https://bugzilla.mozilla.org/show_bug.cgi?id=3D504014">504014</a><=
/div>
<div>I don&#39;t seem to have access to that bug, so I don&#39;t know the c=
omplete</div><div>rationale. =A0However, the note on 700999 says the title =
is &quot;Enforce RFC</div><div>3986=A0syntax for IPv6 literals&quot;. =A0It=
 goes on to say that RFC 3986</div>
<div>&quot;disallows&quot; interface specifiers (a.k.a. zone indices:</div>=
<div><a href=3D"http://en.wikipedia.org/wiki/IPv6_address#Link-local_addres=
ses_and_zone_indices">http://en.wikipedia.org/wiki/IPv6_address#Link-local_=
addresses_and_zone_indices</a>).</div>
<div><br></div><div>I don&#39;t see how a link-local address can be used in=
 this context w/o</div><div>using a zone index. =A0Granted, RFC 3986 doesn&=
#39;t cover this case but</div><div>it also doesn&#39;t prohibit it. =A0Thi=
s leads me to suspect it was an oversight,</div>
<div>so I&#39;m wondering if RFC 3986 needs to be updated to cover it link-=
</div><div>local IPv6 literals? =A0If so, is there a reference that could b=
e used to</div><div>derive the necessary ABNF?</div><div><br></div><div>Tha=
nks, -K-</div>


--0016e646a4888db6ca04b1ab513a--

From Ted.Lemon@nominum.com  Mon Nov 14 01:29:14 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFEAB21F8EC4; Mon, 14 Nov 2011 01:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.558
X-Spam-Level: 
X-Spam-Status: No, score=-106.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpC-C+D4ZQlu; Mon, 14 Nov 2011 01:29:12 -0800 (PST)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id A918521F8EC1; Mon, 14 Nov 2011 01:29:11 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKTsDfWlsuc1mRyVSRcmSwRRMFmjNZ6ab3@postini.com; Mon, 14 Nov 2011 01:29:11 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7ED531B82B5; Mon, 14 Nov 2011 01:28:58 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 63C35190052; Mon, 14 Nov 2011 01:28:57 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Mon, 14 Nov 2011 01:28:57 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Mohacsi Janos <mohacsi@niif.hu>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWshtmA//+T8hI=
Date: Mon, 14 Nov 2011 09:28:56 +0000
Message-ID: <D5254BBA-B020-4803-B5BF-D913C27922F6@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <alpine.BSF.2.00.1111140850130.66599@mignon.ki.iif.hu>
In-Reply-To: <alpine.BSF.2.00.1111140850130.66599@mignon.ki.iif.hu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 09:29:15 -0000

On Nov 14, 2011, at 3:55 PM, "Mohacsi Janos" <mohacsi@niif.hu> wrote:
> I think in reality it will not be very easy to implement all these things=
. Some Operating System might implement RA(SEND), some the Secure DHCP, som=
e none of above. . The operator should operate the network consistently: - =
same information all the relevant channel..... This preferential treatment =
can give  some protections against malicious activity or misconfiguration.

This is true, but the problem is that the RA may be trustworthy and DHCP no=
t, or vice versa. So it's not safe to assume that the information you get f=
rom each one is trustworthy, even though of course on a good network it sho=
uld be.=20


From brian.e.carpenter@gmail.com  Mon Nov 14 01:41:18 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEB721F8DC8 for <ipv6@ietfa.amsl.com>; Mon, 14 Nov 2011 01:41:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.268
X-Spam-Level: 
X-Spam-Status: No, score=-103.268 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v5mcp+vCggST for <ipv6@ietfa.amsl.com>; Mon, 14 Nov 2011 01:40:57 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 56EB021F8F3F for <ipv6@ietf.org>; Mon, 14 Nov 2011 01:40:27 -0800 (PST)
Received: by ywt34 with SMTP id 34so4510062ywt.31 for <ipv6@ietf.org>; Mon, 14 Nov 2011 01:40:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gzLLpqvEVKha5yc4I8hBCYE0Mus6HYCbRUVJ9Jjc9VI=; b=qVzElKAWa7+fIVXiH/2oyUIHXrP2dfzCaKBnKw0Gc7uJxMFLYLpnFCMKa6KwR4qaA9 v2+u/ESXk3lsdf3tyCbWK5ZDqwDLjKDNZGA9PtgVbuFCfWuecuHP5nWnykel9gHhfr+T Ly/YjanjO7++MoX9rvYKoKmLqgHd7fUns40eg=
Received: by 10.236.175.72 with SMTP id y48mr13287270yhl.17.1321263626388; Mon, 14 Nov 2011 01:40:26 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id l19sm59708466anc.14.2011.11.14.01.40.23 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 01:40:25 -0800 (PST)
Message-ID: <4EC0E1FD.6050107@gmail.com>
Date: Mon, 14 Nov 2011 22:40:13 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Kerry Lynn <kerlyn2001@gmail.com>
Subject: Re: Link-local IPv6 addresses in URIs
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com>
In-Reply-To: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 09:41:24 -0000

Kerry,

On 2011-11-14 18:41, Kerry Lynn wrote:
> Greetings,
> 
> I've noticed that a "bug" has re-appeared in Firefox:
> https://bugzilla.mozilla.org/show_bug.cgi?id=700999
> 
> In older versions of Firefox (e.g. 3.6.23) it is possible to enter URIs of
> the form http://[fe80::206:98ff:fe00:232%tap0] in the
> location bar and get a positive result.  This capability is quite handy in
> simple testing scenarios and obviously requires the client and server
> to be on a common link (so I don't necessarily see how it creates a
> security risk.)
> 
> According to a note attached to the bug, the regression occurred as a
> result of fixing a security bug:
> https://bugzilla.mozilla.org/show_bug.cgi?id=<https://bugzilla.mozilla.org/show_bug.cgi?id=700999>
> 504014 <https://bugzilla.mozilla.org/show_bug.cgi?id=504014>
> I don't seem to have access to that bug, so I don't know the complete
> rationale.  However, the note on 700999 says the title is "Enforce RFC
> 3986 syntax for IPv6 literals".  It goes on to say that RFC 3986
> "disallows" interface specifiers (a.k.a. zone indices:
> http://en.wikipedia.org/wiki/IPv6_address#Link-local_addresses_and_zone_indices
> ).
> 
> I don't see how a link-local address can be used in this context w/o
> using a zone index.  

As soon as there's more than one interface, there is an issue.

> Granted, RFC 3986 doesn't cover this case but
> it also doesn't prohibit it.  

Yes it does, because the ABNF for IPv6address is for an address, not
a scoped address. A scoped address would not conform to the ABNF, so
that amounts to a prohibition.

> This leads me to suspect it was an oversight,

This part of RFC 3986 derives from RFC 2732 (which had broken ABNF,
and didn't allow for a scoped address, because they didn't exist then).

> so I'm wondering if RFC 3986 needs to be updated to cover it link-
> local IPv6 literals?  If so, is there a reference that could be used to
> derive the necessary ABNF?

I don't believe so. The ABNF has never been extended to cover RFC 4007
as far as I know.

Getting RFC 3986 updated would be reasonably complicated I suspect.
It involves a chat with the W3C people for a start.

   Brian


From internet-drafts@ietf.org  Mon Nov 14 03:08:57 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A38F911E8201; Mon, 14 Nov 2011 03:08:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-buVPmJIPG4; Mon, 14 Nov 2011 03:08:57 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C02211E811C; Mon, 14 Nov 2011 03:08:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-impatient-nud-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.63
Message-ID: <20111114110857.3402.20320.idtracker@ietfa.amsl.com>
Date: Mon, 14 Nov 2011 03:08:57 -0800
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 11:08:57 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the IPv6 Maintenance Working Group of the=
 IETF.

	Title           : Neighbor Unreachability Detection is too impatient
	Author(s)       : Erik Nordmark
                          Igor Gashinsky
	Filename        : draft-ietf-6man-impatient-nud-00.txt
	Pages           : 7
	Date            : 2011-11-14

   IPv6 Neighbor Discovery includes Neighbor Unreachability Detection.
   That function is very useful when a host has an alternative, for
   instance multiple default routers, since it allows the host to switch
   to the alternative in short time.  This time is 3 seconds after the
   node starts probing.  However, if there are no alternatives, this is
   far too impatient.  This document proposes an approach where an
   implementation can choose the timeout behavior to be different based
   on whether or not there are alternatives.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-impatient-nud-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-impatient-nud-00.txt

From denghui02@gmail.com  Mon Nov 14 03:10:57 2011
Return-Path: <denghui02@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 103B421F8B7E; Mon, 14 Nov 2011 03:10:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FExjS5TWswYC; Mon, 14 Nov 2011 03:10:56 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9459421F8B84; Mon, 14 Nov 2011 03:10:54 -0800 (PST)
Received: by yenq4 with SMTP id q4so3201678yen.31 for <multiple recipients>; Mon, 14 Nov 2011 03:10:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=Z1teKVB2wgHV9DSqbcgeaFDvjZCM/6R9OBLzxwJM56Y=; b=oFNvCqXlml+Lnm+ijwyxiMCr+QPTVMFfFpQ98SR7sxxSjGbFzSPNSMh9yDcSybthnx B6pwy2F9V17E7o2KEtJ5UzdA7Hp/uOgOgMvcTVSBeas+bcNcICt3JcR+k6hgGMw/qLAN e12H8MGaUWeojuIjo+jVllzMPLoc7tacK8hFk=
MIME-Version: 1.0
Received: by 10.236.155.2 with SMTP id i2mr13727959yhk.115.1321269038977; Mon, 14 Nov 2011 03:10:38 -0800 (PST)
Received: by 10.146.84.10 with HTTP; Mon, 14 Nov 2011 03:10:38 -0800 (PST)
Date: Mon, 14 Nov 2011 19:10:38 +0800
Message-ID: <CANF0JMDxqGPZNbTCzXUGRMvi2=aFN8VxqBnhNmt7jLRntbNybg@mail.gmail.com>
Subject: New MIF agenda posted
From: Hui Deng <denghui02@gmail.com>
To: MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary=20cf30363adbb8934404b1afeb9f
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 11:10:57 -0000

--20cf30363adbb8934404b1afeb9f
Content-Type: text/plain; charset=ISO-8859-1

Hello all

We are going to postpone the mif dhc route option discussion to the second
session to avoid the confliction with Softwire

http://www.ietf.org/proceedings/82/agenda/mif.txt

thanks for your work

-Hui

--20cf30363adbb8934404b1afeb9f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello all</div>
<div>=A0</div>
<div>We are going to postpone the mif dhc route option discussion to the se=
cond session to avoid the confliction with Softwire</div>
<div>=A0</div>
<div><a href=3D"http://www.ietf.org/proceedings/82/agenda/mif.txt">http://w=
ww.ietf.org/proceedings/82/agenda/mif.txt</a></div>
<div>=A0</div>
<div>thanks for your work</div>
<div>=A0</div>
<div>-Hui</div>

--20cf30363adbb8934404b1afeb9f--

From internet-drafts@ietf.org  Mon Nov 14 17:10:20 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED2E1F0C8B; Mon, 14 Nov 2011 17:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oV4lwwyP+oQm; Mon, 14 Nov 2011 17:10:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 959231F0C7D; Mon, 14 Nov 2011 17:10:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-rpl-option-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.63
Message-ID: <20111115011018.5739.71694.idtracker@ietfa.amsl.com>
Date: Mon, 14 Nov 2011 17:10:18 -0800
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2011 01:10:20 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the IPv6 Maintenance Working Group of the=
 IETF.

	Title           : RPL Option for Carrying RPL Information in Data-Plane Da=
tagrams
	Author(s)       : Jonathan W. Hui
                          JP Vasseur
	Filename        : draft-ietf-6man-rpl-option-05.txt
	Pages           : 15
	Date            : 2011-11-14

   The RPL protocol requires data-plane datagrams to carry RPL routing
   information that is processed by RPL routers when forwarding those
   datagrams.  This document describes the RPL Option for use among RPL
   routers.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-rpl-option-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-rpl-option-05.txt

From internet-drafts@ietf.org  Mon Nov 14 17:11:32 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E49911E8162; Mon, 14 Nov 2011 17:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VOYp5DrlEDdT; Mon, 14 Nov 2011 17:11:31 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2FB211E8134; Mon, 14 Nov 2011 17:11:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-rpl-routing-header-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.63
Message-ID: <20111115011131.7436.73328.idtracker@ietfa.amsl.com>
Date: Mon, 14 Nov 2011 17:11:31 -0800
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2011 01:11:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the IPv6 Maintenance Working Group of the=
 IETF.

	Title           : An IPv6 Routing Header for Source Routes with RPL
	Author(s)       : Jonathan W. Hui
                          JP Vasseur
                          David E. Culler
                          Vishwas Manral
	Filename        : draft-ietf-6man-rpl-routing-header-05.txt
	Pages           : 18
	Date            : 2011-11-14

   In Low power and Lossy Networks (LLNs), memory constraints on routers
   may limit them to maintaining at most a few routes.  In some
   configurations, it is necessary to use these memory constrained
   routers to deliver datagrams to nodes within the LLN.  The Routing
   for Low Power and Lossy Networks (RPL) protocol can be used in some
   deployments to store most, if not all, routes on one (e.g. the
   Directed Acyclic Graph (DAG) root) or few routers and forward the
   IPv6 datagram using a source routing technique to avoid large routing
   tables on memory constrained routers.  This document specifies a new
   IPv6 Routing header type for delivering datagrams within a RPL
   Instance.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-rpl-routing-header-05.t=
xt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-rpl-routing-header-05.txt

From shemant@cisco.com  Mon Nov 14 21:56:35 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6198D11E8146 for <ipv6@ietfa.amsl.com>; Mon, 14 Nov 2011 21:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.175
X-Spam-Level: 
X-Spam-Status: No, score=-6.175 tagged_above=-999 required=5 tests=[AWL=0.423,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VfEkep8pOCmM for <ipv6@ietfa.amsl.com>; Mon, 14 Nov 2011 21:56:34 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id DFB0311E809C for <ipv6@ietf.org>; Mon, 14 Nov 2011 21:56:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=12152; q=dns/txt; s=iport; t=1321336594; x=1322546194; h=mime-version:subject:date:message-id:in-reply-to: references:from:to; bh=KFa7voPaR7kW2uHLuRBxzQ+sCfSygkkO5AQs4YsFLck=; b=TtZsaMIqEdFldZ8sv6ZSjAT5GzABsbqfi4mQknjseqzI8Er/VtnF0km1 QUYNg0SGeoK9dhtztnyi+jNzk9Tm5wkavt/frlIh79XM0brndBPK+YcQe VFR7JuxDHlqCmdArSb2+Zg9lJ83QWYoTQnN0IVDnkBVbG3LWYZY7+IalG s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApkAAI/+wU6tJXG+/2dsb2JhbABEgk2XF5AFgQWBcgEBAQQSAQkRA1kCAQgRBAEBCwYXAQYBRQkIAQEEARIIARmHaJxrAZ8IiSFjBIgRkWOMVQ
X-IronPort-AV: E=Sophos;i="4.69,513,1315180800"; d="scan'208,217";a="36008109"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-6.cisco.com with ESMTP; 15 Nov 2011 05:56:33 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAF5uWwp005459 for <ipv6@ietf.org>; Tue, 15 Nov 2011 05:56:32 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Nov 2011 23:56:32 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCA35B.532526EB"
Subject: RE: further responses for comments at the mic in 6man fordraft-hsingh-6man-enhanced-dad-02.txt
Date: Mon, 14 Nov 2011 23:56:29 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303494FDE@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303494B7C@XMB-RCD-109.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: further responses for comments at the mic in 6man fordraft-hsingh-6man-enhanced-dad-02.txt
Thread-Index: AcyikYXqCmkayE20RKKfY9DN+0mBxwAxs0qg
References: <5B6B2B64C9FE2A489045EEEADDAFF2C303494B7C@XMB-RCD-109.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 15 Nov 2011 05:56:32.0150 (UTC) FILETIME=[53484B60:01CCA35B]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2011 05:56:35 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCA35B.532526EB
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Suresh,

=20

Here is proposed change to text in section 4.5 of=20

=20

http://www.ietf.org/id/draft-hsingh-6man-enhanced-dad-02.txt

=20

Old text:

=20

A router that supports IPv6 DAD MUST implement the detection of

=20

New text:

=20

A router as specified in [I-D.ietf-6man-node-req-bis] that supports IPv6
DAD MUST implement the detection=20

=20

Thanks,

=20

Hemant

=20

From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Hemant Singh (shemant)
Sent: Monday, November 14, 2011 1:52 PM
To: ipv6@ietf.org
Cc: cheshire@apple.com
Subject: further responses for comments at the mic in 6man
fordraft-hsingh-6man-enhanced-dad-02.txt

=20

3.      Suresh - comments on the "Changes to RFC 4862" titled slide in
the presentation.  The text needs work for router vs. ...

I already replied during the presentation the router in the text is a
router as specified in RFC 4861 vs. a host defined in the same document.
Please suggest what change we can make to the text in the document.  The
text from section 4.5 is shown below.

   [4.5.  Changes to RFC 4862

   The following text is added to [RFC4862] at a yet to be determined

   location in [RFC4862].

   A router that supports IPv6 DAD MUST implement the detection of

   looped back NS messages during DAD operation as specified in this

   document.  A network interface on any other IPv6 node that is not a

   router SHOULD implement the detection of looped back NS messages

   during DAD operation as specified in this document.]

Thanks,

Hemant


------_=_NextPart_001_01CCA35B.532526EB
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><title>further responses for comments at the mic in =
6man for draft-hsingh-6man-enhanced-dad-02.txt</title><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:338771947;
	mso-list-template-ids:-828502886;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1
	{mso-list-id:493298136;
	mso-list-template-ids:24143028;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l2
	{mso-list-id:1481733195;
	mso-list-template-ids:1903714716;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Suresh,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Here is proposed change to text in section 4.5 of =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><a =
href=3D"http://www.ietf.org/id/draft-hsingh-6man-enhanced-dad-02.txt">htt=
p://www.ietf.org/id/draft-hsingh-6man-enhanced-dad-02.txt</a><o:p></o:p><=
/span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Old text:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>A router that =
supports IPv6 DAD MUST implement the detection =
of<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>New text:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><pre><span style=3D'font-size:11.0pt'>A =
router as specified in [I-D.ietf-6man-node-req-bis] that supports IPv6 =
DAD MUST implement the detection </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></pre><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hemant<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] <b>On Behalf Of =
</b>Hemant Singh (shemant)<br><b>Sent:</b> Monday, November 14, 2011 =
1:52 PM<br><b>To:</b> ipv6@ietf.org<br><b>Cc:</b> =
cheshire@apple.com<br><b>Subject:</b> further responses for comments at =
the mic in 6man =
fordraft-hsingh-6man-enhanced-dad-02.txt<o:p></o:p></span></p></div></div=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p><span =
style=3D'font-family:"Courier =
New"'>3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span> <span =
style=3D'font-family:"Courier New"'>Suresh - comments on the</span> =
<span style=3D'font-family:"Courier New"'>&#8220;Changes to RFC =
4862&#8221; titled slide in the presentation.</span>&nbsp; <span =
style=3D'font-family:"Courier New"'>The text needs work for router =
vs.</span> <span style=3D'font-family:"Courier =
New"'>&#8230;</span><o:p></o:p></p><p style=3D'margin-left:.5in'><span =
style=3D'font-family:"Courier New"'>I already replied</span> <span =
style=3D'font-family:"Courier New"'>during the presentation</span> <span =
style=3D'font-family:"Courier New"'>the router in the text is a</span> =
<span style=3D'font-family:"Courier New"'>router as specified in RFC =
4861 vs. a host defined in the same document.&nbsp;</span> <span =
style=3D'font-family:"Courier New"'>Please suggest what change we can =
make to the text in the document.</span>&nbsp; <span =
style=3D'font-family:"Courier New"'>The text from section 4.5 is shown =
below.</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
[4.5.&nbsp; Changes to RFC 4862</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; The =
following text is added to [RFC4862] at a yet to be =
determined</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
location in [RFC4862].</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; A =
router that supports IPv6 DAD MUST implement the detection =
of</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; looped =
back NS messages during DAD operation as specified in =
this</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
document.&nbsp; A network interface on any other IPv6 node that is not =
a</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; router =
SHOULD implement the detection of looped back NS =
messages</span><o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; during =
DAD operation as specified in this document.</span><span =
style=3D'font-family:"Courier New"'>]</span><o:p></o:p></p><p><span =
style=3D'font-family:"Courier =
New"'>Thanks,</span><o:p></o:p></p><p><span =
style=3D'font-family:"Courier =
New"'>Hemant</span><o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CCA35B.532526EB--

From dthaler@microsoft.com  Wed Nov 16 03:48:48 2011
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B11321F94B3 for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 03:48:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.587
X-Spam-Level: 
X-Spam-Status: No, score=-110.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GONgnbUbhMK8 for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 03:48:47 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id 88C2C21F9450 for <ipv6@ietf.org>; Wed, 16 Nov 2011 03:48:47 -0800 (PST)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 16 Nov 2011 03:48:47 -0800
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server (TLS) id 14.1.355.3; Wed, 16 Nov 2011 03:48:47 -0800
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.162]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.01.0355.003; Wed, 16 Nov 2011 03:48:47 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: 6man <ipv6@ietf.org>
Subject: RE: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
Thread-Topic: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
Thread-Index: AQHMnnyA8bHdVFCXiUyuTF/wKIyRo5WrAv2AgADytwCAA3L0cA==
Date: Wed, 16 Nov 2011 11:48:47 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B3091F7@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <4EB9D332.1040003@gmail.com> <81C461F1-C088-446A-892C-D8B233CF1EB7@nttv6.net> <4EC0491C.2050406@gmail.com>
In-Reply-To: <4EC0491C.2050406@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 11:48:48 -0000

I have read and reviewed -05.

The document is a good start, but I have some issues with it currently.  =20

Summary of substantial technical issues:

1) In the updated prefix policy table, the order of rows is ok, but the pre=
cedence
values are a major problem that would make it difficult if not impossible f=
or us
to implement/deploy the current draft. Please change to preserve the preced=
ence
values to be the same as in RFC 3484 except where a change is actually requ=
ired.
For example, ::1/128 should remain 50. Teredo should be 5, which is what ha=
s=20
been deployed for many years now.   The operational issues center around wa=
ys
to configure nodes with additional rules.   Ones already exist in some impl=
ementations
and changing the values means that you can't push a rule out to a host unle=
ss you
know it's a new vs old host.   Avoiding gratuitous changes means you can ha=
ve=20
one new-row pushed out to all hosts.   I personally consider this a showsto=
pper=20
for the draft.

2) The current Rule 5.1 text=20
"Rule 5.1: Use an address assigned by the selected next-hop."
is problematic for two reasons:
   i) Next-hops don't assign addresses, they advertise prefixes. Addresses =
are=20
      assigned by the hosts themselves (in SLAAC) or by DHCP servers.
      It should say something like "Prefer addresses in a prefix advertised=
 by the next-hop"
   ii) nowhere does the doc have text about whether a host must remember=20
     who it got an on-link prefix from. RFC 4861 section 5 doesn't say it d=
oes.
     RFC 4191 section 3 doesn't either. And this document has no section=20
     that's similar to either one. Note that 4191 section 3 defines some as=
=20
     being optional. Is this one optional or required?    I don't have a co=
ncern
     either way, my concern is that the document doesn't say anything like
     what it ought to cover in order to enable this rule.

Summary of editorial issues:

1) As Brian pointed out one instance of, many places in the doc say what _c=
ould_=20
be done.  A standards track document needs to instead specify what _is_ don=
e.

2) Several informative references (that are drafts not RFCs) are used in te=
xt in=20
normative ways.   Rather than making them be normative references, the text
should be updated so that the use is clearly informative.

3) A number of grammar issues.  Parts of Appendix B are rather hard to read=
=20
for instance.  Perhaps it can just be deleted.


Also I prefer the Updates (not Obsoletes) option, where the document=20
specifies the deltas.   This is the current approach in the doc.

-Dave

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Monday, November 14, 2011 6:48 AM
> To: Arifumi Matsumoto
> Cc: 6man
> Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
>=20
> > So, which of update or replace do you prefer ?
>=20
> Hmm. If we want to go quickly, an update that makes it easy for the
> implementer to find the changes is better.
>=20
> Regards
>    Brian
>=20
> On 2011-11-13 21:19, Arifumi Matsumoto wrote:
> > Brian,
> >
> > thank you for your comments.
> >
> > On 2011/11/09, at 10:11, Brian E Carpenter wrote:
> >
> >> Hi,
> >>
> >> I think I'm going to make myself unpopular.
> >>
> >> Reading this document as a proposed standard, I think it will confuse =
the
> reader.
> >> I think that what we actually need is a 100% replacement of RFC 3484,
> >> that can be read on its own.
> >>
> >> (We've been here before - the same argument is why we ended up doing
> >> 3697bis.)
> >>
> >> If that is not done, I would suggest reorganising the text so that
> >> (after a short Introduction) the reader finds:
> >>
> >> - firstly, a complete but concise statement of the normative changes
> >> made to 3484  (such as section 2.1.5, and the new rules 5.1 and 9)
> >>
> >> - secondly, the explanations (such as sections 2.1.1-2.1.4).
> >>
> >> An implementer would only need to read the first part.
> >
> > This document had started as an update, because there was not so many
> > things to update at first.
> >
> > As the document gets older, it got a bit bigger than I had expected.
> >
> > So, which of update or replace do you prefer ?
> >
> >> Trivia:
> >>
> >> Needs a header: Updates: 3484 (if approved)
> >>
> >>> 4.  IANA Considerations
> >>>
> >>>   Address type number for the policy table may have to be assigned by
> >>>   IANA.
> >> You can't say "may", you have to tell IANA exactly what to do in which
> registry.
> >
> > Thanks !
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From dthaler@microsoft.com  Wed Nov 16 03:50:21 2011
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E184021F9537 for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 03:50:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.587
X-Spam-Level: 
X-Spam-Status: No, score=-110.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4vPQf3aiFS8 for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 03:50:21 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id DE50721F9544 for <ipv6@ietf.org>; Wed, 16 Nov 2011 03:50:19 -0800 (PST)
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 16 Nov 2011 03:50:19 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) with Microsoft SMTP Server (TLS) id 14.1.355.3; Wed, 16 Nov 2011 03:50:19 -0800
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.162]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0355.003; Wed, 16 Nov 2011 03:50:19 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: 6man <ipv6@ietf.org>
Subject: RE: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
Thread-Topic: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
Thread-Index: AQHMnnyA8bHdVFCXiUyuTF/wKIyRo5WrAv2AgADytwCAA3L0cIAABdmw
Date: Wed, 16 Nov 2011 11:50:18 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B309227@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <4EB9D332.1040003@gmail.com> <81C461F1-C088-446A-892C-D8B233CF1EB7@nttv6.net> <4EC0491C.2050406@gmail.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 11:50:22 -0000

A marked-up version with my full comments in context can be found at
http://research.microsoft.com/~dthaler/draft-ietf-6man-rfc3484-revise-05.pd=
f

-Dave

> -----Original Message-----
> From: Dave Thaler
> Sent: Wednesday, November 16, 2011 7:49 PM
> To: 6man
> Cc: 'Brian E Carpenter'; Arifumi Matsumoto
> Subject: RE: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
>=20
> I have read and reviewed -05.
>=20
> The document is a good start, but I have some issues with it currently.
>=20
> Summary of substantial technical issues:
>=20
> 1) In the updated prefix policy table, the order of rows is ok, but the
> precedence values are a major problem that would make it difficult if not
> impossible for us to implement/deploy the current draft. Please change to
> preserve the precedence values to be the same as in RFC 3484 except where
> a change is actually required.
> For example, ::1/128 should remain 50. Teredo should be 5, which is what
> has
> been deployed for many years now.   The operational issues center around
> ways
> to configure nodes with additional rules.   Ones already exist in some
> implementations
> and changing the values means that you can't push a rule out to a host
> unless you
> know it's a new vs old host.   Avoiding gratuitous changes means you can
> have
> one new-row pushed out to all hosts.   I personally consider this a
> showstopper
> for the draft.
>=20
> 2) The current Rule 5.1 text
> "Rule 5.1: Use an address assigned by the selected next-hop."
> is problematic for two reasons:
>    i) Next-hops don't assign addresses, they advertise prefixes. Addresse=
s are
>       assigned by the hosts themselves (in SLAAC) or by DHCP servers.
>       It should say something like "Prefer addresses in a prefix advertis=
ed by
> the next-hop"
>    ii) nowhere does the doc have text about whether a host must remember
>      who it got an on-link prefix from. RFC 4861 section 5 doesn't say it=
 does.
>      RFC 4191 section 3 doesn't either. And this document has no section
>      that's similar to either one. Note that 4191 section 3 defines some =
as
>      being optional. Is this one optional or required?    I don't have a =
concern
>      either way, my concern is that the document doesn't say anything lik=
e
>      what it ought to cover in order to enable this rule.
>=20
> Summary of editorial issues:
>=20
> 1) As Brian pointed out one instance of, many places in the doc say what
> _could_ be done.  A standards track document needs to instead specify wha=
t
> _is_ done.
>=20
> 2) Several informative references (that are drafts not RFCs) are used in =
text
> in
> normative ways.   Rather than making them be normative references, the
> text
> should be updated so that the use is clearly informative.
>=20
> 3) A number of grammar issues.  Parts of Appendix B are rather hard to re=
ad
> for instance.  Perhaps it can just be deleted.
>=20
>=20
> Also I prefer the Updates (not Obsoletes) option, where the document
> specifies the deltas.   This is the current approach in the doc.
>=20
> -Dave
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> > Brian E Carpenter
> > Sent: Monday, November 14, 2011 6:48 AM
> > To: Arifumi Matsumoto
> > Cc: 6man
> > Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
> >
> > > So, which of update or replace do you prefer ?
> >
> > Hmm. If we want to go quickly, an update that makes it easy for the
> > implementer to find the changes is better.
> >
> > Regards
> >    Brian
> >
> > On 2011-11-13 21:19, Arifumi Matsumoto wrote:
> > > Brian,
> > >
> > > thank you for your comments.
> > >
> > > On 2011/11/09, at 10:11, Brian E Carpenter wrote:
> > >
> > >> Hi,
> > >>
> > >> I think I'm going to make myself unpopular.
> > >>
> > >> Reading this document as a proposed standard, I think it will confus=
e
> the
> > reader.
> > >> I think that what we actually need is a 100% replacement of RFC 3484=
,
> > >> that can be read on its own.
> > >>
> > >> (We've been here before - the same argument is why we ended up
> doing
> > >> 3697bis.)
> > >>
> > >> If that is not done, I would suggest reorganising the text so that
> > >> (after a short Introduction) the reader finds:
> > >>
> > >> - firstly, a complete but concise statement of the normative changes
> > >> made to 3484  (such as section 2.1.5, and the new rules 5.1 and 9)
> > >>
> > >> - secondly, the explanations (such as sections 2.1.1-2.1.4).
> > >>
> > >> An implementer would only need to read the first part.
> > >
> > > This document had started as an update, because there was not so many
> > > things to update at first.
> > >
> > > As the document gets older, it got a bit bigger than I had expected.
> > >
> > > So, which of update or replace do you prefer ?
> > >
> > >> Trivia:
> > >>
> > >> Needs a header: Updates: 3484 (if approved)
> > >>
> > >>> 4.  IANA Considerations
> > >>>
> > >>>   Address type number for the policy table may have to be assigned =
by
> > >>>   IANA.
> > >> You can't say "may", you have to tell IANA exactly what to do in whi=
ch
> > registry.
> > >
> > > Thanks !
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------


From brian.e.carpenter@gmail.com  Wed Nov 16 21:00:43 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06FF811E80C2 for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 21:00:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.25
X-Spam-Level: 
X-Spam-Status: No, score=-103.25 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCHsXdDiqh99 for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 21:00:36 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 22AB811E80ED for <ipv6@ietf.org>; Wed, 16 Nov 2011 21:00:36 -0800 (PST)
Received: by ywt34 with SMTP id 34so663779ywt.31 for <ipv6@ietf.org>; Wed, 16 Nov 2011 21:00:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ekCKQ1KEaQZD74jmCNiwHEx7nkBprHt40SPYOCYqTuY=; b=S09D6laipebheNmbv1Xp2x7NEcaD3iAvtZ/uMpZ52tGeuqSoQKGQcbEgpIf94XwRVv a2BD7PE6rkK0+xLY27+A/VOd+Z0zxenYJz2VVGyaSFBp9ZL38g9dvCImE/Ug7J+YYmqV vSXuwfkmMCgPONSR1viG+bcL31bRFAfTpKF90=
Received: by 10.236.9.36 with SMTP id 24mr6543360yhs.62.1321506035652; Wed, 16 Nov 2011 21:00:35 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id 33sm77098827ano.1.2011.11.16.21.00.33 (version=SSLv3 cipher=OTHER); Wed, 16 Nov 2011 21:00:34 -0800 (PST)
Message-ID: <4EC494EB.4070000@gmail.com>
Date: Thu, 17 Nov 2011 18:00:27 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: Link-local IPv6 addresses in URIs
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com>
In-Reply-To: <4EC0E1FD.6050107@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 05:00:43 -0000

Dear 6man,

Kerry and I talked about this. It seems to me that, given we allow for
IPv6 literals in URIs principally for diagnostic purposes, it is indeed
unfortunate that http://[fe80::206:98ff:fe00:232%tap0] is not
allowed by the formal syntax.

This would need to be fixed by a small RFC that updates 3986,
just as 2732 updated 2396 in its day.

Do people agree that this is a reasonable thing to do? If so, I'll
follow it up appropriately (i.e. I will draft something when time permits).

Regards
   Brian

On 2011-11-14 22:40, Brian E Carpenter wrote:
> Kerry,
> 
> On 2011-11-14 18:41, Kerry Lynn wrote:
>> Greetings,
>>
>> I've noticed that a "bug" has re-appeared in Firefox:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=700999
>>
>> In older versions of Firefox (e.g. 3.6.23) it is possible to enter URIs of
>> the form http://[fe80::206:98ff:fe00:232%tap0] in the
>> location bar and get a positive result.  This capability is quite handy in
>> simple testing scenarios and obviously requires the client and server
>> to be on a common link (so I don't necessarily see how it creates a
>> security risk.)
>>
>> According to a note attached to the bug, the regression occurred as a
>> result of fixing a security bug:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=<https://bugzilla.mozilla.org/show_bug.cgi?id=700999>
>> 504014 <https://bugzilla.mozilla.org/show_bug.cgi?id=504014>
>> I don't seem to have access to that bug, so I don't know the complete
>> rationale.  However, the note on 700999 says the title is "Enforce RFC
>> 3986 syntax for IPv6 literals".  It goes on to say that RFC 3986
>> "disallows" interface specifiers (a.k.a. zone indices:
>> http://en.wikipedia.org/wiki/IPv6_address#Link-local_addresses_and_zone_indices
>> ).
>>
>> I don't see how a link-local address can be used in this context w/o
>> using a zone index.  
> 
> As soon as there's more than one interface, there is an issue.
> 
>> Granted, RFC 3986 doesn't cover this case but
>> it also doesn't prohibit it.  
> 
> Yes it does, because the ABNF for IPv6address is for an address, not
> a scoped address. A scoped address would not conform to the ABNF, so
> that amounts to a prohibition.
> 
>> This leads me to suspect it was an oversight,
> 
> This part of RFC 3986 derives from RFC 2732 (which had broken ABNF,
> and didn't allow for a scoped address, because they didn't exist then).
> 
>> so I'm wondering if RFC 3986 needs to be updated to cover it link-
>> local IPv6 literals?  If so, is there a reference that could be used to
>> derive the necessary ABNF?
> 
> I don't believe so. The ABNF has never been extended to cover RFC 4007
> as far as I know.
> 
> Getting RFC 3986 updated would be reasonably complicated I suspect.
> It involves a chat with the W3C people for a start.
> 
>    Brian
> 
> 

From cabo@tzi.org  Wed Nov 16 21:13:29 2011
Return-Path: <cabo@tzi.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95C91F0C42 for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 21:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6p+zscj-Med for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 21:13:29 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF551F0CC3 for <ipv6@ietf.org>; Wed, 16 Nov 2011 21:13:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id pAH5DLCM022689; Thu, 17 Nov 2011 06:13:21 +0100 (CET)
Received: from dhcp-9069.meeting.ietf.org (dhcp-9069.meeting.ietf.org [130.129.8.105]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id BD7FE9A5; Thu, 17 Nov 2011 06:13:18 +0100 (CET)
Subject: Re: Link-local IPv6 addresses in URIs
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4EC494EB.4070000@gmail.com>
Date: Thu, 17 Nov 2011 13:13:13 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org>
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: 6man <ipv6@ietf.org>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 05:13:30 -0000

On Nov 17, 2011, at 13:00, Brian E Carpenter wrote:

> Do people agree that this is a reasonable thing to do?=20

Yes please!

I trust that the update spec will explain the "for debugging" focus and =
will have appropriate warning=20

-- that the link identifiers are node-local names with node-local =
semantics, and=20
-- about security considerations, e.g., that this capability might be =
used to send packets to random links from malicious web pages unless =
properly restricted in a browser.

Gr=FC=DFe, Carsten


From kerlyn2001@gmail.com  Wed Nov 16 22:14:21 2011
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B5A21F978D for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 22:14:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vQF6Iy22bLV7 for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2011 22:14:16 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id E512D21F9792 for <ipv6@ietf.org>; Wed, 16 Nov 2011 22:14:15 -0800 (PST)
Received: by eyg24 with SMTP id 24so1800522eyg.31 for <ipv6@ietf.org>; Wed, 16 Nov 2011 22:14:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QUpDykIljxPBbWwWweu/Up4Y/9FoIWkOVMgBrn1w46Q=; b=PjP6982DIEoPDTF8Uq4NHMxoTP6s+8PpFH2JojXqQEUjq0gkhd4FnAxoows9F08D4o DUw9X2mznT1D1PJPj3DyPGAh9MSc07kxfmgo6QG6KDvEaMOnnVhDFNYsaZj2Ly805K/w 9l3283o5Ht4Ow2iYZTo2JSHGr6kAH3xH+D828=
MIME-Version: 1.0
Received: by 10.14.14.16 with SMTP id c16mr2596151eec.34.1321510454957; Wed, 16 Nov 2011 22:14:14 -0800 (PST)
Received: by 10.14.96.68 with HTTP; Wed, 16 Nov 2011 22:14:14 -0800 (PST)
In-Reply-To: <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org>
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com> <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org>
Date: Thu, 17 Nov 2011 01:14:14 -0500
Message-ID: <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com>
Subject: Re: Link-local IPv6 addresses in URIs
From: Kerry Lynn <kerlyn2001@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=0016e656b5063c16fb04b1e82198
X-Mailman-Approved-At: Thu, 17 Nov 2011 00:07:48 -0800
Cc: 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 06:14:21 -0000

--0016e656b5063c16fb04b1e82198
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 17, 2011 at 12:13 AM, Carsten Bormann <cabo@tzi.org> wrote:

> On Nov 17, 2011, at 13:00, Brian E Carpenter wrote:
>
> > Do people agree that this is a reasonable thing to do?
>
> Yes please!
>
> My ABNF is pretty rusty, so I offer the following extension to the RFC 39=
86
IPv6address rule only as a starting point:

/ "FE80::" [ *3( h16 ":" ) h16 ] [ "%" 1*4(ALPHA / DIGIT) ]

If we proceed with this, should we fix the IPv6address rule to align with
RFC 5952 or just make the minimal change?


> I trust that the update spec will explain the "for debugging" focus and
> will have appropriate warning


> -- that the link identifiers are node-local names with node-local
> semantics, and
> -- about security considerations, e.g., that this capability might be use=
d
> to send packets to random links from malicious web pages unless properly
> restricted in a browser.
>
> You mean "specified links", right?  I still don't understand the security
risk
this poses, so maybe we could discuss it offline.

Thanks, -K-


> Gr=FC=DFe, Carsten
>
>

--0016e656b5063c16fb04b1e82198
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 17, 2011 at 12:13 AM, Carsten Bormann <span dir=3D"ltr">&lt;<a =
href=3D"mailto:cabo@tzi.org">cabo@tzi.org</a>&gt;</span> wrote:<br><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Nov 17, 2011, at 13:00, Brian E Carpenter wrote:<br>
<br>
&gt; Do people agree that this is a reasonable thing to do?<br>
<br>
</div>Yes please!<br>
<br></blockquote><div>My ABNF is pretty rusty, so I offer the following ext=
ension to the RFC 3986</div><div>IPv6address rule only as a starting point:=
</div><div><br></div><div>/ &quot;FE80::&quot; [ *3( h16 &quot;:&quot; ) h1=
6 ] [ &quot;%&quot; 1*4(ALPHA / DIGIT) ]</div>
<div><br></div><div>If we proceed with this, should we fix the IPv6address =
rule to align with</div><div>RFC 5952 or just make the minimal change?</div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-widt=
h: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; pa=
dding-left: 1ex; ">
I trust that the update spec will explain the &quot;for debugging&quot; foc=
us and will have appropriate warning</blockquote><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex;">

<br>
-- that the link identifiers are node-local names with node-local semantics=
, and<br>
-- about security considerations, e.g., that this capability might be used =
to send packets to random links from malicious web pages unless properly re=
stricted in a browser.<br>
<br></blockquote><div>You mean &quot;specified links&quot;, right? =A0I sti=
ll don&#39;t understand the security risk</div><div>this poses, so maybe we=
 could discuss it offline.</div><div><br></div><div>Thanks, -K-</div><div>
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex;">
Gr=FC=DFe, Carsten<br>
<br>
</blockquote></div><br>

--0016e656b5063c16fb04b1e82198--

From ichiroumakino@gmail.com  Thu Nov 17 03:28:30 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68ABA21F9B9D for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 03:28:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuBxvQ00VxOi for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 03:28:25 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 75F1F21F99C3 for <ipv6@ietf.org>; Thu, 17 Nov 2011 03:28:25 -0800 (PST)
Received: by yenq4 with SMTP id q4so1055385yen.31 for <ipv6@ietf.org>; Thu, 17 Nov 2011 03:28:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=2XzTRgRqXy00eTtvCz8ZMqH8XMBx+m1DZW3R/QVdbSU=; b=BHX/R84/J4+1gbXDICdozs/nJzzqy8D2ks6XdFi9lwQ1QcZVa5BWANQBpSFHMMNgjE zoUv2edKCqU81b90wiTiDibSrZgam31SNw1E5xSlGlFRO/qL/9Sj52XewHnPMf4PIhOF ajbfdem75Y7YGH39s2J3Iu851VnOSxJ1tW5/U=
Received: by 10.236.200.194 with SMTP id z42mr8543102yhn.70.1321529305144; Thu, 17 Nov 2011 03:28:25 -0800 (PST)
Received: from [192.168.0.50] (220-132-142-73.HINET-IP.hinet.net. [220.132.142.73]) by mx.google.com with ESMTPS id l19sm95266946anc.14.2011.11.17.03.28.20 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Nov 2011 03:28:22 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1321238859.2514.73.camel@karl>
Date: Thu, 17 Nov 2011 19:28:15 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B84BC7DF-4CAB-43B8-B762-0289CEF97544@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl> <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org> <1321238859.2514.73.camel@karl>
To: Karl Auer <kauer@biplane.com.au>
X-Mailer: Apple Mail (2.1084)
Cc: IETF IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 11:28:30 -0000

Karl,

>> can you give examples of what information cannot be merged?
>> certainly a default router list can be merged...
>=20
> If one source says that the domain search list is "a.com b.com c.com"
> and another source says it is "c.com a.com b.com", how can you merge =
the
> search lists?

refer to Mark's mail on search lists.

> Or if one source says that the default route is via IP address 1, and
> the other source says that the default route is via IP address 2, =
which
> IP address are you supposed to use as your default route? Sure, you =
can
> set up two default routes - but when a packet turns up for which you
> have no more specific route, which IP address will you send it to?
> Something has to choose, using some criterion or other.

huh? that's exactly how router discovery in IPv6 works.
put all default routers on your default routers list. read 4861 and 4191 =
for more details.

> Some things cannot be merged - that's what "conflict" means.

I am yet to see what information that would be.

cheers,
Ole=

From ichiroumakino@gmail.com  Thu Nov 17 03:30:56 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A62721F9BFE for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 03:30:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aomiBQ8srNc3 for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 03:30:55 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id AE88221F9BFB for <ipv6@ietf.org>; Thu, 17 Nov 2011 03:30:55 -0800 (PST)
Received: by yenq4 with SMTP id q4so1058476yen.31 for <ipv6@ietf.org>; Thu, 17 Nov 2011 03:30:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=pvlBHWPblkwGTpbmiVGxkgwnIhlSUc+GsdOhy4p98jk=; b=dNaXGp0XVOZ9f7IWnE3+k2LQE0defjcVGfMoq+tells3w3XMQyDGopzvapY/Thj2lL 2eYZgghdy1+9Ry31X4tvREMbaHZfUnWPQFa8TiWnERsJ9PBMPAPFmjct8VkAw2sCoBHh DJl8gL6XpNM0U7omNpPNXB2VF1jPs7NqaddjI=
Received: by 10.236.154.42 with SMTP id g30mr8603617yhk.3.1321529455200; Thu, 17 Nov 2011 03:30:55 -0800 (PST)
Received: from [192.168.0.50] (220-132-142-73.HINET-IP.hinet.net. [220.132.142.73]) by mx.google.com with ESMTPS id h45sm5009130yhm.15.2011.11.17.03.30.51 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Nov 2011 03:30:53 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1321238859.2514.73.camel@karl>
Date: Thu, 17 Nov 2011 19:30:45 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D703BE4-37B5-4201-8AC5-5131178B59D5@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl> <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org> <1321238859.2514.73.camel@karl>
To: Karl Auer <kauer@biplane.com.au>
X-Mailer: Apple Mail (2.1084)
Cc: IETF IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 11:30:56 -0000

Karl,

>> can you give examples of what information cannot be merged?
>> certainly a default router list can be merged...
>=20
> If one source says that the domain search list is "a.com b.com c.com"
> and another source says it is "c.com a.com b.com", how can you merge =
the
> search lists?
>=20
> Or if one source says that the default route is via IP address 1, and
> the other source says that the default route is via IP address 2, =
which
> IP address are you supposed to use as your default route? Sure, you =
can
> set up two default routes - but when a packet turns up for which you
> have no more specific route, which IP address will you send it to?
> Something has to choose, using some criterion or other.
>=20
> Some things cannot be merged - that's what "conflict" means.

I presume we are talking about merging information received on a single =
interface?
for the multiple interface case I would consider each interface's =
configuration information independent.

Ole


From kauer@biplane.com.au  Thu Nov 17 04:01:19 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B958211E80DB for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 04:01:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9dEsrRf4G35 for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 04:01:18 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBDF21F9AC2 for <ipv6@ietf.org>; Thu, 17 Nov 2011 04:01:16 -0800 (PST)
Received: from eth4284.nsw.adsl.internode.on.net ([150.101.127.187] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1RR0eW-000129-Di for ipv6@ietf.org; Thu, 17 Nov 2011 07:01:12 -0500
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
From: Karl Auer <kauer@biplane.com.au>
To: IETF IPv6 <ipv6@ietf.org>
In-Reply-To: <B84BC7DF-4CAB-43B8-B762-0289CEF97544@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <1321236631.2514.48.camel@karl> <AD6BF089-0E02-4E2E-87DF-6F0B848189A4@employees.org> <1321238859.2514.73.camel@karl> <B84BC7DF-4CAB-43B8-B762-0289CEF97544@employees.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-QiL4cSCRZVOSnmSZQ8Qy"
Date: Thu, 17 Nov 2011 23:01:09 +1100
Message-ID: <1321531269.2514.412.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 12:01:19 -0000

--=-QiL4cSCRZVOSnmSZQ8Qy
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, 2011-11-17 at 19:28 +0800, Ole Troan wrote:
> refer to Mark's mail on search lists.

Why? It has no bearing on your question. You asked for things which
could not be merged. I gave you an example. It wasn't a recommendation.

> huh? that's exactly how router discovery in IPv6 works.
> put all default routers on your default routers list. read 4861 and 4191 =
for more details.

Perhaps you should. Most of the discussion of default routers in those
RFCs is actually about discriminating between not-so-default-after-all
routers. However, it was indeed a poor example under the circumstances.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-QiL4cSCRZVOSnmSZQ8Qy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk7E930ACgkQMAcU7Vc29ofThgCgh7rSD4pbICbD4+2qug3UhWXt
7JAAoM2fDOW9MeyiBD3sNjCB/43gNzlQ
=Jwkq
-----END PGP SIGNATURE-----

--=-QiL4cSCRZVOSnmSZQ8Qy--


From brian@innovationslab.net  Thu Nov 17 04:56:03 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E8021F9A2E for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 04:56:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.885
X-Spam-Level: 
X-Spam-Status: No, score=-102.885 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WEoB2oLnBs4w for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 04:56:02 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id D162321F9A2D for <ipv6@ietf.org>; Thu, 17 Nov 2011 04:56:02 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 9986488214 for <ipv6@ietf.org>; Thu, 17 Nov 2011 04:56:02 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 66219130002 for <ipv6@ietf.org>; Thu, 17 Nov 2011 04:56:02 -0800 (PST)
Message-ID: <4EC50461.7070909@innovationslab.net>
Date: Thu, 17 Nov 2011 07:56:01 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Link-local IPv6 addresses in URIs
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com>
In-Reply-To: <4EC494EB.4070000@gmail.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 12:56:03 -0000

On 11/17/11 12:00 AM, Brian E Carpenter wrote:
> Dear 6man,
> 
> Kerry and I talked about this. It seems to me that, given we allow for
> IPv6 literals in URIs principally for diagnostic purposes, it is indeed
> unfortunate that http://[fe80::206:98ff:fe00:232%tap0] is not
> allowed by the formal syntax.
> 
> This would need to be fixed by a small RFC that updates 3986,
> just as 2732 updated 2396 in its day.
> 
> Do people agree that this is a reasonable thing to do? If so, I'll
> follow it up appropriately (i.e. I will draft something when time permits).

I agree that it is reasonable to do.

Regards,
Brian


From tomasz.mrugalski@gmail.com  Thu Nov 17 06:38:19 2011
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2A2B11E810A for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 06:38:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.239
X-Spam-Level: 
X-Spam-Status: No, score=-3.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixlwWKmPo6FI for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 06:38:19 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 70F6821F9A25 for <ipv6@ietf.org>; Thu, 17 Nov 2011 06:38:19 -0800 (PST)
Received: by ywt34 with SMTP id 34so1340982ywt.31 for <ipv6@ietf.org>; Thu, 17 Nov 2011 06:38:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; bh=a/NfReNCJ4jH7VC+mYwNfgvvQAy/5gJR0MUT5yO7VW8=; b=QwwvMVDkZp637MQZLmOQOJ0+HjhtQI6w1Qg1LGChb6qZoQZl6p129wVDdMKlfIiqp8 /87iyHFazLIez8BlXejeaUygKCvDSFa64OfdbW489P/eCpsbQmsX6R3bZEh6msO1IkHG /ktoI+MIlvPhPyU0HEmISIDO2SfmAkSFkSVDo=
Received: by 10.236.136.38 with SMTP id v26mr9795305yhi.69.1321540699082; Thu, 17 Nov 2011 06:38:19 -0800 (PST)
Received: from dhcp-41d0.meeting.ietf.org ([2001:df8:0:64:de2b:61ff:fee5:409c]) by mx.google.com with ESMTPS id h28sm11093907ani.17.2011.11.17.06.38.16 (version=SSLv3 cipher=OTHER); Thu, 17 Nov 2011 06:38:18 -0800 (PST)
Message-ID: <4EC51C56.1090403@gmail.com>
Date: Thu, 17 Nov 2011 22:38:14 +0800
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Discussion on feasibility of route configuration over DHCPv6
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 14:38:19 -0000

Hi,
Everyone's favourite topic is back. There is pretty good chance that
current discussion will lead to either publication of
draft-ietf-mif-dhcpv6-route-option or its abandonment.

If you care about this topic, you are encouraged to read and post in:

Why we need route option thread:
http://www.ietf.org/mail-archive/web/mif/current/msg01431.html

Why we should drop route option thread:
http://www.ietf.org/mail-archive/web/mif/current/msg01432.html

There are questions raised if MIF is the best place for this option, but
since it is adopted there, MIF list seems like a reasonable place to
discuss its faith. There are at least 5 (DHC, MIF, HOMENET, V6OPS, 6MAN)
WGs that may be interested in this. There may be others. I consider
cross-posting to 5 mailing lists as highly inappropriate.

Similar posts as this will be sent to DHC, HOMENET, V6OPS and 6MAN shortly.

Cheers,
Tomek Mrugalski
ISC

From albert.e.manfredi@boeing.com  Thu Nov 17 11:11:52 2011
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD05811E8088 for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 11:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZATDFqbOkx1 for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 11:11:51 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id A77F911E8086 for <ipv6@ietf.org>; Thu, 17 Nov 2011 11:11:51 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id pAHJBiWb019738 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ipv6@ietf.org>; Thu, 17 Nov 2011 13:11:48 -0600 (CST)
Received: from localhost (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with SMTP id pAHJBhJn003989 for <ipv6@ietf.org>; Thu, 17 Nov 2011 11:11:43 -0800 (PST)
Received: from XCH-MWHT-03.mw.nos.boeing.com (xch-mwht-03.mw.nos.boeing.com [134.57.119.161]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id pAHJBf8r003917 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 17 Nov 2011 11:11:42 -0800 (PST)
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.119.191]) by XCH-MWHT-03.mw.nos.boeing.com ([134.57.119.161]) with mapi; Thu, 17 Nov 2011 13:11:41 -0600
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
Date: Thu, 17 Nov 2011 13:11:38 -0600
Subject: RE: Link-local IPv6 addresses in URIs
Thread-Topic: Link-local IPv6 addresses in URIs
Thread-Index: Acyk5eOn8R87VgKqQTSLHjJHPnm5FgAdsguw
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02B32DDBEF@XCH-MW-08V.mw.nos.boeing.com>
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com>
In-Reply-To: <4EC494EB.4070000@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 19:11:52 -0000

Yes from me. Thanks.

Bert

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Bri=
an E Carpenter
Sent: Thursday, November 17, 2011 12:00 AM
To: 6man
Cc: Kerry Lynn
Subject: Re: Link-local IPv6 addresses in URIs

Dear 6man,

Kerry and I talked about this. It seems to me that, given we allow for
IPv6 literals in URIs principally for diagnostic purposes, it is indeed
unfortunate that http://[fe80::206:98ff:fe00:232%tap0] is not
allowed by the formal syntax.

This would need to be fixed by a small RFC that updates 3986,
just as 2732 updated 2396 in its day.

Do people agree that this is a reasonable thing to do? If so, I'll
follow it up appropriately (i.e. I will draft something when time permits).

Regards
   Brian

On 2011-11-14 22:40, Brian E Carpenter wrote:
> Kerry,
>=20
> On 2011-11-14 18:41, Kerry Lynn wrote:
>> Greetings,
>>
>> I've noticed that a "bug" has re-appeared in Firefox:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=3D700999
>>
>> In older versions of Firefox (e.g. 3.6.23) it is possible to enter URIs =
of
>> the form http://[fe80::206:98ff:fe00:232%tap0] in the
>> location bar and get a positive result.  This capability is quite handy =
in
>> simple testing scenarios and obviously requires the client and server
>> to be on a common link (so I don't necessarily see how it creates a
>> security risk.)
>>
>> According to a note attached to the bug, the regression occurred as a
>> result of fixing a security bug:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=3D<https://bugzilla.mozilla=
.org/show_bug.cgi?id=3D700999>
>> 504014 <https://bugzilla.mozilla.org/show_bug.cgi?id=3D504014>
>> I don't seem to have access to that bug, so I don't know the complete
>> rationale.  However, the note on 700999 says the title is "Enforce RFC
>> 3986 syntax for IPv6 literals".  It goes on to say that RFC 3986
>> "disallows" interface specifiers (a.k.a. zone indices:
>> http://en.wikipedia.org/wiki/IPv6_address#Link-local_addresses_and_zone_=
indices
>> ).
>>
>> I don't see how a link-local address can be used in this context w/o
>> using a zone index. =20
>=20
> As soon as there's more than one interface, there is an issue.
>=20
>> Granted, RFC 3986 doesn't cover this case but
>> it also doesn't prohibit it. =20
>=20
> Yes it does, because the ABNF for IPv6address is for an address, not
> a scoped address. A scoped address would not conform to the ABNF, so
> that amounts to a prohibition.
>=20
>> This leads me to suspect it was an oversight,
>=20
> This part of RFC 3986 derives from RFC 2732 (which had broken ABNF,
> and didn't allow for a scoped address, because they didn't exist then).
>=20
>> so I'm wondering if RFC 3986 needs to be updated to cover it link-
>> local IPv6 literals?  If so, is there a reference that could be used to
>> derive the necessary ABNF?
>=20
> I don't believe so. The ABNF has never been extended to cover RFC 4007
> as far as I know.
>=20
> Getting RFC 3986 updated would be reasonably complicated I suspect.
> It involves a chat with the W3C people for a start.
>=20
>    Brian
>=20
>=20
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From tomosann@gmail.com  Thu Nov 17 18:27:19 2011
Return-Path: <tomosann@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9578511E8097 for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 18:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m539fJxhBFyO for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 18:27:18 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3ED11E80B5 for <ipv6@ietf.org>; Thu, 17 Nov 2011 18:27:18 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so3354344bkb.31 for <ipv6@ietf.org>; Thu, 17 Nov 2011 18:27:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=dr4n6nBBn15VOTh/TFIJBWxbO0tMp6VGPxfzo9ZJAOw=; b=cfYNxUflEqUDhEKPkrFZZ8PvXRlFk5FihhT5D17ZVxpmkLqVWwApIft/Xmq7QHfK7L 9HicnqwSc+yEvpl0FVyC4BgA6/W7dC/Dj0XORlKkfG/54EHJRCEOMtWd3+UJyFUoB/B5 nsYYnB86A7BxC1uBTipySRMWb7H94UDzBC5H8=
MIME-Version: 1.0
Received: by 10.204.9.209 with SMTP id m17mr1056262bkm.101.1321583234577; Thu, 17 Nov 2011 18:27:14 -0800 (PST)
Sender: tomosann@gmail.com
Received: by 10.204.15.74 with HTTP; Thu, 17 Nov 2011 18:27:14 -0800 (PST)
In-Reply-To: <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com>
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com> <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org> <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com>
Date: Fri, 18 Nov 2011 11:27:14 +0900
X-Google-Sender-Auth: jwHl-f5Jv_5c_OxoghJXeXFBis0
Message-ID: <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
Subject: Re: Link-local IPv6 addresses in URIs
From: Tomoyuki Sahara <sahara@surt.net>
To: Kerry Lynn <kerlyn2001@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 02:27:19 -0000

Hi,

That sounds good to me too.

> My ABNF is pretty rusty, so I offer the following extension to the RFC 3986
> IPv6address rule only as a starting point:
> / "FE80::" [ *3( h16 ":" ) h16 ] [ "%" 1*4(ALPHA / DIGIT) ]

I have some comments:

  - An interface name may be longer than 4 characters.  But I know we should
    have some limit so I suggest 15 because it's maximum length of interface
    name on *BSD and Linux systems.

  - FYI, there was an attempt to define textual representation of zone id:
    http://tools.ietf.org/html/draft-ietf-ipngwg-scoping-arch-04#section-12

  - Can we have a dot in interface name?  On Linux systems, VLAN interfaces
    have one.  An example in the draft above has "%pvc1.3" (may be an ATM
    interface?).


Thanks,
Tomoyuki.

From arifumi@nttv6.net  Thu Nov 17 21:13:32 2011
Return-Path: <arifumi@nttv6.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9B311E8097 for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 21:13:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.72
X-Spam-Level: 
X-Spam-Status: No, score=-102.72 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ycAc9BdrKQnV for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 21:13:31 -0800 (PST)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by ietfa.amsl.com (Postfix) with ESMTP id 29DCE21F8FE6 for <ipv6@ietf.org>; Thu, 17 Nov 2011 21:13:28 -0800 (PST)
Received: from [127.0.0.1] (localhost.nttv6.net [127.0.0.1]) by leo.nttv6.net (8.14.5/8.14.4) with ESMTP id pAI5BqEe056475; Fri, 18 Nov 2011 14:11:52 +0900 (JST) (envelope-from arifumi@nttv6.net)
Subject: Re: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-14--311351453
From: Arifumi Matsumoto <arifumi@nttv6.net>
In-Reply-To: <03FE6A726D13284495EF1787D25F1DF9018D7907@TK5EX14MBXC266.redmond.corp.microsoft.com>
Date: Fri, 18 Nov 2011 14:13:52 +0900
Message-Id: <74D26F5C-E768-41D3-8F2C-0CC0ADCA33E4@nttv6.net>
References: <03FE6A726D13284495EF1787D25F1DF9018D7907@TK5EX14MBXC266.redmond.corp.microsoft.com>
To: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 05:13:32 -0000

--Apple-Mail-14--311351453
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

thank you for your comment.

On 2011/11/14, at 14:21, Dmitry Anipko wrote:

> Hello,
> =20
> I have a question about this text the -01 revision:
> =20
> >>A node MAY use OPTION_DASP in any of the following two cases:    =20
>                  1: The address selection option is delivered across a =
secure, trusted  =20
>                     channel.     =20
> =20
> The OPTION_DASP is configured by a network administrator, presumably =
based on some knowledge they have about what makes more or less sense in =
the particular network. How whether or not a secure channel has been =
used on one of the networks relates to whether or not the admin of that =
network has knowledge of a completely different network the host may =
simultaneously be connected to?

In any case, the policy delivered on the secured channel should be used.

That is what the draft suggests.

Make sense ?=

--Apple-Mail-14--311351453
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><base href=3D"x-msg://748/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">Hi,<div><br></div><div>thank you for your =
comment.</div><div><br><div><div>On 2011/11/14, at 14:21, Dmitry Anipko =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Monaco; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"Section1" =
style=3D"page: Section1; "><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; ">Hello,<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; ">I have a question about this =
text the -01 revision:<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; ">&gt;&gt;A node MAY use OPTION_DASP in any of the following =
two cases:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; &nbsp;&nbsp; 1: The address selection option is delivered across =
a secure, trusted&nbsp;&nbsp;&nbsp;<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
channel.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; ">The OPTION_DASP is configured =
by a network administrator, presumably based on some knowledge they have =
about what makes more or less sense in the particular network. How =
whether or not a secure channel has been used on one of the networks =
relates to whether or not the admin of that network has knowledge of a =
completely different network the host may simultaneously be connected =
to?</div></div></div></span></blockquote><div><br></div><div>In any =
case, the policy delivered on the secured channel should be =
used.</div><div><br></div><div>That is what the draft =
suggests.</div><div><br></div><div>Make sense =
?</div></div></div></body></html>=

--Apple-Mail-14--311351453--

From Dmitry.Anipko@microsoft.com  Thu Nov 17 21:27:14 2011
Return-Path: <Dmitry.Anipko@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C291F11E80C6 for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 21:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ahJ6ge+CRDBO for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 21:27:13 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 7005011E809D for <ipv6@ietf.org>; Thu, 17 Nov 2011 21:27:13 -0800 (PST)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 17 Nov 2011 21:27:13 -0800
Received: from TK5EX14MBXC265.redmond.corp.microsoft.com ([169.254.3.148]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.01.0355.003; Thu, 17 Nov 2011 21:27:13 -0800
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: RE: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Thread-Topic: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Thread-Index: AcyijTWX59zcnPnKTYaF1gdIRytzuwDZrUYAABCLADA=
Date: Fri, 18 Nov 2011 05:27:12 +0000
Message-ID: <03FE6A726D13284495EF1787D25F1DF9018FE6C5@TK5EX14MBXC265.redmond.corp.microsoft.com>
References: <03FE6A726D13284495EF1787D25F1DF9018D7907@TK5EX14MBXC266.redmond.corp.microsoft.com> <74D26F5C-E768-41D3-8F2C-0CC0ADCA33E4@nttv6.net>
In-Reply-To: <74D26F5C-E768-41D3-8F2C-0CC0ADCA33E4@nttv6.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.70]
Content-Type: multipart/alternative; boundary="_000_03FE6A726D13284495EF1787D25F1DF9018FE6C5TK5EX14MBXC265r_"
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 05:27:14 -0000

--_000_03FE6A726D13284495EF1787D25F1DF9018FE6C5TK5EX14MBXC265r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

>> In any case, the policy delivered on the secured channel should be used.
>>That is what the draft suggests.
>>Make sense ?

If the different policy tables were received from different administrative =
domains, I don't see yet why it would make sense to prefer one of them to a=
nother based on whether one of the channel was secured. In case an interfac=
e which delivered secured policy table is not preferred by routing metric, =
the copy of the table received over such interface may be irrelevant or har=
mful.

Thanks,
Dmitry

From: Arifumi Matsumoto [mailto:arifumi@nttv6.net]
Sent: Thursday, November 17, 2011 9:14 PM
To: Dmitry Anipko
Cc: ipv6@ietf.org
Subject: Re: multiple policy tables handling in draft-ietf-6man-addr-select=
-opt-01

Hi,

thank you for your comment.

On 2011/11/14, at 14:21, Dmitry Anipko wrote:


Hello,

I have a question about this text the -01 revision:

>>A node MAY use OPTION_DASP in any of the following two cases:
                 1: The address selection option is delivered across a secu=
re, trusted
                    channel.

The OPTION_DASP is configured by a network administrator, presumably based =
on some knowledge they have about what makes more or less sense in the part=
icular network. How whether or not a secure channel has been used on one of=
 the networks relates to whether or not the admin of that network has knowl=
edge of a completely different network the host may simultaneously be conne=
cted to?

In any case, the policy delivered on the secured channel should be used.

That is what the draft suggests.

Make sense ?

--_000_03FE6A726D13284495EF1787D25F1DF9018FE6C5TK5EX14MBXC265r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<base href=3D"x-msg://748/"><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: bre=
ak-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Hello,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">&gt;&gt;</span> In any case, the policy delivered on the sec=
ured channel should be used.<o:p></o:p></p>
<p class=3D"MsoNormal">&gt;&gt;That is what the draft suggests.<o:p></o:p><=
/p>
<p class=3D"MsoNormal">&gt;&gt;Make sense ?<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">If the different policy tables were received from different =
administrative domains, I don&#8217;t see yet why it would make sense to pr=
efer one of them to another
 based on whether one of the channel was secured. In case an interface whic=
h delivered secured policy table is not preferred by routing metric, the co=
py of the table received over such interface may be irrelevant or harmful.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Dmitry<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Arifumi =
Matsumoto [mailto:arifumi@nttv6.net]
<br>
<b>Sent:</b> Thursday, November 17, 2011 9:14 PM<br>
<b>To:</b> Dmitry Anipko<br>
<b>Cc:</b> ipv6@ietf.org<br>
<b>Subject:</b> Re: multiple policy tables handling in draft-ietf-6man-addr=
-select-opt-01<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">thank you for your comment.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 2011/11/14, at 14:21, Dmitry Anipko wrote:<o:p></=
o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Hello,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">I have a question about this text the -=
01 revision:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&gt;&gt;A node MAY use OPTION_DASP in a=
ny of the following two cases:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; 1: The address selecti=
on option is delivered across a secure, trusted&nbsp;&nbsp;&nbsp;<o:p></o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; chan=
nel.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">The OPTION_DASP is configured by a netw=
ork administrator, presumably based on some knowledge they have about what =
makes more or less sense in the particular network. How
 whether or not a secure channel has been used on one of the networks relat=
es to whether or not the admin of that network has knowledge of a completel=
y different network the host may simultaneously be connected to?<o:p></o:p>=
</span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In any case, the policy delivered on the secured cha=
nnel should be used.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">That is what the draft suggests.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Make sense ?<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_03FE6A726D13284495EF1787D25F1DF9018FE6C5TK5EX14MBXC265r_--

From kerlyn2001@gmail.com  Thu Nov 17 18:54:01 2011
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7235F1F0C85 for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 18:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.223
X-Spam-Level: 
X-Spam-Status: No, score=-3.223 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t7IIIgFAbZrk for <ipv6@ietfa.amsl.com>; Thu, 17 Nov 2011 18:54:01 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id A6C751F0C34 for <ipv6@ietf.org>; Thu, 17 Nov 2011 18:54:00 -0800 (PST)
Received: by eyg24 with SMTP id 24so3327581eyg.31 for <ipv6@ietf.org>; Thu, 17 Nov 2011 18:53:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IlXwm4nV/zy2xk+aHFR4gWoPDPf584x/N3pKWS9qdao=; b=U4GDoFVUOpRXUW/oLcKTmG0HSIyXAdH8549lFIIzXXcyjQplYo3DaLpIkMPA5UkCLn +leeBXchq2Ir2dcCDNMx57hAMYgz5JHS4i63rO+9vIFlccR347bNmKEtHihEhyDVa/VX M1Dasb/S+ucEL0Q2pKhBBkzL5NvTKBiwGEDeg=
MIME-Version: 1.0
Received: by 10.14.4.80 with SMTP id 56mr99302eei.2.1321584839705; Thu, 17 Nov 2011 18:53:59 -0800 (PST)
Received: by 10.14.96.68 with HTTP; Thu, 17 Nov 2011 18:53:59 -0800 (PST)
In-Reply-To: <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com> <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org> <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com> <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
Date: Thu, 17 Nov 2011 21:53:59 -0500
Message-ID: <CABOxzu2KwBwyY_6q5if-hXFJRG95dXst4mNV7DX1yEx750b81Q@mail.gmail.com>
Subject: Re: Link-local IPv6 addresses in URIs
From: Kerry Lynn <kerlyn2001@gmail.com>
To: Tomoyuki Sahara <sahara@surt.net>
Content-Type: multipart/alternative; boundary=001636416df1e9437204b1f972a6
X-Mailman-Approved-At: Fri, 18 Nov 2011 03:08:54 -0800
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 02:54:01 -0000

--001636416df1e9437204b1f972a6
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Nov 17, 2011 at 9:27 PM, Tomoyuki Sahara <sahara@surt.net> wrote:

> Hi,
>
> That sounds good to me too.
>
> > My ABNF is pretty rusty, so I offer the following extension to the RFC
> 3986
> > IPv6address rule only as a starting point:
> > / "FE80::" [ *3( h16 ":" ) h16 ] [ "%" 1*4(ALPHA / DIGIT) ]
>
> I have some comments:
>
>  - An interface name may be longer than 4 characters.  But I know we should
>    have some limit so I suggest 15 because it's maximum length of interface
>    name on *BSD and Linux systems.
>
>  - FYI, there was an attempt to define textual representation of zone id:
>    http://tools.ietf.org/html/draft-ietf-ipngwg-scoping-arch-04#section-12
>
>  - Can we have a dot in interface name?  On Linux systems, VLAN interfaces
>    have one.  An example in the draft above has "%pvc1.3" (may be an ATM
>    interface?).
>
> Thanks for the reference.  I'll take a look at it before revising the ABNF
again.

-K-

>
> Thanks,
> Tomoyuki.
>

--001636416df1e9437204b1f972a6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br>On Thu, Nov 17, 2011 at 9:27 PM, Tomoyuki Sahara <span dir=3D"ltr">&lt;=
<a href=3D"mailto:sahara@surt.net">sahara@surt.net</a>&gt;</span> wrote:<br=
><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
That sounds good to me too.<br>
<div class=3D"im"><br>
&gt; My ABNF is pretty rusty, so I offer the following extension to the RFC=
 3986<br>
&gt; IPv6address rule only as a starting point:<br>
&gt; / &quot;FE80::&quot; [ *3( h16 &quot;:&quot; ) h16 ] [ &quot;%&quot; 1=
*4(ALPHA / DIGIT) ]<br>
<br>
</div>I have some comments:<br>
<br>
 =A0- An interface name may be longer than 4 characters. =A0But I know we s=
hould<br>
 =A0 =A0have some limit so I suggest 15 because it&#39;s maximum length of =
interface<br>
 =A0 =A0name on *BSD and Linux systems.<br>
<br>
 =A0- FYI, there was an attempt to define textual representation of zone id=
:<br>
 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-ietf-ipngwg-scoping-arc=
h-04#section-12" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-ip=
ngwg-scoping-arch-04#section-12</a><br>
<br>
 =A0- Can we have a dot in interface name? =A0On Linux systems, VLAN interf=
aces<br>
 =A0 =A0have one. =A0An example in the draft above has &quot;%pvc1.3&quot; =
(may be an ATM<br>
 =A0 =A0interface?).<br>
<br></blockquote><div>Thanks for the reference. =A0I&#39;ll take a look at =
it before revising the ABNF again.</div><div><br></div><div>-K-=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex;">

<br>
Thanks,<br>
<font color=3D"#888888">Tomoyuki.<br>
</font></blockquote></div><br>

--001636416df1e9437204b1f972a6--

From brian@innovationslab.net  Fri Nov 18 05:50:58 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2F121F8ACA for <ipv6@ietfa.amsl.com>; Fri, 18 Nov 2011 05:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level: 
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0QF2qYuqVAf6 for <ipv6@ietfa.amsl.com>; Fri, 18 Nov 2011 05:50:54 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 163ED21F8A6C for <ipv6@ietf.org>; Fri, 18 Nov 2011 05:50:54 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id D5B3C880AA for <ipv6@ietf.org>; Fri, 18 Nov 2011 05:50:53 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 9F83B130003 for <ipv6@ietf.org>; Fri, 18 Nov 2011 05:50:53 -0800 (PST)
Message-ID: <4EC662BC.40607@innovationslab.net>
Date: Fri, 18 Nov 2011 08:50:52 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Link-local IPv6 addresses in URIs
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com> <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org> <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com> <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
In-Reply-To: <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 13:50:58 -0000

On 11/17/11 9:27 PM, Tomoyuki Sahara wrote:
> 
>   - FYI, there was an attempt to define textual representation of zone id:
>     http://tools.ietf.org/html/draft-ietf-ipngwg-scoping-arch-04#section-12

Published as RFC 4007 (http://tools.ietf.org/html/rfc4007).

Regards,
Brian


From fx.lebail@yahoo.com  Fri Nov 18 07:33:05 2011
Return-Path: <fx.lebail@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96CE221F8541 for <ipv6@ietfa.amsl.com>; Fri, 18 Nov 2011 07:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.018
X-Spam-Level: 
X-Spam-Status: No, score=-1.018 tagged_above=-999 required=5 tests=[AWL=0.681,  BAYES_00=-2.599, J_CHICKENPOX_37=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rQBy4VvKwhlr for <ipv6@ietfa.amsl.com>; Fri, 18 Nov 2011 07:33:05 -0800 (PST)
Received: from nm2-vm0.bullet.mail.ne1.yahoo.com (nm2-vm0.bullet.mail.ne1.yahoo.com [98.138.91.39]) by ietfa.amsl.com (Postfix) with SMTP id 0180F21F853E for <ipv6@ietf.org>; Fri, 18 Nov 2011 07:33:04 -0800 (PST)
Received: from [98.138.90.51] by nm2.bullet.mail.ne1.yahoo.com with NNFMP; 18 Nov 2011 15:33:01 -0000
Received: from [98.138.87.10] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 18 Nov 2011 15:33:01 -0000
Received: from [127.0.0.1] by omp1010.mail.ne1.yahoo.com with NNFMP; 18 Nov 2011 15:33:01 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 236881.98554.bm@omp1010.mail.ne1.yahoo.com
Received: (qmail 71606 invoked by uid 60001); 18 Nov 2011 15:33:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1321630381; bh=JcQtHiBxiRwIB/rCz7WnNheN/w43lAMuFfu7W/Owi8o=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=T0/aTS8gULVBFof7KPmHZPyAZeGMFlCt+WvQtbTFBDLhTF5FFJHP0NLnDSiFqPE/rojY82/gEupgS1pJJg90e4BFWExZ3wejl6ZGsRytebTjGsSbxu/MDDg/3xdet82PlXN8EpfFKw4w9ehaPXatosiMIQ1L9/IN7NBAeR0U6aA=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=0n2SPUmapMGY1PNOcuM6AuqB04YqDpdIYfWrzSaFAdOqEwAVmlVVWztAL4/fvDGDgHLYy3Ooep+ucdfmfqaDvXBmLmKK2BqokTwIC3uwjYL6wdGgz3+BsObyUx/F20PVxh5LjB4NfrJrhYClLi16rAN6qi6AKsTfBaQCk9qXQzk=;
X-YMail-OSG: 3w79AT8VM1m2.anzNlheBqFcuKA7JsXb4uHBUifTKG9wFD2 RdBgjfIvpArqHiIyXv2wfmrQrLJuLuM5vjntT.db6QKL80BmW33KJTcDQWAJ mqT2xki1LmCYCrdg3VhLOVrmM_EpAgWzHcN13IAa2xIdz6VQy_1u7MXyRTAt EbFcwbeMaHfQGo.z2EJMI84pfJT.vuCj4ET2Rds8cI5iAutLrSLvNR1oqQaO dscaV5NqUi11BbeU.ztacaY_5AxzQxOHCeWuHhDYoQziJ5cdbQM6KUvzsSU6 Imk35_udDX_YTCT78T59sL9JX0guYYOk0eZ.E69ASGEtZN.eFBhH.0pcaxWj ONyRZyNQC847hMk9J4rJJ7mdC1GGIvOxLD7uGXf9txNhtxcxY6ImF2sDHPi4 j6CDSivyuHbD9MaEQzOl4bPM43jHCIUsvvQPRqPZKQ3t3sHSXUu_0TWv1aR4 e2zZnj89V
Received: from [193.49.124.107] by web126002.mail.ne1.yahoo.com via HTTP; Fri, 18 Nov 2011 07:33:01 PST
X-Mailer: YahooMailWebService/0.8.115.325013
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com> <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org> <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com> <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com> <CABOxzu2KwBwyY_6q5if-hXFJRG95dXst4mNV7DX1yEx750b81Q@mail.gmail.com>
Message-ID: <1321630381.56734.YahooMailNeo@web126002.mail.ne1.yahoo.com>
Date: Fri, 18 Nov 2011 07:33:01 -0800 (PST)
From: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
Subject: Re: Link-local IPv6 addresses in URIs
To: Kerry Lynn <kerlyn2001@gmail.com>, Tomoyuki Sahara <sahara@surt.net>
In-Reply-To: <CABOxzu2KwBwyY_6q5if-hXFJRG95dXst4mNV7DX1yEx750b81Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 15:33:05 -0000

=0A=0A=0A=0A=0A=0A=0A>________________________________=0A> From: Kerry Lynn=
 <kerlyn2001@gmail.com>=0A>To: Tomoyuki Sahara <sahara@surt.net> =0A>Cc: 6m=
an <ipv6@ietf.org> =0A>Sent: Friday, November 18, 2011 3:53 AM=0A>Subject: =
Re: Link-local IPv6 addresses in URIs=0A> =0A>=0A>=0A>On Thu, Nov 17, 2011 =
at 9:27 PM, Tomoyuki Sahara <sahara@surt.net> wrote:=0A>=0A>Hi,=0A>>=0A>>Th=
at sounds good to me too.=0A>>=0A>>=0A>>> My ABNF is pretty rusty, so I off=
er the following extension to the RFC 3986=0A>>> IPv6address rule only as a=
 starting point:=0A>>> / "FE80::" [ *3( h16 ":" ) h16 ] [ "%" 1*4(ALPHA / D=
IGIT) ]=0A>>=0A>>I have some comments:=0A>>=0A>>=A0- An interface name may =
be longer than 4 characters. =A0But I know we should=0A>>=A0 =A0have some l=
imit so I suggest 15 because it's maximum length of interface=0A>>=A0 =A0na=
me on *BSD and Linux systems.=0A>>=0A>>=A0- FYI, there was an attempt to de=
fine textual representation of zone id:=0A>>=A0 =A0http://tools.ietf.org/ht=
ml/draft-ietf-ipngwg-scoping-arch-04#section-12=0A>>=0A>>=A0- Can we have a=
 dot in interface name? =A0On Linux systems, VLAN interfaces=0A>>=A0 =A0hav=
e one. =A0An example in the draft above has "%pvc1.3" (may be an ATM=0A>>=
=A0 =A0interface?).=0A>>=0A>>=0A>Thanks for the reference. =A0I'll take a l=
ook at it before revising the ABNF again.=0A=0AHi,=0A=0AIn Linux, you can u=
se any character in VLAN interface name :=0Aexamples:=0Aip link add link et=
h0 name eth0.5=A0 type vlan id 5=0Aip link add link eth0 name eth0-6=A0 typ=
e vlan id 6=0Aip link add link eth0 name eth0#7=A0 type vlan id 7=0Aip link=
 add link eth0 name eth0-8=A0 type vlan id 8=0Aip link add link eth0 name e=
th0+9=A0 type vlan id 9=0Aip link add link eth0 name eth0_10=A0 type vlan i=
d 10=0Aip link add link eth0 name eth0,11=A0 type vlan id 11=0Aip link add =
link eth0 name eth0:::12=A0 type vlan id 12=0Aip link add link eth0 name et=
h0.+-=A0 type vlan id 13=0A=0AThanks,=0AFrancois-Xavier=0A

From fx.lebail@yahoo.com  Fri Nov 18 08:03:34 2011
Return-Path: <fx.lebail@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E62F421F851A for <ipv6@ietfa.amsl.com>; Fri, 18 Nov 2011 08:03:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.094
X-Spam-Level: 
X-Spam-Status: No, score=-1.094 tagged_above=-999 required=5 tests=[AWL=0.605,  BAYES_00=-2.599, J_CHICKENPOX_37=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLkt+OVc+GZc for <ipv6@ietfa.amsl.com>; Fri, 18 Nov 2011 08:03:34 -0800 (PST)
Received: from nm23.bullet.mail.ne1.yahoo.com (nm23.bullet.mail.ne1.yahoo.com [98.138.90.86]) by ietfa.amsl.com (Postfix) with SMTP id 61A7A21F8515 for <ipv6@ietf.org>; Fri, 18 Nov 2011 08:03:34 -0800 (PST)
Received: from [98.138.90.54] by nm23.bullet.mail.ne1.yahoo.com with NNFMP; 18 Nov 2011 16:03:30 -0000
Received: from [98.138.89.252] by tm7.bullet.mail.ne1.yahoo.com with NNFMP; 18 Nov 2011 16:03:30 -0000
Received: from [127.0.0.1] by omp1044.mail.ne1.yahoo.com with NNFMP; 18 Nov 2011 16:03:30 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 582002.75574.bm@omp1044.mail.ne1.yahoo.com
Received: (qmail 56956 invoked by uid 60001); 18 Nov 2011 16:03:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1321632210; bh=huxGn6GUA9MZpAenwFl0yhEkaL13hRbVrcgS9h8dLZs=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=AnWVEM82aOQM6gZpoGubJvCOdn4uRgOM3d3wZfs+vnyJ8gx3TC5QYjcWpii24FT+qXU9292qn1lsLltKsTdhGjWgN5pLJNjiVo+HoqzCmH+ZFjGNGKZGlLH7afn/pYWNyc2bqQA56MYjzXm+PPa1pqx8XXNZkUpCWwDuLKnIGR0=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=SyeROJJScl/zsWa+kP6ZvO1o1OxYXx+a2SdZXkmaNNiz0jmWUhioMQIKZGsKv9yh5eMPcHFHfT50O9jzg2ryMNROcQXNaXOWRU9qdsXX3E0hOZUgov8HKEiVJnP0x9WlBatVWETEi7RmhjMkbD9uLXliB22O7XDruVGu/US0UXY=;
X-YMail-OSG: Nz4Y9jIVM1lOAwszvvh4iuil0r2cOQh_VFqFcW53ZTDbfnV b0BfzMDd7myw9ZyFrBjUGmfq2rj1O4LzziBuhf_UYOOBQSkcyh4YAkmcDShy SaERf0arA2m6rz8yIHCkxF9uUczHk0BnEJRx6jqkg4ONUYLQt9uC3Y5MZ9SM 2oPgI.JPYAqm9tS3JsB5QA514rXbyYfyAg7xoezMRGALvnGu7yvYf4dSn6kw o0s50Xf8lRuYgFCehVk5M8wONnJgy.xvRwxx6R6qKQahnWqppZuCJAWbsZ9z F1Pqwuy1sPdS1uCiX1UGGjt24y3B4eZaXazQj93hl7msqtEQDjZBvg0_VPRe h2pTA8pp2JfQIJO5mxyLnuLDB5jLA0w_V3MqfIt.bc3ZQR4sCECzeA4heSJa QputC70n4YknQ0bXZT_RFurSuzsjbEHbIzg8HF1ZEwm_HJB_6.p9bgqEb1gR SLqIOAvczRCCeOXR8O5SBjrf_I0XjLWYWEsDkwzsbhrkdT_.IDfsXvnade_W LKmXmmO6sl0L.2vrAENI_vNtTqsuQW_dlsIWFD89KTdRkyqFN.wce3RE-
Received: from [193.49.124.107] by web126013.mail.ne1.yahoo.com via HTTP; Fri, 18 Nov 2011 08:03:29 PST
X-Mailer: YahooMailWebService/0.8.115.325013
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com> <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org> <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com> <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com> <CABOxzu2KwBwyY_6q5if-hXFJRG95dXst4mNV7DX1yEx750b81Q@mail.gmail.com> <1321630381.56734.YahooMailNeo@web126002.mail.ne1.yahoo.com>
Message-ID: <1321632209.56936.YahooMailNeo@web126013.mail.ne1.yahoo.com>
Date: Fri, 18 Nov 2011 08:03:29 -0800 (PST)
From: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
Subject: Re: Link-local IPv6 addresses in URIs
To: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>, Kerry Lynn <kerlyn2001@gmail.com>, Tomoyuki Sahara <sahara@surt.net>
In-Reply-To: <1321630381.56734.YahooMailNeo@web126002.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 16:03:35 -0000

> From: Fran=E7ois-Xavier Le Bail <fx.lebail@yahoo.com>=0A> To: Kerry Lynn =
<kerlyn2001@gmail.com>; Tomoyuki Sahara <sahara@surt.net>=0A>> ____________=
____________________=0A>>  From: Kerry Lynn <kerlyn2001@gmail.com>=0A>> To:=
 Tomoyuki Sahara <sahara@surt.net> =0A>> =0A>> On Thu, Nov 17, 2011 at 9:27=
 PM, Tomoyuki Sahara <sahara@surt.net> =0A> wrote:=0A>> =0A>>> That sounds =
good to me too.=0A>>> =0A>>>>  My ABNF is pretty rusty, so I offer the foll=
owing extension to the =0A> RFC 3986=0A>>>>  IPv6address rule only as a sta=
rting point:=0A>>>>  / "FE80::" [ *3( h16 ":" ) h16 ] [ =0A> "%" 1*4(ALPHA =
/ DIGIT) ]=0A>>> =0A>>> I have some comments:=0A>>> =0A>>> =A0- An interfac=
e name may be longer than 4 characters. =A0But I know we =0A> should=0A>>> =
=A0 =A0have some limit so I suggest 15 because it's maximum length of =0A> =
interface=0A>>> =A0 =A0name on *BSD and Linux systems.=0A>>> =0A>>> =A0- FY=
I, there was an attempt to define textual representation of zone =0A> id:=
=0A>>> =A0 =0A> =A0http://tools.ietf.org/html/draft-ietf-ipngwg-scoping-arc=
h-04#section-12=0A>>> =0A>>> =A0- Can we have a dot in interface name? =A0O=
n Linux systems, VLAN =0A> interfaces=0A>>> =A0 =A0have one. =A0An example =
in the draft above has "%pvc1.3" (may =0A> be an ATM=0A>>> =A0 =A0interface=
?).=0A>>> =0A>>> =0A>> Thanks for the reference. =A0I'll take a look at it =
before revising the =0A> ABNF again.=0A> =0A> Hi,=0A> =0A> In Linux, you ca=
n use any character in VLAN interface name :=0A> examples:=0A> ip link add =
link eth0 name eth0.5=A0 type vlan id 5=0A> ip link add link eth0 name eth0=
-6=A0 type vlan id 6=0A> ip link add link eth0 name eth0#7=A0 type vlan id =
7=0A> ip link add link eth0 name eth0-8=A0 type vlan id 8=0A> ip link add l=
ink eth0 name eth0+9=A0 type vlan id 9=0A> ip link add link eth0 name eth0_=
10=A0 type vlan id 10=0A> ip link add link eth0 name eth0,11=A0 type vlan i=
d 11=0A> ip link add link eth0 name eth0:::12=A0 type vlan id 12=0A> ip lin=
k add link eth0 name eth0.+-=A0 type vlan id 13=0A> =0A> Thanks,=0A> Franco=
is-Xavier=0A=0ALuckily, the "%" is invalid.=0A=0AFrancois-Xavier

From arifumi@nttv6.net  Sat Nov 19 10:32:56 2011
Return-Path: <arifumi@nttv6.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06B7021F84ED for <ipv6@ietfa.amsl.com>; Sat, 19 Nov 2011 10:32:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.705
X-Spam-Level: 
X-Spam-Status: No, score=-102.705 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwSInga6t0a1 for <ipv6@ietfa.amsl.com>; Sat, 19 Nov 2011 10:32:55 -0800 (PST)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by ietfa.amsl.com (Postfix) with ESMTP id C58B221F84CE for <ipv6@ietf.org>; Sat, 19 Nov 2011 10:32:54 -0800 (PST)
Received: from [127.0.0.1] (localhost.nttv6.net [IPv6:::1]) by leo.nttv6.net (8.14.5/8.14.4) with ESMTP id pAJIVArZ069589; Sun, 20 Nov 2011 03:31:11 +0900 (JST) (envelope-from arifumi@nttv6.net)
References: <03FE6A726D13284495EF1787D25F1DF9018D7907@TK5EX14MBXC266.redmond.corp.microsoft.com> <74D26F5C-E768-41D3-8F2C-0CC0ADCA33E4@nttv6.net> <03FE6A726D13284495EF1787D25F1DF9018FE6C5@TK5EX14MBXC265.redmond.corp.microsoft.com>
In-Reply-To: <03FE6A726D13284495EF1787D25F1DF9018FE6C5@TK5EX14MBXC265.redmond.corp.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-2--177096092
Message-Id: <E4ED98A1-EDA3-40A6-9A82-8C1A2726DAC2@nttv6.net>
From: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: Re: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Date: Sun, 20 Nov 2011 03:31:27 +0900
To: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Nov 2011 18:32:56 -0000

--Apple-Mail-2--177096092
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-2022-jp

Hi,

On 2011/11/18, at 14:27, Dmitry Anipko wrote:

> Hello,
> =20
> >> In any case, the policy delivered on the secured channel should be =
used.
> >>That is what the draft suggests.
> >>Make sense ?
> =20
> If the different policy tables were received from different =
administrative domains, I don=1B$B!G=1B(Bt see yet why it would make =
sense to prefer one of them to another based on whether one of the =
channel was secured. In case an interface which delivered secured policy =
table is not preferred by routing metric, the copy of the table received =
over such interface may be irrelevant or harmful.

The policy table is a host-wide policy, and not interface specific.
It can have effects even on the routing policy of the host in that it =
has
effects on destination address selection.

The existence of a secure, trusted channel means that the host
belongs to the administrative domain. In that case, the policy of=20
the un-trusted channel should not override the host-wide policy,
even if the default route is directed to the untrusted interface.

If the admin of the administrative domain allows the simultaneous
use of the untrusted domain and to direct the default route to that
untrusted interface, the admin has to design his distributing policy
so that the policy will not bring bad effects from that. If the admin
does not allow the simultaneous connection, the bad effects need
not be taken care.

Of course, this draft does not preclude configuration option to use
the received policy on the untrusted interface, though.

Best regards,

> =20
> Thanks,
> Dmitry
> =20
> From: Arifumi Matsumoto [mailto:arifumi@nttv6.net]=20
> Sent: Thursday, November 17, 2011 9:14 PM
> To: Dmitry Anipko
> Cc: ipv6@ietf.org
> Subject: Re: multiple policy tables handling in =
draft-ietf-6man-addr-select-opt-01
> =20
> Hi,
> =20
> thank you for your comment.
> =20
> On 2011/11/14, at 14:21, Dmitry Anipko wrote:
>=20
>=20
> Hello,
> =20
> I have a question about this text the -01 revision:
> =20
> >>A node MAY use OPTION_DASP in any of the following two cases:    =20
>                  1: The address selection option is delivered across a =
secure, trusted  =20
>                     channel.     =20
> =20
> The OPTION_DASP is configured by a network administrator, presumably =
based on some knowledge they have about what makes more or less sense in =
the particular network. How whether or not a secure channel has been =
used on one of the networks relates to whether or not the admin of that =
network has knowledge of a completely different network the host may =
simultaneously be connected to?
> =20
> In any case, the policy delivered on the secured channel should be =
used.
> =20
> That is what the draft suggests.
> =20
> Make sense ?


--Apple-Mail-2--177096092
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-2022-jp

<html><head><base href=3D"x-msg://748/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">Hi,<div><br><div><div>On 2011/11/18, at 14:27, =
Dmitry Anipko wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"Section1" style=3D"page: Section1; =
"><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
">Hello,<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">&gt;&gt;</span><span class=3D"Apple-converted-space">&nbsp;</span>In =
any case, the policy delivered on the secured channel should be =
used.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; ">&gt;&gt;That is what the draft =
suggests.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; ">&gt;&gt;Make sense =
?<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">If =
the different policy tables were received from different administrative =
domains, I don=1B$B!G=1B(Bt see yet why it would make sense to prefer =
one of them to another based on whether one of the channel was secured. =
In case an interface which delivered secured policy table is not =
preferred by routing metric, the copy of the table received over such =
interface may be irrelevant or =
harmful.</span></div></div></div></span></blockquote><div><br></div><div>T=
he policy table is a host-wide policy, and not interface =
specific.</div><div>It can have effects even on the routing policy of =
the host in that it has</div><div>effects on destination address =
selection.</div><div><br></div><div>The existence of a secure, trusted =
channel means that the host</div><div>belongs to the&nbsp;administrative =
domain. In that case, the policy of&nbsp;</div><div>the =
un-trusted&nbsp;channel should not override the host-wide =
policy,</div><div>even if the default route is directed to the untrusted =
interface.</div><div><br></div><div>If the admin of the administrative =
domain allows the simultaneous</div><div>use of the untrusted domain and =
to direct the default route to that</div><div>untrusted interface, the =
admin has to design his distributing policy</div><div>so that the policy =
will not bring bad effects from that. If the admin</div><div>does not =
allow the simultaneous connection, the bad effects need</div><div>not be =
taken care.</div><div><br></div><div>Of course, this draft does not =
preclude configuration option to use</div><div>the received =
policy&nbsp;on the untrusted interface, =
though.</div><div><br></div><div>Best regards,</div><br><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"Section1" style=3D"page: Section1; =
"><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); "><o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Thanks,<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Dmitry<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div><div style=3D"border-right-style: =
none; border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; border-top-style: solid; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; =
padding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: =
0in; "><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: =
0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>Arifumi Matsumoto =
[mailto:arifumi@nttv6.net]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Thursday, November 17, 2011 =
9:14 PM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Dmitry =
Anipko<br><b>Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ipv6@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">ipv6@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: multiple policy tables =
handling in =
draft-ietf-6man-addr-select-opt-01<o:p></o:p></span></div></div></div><div=
 style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
">Hi,<o:p></o:p></div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">thank you for your =
comment.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">On 2011/11/14, at 14:21, =
Dmitry Anipko wrote:<o:p></o:p></div></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; =
">Hello,<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">I have a =
question about this text the -01 =
revision:<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">&gt;&gt;A =
node MAY use OPTION_DASP in any of the following two =
cases:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></div></div><div><di=
v style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; &nbsp;&nbsp; 1: The address selection option is delivered across =
a secure, =
trusted&nbsp;&nbsp;&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
channel.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></div></div>=
<div><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">The OPTION_DASP is configured by a network administrator, =
presumably based on some knowledge they have about what makes more or =
less sense in the particular network. How whether or not a secure =
channel has been used on one of the networks relates to whether or not =
the admin of that network has knowledge of a completely different =
network the host may simultaneously be connected =
to?<o:p></o:p></span></div></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">In any case, the policy =
delivered on the secured channel should be =
used.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">That is what the draft =
suggests.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Make sense =
?<o:p></o:p></div></div></div></div></div></div></span></blockquote></div>=
<br></div></body></html>=

--Apple-Mail-2--177096092--

From jari.arkko@piuha.net  Mon Nov 21 10:21:59 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399CE11E80EA for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 10:21:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bq9ogxxZmeR4 for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 10:21:54 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 92AED11E80E8 for <ipv6@ietf.org>; Mon, 21 Nov 2011 10:21:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A9DA42CC5A; Mon, 21 Nov 2011 20:21:53 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rfitT4xZsguj; Mon, 21 Nov 2011 20:21:49 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id C34592CC31; Mon, 21 Nov 2011 20:21:48 +0200 (EET)
Message-ID: <4ECA96BB.1020507@piuha.net>
Date: Mon, 21 Nov 2011 10:21:47 -0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: draft-ietf-6man-exthdr@tools.ietf.org,  IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: AD review of draft-ietf-6man-exthdr
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 18:21:59 -0000

I have reviewed this draft. It is ready to move forward, and I have requested a last call to be initiated. In the meantime, I also had a few mostly editorial comments that you may want to take into account:

>     Also, Several existing deployed IPv6 routers and several existing
>

s/Several/several/

> This document intends
>     to define a standard format for IPv6 extension headers.

This document defines a standard ...

>     The base IPv6 standard [RFC2460  <http://tools.ietf.org/html/rfc2460>] defines 3 extension headers (i.e.
>     Routing Header, Destination Options Header, Hop-by-Hop Options
>     Header) to be used for any new IPv6 options.  The same standard only
>     allows the creation of new Extension Headers in limited circumstances
>     [RFC2460] Section 4.6  <http://tools.ietf.org/html/rfc2460#section-4.6>.
>
>     As noted above, the use of any option with Hop-by-Hop behaviour can
>     be problematic in the global public Internet.  So new IPv6 Extension
>     Header(s) having hop-by-hop behaviour MUST NOT be created or
>     specified.  Also, new options for the existing Hop-by-Hop Header
>     SHOULD NOT be created or specified unless no alternative is feasible.
>     Any proposal to create a new option for the existing Hop-by-Hop
>     Header MUST include a detailed explanation of why the hop-by-hop
>     behaviour is absolutely essential in the Internet-Draft proposing the
>     new option with hop-by-hop behaviour.
>

It might also be useful to point to RFCs 5095 and 5871 as pointing out difficulties that the design of new routing header types can bring. E.g. "Similarly, as discussed in RFCs 5095 and 5871, the design of new Routing Header types may lead to security vulnerabilities and alternatives for such designs need to be carefully assessed."

>     The scheme proposed in this document is not intended to be backward
>     compatible with all the currently defined IPv6 extension headers.  It
>     applies only to newly defined extension headers.  Specifically, the
>     fragment header predates this document and does not follow the format
>     proposed in this document.

Are there others? If yes, it would be good to mention them as well.

Jari


From narten@us.ibm.com  Mon Nov 21 12:46:23 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47A7811E80EA for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 12:46:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yfMlSSX9TF1R for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 12:46:22 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id D26AC11E80DF for <ipv6@ietf.org>; Mon, 21 Nov 2011 12:46:22 -0800 (PST)
Received: from /spool/local by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ipv6@ietf.org> from <narten@us.ibm.com>; Mon, 21 Nov 2011 13:36:17 -0700
Received: from d03relay02.boulder.ibm.com ([9.17.195.227]) by e32.co.us.ibm.com ([192.168.1.132]) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 21 Nov 2011 13:36:16 -0700
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pALKa6pM091116; Mon, 21 Nov 2011 13:36:06 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pALKa5Yt026445; Mon, 21 Nov 2011 13:36:05 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-49-158-47.mts.ibm.com [9.49.158.47]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id pALKa1sf026148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Nov 2011 13:36:03 -0700
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id pALKa0eO019515; Mon, 21 Nov 2011 15:36:00 -0500
Message-Id: <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
In-reply-to: <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
Comments: In-reply-to Ted Lemon <Ted.Lemon@nominum.com> message dated "Mon, 14 Nov 2011 02:24:37 +0000."
Date: Mon, 21 Nov 2011 15:36:00 -0500
From: Thomas Narten <narten@us.ibm.com>
x-cbid: 11112120-3270-0000-0000-000001F5EAA9
Cc: MIF Mailing List <mif@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 20:46:23 -0000

Ted Lemon <Ted.Lemon@nominum.com> writes:

> On Nov 14, 2011, at 9:59 AM, "Ole Troan" <otroan@employees.org> wrote:
> > why not just merge all the information received?
> > e.g. if you get DNS server over DHCP and RA, use all.
> > if you get addresses via SLAAC and DHCP, you use all...

> Because "just merge" is essentially equivalent to "just walk across
> the river without your feet getting wet.".  If you can write a spec
> that does this correctly, you are probably the Messiah.

Isn't this what DHC already does? I.e., you run DHCP on two
interfaces, and get conflicting information.

The existing DHCP specs are silent on this, and the DHC WG has never
been willing to specify how to handle this case.

The case of getting conflicting DNS configuration information via DHC
seems a realistic scenario to me.

How do you propose this get handled?

Are you proposing we solve it for the DHC/RA case, but not for the
DHC/DHC case?

Thomas


From narten@us.ibm.com  Mon Nov 21 12:52:57 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B03721F8AF9 for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 12:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7q6aEcmBRzyG for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 12:52:56 -0800 (PST)
Received: from e6.ny.us.ibm.com (e6.ny.us.ibm.com [32.97.182.146]) by ietfa.amsl.com (Postfix) with ESMTP id A51DD21F8AF5 for <ipv6@ietf.org>; Mon, 21 Nov 2011 12:52:56 -0800 (PST)
Received: from /spool/local by e6.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ipv6@ietf.org> from <narten@us.ibm.com>; Mon, 21 Nov 2011 15:52:55 -0500
Received: from d01relay07.pok.ibm.com ([9.56.227.147]) by e6.ny.us.ibm.com ([192.168.1.106]) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 21 Nov 2011 15:52:00 -0500
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pALKpwNR1863822 for <ipv6@ietf.org>; Mon, 21 Nov 2011 15:51:58 -0500
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pALKpwRH011914 for <ipv6@ietf.org>; Mon, 21 Nov 2011 18:51:58 -0200
Received: from cichlid.raleigh.ibm.com (sig-9-49-158-47.mts.ibm.com [9.49.158.47]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id pALKpv52011816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Nov 2011 18:51:57 -0200
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id pALKptcT019591; Mon, 21 Nov 2011 15:51:56 -0500
Message-Id: <201111212051.pALKptcT019591@cichlid.raleigh.ibm.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Offset Indicating option
In-reply-to: <4EC087DE.8050204@gmail.com>
References: <4E7FDEFA.6060808@gmail.com> <20110926143849.GH2931@verdi> <4E80DBCD.1040308@gmail.com> <20110926220044.GJ2931@verdi> <CAL9jLaa1nS7Dz5CQnpGKHVGoYdp6rNLR7AdXosYeF3EbpjiOuA@mail.gmail.com> <4EC087DE.8050204@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Mon, 14 Nov 2011 16:15:42 +1300."
Date: Mon, 21 Nov 2011 15:51:55 -0500
From: Thomas Narten <narten@us.ibm.com>
x-cbid: 11112120-1976-0000-0000-000005C30722
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 20:52:57 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> writes:

> Chris,

> On 2011-11-14 16:06, Christopher Morrow wrote:
> > Just a question about this idea in general, if one of the reasons to
> > do it is to save middleboxes from doing 'lots of work' ... wouldn't a
> > smart attacker just not put this header in? and then choke the
> > middleboxes?

Actually, I think the argument is not that middleboxes will do less
work if this option is present, it's that they won't do the work at
all in the case where the option is *not* present. I.e., they won't
parse all the extension headers to get to the TCP Port numbers in
order to do (say) ECMP. If they could parse them, i.e., they have the
code and can do so, then they don't need the option in the first
place. I thought the premise for this work was middleboxes that
couldn't be bothered with parsing extension headers properly.

Thus, if a source includes this option, perhaps it will get slightly
better performance because ECMP works better on one of the paths.

If the option is missing, ECMP won't work as well.

IMO, no source will bother to implement the option based on this
cost/benefit.

> I could use that argument against *any* optimisation, couldn't I?
> DoS is hard to defeat.

I think this is backwards. You have previously made the case that
middle boxes can't/won't parse extension headers. So they won't be
doing the extra work if the option is not present. Right?

So this isn't an optimization. This is to get around middleboxes that
are unwilling/unable to implement the specs as specified.

> > 
> > what's the incentive for a source to add this header? (it's not in
> > their interest to make things 'easier' is it?)

> Well, you can argue that it's a small price to get a small improvement
> in response time from busy servers, but I agree, this would be a matter
> of persuading stack vendors to do it because it's good to do it.

Sorry, what has this got to do with "busy servers"? this option is
only for middle boxes. Servers will ignore it.

Thomas


From Ted.Lemon@nominum.com  Mon Nov 21 13:45:56 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C9F11E8119; Mon, 21 Nov 2011 13:45:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6X8DUkiQTjOt; Mon, 21 Nov 2011 13:45:56 -0800 (PST)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id B789211E80ED; Mon, 21 Nov 2011 13:45:54 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKTsrGiYlpmWw6Jm1FRFAY2302acyTXPM/@postini.com; Mon, 21 Nov 2011 13:45:55 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5B6671B826E; Mon, 21 Nov 2011 13:45:45 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 3B379190052; Mon, 21 Nov 2011 13:45:42 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Mon, 21 Nov 2011 13:45:42 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeADLdcAIAAE2+A
Date: Mon, 21 Nov 2011 21:45:41 +0000
Message-ID: <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com> <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com>
In-Reply-To: <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C727F556048CAF43B52EF19ECE5F6794@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 21:45:56 -0000

On Nov 21, 2011, at 3:36 PM, Thomas Narten wrote:
> Isn't this what DHC already does? I.e., you run DHCP on two
> interfaces, and get conflicting information.

I don't know what the antecedent to "this" was intended to be.

> The existing DHCP specs are silent on this, and the DHC WG has never
> been willing to specify how to handle this case.

Right, because it's been our position that this is not a DHCP problem.

> The case of getting conflicting DNS configuration information via DHC
> seems a realistic scenario to me.

It is completely realistic.

> How do you propose this get handled?

I think the right way to handle this is the way that the MIF working group =
has proposed: treat each provisioning domain separately.   Do not try to me=
rge information you have no basis for assuming is valid across provisioning=
 domains (which is all configuration information).   You wouldn't typically=
 send an IP packet with a source address for interface 2 out of interface 2=
.   Why would you query a DNS server out of interface 2 when you learned ab=
out it through interface 1?

> Are you proposing we solve it for the DHC/RA case, but not for the
> DHC/DHC case?

I think that having two ways of configuring things is a bad idea, and hence=
 I claim that standardizing the RA DNS server option was a mistake, one whi=
ch unfortunately can't be undone at this point.   I think that if we are go=
ing to say that RAs and DHCP servers can both provide some piece of configu=
ration information, then we kind of have to treat them as separate provisio=
ning domains.   But we can't really do that, because some information is pr=
ovided only in RAs at the moment.

My main wish is just to not make the mess any worse; secondarily, I'd like =
to do what we can to make it less bad.=

From marc.blanchet@viagenie.ca  Mon Nov 21 13:58:09 2011
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D88B721F87D3; Mon, 21 Nov 2011 13:58:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.483
X-Spam-Level: 
X-Spam-Status: No, score=-102.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpWC+ip-28dw; Mon, 21 Nov 2011 13:57:49 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id 9791A21F8593; Mon, 21 Nov 2011 13:57:49 -0800 (PST)
Received: from [IPv6:2607:fa48:6e6b:c280:15c9:6087:dafd:d077] (unknown [IPv6:2607:fa48:6e6b:c280:15c9:6087:dafd:d077]) by jazz.viagenie.ca (Postfix) with ESMTPSA id D384621F6D; Mon, 21 Nov 2011 16:57:18 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com>
Date: Mon, 21 Nov 2011 16:57:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A43AEC2-9EF2-4F54-8ECE-76A254DD1B39@viagenie.ca>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com> <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com> <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com>
To: ipv6@ietf.org, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 21:58:10 -0000

my take: the MIF problem statement draft about to be published as RFC) =
discusses the various scenarios. probably more exists. But the issue of =
receiving config info from multiple sources is not specific to dhcpv6. =
it is related to any protocol sending config info. so it is a problem of =
pppv4, pppv6, dhcpv4, dhcpv6, RA, maybe even others.  Therefore, we need =
to find the right solution for all the cases together, instead of just =
looking at one specific provisioning protocol IP address family.  In =
this context, it appears to me that the right place to discuss that is =
within MIF wg.

my 2 cents.

Marc.

Le 2011-11-21 =E0 16:45, Ted Lemon a =E9crit :

> On Nov 21, 2011, at 3:36 PM, Thomas Narten wrote:
>> Isn't this what DHC already does? I.e., you run DHCP on two
>> interfaces, and get conflicting information.
>=20
> I don't know what the antecedent to "this" was intended to be.
>=20
>> The existing DHCP specs are silent on this, and the DHC WG has never
>> been willing to specify how to handle this case.
>=20
> Right, because it's been our position that this is not a DHCP problem.
>=20
>> The case of getting conflicting DNS configuration information via DHC
>> seems a realistic scenario to me.
>=20
> It is completely realistic.
>=20
>> How do you propose this get handled?
>=20
> I think the right way to handle this is the way that the MIF working =
group has proposed: treat each provisioning domain separately.   Do not =
try to merge information you have no basis for assuming is valid across =
provisioning domains (which is all configuration information).   You =
wouldn't typically send an IP packet with a source address for interface =
2 out of interface 2.   Why would you query a DNS server out of =
interface 2 when you learned about it through interface 1?
>=20
>> Are you proposing we solve it for the DHC/RA case, but not for the
>> DHC/DHC case?
>=20
> I think that having two ways of configuring things is a bad idea, and =
hence I claim that standardizing the RA DNS server option was a mistake, =
one which unfortunately can't be undone at this point.   I think that if =
we are going to say that RAs and DHCP servers can both provide some =
piece of configuration information, then we kind of have to treat them =
as separate provisioning domains.   But we can't really do that, because =
some information is provided only in RAs at the moment.
>=20
> My main wish is just to not make the mess any worse; secondarily, I'd =
like to do what we can to make it less bad.
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From iesg-secretary@ietf.org  Mon Nov 21 14:42:49 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1982F21F847A; Mon, 21 Nov 2011 14:42:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tnI6EriaDeeQ; Mon, 21 Nov 2011 14:42:44 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABE8211E811F; Mon, 21 Nov 2011 14:42:44 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-6man-exthdr-05.txt> (An uniform format for IPv6 extension headers) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111121224244.27924.70956.idtracker@ietfa.amsl.com>
Date: Mon, 21 Nov 2011 14:42:44 -0800
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 22:42:49 -0000

The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document:
- 'An uniform format for IPv6 extension headers'
  <draft-ietf-6man-exthdr-05.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-12-05. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   In IPv6, optional internet-layer information is encoded in separate
   headers that may be placed between the IPv6 header and the transport
   layer header.  There are a small number of such extension headers
   currently defined.  This document describes the issues that can arise
   when defining new extension headers and discusses the alternative
   extension mechanisms in IPv6.  It also provides a format for defining
   new IPv6 extension headers that would allow implementations to
   process past unknown extension headers.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-6man-exthdr/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-6man-exthdr/


No IPR declarations have been submitted directly on this I-D.



From brian.e.carpenter@gmail.com  Mon Nov 21 18:57:03 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4041311E8087 for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 18:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.2
X-Spam-Level: 
X-Spam-Status: No, score=-103.2 tagged_above=-999 required=5 tests=[AWL=-0.201, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vul5IMCXhOic for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 18:56:59 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E58AA11E8085 for <ipv6@ietf.org>; Mon, 21 Nov 2011 18:56:58 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so3817287vcb.31 for <ipv6@ietf.org>; Mon, 21 Nov 2011 18:56:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=c9FemJ/rG4gBlfT9l/y0rj1d3jbwuQBA4FwQdWYeen8=; b=FxoJkd4vwH8v5LRIw63KrFzL+O/JysVv9N9UMoSgrBuO1mVXuM873h7ublv0EUJurs IXCdRmJdtluCJwz/Se4mHuBQ38ETI2SoPi4ILmmYKYkUJkbkgkeCdC46wFcFt5eT3CTB fObGPnLAfeFK6omcX/NuujBpVGpuRAr5uqVM8=
Received: by 10.52.21.148 with SMTP id v20mr16087920vde.89.1321930618488; Mon, 21 Nov 2011 18:56:58 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id a2sm11412294vdj.3.2011.11.21.18.56.55 (version=SSLv3 cipher=OTHER); Mon, 21 Nov 2011 18:56:57 -0800 (PST)
Message-ID: <4ECB0F84.5080802@gmail.com>
Date: Tue, 22 Nov 2011 15:57:08 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Tomoyuki Sahara <sahara@surt.net>
Subject: Re: Link-local IPv6 addresses in URIs
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com>	<4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com>	<880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org>	<CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com> <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
In-Reply-To: <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 02:57:03 -0000

On 2011-11-18 15:27, Tomoyuki Sahara wrote:
> Hi,
> 
> That sounds good to me too.
> 
>> My ABNF is pretty rusty, so I offer the following extension to the RFC 3986
>> IPv6address rule only as a starting point:
>> / "FE80::" [ *3( h16 ":" ) h16 ] [ "%" 1*4(ALPHA / DIGIT) ]

That's one option; another one is to define the syntax for *any*
address format and restrict it to fe80::/10 by a SHOULD.
I'm inclined towards the latter, in case some other use case
shows up later.

> 
> I have some comments:
> 
>   - An interface name may be longer than 4 characters.  But I know we should
>     have some limit so I suggest 15 because it's maximum length of interface
>     name on *BSD and Linux systems.

Seems reasonable.

> 
>   - FYI, there was an attempt to define textual representation of zone id:
>     http://tools.ietf.org/html/draft-ietf-ipngwg-scoping-arch-04#section-12

That's RFC 4007 now.

> 
>   - Can we have a dot in interface name?  On Linux systems, VLAN interfaces
>     have one.  An example in the draft above has "%pvc1.3" (may be an ATM
>     interface?).

Yes, we can use the character set "unreserved" from the URI syntax
which is defined by

   unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"

      Brian

From marka@isc.org  Mon Nov 21 19:30:20 2011
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0F1311E814F for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 19:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.456
X-Spam-Level: 
X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-+IwC9ohM1G for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 19:30:20 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 6820411E810C for <ipv6@ietf.org>; Mon, 21 Nov 2011 19:30:20 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 2267CC9422; Tue, 22 Nov 2011 03:30:06 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id D7D97216C6B; Tue, 22 Nov 2011 03:30:05 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id B6D1817DF522; Tue, 22 Nov 2011 14:30:03 +1100 (EST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Mark Andrews <marka@isc.org>
Subject: Link-local IPv6 addresses in the DNS
In-reply-to: Your message of "Tue, 22 Nov 2011 15:57:08 +1300." <4ECB0F84.5080802@gmail.com>
Date: Tue, 22 Nov 2011 14:30:03 +1100
Message-Id: <20111122033003.B6D1817DF522@drugs.dv.isc.org>
Cc: 6man <ipv6@ietf.org>, Tomoyuki Sahara <sahara@surt.net>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 03:30:21 -0000

On a related issue to link locals in URI's, we don't currently have
a good method of supporting link locals in the DNS.  Sure we can
add them as AAAA records but they are essentially useless as the
scope information is lost.  People keep saying use LL for disconnected
but it just doesn't work without more support.

Mark

DNS
host.example.net. SAAAA  FE80::1 link.example.net.
host.example.net. SAAAA  2001:DB8::1 .		; "." indicates global scope
host.example.net. SAAAA  ::ffff:198.51.100.0 .	; "." indicates global scope
host.example.net. AAAA  2001:DB8::1
host.example.net. A  198.51.100.1

RA LINK-NAME link.example.net
DHCP LINK-NAME link.example.net

getaddrinfo()
AI_FILTERED  filter scoped addresses which don't match a local scope name.
	     Set in AI_DEFAULT.

If you get a response to a SAAAA lookup you don't need to do a A/AAAA lookup
as it is a superset of A and AAAA.

host.example.net SAAAA :: .  indicates a machine that exist but is off net

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From suresh.krishnan@ericsson.com  Mon Nov 21 21:08:23 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01D2B21F8AF4 for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 21:08:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.466
X-Spam-Level: 
X-Spam-Status: No, score=-106.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QOYk0vF4Gamt for <ipv6@ietfa.amsl.com>; Mon, 21 Nov 2011 21:08:22 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2B221F8AEA for <ipv6@ietf.org>; Mon, 21 Nov 2011 21:08:22 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAM58E4H024354; Mon, 21 Nov 2011 23:08:17 -0600
Received: from [164.48.125.10] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.137.0; Tue, 22 Nov 2011 00:08:08 -0500
Message-ID: <4ECB2E32.8030001@ericsson.com>
Date: Tue, 22 Nov 2011 00:08:02 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: AD review of draft-ietf-6man-exthdr
References: <4ECA96BB.1020507@piuha.net>
In-Reply-To: <4ECA96BB.1020507@piuha.net>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-6man-exthdr@tools.ietf.org" <draft-ietf-6man-exthdr@tools.ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 05:08:23 -0000

Hi Jari,
  Thanks for the review. Please find responses inline.


On 11/21/2011 01:21 PM, Jari Arkko wrote:
> I have reviewed this draft. It is ready to move forward, and I have requested a last call to be initiated. In the meantime, I also had a few mostly editorial comments that you may want to take into account:
> 
>>     Also, Several existing deployed IPv6 routers and several existing
>>
> 
> s/Several/several/

Will fix.

> 
>> This document intends
>>     to define a standard format for IPv6 extension headers.
> 
> This document defines a standard ...

Will fix.

> 
>>     The base IPv6 standard [RFC2460  <http://tools.ietf.org/html/rfc2460>] defines 3 extension headers (i.e.
>>     Routing Header, Destination Options Header, Hop-by-Hop Options
>>     Header) to be used for any new IPv6 options.  The same standard only
>>     allows the creation of new Extension Headers in limited circumstances
>>     [RFC2460] Section 4.6  <http://tools.ietf.org/html/rfc2460#section-4.6>.
>>
>>     As noted above, the use of any option with Hop-by-Hop behaviour can
>>     be problematic in the global public Internet.  So new IPv6 Extension
>>     Header(s) having hop-by-hop behaviour MUST NOT be created or
>>     specified.  Also, new options for the existing Hop-by-Hop Header
>>     SHOULD NOT be created or specified unless no alternative is feasible.
>>     Any proposal to create a new option for the existing Hop-by-Hop
>>     Header MUST include a detailed explanation of why the hop-by-hop
>>     behaviour is absolutely essential in the Internet-Draft proposing the
>>     new option with hop-by-hop behaviour.
>>
> 
> It might also be useful to point to RFCs 5095 and 5871 as pointing out difficulties that the design of new routing header types can bring. E.g. "Similarly, as discussed in RFCs 5095 and 5871, the design of new Routing Header types may lead to security vulnerabilities and alternatives for such designs need to be carefully assessed."

These two RFCs deal with security issues specific to routing headers
that are not widely applicable to other extension headers that may be
created. Also new routing header types can be created without even
creating any new extension headers. Is there something specific from
these RFCs that you think will be applicable here?

> 
>>     The scheme proposed in this document is not intended to be backward
>>     compatible with all the currently defined IPv6 extension headers.  It
>>     applies only to newly defined extension headers.  Specifically, the
>>     fragment header predates this document and does not follow the format
>>     proposed in this document.
> 
> Are there others? If yes, it would be good to mention them as well.

AH and ESP do not follow this scheme either but there was no consensus
to treat them as extension headers since they could be used with IPv4 as
well. I argued that RFC2460 identifies them as extension headers but
there were not many takers for that argument.

Thanks
Suresh

From brian@innovationslab.net  Tue Nov 22 05:12:04 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C1D21F8D66 for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 05:12:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IjjbRINhJHpI for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 05:12:03 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 96E8721F8D48 for <ipv6@ietf.org>; Tue, 22 Nov 2011 05:12:03 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 2AA23880C7 for <ipv6@ietf.org>; Tue, 22 Nov 2011 05:12:03 -0800 (PST)
Received: from Littlejohn.local (c-68-33-164-105.hsd1.dc.comcast.net [68.33.164.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id BB62E130003 for <ipv6@ietf.org>; Tue, 22 Nov 2011 05:12:02 -0800 (PST)
Message-ID: <4ECB9FA1.8090708@innovationslab.net>
Date: Tue, 22 Nov 2011 08:12:01 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Offset Indicating option
References: <4E7FDEFA.6060808@gmail.com> <20110926143849.GH2931@verdi> <4E80DBCD.1040308@gmail.com> <20110926220044.GJ2931@verdi> <CAL9jLaa1nS7Dz5CQnpGKHVGoYdp6rNLR7AdXosYeF3EbpjiOuA@mail.gmail.com> <4EC087DE.8050204@gmail.com> <201111212051.pALKptcT019591@cichlid.raleigh.ibm.com>
In-Reply-To: <201111212051.pALKptcT019591@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 13:12:04 -0000

Thomas,

On 11/21/11 3:51 PM, Thomas Narten wrote:
> Brian E Carpenter<brian.e.carpenter@gmail.com>  writes:
>
>> Chris,
>
>> On 2011-11-14 16:06, Christopher Morrow wrote:
>>> Just a question about this idea in general, if one of the reasons to
>>> do it is to save middleboxes from doing 'lots of work' ... wouldn't a
>>> smart attacker just not put this header in? and then choke the
>>> middleboxes?
>
> Actually, I think the argument is not that middleboxes will do less
> work if this option is present, it's that they won't do the work at
> all in the case where the option is *not* present. I.e., they won't
> parse all the extension headers to get to the TCP Port numbers in
> order to do (say) ECMP. If they could parse them, i.e., they have the
> code and can do so, then they don't need the option in the first
> place. I thought the premise for this work was middleboxes that
> couldn't be bothered with parsing extension headers properly.
>
> Thus, if a source includes this option, perhaps it will get slightly
> better performance because ECMP works better on one of the paths.
>
> If the option is missing, ECMP won't work as well.

I am hoping that the use of the flow label for ECMP will mitigate this 
type of failure scenario.

>
> IMO, no source will bother to implement the option based on this
> cost/benefit.
>
>> I could use that argument against *any* optimisation, couldn't I?
>> DoS is hard to defeat.
>
> I think this is backwards. You have previously made the case that
> middle boxes can't/won't parse extension headers. So they won't be
> doing the extra work if the option is not present. Right?
>
> So this isn't an optimization. This is to get around middleboxes that
> are unwilling/unable to implement the specs as specified.
>
>>>
>>> what's the incentive for a source to add this header? (it's not in
>>> their interest to make things 'easier' is it?)
>
>> Well, you can argue that it's a small price to get a small improvement
>> in response time from busy servers, but I agree, this would be a matter
>> of persuading stack vendors to do it because it's good to do it.
>
> Sorry, what has this got to do with "busy servers"? this option is
> only for middle boxes. Servers will ignore it.

They will ignore it because they need to process all the options 
included in the packet.

Regards,
Brian H.



From ichiroumakino@gmail.com  Tue Nov 22 05:18:40 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FFB921F8CA3; Tue, 22 Nov 2011 05:18:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.559
X-Spam-Level: 
X-Spam-Status: No, score=-3.559 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cjh+Xw5uZ9-H; Tue, 22 Nov 2011 05:18:39 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1D821F8CA2; Tue, 22 Nov 2011 05:18:39 -0800 (PST)
Received: by wwe3 with SMTP id 3so7216977wwe.1 for <multiple recipients>; Tue, 22 Nov 2011 05:18:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=vLvqvycQR/Qk+9s7/K25kYzjx+PRYb60ICw9p3eT+pk=; b=hjLk2ozLzE45FWBL/6snPxKd/lcMDxUjvnqXs/RM/8HdGtuUb7vakItOLtuDbrevqm 0VLXBuI/oB4DHIh4/7lgujJsaiwX8xulxZgf3wEJRVIGQslRR/DFV6lKoDGvYJR8PY3W 6+uDh8SbgrHtKHr1I+dqAmNDiUnqoMKXPtZpM=
Received: by 10.227.207.146 with SMTP id fy18mr8335362wbb.18.1321967916906; Tue, 22 Nov 2011 05:18:36 -0800 (PST)
Received: from ams3-vpn-dhcp4888.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id em4sm16579372wbb.20.2011.11.22.05.18.32 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Nov 2011 05:18:35 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com>
Date: Tue, 22 Nov 2011 14:18:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4EFC3D8-AF56-4D90-AE08-767FC68CC468@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com> <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com> <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: Thomas Narten <narten@us.ibm.com>, MIF Mailing List <mif@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 13:18:40 -0000

>> How do you propose this get handled?
>=20
> I think the right way to handle this is the way that the MIF working =
group has proposed: treat each provisioning domain separately.   Do not =
try to merge information you have no basis for assuming is valid across =
provisioning domains (which is all configuration information). You =
wouldn't typically send an IP packet with a source address for interface =
2 out of interface 2.   Why would you query a DNS server out of =
interface 2 when you learned about it through interface 1?

for clarification, that was not my proposal. my suggestion was to merge =
all information within one "provisioning domain".
unsure if we will end up with provisioning domain =3D link, as detection =
of multiple provisioning domains on a single link may not be trivial in =
all corner cases.

cheers,
Ole



From Ted.Lemon@nominum.com  Tue Nov 22 07:31:46 2011
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0A021F8C6B; Tue, 22 Nov 2011 07:31:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level: 
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVQMgANepJNT; Tue, 22 Nov 2011 07:31:45 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 4B28C21F8C60; Tue, 22 Nov 2011 07:31:45 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTsvAYCxrZBBXrBtpYQP4cofz7XIKlAc7@postini.com; Tue, 22 Nov 2011 07:31:45 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4EBE41B827D; Tue, 22 Nov 2011 07:31:44 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 3B048190052; Tue, 22 Nov 2011 07:31:44 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Tue, 22 Nov 2011 07:31:44 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeADLdcAIAAE2+AgAEEqoCAACU3AA==
Date: Tue, 22 Nov 2011 15:31:43 +0000
Message-ID: <DF1C8CC9-13D0-494B-AB45-5A17AECD1CB4@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com> <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com> <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com> <F4EFC3D8-AF56-4D90-AE08-767FC68CC468@employees.org>
In-Reply-To: <F4EFC3D8-AF56-4D90-AE08-767FC68CC468@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_DF1C8CC913D0494BAB455A17AECD1CB4nominumcom_"
MIME-Version: 1.0
Cc: Thomas Narten <narten@us.ibm.com>, MIF Mailing List <mif@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 15:31:46 -0000

--_000_DF1C8CC913D0494BAB455A17AECD1CB4nominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Nov 22, 2011, at 8:18 AM, Ole Troan wrote:
for clarification, that was not my proposal. my suggestion was to merge all=
 information within one "provisioning domain".
unsure if we will end up with provisioning domain =3D link, as detection of=
 multiple provisioning domains on a single link may not be trivial in all c=
orner cases.

I agree with you that right now detecting provisioning domains is not trivi=
al; indeed, in some cases it's impossible.   However, if you think provisio=
ning domain =3D=3D link, then that's a problem that needs fixing.   Indeed,=
 that's *the* problem that needs fixing.   I think we have to fix it; if we=
 punt, we're going to pay for it later.


--_000_DF1C8CC913D0494BAB455A17AECD1CB4nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <2DE43083E24BF04E9495A21BC58F95C9@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Nov 22, 2011, at 8:18 AM, Ole Troan wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">for
 clarification, that was not my proposal. my suggestion was to merge all in=
formation within one &quot;provisioning domain&quot;.</span></blockquote>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">unsure
 if we will end up with provisioning domain =3D link, as detection of multi=
ple provisioning domains on a single link may not be trivial in all corner =
cases.</span></blockquote>
</div>
<br>
<div>I agree with you that right now detecting provisioning domains is not =
trivial; indeed, in some cases it's impossible. &nbsp; However, if you thin=
k provisioning domain =3D=3D link, then that's a problem that needs fixing.=
 &nbsp; Indeed, that's *the* problem that needs
 fixing. &nbsp; I think we have to fix it; if we punt, we're going to pay f=
or it later.</div>
<div><br>
</div>
</body>
</html>

--_000_DF1C8CC913D0494BAB455A17AECD1CB4nominumcom_--

From pch-b29AA871B@u-1.phicoh.com  Tue Nov 22 08:35:06 2011
Return-Path: <pch-b29AA871B@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6ED321F8BCD for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 08:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fIsSKdxkI5TB for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 08:35:06 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id D9CF821F8BAB for <ipv6@ietf.org>; Tue, 22 Nov 2011 08:35:05 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #76) id m1RStJG-0001jCC; Tue, 22 Nov 2011 17:35:02 +0100
Message-Id: <m1RStJG-0001jCC@stereo.hq.phicoh.net>
To: Mark Andrews <marka@isc.org>
Subject: Re: Link-local IPv6 addresses in the DNS 
From: Philip Homburg <pch-6man-1a@u-1.phicoh.com>
Sender: pch-b29AA871B@u-1.phicoh.com
In-reply-to: Your message of "Tue, 22 Nov 2011 14:30:03 +1100 ." <20111122033003.B6D1817DF522@drugs.dv.isc.org> 
Date: Tue, 22 Nov 2011 17:34:49 +0100
X-Mailman-Approved-At: Tue, 22 Nov 2011 08:41:58 -0800
Cc: Tomoyuki Sahara <sahara@surt.net>, 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 16:35:06 -0000

In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:
>On a related issue to link locals in URI's, we don't currently have
>a good method of supporting link locals in the DNS.  Sure we can
>add them as AAAA records but they are essentially useless as the
>scope information is lost.  People keep saying use LL for disconnected
>but it just doesn't work without more support.

For disconnected operation, why not have getaddrinfo fill in the scope?
Just set it to the interface over which the DNS reply arrived. 

I have to admit that this may become a bit tricky if the DNS resolver is local
or if interface information is lost in some other way.


From brian.e.carpenter@gmail.com  Tue Nov 22 13:09:58 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA73A21F8770 for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 13:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.499
X-Spam-Level: 
X-Spam-Status: No, score=-104.499 tagged_above=-999 required=5 tests=[AWL=1.100, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H3Xcoa9aJk6f for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 13:09:58 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9A24921F8753 for <ipv6@ietf.org>; Tue, 22 Nov 2011 13:09:57 -0800 (PST)
Received: by ywt34 with SMTP id 34so733198ywt.31 for <ipv6@ietf.org>; Tue, 22 Nov 2011 13:09:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=762v6eFeGs8/TWJ6jwNCCD4anun4okQwAGz845faGV4=; b=FjNxJoEAb6QwosCDwiQG5xXsNoyWpFQpiaQB671UITnTpwtkiRMxt1hSmotVezYR+I 28K5EoYp7tt5q111KdCjz2sWrEC65NmGsPz/+AuWttNaDgSbpkpkCvkJvOqd2KdjKwwk yfuOVeLEaBvlOoQVOLeMBr5zmP7xScM7Zcy1Y=
Received: by 10.213.109.15 with SMTP id h15mr1789588ebp.70.1321995185397; Tue, 22 Nov 2011 12:53:05 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id 5sm45302086eev.2.2011.11.22.12.53.01 (version=SSLv3 cipher=OTHER); Tue, 22 Nov 2011 12:53:04 -0800 (PST)
Message-ID: <4ECC0BAB.4040401@gmail.com>
Date: Wed, 23 Nov 2011 09:52:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Philip Homburg <pch-6man-1a@u-1.phicoh.com>
Subject: Re: Link-local IPv6 addresses in the DNS
References: <m1RStJG-0001jCC@stereo.hq.phicoh.net>
In-Reply-To: <m1RStJG-0001jCC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Tomoyuki Sahara <sahara@surt.net>, 6man <ipv6@ietf.org>, Mark Andrews <marka@isc.org>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 21:09:58 -0000

On 2011-11-23 05:34, Philip Homburg wrote:
> In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:
>> On a related issue to link locals in URI's, we don't currently have
>> a good method of supporting link locals in the DNS.  Sure we can
>> add them as AAAA records but they are essentially useless as the
>> scope information is lost.  People keep saying use LL for disconnected
>> but it just doesn't work without more support.

Other people keep saying "use ULA for disconnected". The fact
that you can put ULA into (er, local) DNS without any fancy
stuff is a distinct advantage.

IMHO link-local should be used only for bootstrapping a host and
for diagnostic purposes. I guess I could statically configure a
printer on fe00::a%1 if I really had no choice.

   Brian

> 
> For disconnected operation, why not have getaddrinfo fill in the scope?
> Just set it to the interface over which the DNS reply arrived. 
> 
> I have to admit that this may become a bit tricky if the DNS resolver is local
> or if interface information is lost in some other way.
> 
> 

From brian.e.carpenter@gmail.com  Tue Nov 22 13:36:02 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E9F911E80D4 for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 13:36:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.368
X-Spam-Level: 
X-Spam-Status: No, score=-103.368 tagged_above=-999 required=5 tests=[AWL=-0.069, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uqa6tyMArUnr for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 13:36:01 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id C20B911E80D3 for <ipv6@ietf.org>; Tue, 22 Nov 2011 13:36:01 -0800 (PST)
Received: by yenm7 with SMTP id m7so796603yen.31 for <ipv6@ietf.org>; Tue, 22 Nov 2011 13:36:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LQY/+9uBCgKE92AO7JZP/c43Dd+Iku0QgpHHLIJhcqM=; b=BLHAh4y/ctHJIY2k579cZnaMSvNXeZFDcmlFwY04lDDWLUX2qJ9sLhP5q2T5fOBmC9 jdlr2/ov4NX45Hev3onSWZvc1IFk9gDjoFahibyf1NPTIiabf/U6D91NoMnm3r/WgQtk QKQoJCH/N7n5Elg42oUjIYugiJ0g4z6H/YES8=
Received: by 10.213.22.131 with SMTP id n3mr1860341ebb.131.1321997760749; Tue, 22 Nov 2011 13:36:00 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id d6sm45536371eec.10.2011.11.22.13.35.57 (version=SSLv3 cipher=OTHER); Tue, 22 Nov 2011 13:36:00 -0800 (PST)
Message-ID: <4ECC15BB.9010503@gmail.com>
Date: Wed, 23 Nov 2011 10:35:55 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?RnJhbsOnb2lzLVhhdmllciBMZSBCYWls?= <fx.lebail@yahoo.com>
Subject: Re: Link-local IPv6 addresses in URIs
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com>	<4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com>	<880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org>	<CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com>	<CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com>	<CABOxzu2KwBwyY_6q5if-hXFJRG95dXst4mNV7DX1yEx750b81Q@mail.gmail.com>	<1321630381.56734.YahooMailNeo@web126002.mail.ne1.yahoo.com> <1321632209.56936.YahooMailNeo@web126013.mail.ne1.yahoo.com>
In-Reply-To: <1321632209.56936.YahooMailNeo@web126013.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: 6man <ipv6@ietf.org>, Tomoyuki Sahara <sahara@surt.net>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 21:36:02 -0000

On 2011-11-19 05:03, Fran=C3=A7ois-Xavier Le Bail wrote:

=2E..
>> In Linux, you can use any character in VLAN interface name :
>> examples:
>> ip link add link eth0 name eth0.5  type vlan id 5
>> ip link add link eth0 name eth0-6  type vlan id 6
>> ip link add link eth0 name eth0#7  type vlan id 7
>> ip link add link eth0 name eth0-8  type vlan id 8
>> ip link add link eth0 name eth0+9  type vlan id 9
>> ip link add link eth0 name eth0_10  type vlan id 10
>> ip link add link eth0 name eth0,11  type vlan id 11
>> ip link add link eth0 name eth0:::12  type vlan id 12
>> ip link add link eth0 name eth0.+-  type vlan id 13
>>
>> Thanks,
>> Francois-Xavier
>=20
> Luckily, the "%" is invalid.

Unfortunately, the obvious subset in URI syntax is more limited:

   unreserved  =3D ALPHA / DIGIT / "-" / "." / "_" / "~"

If you could live without #+,.: it would be much simpler.

   Brian


From brian.e.carpenter@gmail.com  Tue Nov 22 16:03:14 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 344F31F0C73 for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 16:03:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.517
X-Spam-Level: 
X-Spam-Status: No, score=-104.517 tagged_above=-999 required=5 tests=[AWL=1.082, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id paujPN8X+Dct for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 16:03:13 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7930C1F0C6E for <ipv6@ietf.org>; Tue, 22 Nov 2011 16:03:13 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so970825vcb.31 for <ipv6@ietf.org>; Tue, 22 Nov 2011 16:03:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Z42uPdqLNE9rizU6SUofZXpAcVEUVOvQ42tS0UtIOzg=; b=MusE4YyBQeJWC3By9dYZ++bHkO96llC7gsiBnPB0XIsnEiZlUV5nr6p0NkM0cgMtfQ XGJ/HPrjhq3ignUXbkG1aLP8q/yjVRVWuPy+LQ3tdCd752KNBnks34sVYBE8d301TPYU eE47zuK8n1QcxcIDqv4OO+gpANQQJxYNXfh9I=
Received: by 10.220.150.142 with SMTP id y14mr1539414vcv.269.1322006592924; Tue, 22 Nov 2011 16:03:12 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id eo2sm13160732vdb.5.2011.11.22.16.03.10 (version=SSLv3 cipher=OTHER); Tue, 22 Nov 2011 16:03:12 -0800 (PST)
Message-ID: <4ECC3846.9080708@gmail.com>
Date: Wed, 23 Nov 2011 13:03:18 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Kerry Lynn <kerlyn2001@gmail.com>
Subject: Re: Link-local IPv6 addresses in the DNS
References: <m1RStJG-0001jCC@stereo.hq.phicoh.net>	<4ECC0BAB.4040401@gmail.com> <CABOxzu3Xd=0iXauAUCO0ZeqjwZah8_+OE3n_TuLhTNZpT9BoUw@mail.gmail.com>
In-Reply-To: <CABOxzu3Xd=0iXauAUCO0ZeqjwZah8_+OE3n_TuLhTNZpT9BoUw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2011 00:03:14 -0000

Kerry,

> In the case of link-
> local adresses stored in AAAA records, the zone index would seem to
> indicate the corresponding interface with respect to the *server* (assuming
> a multi-homed server here).

Which is completely and utterly irrelevant to any host except
that one particular physical DNS server. So I don't see what
possible use it has for anyone.

Regards
   Brian

On 2011-11-23 10:56, Kerry Lynn wrote:
> On Tue, Nov 22, 2011 at 3:52 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> On 2011-11-23 05:34, Philip Homburg wrote:
>>> In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:
>>>> On a related issue to link locals in URI's, we don't currently have
>>>> a good method of supporting link locals in the DNS.  Sure we can
>>>> add them as AAAA records but they are essentially useless as the
>>>> scope information is lost.  People keep saying use LL for disconnected
>>>> but it just doesn't work without more support.
>> Other people keep saying "use ULA for disconnected". The fact
>> that you can put ULA into (er, local) DNS without any fancy
>> stuff is a distinct advantage.
>>
>> IMHO link-local should be used only for bootstrapping a host and
>> for diagnostic purposes. I guess I could statically configure a
>> printer on fe00::a%1 if I really had no choice.
>>
>> This is a distinctly different problem than the one that kicked off the
> link-
> local discussion.  In the web browser case, you know the link-local
> destination address of the server a priori but it only has validity with
> respect to a particular link, and there's no way to indicate the zone
> index to the browser (assuming multi-homed client here).  The once-
> existing capability was removed because there is no RFC support for it.
> 
> The DNS case seems like a server-side issue.  In the case of link-
> local adresses stored in AAAA records, the zone index would seem to
> indicate the corresponding interface with respect to the *server* (assuming
> a multi-homed server here).  What's more, the DNS server would need to
> keep track of the interface on which the query arrived and only respond
> with a link-local address if the client and server are on the same
> interface.
> 
> Some additional observations:
> - If you want to stay with link-local addresses then perhaps multicast
>   DNS is the best solution for you.
> - If you want to stay with unicast DNS, then ULAs have the advantage
>   of being routable and the problem goes away.
> - If you want to stay with link-local addresses *and* DNS, then perhaps
>   you need to engage dnsext WG to discuss the server-side issues.
> 
> -K-
> 
> 
>   Brian
>>> For disconnected operation, why not have getaddrinfo fill in the scope?
>>> Just set it to the interface over which the DNS reply arrived.
>>>
>>> I have to admit that this may become a bit tricky if the DNS resolver is
>> local
>>> or if interface information is lost in some other way.
>>>
>>>
> 

From brian.e.carpenter@gmail.com  Tue Nov 22 16:14:53 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B25281F0C85 for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 16:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.532
X-Spam-Level: 
X-Spam-Status: No, score=-104.532 tagged_above=-999 required=5 tests=[AWL=1.067, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 426GYIVt9zOt for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 16:14:53 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 20AFF1F0C7E for <ipv6@ietf.org>; Tue, 22 Nov 2011 16:14:53 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so945311vbb.31 for <ipv6@ietf.org>; Tue, 22 Nov 2011 16:14:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=reoMjxr2xm5SfTap6qLcfBwLNleWBpkem8uIvU/PR88=; b=LDNRfmuUqI7aRSCIz9Hacw6MDwF4i74APSkSCrAV5FxFbnxhrjKJNcG1fzAX7l0yH+ XqeuqMi6pwiqhQ8wblZNTxgP2U1BFMxc8QA2iICViTepShRPLtFhp2O0rJd3zC+xTrqz 7YeZ47g24tc9oWgC7F1WT2pBgCACysFrsCxz0=
Received: by 10.52.23.12 with SMTP id i12mr23072326vdf.37.1322007292067; Tue, 22 Nov 2011 16:14:52 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id z6sm21014257vdg.18.2011.11.22.16.14.48 (version=SSLv3 cipher=OTHER); Tue, 22 Nov 2011 16:14:51 -0800 (PST)
Message-ID: <4ECC3B00.4070508@gmail.com>
Date: Wed, 23 Nov 2011 13:14:56 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Kerry Lynn <kerlyn2001@gmail.com>
Subject: Re: Link-local IPv6 addresses in the DNS
References: <m1RStJG-0001jCC@stereo.hq.phicoh.net>	<4ECC0BAB.4040401@gmail.com>	<CABOxzu3Xd=0iXauAUCO0ZeqjwZah8_+OE3n_TuLhTNZpT9BoUw@mail.gmail.com> <CABOxzu1j=YUJ+ioS_VGzJvma__amyf74_RoSEuLc6qD6MXizLA@mail.gmail.com>
In-Reply-To: <CABOxzu1j=YUJ+ioS_VGzJvma__amyf74_RoSEuLc6qD6MXizLA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>, Philip Homburg <pch-6man-1a@u-1.phicoh.com>, Mark Andrews <marka@isc.org>, Tomoyuki Sahara <sahara@surt.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2011 00:14:53 -0000

On 2011-11-23 11:09, Kerry Lynn wrote:
> On Tue, Nov 22, 2011 at 4:56 PM, Kerry Lynn <kerlyn2001@gmail.com> wrote:
> 
>> On Tue, Nov 22, 2011 at 3:52 PM, Brian E Carpenter <
>> brian.e.carpenter@gmail.com> wrote:
>>
>>> On 2011-11-23 05:34, Philip Homburg wrote:
>>>> In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:
>>>>> On a related issue to link locals in URI's, we don't currently have
>>>>> a good method of supporting link locals in the DNS.  Sure we can
>>>>> add them as AAAA records but they are essentially useless as the
>>>>> scope information is lost.  People keep saying use LL for disconnected
>>>>> but it just doesn't work without more support.
>>> Other people keep saying "use ULA for disconnected". The fact
>>> that you can put ULA into (er, local) DNS without any fancy
>>> stuff is a distinct advantage.
>>>
>>> IMHO link-local should be used only for bootstrapping a host and
>>> for diagnostic purposes. I guess I could statically configure a
>>> printer on fe00::a%1 if I really had no choice.
>>>
>>> BTW, I realized this whole conversation is probably re: local host files
> just after I hit the "send" button ;-)

Yes, I could put

fe80::a%1  printer1.local

in my hosts file I guess. Except that on my o/s, the zone ID is
not handled by the resolver at all, unsurprisingly.

   Brian


From marka@isc.org  Tue Nov 22 17:48:21 2011
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67D3521F84F8 for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 17:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.458
X-Spam-Level: 
X-Spam-Status: No, score=-3.458 tagged_above=-999 required=5 tests=[AWL=1.141,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p+0f0dTzmTSh for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 17:48:21 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id DAE9821F84DD for <ipv6@ietf.org>; Tue, 22 Nov 2011 17:48:20 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id EF75BC9473; Wed, 23 Nov 2011 01:48:07 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 88597216C6A; Wed, 23 Nov 2011 01:48:07 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 444C617E5E83; Wed, 23 Nov 2011 12:48:03 +1100 (EST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <m1RStJG-0001jCC@stereo.hq.phicoh.net> <4ECC0BAB.4040401@gmail.com>
Subject: Re: Link-local IPv6 addresses in the DNS
In-reply-to: Your message of "Wed, 23 Nov 2011 09:52:59 +1300." <4ECC0BAB.4040401@gmail.com>
Date: Wed, 23 Nov 2011 12:48:02 +1100
Message-Id: <20111123014803.444C617E5E83@drugs.dv.isc.org>
Cc: 6man <ipv6@ietf.org>, Kerry Lynn <kerlyn2001@gmail.com>, Philip Homburg <pch-6man-1a@u-1.phicoh.com>, Tomoyuki Sahara <sahara@surt.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2011 01:48:21 -0000

In message <4ECC0BAB.4040401@gmail.com>, Brian E Carpenter writes:
> On 2011-11-23 05:34, Philip Homburg wrote:
> > In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:
> >> On a related issue to link locals in URI's, we don't currently have
> >> a good method of supporting link locals in the DNS.  Sure we can
> >> add them as AAAA records but they are essentially useless as the
> >> scope information is lost.  People keep saying use LL for disconnected
> >> but it just doesn't work without more support.
> 
> Other people keep saying "use ULA for disconnected". The fact
> that you can put ULA into (er, local) DNS without any fancy
> stuff is a distinct advantage.
> 
> IMHO link-local should be used only for bootstrapping a host and
> for diagnostic purposes. I guess I could statically configure a
> printer on fe00::a%1 if I really had no choice.
> 
>    Brian

ULA has similar scope issues.  It's just that the OS don't knock
you over when you do bind(), connect(), sendto() and sendmsg()
without scope information.  You can avoid using non local ULA with
the same filtering mechanisms.

> > For disconnected operation, why not have getaddrinfo fill in the scope?
> > Just set it to the interface over which the DNS reply arrived. 
> > 
> > I have to admit that this may become a bit tricky if the DNS resolver is lo
> cal
> > or if interface information is lost in some other way.
> > 
> > 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From huitema@microsoft.com  Tue Nov 22 19:28:40 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D86821F84A6 for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 19:28:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5 tests=[AWL=-3.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UkCfXA-VUm8t for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 19:28:39 -0800 (PST)
Received: from AM1EHSOBE006.bigfish.com (am1ehsobe006.messaging.microsoft.com [213.199.154.209]) by ietfa.amsl.com (Postfix) with ESMTP id 71FD621F84A5 for <ipv6@ietf.org>; Tue, 22 Nov 2011 19:28:39 -0800 (PST)
Received: from mail21-am1-R.bigfish.com (10.3.201.249) by AM1EHSOBE006.bigfish.com (10.3.204.26) with Microsoft SMTP Server id 14.1.225.22; Wed, 23 Nov 2011 03:27:57 +0000
Received: from mail21-am1 (localhost [127.0.0.1])	by mail21-am1-R.bigfish.com (Postfix) with ESMTP id 8879D16038C; Wed, 23 Nov 2011 03:29:08 +0000 (UTC)
X-SpamScore: 0
X-BigFish: VS0(zzzz1202hzzz2fh2a8h668h839h944h)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14HUBC103.redmond.corp.microsoft.com; RD:none; EFVD:NLI
Received-SPF: pass (mail21-am1: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=huitema@microsoft.com; helo=TK5EX14HUBC103.redmond.corp.microsoft.com ; icrosoft.com ; 
Received: from mail21-am1 (localhost.localdomain [127.0.0.1]) by mail21-am1 (MessageSwitch) id 1322018948482103_14663; Wed, 23 Nov 2011 03:29:08 +0000 (UTC)
Received: from AM1EHSMHS005.bigfish.com (unknown [10.3.201.243])	by mail21-am1.bigfish.com (Postfix) with ESMTP id 65C0FE0043; Wed, 23 Nov 2011 03:29:08 +0000 (UTC)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.8) by AM1EHSMHS005.bigfish.com (10.3.207.105) with Microsoft SMTP Server (TLS) id 14.1.225.22; Wed, 23 Nov 2011 03:27:56 +0000
Received: from TK5EX14MBXC274.redmond.corp.microsoft.com ([169.254.3.79]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.01.0355.002; Tue, 22 Nov 2011 19:28:34 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Philip Homburg <pch-6man-1a@u-1.phicoh.com>
Subject: RE: Link-local IPv6 addresses in the DNS
Thread-Topic: Link-local IPv6 addresses in the DNS
Thread-Index: AQHMqVslW6M2OjKFOUyrTCbwZ8aB4ZW5zOkg
Date: Wed, 23 Nov 2011 03:28:33 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0DC107@TK5EX14MBXC274.redmond.corp.microsoft.com>
References: <m1RStJG-0001jCC@stereo.hq.phicoh.net> <4ECC0BAB.4040401@gmail.com>
In-Reply-To: <4ECC0BAB.4040401@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.33]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: 6man <ipv6@ietf.org>, Tomoyuki Sahara <sahara@surt.net>, Mark Andrews <marka@isc.org>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2011 03:28:40 -0000

> IMHO link-local should be used only for bootstrapping a host and for diag=
nostic purposes. I guess I could statically configure a printer on fe00::a%=
1 if I really had no choice.

I would rather not rely on DNS for that. Local discovery protocols like UPN=
P look more adequate to the task of printer discovery.

-- Christian Huitema




From kerlyn2001@gmail.com  Tue Nov 22 13:56:38 2011
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F53D1F0C6D for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 13:56:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.478
X-Spam-Level: 
X-Spam-Status: No, score=-4.478 tagged_above=-999 required=5 tests=[AWL=1.120,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KzI5OLFjgm6Y for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 13:56:37 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 80BDA1F0C6B for <ipv6@ietf.org>; Tue, 22 Nov 2011 13:56:37 -0800 (PST)
Received: by yenm7 with SMTP id m7so816024yen.31 for <ipv6@ietf.org>; Tue, 22 Nov 2011 13:56:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SDehWm+5GdZFBE04A0qrmEdXRwkrjHBpTKwBFweTzqM=; b=gXrlk2YcXctnXbiC7e6qWFMdD1VxpY1HDrzsZs3TiqjLe7NcWV+0PPwcUhFzIgToIg ywIedVOImaY3YHPomanSga5OYRFY4XaSCh/a65eKblhwVTIzO6aS/t6CT+YDh4m3ZoMz z8eKwFJlnvEagnwSFlnekzGw8nh4QOH3gU/wo=
MIME-Version: 1.0
Received: by 10.14.14.37 with SMTP id c37mr1139217eec.88.1321998996528; Tue, 22 Nov 2011 13:56:36 -0800 (PST)
Received: by 10.14.7.80 with HTTP; Tue, 22 Nov 2011 13:56:36 -0800 (PST)
In-Reply-To: <4ECC0BAB.4040401@gmail.com>
References: <m1RStJG-0001jCC@stereo.hq.phicoh.net> <4ECC0BAB.4040401@gmail.com>
Date: Tue, 22 Nov 2011 16:56:36 -0500
Message-ID: <CABOxzu3Xd=0iXauAUCO0ZeqjwZah8_+OE3n_TuLhTNZpT9BoUw@mail.gmail.com>
Subject: Re: Link-local IPv6 addresses in the DNS
From: Kerry Lynn <kerlyn2001@gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=0016e659fe0c94dedc04b259e0a0
X-Mailman-Approved-At: Wed, 23 Nov 2011 05:29:02 -0800
Cc: 6man <ipv6@ietf.org>, Philip Homburg <pch-6man-1a@u-1.phicoh.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Tomoyuki Sahara <sahara@surt.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 21:56:38 -0000

--0016e659fe0c94dedc04b259e0a0
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 22, 2011 at 3:52 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 2011-11-23 05:34, Philip Homburg wrote:
> > In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:
> >> On a related issue to link locals in URI's, we don't currently have
> >> a good method of supporting link locals in the DNS.  Sure we can
> >> add them as AAAA records but they are essentially useless as the
> >> scope information is lost.  People keep saying use LL for disconnected
> >> but it just doesn't work without more support.
>
> Other people keep saying "use ULA for disconnected". The fact
> that you can put ULA into (er, local) DNS without any fancy
> stuff is a distinct advantage.
>
> IMHO link-local should be used only for bootstrapping a host and
> for diagnostic purposes. I guess I could statically configure a
> printer on fe00::a%1 if I really had no choice.
>
> This is a distinctly different problem than the one that kicked off the
link-
local discussion.  In the web browser case, you know the link-local
destination address of the server a priori but it only has validity with
respect to a particular link, and there's no way to indicate the zone
index to the browser (assuming multi-homed client here).  The once-
existing capability was removed because there is no RFC support for it.

The DNS case seems like a server-side issue.  In the case of link-
local adresses stored in AAAA records, the zone index would seem to
indicate the corresponding interface with respect to the *server* (assuming
a multi-homed server here).  What's more, the DNS server would need to
keep track of the interface on which the query arrived and only respond
with a link-local address if the client and server are on the same
interface.

Some additional observations:
- If you want to stay with link-local addresses then perhaps multicast
  DNS is the best solution for you.
- If you want to stay with unicast DNS, then ULAs have the advantage
  of being routable and the problem goes away.
- If you want to stay with link-local addresses *and* DNS, then perhaps
  you need to engage dnsext WG to discuss the server-side issues.

-K-


  Brian
>
> >
> > For disconnected operation, why not have getaddrinfo fill in the scope?
> > Just set it to the interface over which the DNS reply arrived.
> >
> > I have to admit that this may become a bit tricky if the DNS resolver is
> local
> > or if interface information is lost in some other way.
> >
> >
>

--0016e659fe0c94dedc04b259e0a0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Tue, Nov 22, 2011 at 3:52 PM, Brian E Car=
penter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com"=
>brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex;">
<div class=3D"im">On 2011-11-23 05:34, Philip Homburg wrote:<br>
&gt; In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:<br>
&gt;&gt; On a related issue to link locals in URI&#39;s, we don&#39;t curre=
ntly have<br>
&gt;&gt; a good method of supporting link locals in the DNS. =A0Sure we can=
<br>
&gt;&gt; add them as AAAA records but they are essentially useless as the<b=
r>
&gt;&gt; scope information is lost. =A0People keep saying use LL for discon=
nected<br>
&gt;&gt; but it just doesn&#39;t work without more support.<br>
<br>
</div>Other people keep saying &quot;use ULA for disconnected&quot;. The fa=
ct<br>
that you can put ULA into (er, local) DNS without any fancy<br>
stuff is a distinct advantage.<br>
<br>
IMHO link-local should be used only for bootstrapping a host and<br>
for diagnostic purposes. I guess I could statically configure a<br>
printer on fe00::a%1 if I really had no choice.<br>
<font color=3D"#888888"><br></font></blockquote><div>This is a distinctly d=
ifferent problem than the one that kicked off the link-</div><div>local dis=
cussion. =A0In the web browser case, you know the link-local</div><div>dest=
ination address of the server a priori but it only has validity with</div>
<div>respect to a particular link, and there&#39;s no way to indicate the z=
one</div><div>index to the browser (assuming multi-homed client here). =A0T=
he once-</div><div>existing capability was removed=A0because there is no RF=
C support for it.</div>
<div><br></div><div>The DNS case seems like a server-side issue. =A0In the =
case of link-</div><div>local adresses stored in AAAA records, the zone ind=
ex would seem to</div><div>indicate the corresponding interface with respec=
t to the *server* (assuming</div>
<div>a multi-homed server here). =A0What&#39;s more, the DNS server would n=
eed to</div><div>keep track of the interface on which the query arrived and=
 only respond</div><div>with a link-local address if the client and server =
are on the same interface.</div>
<div><br></div><div>Some additional observations:</div><div>- If you want t=
o stay with link-local addresses then perhaps multicast</div><div>=A0 DNS i=
s the best solution for you.</div><div>- If you want to stay with unicast D=
NS, then ULAs have the advantage</div>
<div>=A0 of being routable and the problem goes away.</div><div>- If you wa=
nt to stay with link-local addresses *and* DNS, then perhaps</div><div>=A0 =
you need to engage dnsext WG to discuss the server-side issues.</div><div><=
br>
</div><div>-K-</div><div><br></div><div><br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex;"><font color=3D"#888888">
 =A0 Brian<br>
</font><div><div></div><div class=3D"h5"><br>
&gt;<br>
&gt; For disconnected operation, why not have getaddrinfo fill in the scope=
?<br>
&gt; Just set it to the interface over which the DNS reply arrived.<br>
&gt;<br>
&gt; I have to admit that this may become a bit tricky if the DNS resolver =
is local<br>
&gt; or if interface information is lost in some other way.<br>
&gt;<br>
&gt;<br>
</div></div></blockquote></div><br>

--0016e659fe0c94dedc04b259e0a0--

From kerlyn2001@gmail.com  Tue Nov 22 14:09:31 2011
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECB421F85AE for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 14:09:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.665
X-Spam-Level: 
X-Spam-Status: No, score=-4.665 tagged_above=-999 required=5 tests=[AWL=0.933,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QsYFg5dMJVka for <ipv6@ietfa.amsl.com>; Tue, 22 Nov 2011 14:09:30 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8048F21F85AA for <ipv6@ietf.org>; Tue, 22 Nov 2011 14:09:30 -0800 (PST)
Received: by ywt34 with SMTP id 34so790533ywt.31 for <ipv6@ietf.org>; Tue, 22 Nov 2011 14:09:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OEWrdvPVp7kLqbBgMGauLb3wB14A0LwTGwjOs2eWKH8=; b=R7aWzpxq7f1fUPTIKT9wEWVgZb2499HU+qqFv7Fj+1RJdBksYUwVvXjQeDRTL1qsqA dc9lSZ2qx5EGV/+gJD8qM79kCW9Wzs5wVlpgrCSDLym7SmZCqCQyVpUXtqKgnqei9ofp DD5ANFD/k08ejII4gYN/2eEZCcKZjTDRPV+fw=
MIME-Version: 1.0
Received: by 10.213.17.145 with SMTP id s17mr1718392eba.14.1321999769470; Tue, 22 Nov 2011 14:09:29 -0800 (PST)
Received: by 10.14.7.80 with HTTP; Tue, 22 Nov 2011 14:09:29 -0800 (PST)
In-Reply-To: <CABOxzu3Xd=0iXauAUCO0ZeqjwZah8_+OE3n_TuLhTNZpT9BoUw@mail.gmail.com>
References: <m1RStJG-0001jCC@stereo.hq.phicoh.net> <4ECC0BAB.4040401@gmail.com> <CABOxzu3Xd=0iXauAUCO0ZeqjwZah8_+OE3n_TuLhTNZpT9BoUw@mail.gmail.com>
Date: Tue, 22 Nov 2011 17:09:29 -0500
Message-ID: <CABOxzu1j=YUJ+ioS_VGzJvma__amyf74_RoSEuLc6qD6MXizLA@mail.gmail.com>
Subject: Re: Link-local IPv6 addresses in the DNS
From: Kerry Lynn <kerlyn2001@gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=0015174c3422a7092104b25a0e56
X-Mailman-Approved-At: Wed, 23 Nov 2011 05:29:02 -0800
Cc: 6man <ipv6@ietf.org>, Philip Homburg <pch-6man-1a@u-1.phicoh.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Tomoyuki Sahara <sahara@surt.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 22:09:31 -0000

--0015174c3422a7092104b25a0e56
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 22, 2011 at 4:56 PM, Kerry Lynn <kerlyn2001@gmail.com> wrote:

>
> On Tue, Nov 22, 2011 at 3:52 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>
>> On 2011-11-23 05:34, Philip Homburg wrote:
>> > In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:
>> >> On a related issue to link locals in URI's, we don't currently have
>> >> a good method of supporting link locals in the DNS.  Sure we can
>> >> add them as AAAA records but they are essentially useless as the
>> >> scope information is lost.  People keep saying use LL for disconnected
>> >> but it just doesn't work without more support.
>>
>> Other people keep saying "use ULA for disconnected". The fact
>> that you can put ULA into (er, local) DNS without any fancy
>> stuff is a distinct advantage.
>>
>> IMHO link-local should be used only for bootstrapping a host and
>> for diagnostic purposes. I guess I could statically configure a
>> printer on fe00::a%1 if I really had no choice.
>>
>> BTW, I realized this whole conversation is probably re: local host files
just after I hit the "send" button ;-)


> This is a distinctly different problem than the one that kicked off the
> link-
> local discussion.  In the web browser case, you know the link-local
> destination address of the server a priori but it only has validity with
> respect to a particular link, and there's no way to indicate the zone
> index to the browser (assuming multi-homed client here).  The once-
> existing capability was removed because there is no RFC support for it.
>
> The DNS case seems like a server-side issue.  In the case of link-
> local adresses stored in AAAA records, the zone index would seem to
> indicate the corresponding interface with respect to the *server* (assuming
> a multi-homed server here).  What's more, the DNS server would need to
> keep track of the interface on which the query arrived and only respond
> with a link-local address if the client and server are on the same
> interface.
>
> Some additional observations:
> - If you want to stay with link-local addresses then perhaps multicast
>   DNS is the best solution for you.
> - If you want to stay with unicast DNS, then ULAs have the advantage
>   of being routable and the problem goes away.
> - If you want to stay with link-local addresses *and* DNS, then perhaps
>   you need to engage dnsext WG to discuss the server-side issues.
>
> -K-
>
>
>   Brian
>>
>> >
>> > For disconnected operation, why not have getaddrinfo fill in the scope?
>> > Just set it to the interface over which the DNS reply arrived.
>> >
>> > I have to admit that this may become a bit tricky if the DNS resolver
>> is local
>> > or if interface information is lost in some other way.
>> >
>> >
>>
>
>

--0015174c3422a7092104b25a0e56
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 22, 2011 at 4:56 PM, Kerry Lynn <span dir=3D"ltr">&lt;<a href=
=3D"mailto:kerlyn2001@gmail.com">kerlyn2001@gmail.com</a>&gt;</span> wrote:=
<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><div class=3D"gmail_quote"><div class=3D"im">On Tue, Nov 22, 2011 at 3:=
52 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.ca=
rpenter@gmail.com" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div>On 2011-11-23 05:34, Philip Homburg wrote:<br>
&gt; In your letter dated Tue, 22 Nov 2011 14:30:03 +1100 you wrote:<br>
&gt;&gt; On a related issue to link locals in URI&#39;s, we don&#39;t curre=
ntly have<br>
&gt;&gt; a good method of supporting link locals in the DNS. =A0Sure we can=
<br>
&gt;&gt; add them as AAAA records but they are essentially useless as the<b=
r>
&gt;&gt; scope information is lost. =A0People keep saying use LL for discon=
nected<br>
&gt;&gt; but it just doesn&#39;t work without more support.<br>
<br>
</div>Other people keep saying &quot;use ULA for disconnected&quot;. The fa=
ct<br>
that you can put ULA into (er, local) DNS without any fancy<br>
stuff is a distinct advantage.<br>
<br>
IMHO link-local should be used only for bootstrapping a host and<br>
for diagnostic purposes. I guess I could statically configure a<br>
printer on fe00::a%1 if I really had no choice.<br>
<font color=3D"#888888"><br></font></blockquote></div></div></blockquote><d=
iv>BTW, I realized this whole conversation is probably re: local host files=
</div><div>just after I hit the &quot;send&quot; button ;-)</div><div>=A0</=
div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"gmail_quote"><div class=3D"im=
"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<font color=3D"#888888"></font></blockquote></div><div>This is a distinctly=
 different problem than the one that kicked off the link-</div><div>local d=
iscussion. =A0In the web browser case, you know the link-local</div><div>de=
stination address of the server a priori but it only has validity with</div=
>

<div>respect to a particular link, and there&#39;s no way to indicate the z=
one</div><div>index to the browser (assuming multi-homed client here). =A0T=
he once-</div><div>existing capability was removed=A0because there is no RF=
C support for it.</div>

<div><br></div><div>The DNS case seems like a server-side issue. =A0In the =
case of link-</div><div>local adresses stored in AAAA records, the zone ind=
ex would seem to</div><div>indicate the corresponding interface with respec=
t to the *server* (assuming</div>

<div>a multi-homed server here). =A0What&#39;s more, the DNS server would n=
eed to</div><div>keep track of the interface on which the query arrived and=
 only respond</div><div>with a link-local address if the client and server =
are on the same interface.</div>

<div><br></div><div>Some additional observations:</div><div>- If you want t=
o stay with link-local addresses then perhaps multicast</div><div>=A0 DNS i=
s the best solution for you.</div><div>- If you want to stay with unicast D=
NS, then ULAs have the advantage</div>

<div>=A0 of being routable and the problem goes away.</div><div>- If you wa=
nt to stay with link-local addresses *and* DNS, then perhaps</div><div>=A0 =
you need to engage dnsext WG to discuss the server-side issues.</div><div>
<br>
</div><font color=3D"#888888"><div>-K-</div></font><div class=3D"im"><div><=
br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font color=3D"#8888=
88">
 =A0 Brian<br>
</font><div><div></div><div><br>
&gt;<br>
&gt; For disconnected operation, why not have getaddrinfo fill in the scope=
?<br>
&gt; Just set it to the interface over which the DNS reply arrived.<br>
&gt;<br>
&gt; I have to admit that this may become a bit tricky if the DNS resolver =
is local<br>
&gt; or if interface information is lost in some other way.<br>
&gt;<br>
&gt;<br>
</div></div></blockquote></div></div><br>
</blockquote></div><br>

--0015174c3422a7092104b25a0e56--

From pch-b29AA871B@u-1.phicoh.com  Wed Nov 23 05:00:02 2011
Return-Path: <pch-b29AA871B@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAD7021F8C67 for <ipv6@ietfa.amsl.com>; Wed, 23 Nov 2011 05:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mVE8O-er0uXg for <ipv6@ietfa.amsl.com>; Wed, 23 Nov 2011 05:00:02 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2B921F8C66 for <ipv6@ietf.org>; Wed, 23 Nov 2011 05:00:00 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #76) id m1RTCQh-0001iXC; Wed, 23 Nov 2011 13:59:59 +0100
Message-Id: <m1RTCQh-0001iXC@stereo.hq.phicoh.net>
To: Mark Andrews <marka@isc.org>
Subject: Re: Link-local IPv6 addresses in the DNS 
From: Philip Homburg <pch-6man-1a@u-1.phicoh.com>
Sender: pch-b29AA871B@u-1.phicoh.com
References: <m1RStJG-0001jCC@stereo.hq.phicoh.net> <4ECC0BAB.4040401@gmail.com> <20111123014803.444C617E5E83@drugs.dv.isc.org> 
In-reply-to: Your message of "Wed, 23 Nov 2011 12:48:02 +1100 ." <20111123014803.444C617E5E83@drugs.dv.isc.org> 
Date: Wed, 23 Nov 2011 13:59:53 +0100
X-Mailman-Approved-At: Wed, 23 Nov 2011 05:29:02 -0800
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2011 13:00:02 -0000

In your letter dated Wed, 23 Nov 2011 12:48:02 +1100 you wrote:
>ULA has similar scope issues.  It's just that the OS don't knock
>you over when you do bind(), connect(), sendto() and sendmsg()
>without scope information.  You can avoid using non local ULA with
>the same filtering mechanisms.

I think this a different discussion. It is whether you want to mix local and
global information in DNS. My preference would be to keep it separate (i.e.
never have globally visible zones that contain local addresses) but other
people may think differently.

However, that is a much more generic discussion that doesn't belong on this
list, but should on dnsext or something like that.



From fx.lebail@yahoo.com  Wed Nov 23 05:57:19 2011
Return-Path: <fx.lebail@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8B1B21F8C8E for <ipv6@ietfa.amsl.com>; Wed, 23 Nov 2011 05:57:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.155
X-Spam-Level: 
X-Spam-Status: No, score=-0.155 tagged_above=-999 required=5 tests=[AWL=-0.456, BAYES_50=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XYG-BjrjeX8a for <ipv6@ietfa.amsl.com>; Wed, 23 Nov 2011 05:57:19 -0800 (PST)
Received: from nm35-vm1.bullet.mail.ne1.yahoo.com (nm35-vm1.bullet.mail.ne1.yahoo.com [98.138.229.97]) by ietfa.amsl.com (Postfix) with SMTP id 2717421F8C85 for <ipv6@ietf.org>; Wed, 23 Nov 2011 05:57:19 -0800 (PST)
Received: from [98.138.90.50] by nm35.bullet.mail.ne1.yahoo.com with NNFMP; 23 Nov 2011 13:57:16 -0000
Received: from [98.138.89.234] by tm3.bullet.mail.ne1.yahoo.com with NNFMP; 23 Nov 2011 13:57:16 -0000
Received: from [127.0.0.1] by omp1049.mail.ne1.yahoo.com with NNFMP; 23 Nov 2011 13:57:16 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 175993.56771.bm@omp1049.mail.ne1.yahoo.com
Received: (qmail 1145 invoked by uid 60001); 23 Nov 2011 13:57:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1322056636; bh=JqfnBndwisqxwFeisWZlBxqWK5gBxWCd9QafJFQ6wGE=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=xuT3scYTQPu26xc+jvCcnaqLBzVpWBH7xEuGHdHiN1YKicfqda85NNUqehkJL68DsfQEO7da2+fZryinWE66zotRn+2euUXAxpIsvzAj/Ybub/M/fPsLGrUw15YGFQPASmyUV3/DTHMcgatcvxh9HEc2wrxnTL1AZgseEdIdSuM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Nol3XJE3T3mjAsu8+C13/qsQ7utDmOiq8Xt+RoUcgegQg03O/sUhhCV2BMtJ4/MeyusZmOhngSJniCk/vwYjfHknjIzzdGcF76rdWu4V0r+TjZPDbtetTqbQqC6pkAA8aa3yUmDl0UYPyr4beY+wYioXKvHtdfwwMi78bTJoZgk=;
X-YMail-OSG: 4WXtSEsVM1nunoxc.mcIAVIqXcjGxMmp.Z59c88RhoV_is. 0vjPjF1AxRDVnCR0tT7F8Tgv_GFaHq_k.aoe6hjgJxkRLpKoVMcFqnUGgBp_ xskfSbmlMLm5CIH8JqRBaGmiD8EF7sCmiYQCTmJy4mFY.jRysBW0gSC5ic_G TSgyJg6l49OF27Vy1JDPiLAg3eGyFTfSnvVlXhjHYF4Bp9KFGwuYBCyYHGfb SHdoqU3P833kOlQ7hrLNqdfD3g8OSROxEoljlJ_0tVGatNfbIJ0OD5eNmIfa LOqrcruS3A57Az5A9LWqXor_4fh.MbMruoVSZVJmmds05jAHa1HMk2To6PkI 0wb42cyjMLujYR6PY3mLMcOGW0RXHt5XtvhPBHeC0lV92vse2ZUnmN1jEWyJ RhGHBVy37RerFroDDt4.h7yL0upyWsxggzcRu2Z8yXGBMjaMaJvH0gJgk3OJ 2zFqTWKh5
Received: from [193.49.124.107] by web126010.mail.ne1.yahoo.com via HTTP; Wed, 23 Nov 2011 05:57:16 PST
X-Mailer: YahooMailWebService/0.8.115.325013
References: <CABOxzu0np9tCJgurrL6zCc1CpHd6KbrUdwnL5UocE6TM8a_G2w@mail.gmail.com> <4EC0E1FD.6050107@gmail.com> <4EC494EB.4070000@gmail.com> <880C9B8D-9DCD-4ED7-8FA0-5BBDBB37E25E@tzi.org> <CABOxzu1Rwj9Aa8oOZcqQDHVef52R04FcXBo6HwzCubvss=WGuw@mail.gmail.com> <CAH=tA5s1zEhcUm6y1E+BU0VLEiu+qHFTJATPpd+_GKf7JNtwXw@mail.gmail.com> <CABOxzu2KwBwyY_6q5if-hXFJRG95dXst4mNV7DX1yEx750b81Q@mail.gmail.com> <1321630381.56734.YahooMailNeo@web126002.mail.ne1.yahoo.com> <1321632209.56936.YahooMailNeo@web126013.mail.ne1.yahoo.com> <4ECC15BB.9010503@gmail.com>
Message-ID: <1322056636.95026.YahooMailNeo@web126010.mail.ne1.yahoo.com>
Date: Wed, 23 Nov 2011 05:57:16 -0800 (PST)
From: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
Subject: Re: Link-local IPv6 addresses in URIs
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4ECC15BB.9010503@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 6man <ipv6@ietf.org>, Tomoyuki Sahara <sahara@surt.net>, Kerry Lynn <kerlyn2001@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: =?iso-8859-1?Q?Fran=E7ois-Xavier_Le_Bail?= <fx.lebail@yahoo.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2011 13:57:19 -0000

> From: Brian E Carpenter <brian.e.carpenter@gmail.com>=0A> To: Fran=E7ois-=
Xavier Le Bail <fx.lebail@yahoo.com>=0A> Cc: Kerry Lynn <kerlyn2001@gmail.c=
om>; Tomoyuki Sahara <sahara@surt.net>; 6man <ipv6@ietf.org>=0A> Sent: Tues=
day, November 22, 2011 10:35 PM=0A> Subject: Re: Link-local IPv6 addresses =
in URIs=0A> =0A> On 2011-11-19 05:03, Fran=E7ois-Xavier Le Bail wrote:=0A> =
=0A> ...=0A>>>  In Linux, you can use any character in VLAN interface name =
:=0A>>>  examples:=0A>>>  ip link add link eth0 name eth0.5=A0 type vlan id=
 5=0A>>>  ip link add link eth0 name eth0-6=A0 type vlan id 6=0A>>>  ip lin=
k add link eth0 name eth0#7=A0 type vlan id 7=0A>>>  ip link add link eth0 =
name eth0-8=A0 type vlan id 8=0A>>>  ip link add link eth0 name eth0+9=A0 t=
ype vlan id 9=0A>>>  ip link add link eth0 name eth0_10=A0 type vlan id 10=
=0A>>>  ip link add link eth0 name eth0,11=A0 type vlan id 11=0A>>>  ip lin=
k add link eth0 name eth0:::12=A0 type vlan id 12=0A>>>  ip link add link e=
th0 name eth0.+-=A0 type vlan id 13=0A>>> =0A>>>  Thanks,=0A>>>  Francois-X=
avier=0A>> =0A>>  Luckily, the "%" is invalid.=0A> =0A> Unfortunately, the =
obvious subset in URI syntax is more limited:=0A> =0A> =A0  unreserved=A0 =
=3D ALPHA / DIGIT / "-" / "." / "_" / =0A> "~"=0A> =0A> If you could live w=
ithout #+,.: it would be much simpler.=0A> =0A> =A0  Brian=0A=0AI totally a=
gree, my (unclear) message was only a warning for Linux users.=0A=0AFran=E7=
ois-Xavier=0A

From internet-drafts@ietf.org  Mon Nov 28 11:00:31 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5D61F0C41; Mon, 28 Nov 2011 11:00:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSYkjWbllwKS; Mon, 28 Nov 2011 11:00:30 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0E0B1F0C3D; Mon, 28 Nov 2011 11:00:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-3627-historic-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111128190030.17335.6978.idtracker@ietfa.amsl.com>
Date: Mon, 28 Nov 2011 11:00:30 -0800
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Nov 2011 19:00:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the IPv6 Maintenance Working Group of the=
 IETF.

	Title           : RFC3627 to Historic status
	Author(s)       : Wesley George
	Filename        : draft-ietf-6man-3627-historic-00.txt
	Pages           : 4
	Date            : 2011-11-28

   This document moves RFC3627 (Use of /127 Prefix Length Between
   Routers Considered Harmful) to HISTORIC status to reflect the updated
   guidance contained in RFC6164 (Using 127-Bit IPv6 Prefixes on Inter-
   Router Links).  While a standards track document already supersedes
   an informational document and therefore RFC6164 is the appropriate
   guidance to follow when the two documents are in conflict, this links
   the two documents so that it is clearer that the IETF has updated
   guidance on the matter.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-3627-historic-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-3627-historic-00.txt


From wesley.george@twcable.com  Tue Nov 29 06:03:04 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D76EA21F85DB for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 06:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.187
X-Spam-Level: 
X-Spam-Status: No, score=0.187 tagged_above=-999 required=5 tests=[AWL=-0.650,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  MANGLED_TOOL=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X4PeV9ZdD6-e for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 06:03:03 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 4997821F852E for <ipv6@ietf.org>; Tue, 29 Nov 2011 06:03:03 -0800 (PST)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,590,1315195200"; d="scan'208";a="303130831"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 29 Nov 2011 08:58:04 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Tue, 29 Nov 2011 09:03:00 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Date: Tue, 29 Nov 2011 09:02:58 -0500
Subject: ready for WGLC? (was RE: I-D Action: draft-ietf-6man-3627-historic-00.txt)
Thread-Topic: ready for WGLC? (was RE: I-D Action: draft-ietf-6man-3627-historic-00.txt)
Thread-Index: AcyuAAm/NRYxjwynQsGh13WpGcFgTQAnye6Q
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791452CA9574@PRVPEXVS03.corp.twcable.com>
References: <20111128190030.17335.6978.idtracker@ietfa.amsl.com>
In-Reply-To: <20111128190030.17335.6978.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2011 14:03:04 -0000

This is simply a name-change to reflect WG adoption. All feedback that I've=
 received was addressed in the revision of draft-george-6man from 00 to 01,=
 so I believe that this document is ready for WGLC. Chairs, if you agree, c=
ould you please put forward the formal LC?

http://tools.ietf.org/html/draft-ietf-6man-3627-historic-00

Thanks,

Wes George

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Monday, November 28, 2011 2:01 PM
> To: i-d-announce@ietf.org
> Cc: ipv6@ietf.org
> Subject: I-D Action: draft-ietf-6man-3627-historic-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the IPv6 Maintenance Working
> Group of the IETF.
>
>       Title           : RFC3627 to Historic status
>       Author(s)       : Wesley George
>       Filename        : draft-ietf-6man-3627-historic-00.txt
>       Pages           : 4
>       Date            : 2011-11-28
>
>    This document moves RFC3627 (Use of /127 Prefix Length Between
>    Routers Considered Harmful) to HISTORIC status to reflect the
> updated
>    guidance contained in RFC6164 (Using 127-Bit IPv6 Prefixes on Inter-
>    Router Links).  While a standards track document already supersedes
>    an informational document and therefore RFC6164 is the appropriate
>    guidance to follow when the two documents are in conflict, this
> links
>    the two documents so that it is clearer that the IETF has updated
>    guidance on the matter.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-6man-3627-historic-
> 00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-6man-3627-historic-00.txt
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From brian@innovationslab.net  Tue Nov 29 07:52:00 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8131F0C53 for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 07:52:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dk3gTD1gQ7aE for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 07:51:55 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id C97501F0C55 for <ipv6@ietf.org>; Tue, 29 Nov 2011 07:51:54 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 8801B8818C; Tue, 29 Nov 2011 07:51:54 -0800 (PST)
Received: from tigers.local (unknown [75.94.92.25]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 0B59D130003; Tue, 29 Nov 2011 07:51:53 -0800 (PST)
Message-ID: <4ED4FF87.80703@innovationslab.net>
Date: Tue, 29 Nov 2011 10:51:35 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.24) Gecko/20111103 Thunderbird/3.1.16
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2011 15:52:00 -0000

All,
     This message starts a two week 6MAN Working Group on advancing:

Title     : RFC3627 to Historic status
Author(s) : Wesley George
Filename  : draft-ietf-6man-3627-historic-00.txt
Pages     : 4
Date      : 2011-11-28

as Informational.  Substantive comments and statements of support for
advancing this document should be directed to the mailing list.
Editorial suggestions can be sent to the authors.  This last call will
end on December 13, 2011.

Regards,
Brian Haberman & Bob Hinden

From brian.e.carpenter@gmail.com  Tue Nov 29 12:18:39 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58F381F0CA6 for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 12:18:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ME4M4REkVhfg for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 12:18:37 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7ACD31F0CA4 for <ipv6@ietf.org>; Tue, 29 Nov 2011 12:18:37 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so11544180bkb.31 for <ipv6@ietf.org>; Tue, 29 Nov 2011 12:18:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DdKxBvJA+KJGGBth5+GdVWAGUG2pbQz2gLR8IsnuJxA=; b=Vitwd8iDEqKqfgtec/pkANdZ5ddf3KQu7XZwYcR2ekb46yHgaklTqYSoQ+WpN/j3Bp w1vimgx42Ete5t9M4gnHPx6ndJC3qaKvGY55tXl7S+9GqQJW0VNEv0zquanQ1c8jL5sG tFcisTeBmMue+XL8W3/9RA+5dTms/1rnJ2EEo=
Received: by 10.204.129.70 with SMTP id n6mr52857129bks.0.1322597916568; Tue, 29 Nov 2011 12:18:36 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id x14sm39376136bkf.10.2011.11.29.12.18.34 (version=SSLv3 cipher=OTHER); Tue, 29 Nov 2011 12:18:35 -0800 (PST)
Message-ID: <4ED53E18.6090202@gmail.com>
Date: Wed, 30 Nov 2011 09:18:32 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
References: <4ED4FF87.80703@innovationslab.net>
In-Reply-To: <4ED4FF87.80703@innovationslab.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2011 20:18:39 -0000

I support this. 3627 has become misleading.

Regards
   Brian Carpenter

On 2011-11-30 04:51, Brian Haberman wrote:
> All,
>      This message starts a two week 6MAN Working Group on advancing:
> 
> Title     : RFC3627 to Historic status
> Author(s) : Wesley George
> Filename  : draft-ietf-6man-3627-historic-00.txt
> Pages     : 4
> Date      : 2011-11-28
> 
> as Informational.  Substantive comments and statements of support for
> advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent to the authors.  This last call will
> end on December 13, 2011.
> 
> Regards,
> Brian Haberman & Bob Hinden
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

From suresh.krishnan@ericsson.com  Tue Nov 29 14:39:35 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86B4C11E809C for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 14:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.41
X-Spam-Level: 
X-Spam-Status: No, score=-104.41 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_FUTURE_12_24=2.189, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tDtyibyMSLYd for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 14:39:35 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 12BCC11E8085 for <ipv6@ietf.org>; Tue, 29 Nov 2011 14:39:35 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pATMdUr6006388 for <ipv6@ietf.org>; Tue, 29 Nov 2011 16:39:34 -0600
Received: from [142.133.10.111] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.137.0; Tue, 29 Nov 2011 17:39:26 -0500
Message-ID: <4ED6B08A.6090004@ericsson.com>
Date: Wed, 30 Nov 2011 17:39:06 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Character set for Line ID
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2011 22:39:35 -0000

Hi all,
  Glen Turner and Ran Atkinson raised an issue about the Line ID being
opaque in draft-ietf-6man-lineid-02. When I asked the wg during the
Taipei meeting, the sense of the room was to specify the field as opaque
with an exact match policy. I would like to verify this on the mailing
list. If you have an issue with going forward with this, please propose
new text that you think would be appropriate. The only requirement for
this field is that it should be able to support text strings (e.g. a
circuit descriptor) and numbers (e.g. 32 bit ids).

Thanks
Suresh


From randy@psg.com  Tue Nov 29 20:08:44 2011
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6600321F84CB for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 20:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32h5HMKcqWny for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 20:08:44 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC1C21F84B7 for <ipv6@ietf.org>; Tue, 29 Nov 2011 20:08:44 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RVbTO-0007yI-0s; Wed, 30 Nov 2011 04:08:42 +0000
Date: Wed, 30 Nov 2011 13:09:02 +0900
Message-ID: <m2ty5m45gh.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
In-Reply-To: <4ED4FF87.80703@innovationslab.net>
References: <4ED4FF87.80703@innovationslab.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 04:08:44 -0000

> This message starts a two week 6MAN Working Group on advancing:
> Title     : RFC3627 to Historic status
> as Informational.

support

randy

From victor.kuarsingh@gmail.com  Tue Nov 29 21:35:44 2011
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6327321F84B5 for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 21:35:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dJp+26J5gfFo for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 21:35:42 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2868F21F84B2 for <ipv6@ietf.org>; Tue, 29 Nov 2011 21:35:42 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so106199vcb.31 for <ipv6@ietf.org>; Tue, 29 Nov 2011 21:35:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=d0fXNLMH2VNAUji6oA2oxi83zds+/TW77fuMkj/24BY=; b=v4TqoUcS4WzSk4TxKAM0ly4SzTuqd2h47upIF8LqO1cb07mV9KblP2dXuw9gLaDmmx l7wsSph0XimZriNmhoxt1zrkogFn6JnMbArSXzTPb/tMYM021jVu9ps1XFU50VfhLPGQ 7k1Axj7cf1Kmk3e4N2lztfQ9HmrqaCmhC/qPw=
Received: by 10.220.107.210 with SMTP id c18mr177716vcp.12.1322631341531; Tue, 29 Nov 2011 21:35:41 -0800 (PST)
Received: from [192.168.200.167] (CPE24ab81b96d12-CM001a666bafe6.cpe.net.cable.rogers.com. [99.230.124.175]) by mx.google.com with ESMTPS id q17sm1089602vdi.14.2011.11.29.21.35.39 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Nov 2011 21:35:40 -0800 (PST)
References: <4ED4FF87.80703@innovationslab.net> <m2ty5m45gh.wl%randy@psg.com>
In-Reply-To: <m2ty5m45gh.wl%randy@psg.com>
Mime-Version: 1.0 (iPad Mail 8J2)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Message-Id: <F7EE684C-BB31-406C-AEBF-D61C41FB5768@gmail.com>
X-Mailer: iPad Mail (8J2)
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
Date: Wed, 30 Nov 2011 00:35:50 -0500
To: Randy Bush <randy@psg.com>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 05:35:44 -0000

Support

Victor k

Sent from my iPad

On 2011-11-29, at 11:09 PM, Randy Bush <randy@psg.com> wrote:

>> This message starts a two week 6MAN Working Group on advancing:
>> Title     : RFC3627 to Historic status
>> as Informational.
> 
> support
> 
> randy
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From Tina.Tsou.Zouting@huawei.com  Tue Nov 29 21:37:35 2011
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69CC61F0C4A for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 21:37:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.374
X-Spam-Level: 
X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBNhJI65U6T1 for <ipv6@ietfa.amsl.com>; Tue, 29 Nov 2011 21:37:34 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 597341F0C44 for <ipv6@ietf.org>; Tue, 29 Nov 2011 21:37:34 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVG00C16KYA0H@szxga04-in.huawei.com> for ipv6@ietf.org; Wed, 30 Nov 2011 13:37:22 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVG00KD9KYAUG@szxga04-in.huawei.com> for ipv6@ietf.org; Wed, 30 Nov 2011 13:37:22 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFI60773; Wed, 30 Nov 2011 13:37:22 +0800
Received: from SZXEML417-HUB.china.huawei.com (10.82.67.156) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 30 Nov 2011 13:37:14 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.40]) by szxeml417-hub.china.huawei.com ([10.82.67.156]) with mapi id 14.01.0218.012; Wed, 30 Nov 2011 13:37:13 +0800
Date: Wed, 30 Nov 2011 05:37:13 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: RE: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
In-reply-to: <F7EE684C-BB31-406C-AEBF-D61C41FB5768@gmail.com>
X-Originating-IP: [10.212.246.234]
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>, Randy Bush <randy@psg.com>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C201A22@szxeml526-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
Thread-index: AQHMrq7O8RkfhFuxkUeGuunXztlbGZXESBsAgAAYQQCAAIZVkA==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <4ED4FF87.80703@innovationslab.net> <m2ty5m45gh.wl%randy@psg.com> <F7EE684C-BB31-406C-AEBF-D61C41FB5768@gmail.com>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 05:37:35 -0000

Support

Tina

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Victor Kuarsingh
Sent: Tuesday, November 29, 2011 9:36 PM
To: Randy Bush
Cc: 6man Chairs; Brian Haberman; ipv6@ietf.org
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt

Support

Victor k

Sent from my iPad

On 2011-11-29, at 11:09 PM, Randy Bush <randy@psg.com> wrote:

>> This message starts a two week 6MAN Working Group on advancing:
>> Title     : RFC3627 to Historic status
>> as Informational.
> 
> support
> 
> randy
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From tore.anderson@redpill-linpro.com  Wed Nov 30 05:09:44 2011
Return-Path: <tore.anderson@redpill-linpro.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D533A21F8B29 for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 05:09:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BqhDhIDqOPQm for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 05:09:44 -0800 (PST)
Received: from zimbra.redpill-linpro.com (zimbra.redpill-linpro.com [IPv6:2a02:c0:200:c000::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B0A821F8B27 for <ipv6@ietf.org>; Wed, 30 Nov 2011 05:09:44 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.redpill-linpro.com (Postfix) with ESMTP id B5F391030016 for <ipv6@ietf.org>; Wed, 30 Nov 2011 14:09:40 +0100 (CET)
X-Virus-Scanned: amavisd-new at claudius.linpro.no
Received: from zimbra.redpill-linpro.com ([127.0.0.1]) by localhost (zimbra.redpill-linpro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxMHhS4RgqrR; Wed, 30 Nov 2011 14:09:40 +0100 (CET)
Received: from envy.fud.no (ms-vpn.i.bitbit.net [87.238.42.7]) by zimbra.redpill-linpro.com (Postfix) with ESMTPSA id 35015103001B; Wed, 30 Nov 2011 14:09:40 +0100 (CET)
Message-ID: <4ED62B12.5020808@redpill-linpro.com>
Date: Wed, 30 Nov 2011 14:09:38 +0100
From: Tore Anderson <tore.anderson@redpill-linpro.com>
Organization: Redpill Linpro AS
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
References: <4ED4FF87.80703@innovationslab.net>
In-Reply-To: <4ED4FF87.80703@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 13:09:44 -0000

* Brian Haberman

>      This message starts a two week 6MAN Working Group on advancing:
> 
> Title     : RFC3627 to Historic status
> Author(s) : Wesley George
> Filename  : draft-ietf-6man-3627-historic-00.txt
> Pages     : 4
> Date      : 2011-11-28
> 
> as Informational.  Substantive comments and statements of support for
> advancing this document should be directed to the mailing list.

Support.

-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/

From aservin@lacnic.net  Wed Nov 30 06:11:13 2011
Return-Path: <aservin@lacnic.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85D9121F84F9 for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 06:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4cSZDsiNlCa for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 06:11:13 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id D38B121F84DD for <ipv6@ietf.org>; Wed, 30 Nov 2011 06:11:12 -0800 (PST)
Received: from [IPv6:2001:13c7:7001:5128:b02e:743:a940:6b25] (unknown [IPv6:2001:13c7:7001:5128:b02e:743:a940:6b25]) by mail.lacnic.net.uy (Postfix) with ESMTP id 91B8F308427; Wed, 30 Nov 2011 12:11:05 -0200 (UYST)
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <4ED4FF87.80703@innovationslab.net>
Date: Wed, 30 Nov 2011 12:11:05 -0200
Content-Transfer-Encoding: 7bit
Message-Id: <99DD1FFA-EC28-497A-8269-B73516FD3E1B@lacnic.net>
References: <4ED4FF87.80703@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1251.1)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 14:11:13 -0000

	Support.

-as

On 29 Nov 2011, at 13:51, Brian Haberman wrote:

> All,
>     This message starts a two week 6MAN Working Group on advancing:
> 
> Title     : RFC3627 to Historic status
> Author(s) : Wesley George
> Filename  : draft-ietf-6man-3627-historic-00.txt
> Pages     : 4
> Date      : 2011-11-28
> 
> as Informational.  Substantive comments and statements of support for
> advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent to the authors.  This last call will
> end on December 13, 2011.
> 
> Regards,
> Brian Haberman & Bob Hinden
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From maz@iij.ad.jp  Wed Nov 30 06:21:23 2011
Return-Path: <maz@iij.ad.jp>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4011521F84F5 for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 06:21:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxEa6kZtPMPo for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 06:21:22 -0800 (PST)
Received: from omgo.iij.ad.jp (mo30.iij.ad.jp [202.232.30.71]) by ietfa.amsl.com (Postfix) with ESMTP id 8C80721F84DF for <ipv6@ietf.org>; Wed, 30 Nov 2011 06:21:22 -0800 (PST)
DKIM-Signature: v=1;a=rsa-sha256;c=relaxed/simple;d=iij.ad.jp;h=Date: Message-Id:To:Subject:From:In-Reply-To:References:Mime-Version:Content-Type: Content-Transfer-Encoding; i=maz@iij.ad.jp; s=omgo1; t=1322662880; x=1323872480; bh=uoViyEUq35ZhYHjwJnMMoTOErmKmY5qRC8bPFbmZRYk=; b=fvOp2C5z3S53nGDESolvSyI6zoH N87GiwPNlBWpld4RDkjAlR4Fx0ljIUezhVgiX/f/V+JH3fKCXzex1IVCNAZpiYSbAQxjlt8PMH9J9 rkrvwr9cKBikzlyKG6h/Gd3BG1bJOpnFnbLfTiYLSCjhHIFOU/qxDWVAr0lcS71eFJ8=;
Received: by omgo.iij.ad.jp (mo30) id pAUELKmE007800; Wed, 30 Nov 2011 23:21:20 +0900
Date: Wed, 30 Nov 2011 23:21:16 +0900 (JST)
Message-Id: <20111130.232116.258053305.maz@iij.ad.jp>
To: ipv6@ietf.org
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
From: Matsuzaki Yoshinobu <maz@iij.ad.jp>
In-Reply-To: <4ED4FF87.80703@innovationslab.net>
References: <4ED4FF87.80703@innovationslab.net>
X-PGP-Fingerprint: 8E 9C EC 04 87 6B B5 0E  1B 6D 46 3B CB F7 72 CE
X-PGP-Fingerprint-DSA: CCF0 9311 060F DD75 2B63  9578 7FED 4A9C 4DBF 0817
Organization: IIJ Network Engineering and Operations
X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 14:21:23 -0000

Brian Haberman <brian@innovationslab.net> wrote
>      This message starts a two week 6MAN Working Group on advancing:
> 
> Title     : RFC3627 to Historic status
 :
> as Informational.  Substantive comments and statements of support for
> advancing this document should be directed to the mailing list.

Support.
-----
Matsuzaki Yoshinobu <maz@iij.ad.jp>
 - IIJ/AS2497  INOC-DBA: 2497*629

From shtsuchi@cisco.com  Wed Nov 30 08:21:45 2011
Return-Path: <shtsuchi@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E6021F8B1B for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 08:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkbUJ1xsslzm for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 08:21:44 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 9E97221F8B15 for <ipv6@ietf.org>; Wed, 30 Nov 2011 08:21:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shtsuchi@cisco.com; l=976; q=dns/txt; s=iport; t=1322670104; x=1323879704; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=stlbz7ORUheKZFWYd9jleUW+FptaZZO+66R1Sy7VumE=; b=ckmjdYhMqk1zGPVTsDes86OKM3q3WgaWFdJaJIr42ranvQCeqkZhvST6 GcKPD8dd5UFfztf6D/G9jCdEuA3QS9jVhTJb1aI6GvaORB6BSbvs4Yo3Y L8sF1vm/DDY8RniEm19WQQ8IcqQHEPyBj3OMBxMvx50F0SfI46YbJ4ovD Y=;
X-IronPort-AV: E=Sophos;i="4.69,597,1315180800";  d="scan'208";a="516965"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 30 Nov 2011 16:21:42 +0000
Received: from [10.70.231.156] (tky-vpn-client-231-156.cisco.com [10.70.231.156]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAUGLdlt032462; Wed, 30 Nov 2011 16:21:40 GMT
Message-ID: <4ED65813.1000805@cisco.com>
Date: Thu, 01 Dec 2011 01:21:39 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: brian@innovationslab.net
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
References: <4ED4FF87.80703@innovationslab.net>
In-Reply-To: <4ED4FF87.80703@innovationslab.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 16:21:45 -0000

Support!
Thank you for this document.
This is understandable/useful guide line to avoid conflict for users.

Regards,
-Shishio

(2011/11/30 0:51), Brian Haberman wrote:
> All,
> This message starts a two week 6MAN Working Group on advancing:
> 
> Title : RFC3627 to Historic status
> Author(s) : Wesley George
> Filename : draft-ietf-6man-3627-historic-00.txt
> Pages : 4
> Date : 2011-11-28
> 
> as Informational. Substantive comments and statements of support for
> advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent to the authors. This last call will
> end on December 13, 2011.
> 
> Regards,
> Brian Haberman & Bob Hinden
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 



From hisuntao@gmail.com  Wed Nov 30 10:30:27 2011
Return-Path: <hisuntao@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 461271F0C3B; Wed, 30 Nov 2011 10:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MnXpYvYaBHdR; Wed, 30 Nov 2011 10:30:26 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 32F7421F8B29; Wed, 30 Nov 2011 10:30:26 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so793536vcb.31 for <multiple recipients>; Wed, 30 Nov 2011 10:30:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2U/S+8zlFLdKDpU5faZ4B+uGMJEMyy1I+8HOKR1ovEw=; b=fe0/7bQ7bIM2XlgYsAOfpGrSEVm306+rMrTaZpOEahVTgmA2hJ7Jb2qsTY+CBAFXjk Hm0vkzACglm4unAV5V03p4+ODKbtlxFXhhVG9dk4I5s8cjGiCSPfphqcbdBdXp7oXw7i CK+Ys+mp6D0R62XqqKHwO2qQ0Ekv5jWI8HhQo=
MIME-Version: 1.0
Received: by 10.52.24.13 with SMTP id q13mr3095610vdf.104.1322677825740; Wed, 30 Nov 2011 10:30:25 -0800 (PST)
Received: by 10.220.194.133 with HTTP; Wed, 30 Nov 2011 10:30:25 -0800 (PST)
In-Reply-To: <DF1C8CC9-13D0-494B-AB45-5A17AECD1CB4@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com> <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com> <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com> <F4EFC3D8-AF56-4D90-AE08-767FC68CC468@employees.org> <DF1C8CC9-13D0-494B-AB45-5A17AECD1CB4@nominum.com>
Date: Thu, 1 Dec 2011 02:30:25 +0800
Message-ID: <CA+H2C9a+=JA25iBkk0XWNEuPuYkN_P1ONZUgDJXQyAVo9bV6Mw@mail.gmail.com>
Subject: Re: [mif] [dhcwg] Conflict between RA and DHCP in MIF case
From: Tao Sun <hisuntao@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=20cf3071cd00f49f6f04b2f7ed64
X-Mailman-Approved-At: Wed, 30 Nov 2011 11:21:42 -0800
Cc: Thomas Narten <narten@us.ibm.com>, "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 18:30:27 -0000

--20cf3071cd00f49f6f04b2f7ed64
Content-Type: text/plain; charset=ISO-8859-1

Sorry for jump to this discussion thread late.
The route policy shall be well considered by the operator/network. If we
discuss confliction, it is more like to be the network configuration that
may appear for MIF host rather than the mechanism of DHCPv6 or RA. Even we
only use RIO, the confliction may still apprear on different interfaces.

You may refer to the problem analysis discussed and agreed in 3GPP:
http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_85_XiAN/Docs/S2-112902.zip
Regards,

Tao
On Tue, Nov 22, 2011 at 11:31 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>   On Nov 22, 2011, at 8:18 AM, Ole Troan wrote:
>
> for clarification, that was not my proposal. my suggestion was to merge
> all information within one "provisioning domain".
>
> unsure if we will end up with provisioning domain = link, as detection of
> multiple provisioning domains on a single link may not be trivial in all
> corner cases.
>
>
> I agree with you that right now detecting provisioning domains is not
> trivial; indeed, in some cases it's impossible.   However, if you think
> provisioning domain == link, then that's a problem that needs fixing.
> Indeed, that's *the* problem that needs fixing.   I think we have to fix
> it; if we punt, we're going to pay for it later.
>
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>
>

--20cf3071cd00f49f6f04b2f7ed64
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Sorry for jump to this=A0discussion thread=A0late. </div>
<div>The route policy shall be well considered by the operator/network. If =
we discuss confliction, it is more like to be the network configuration tha=
t may appear for MIF host rather than the mechanism of DHCPv6 or RA. Even=
=A0we only use RIO, the confliction may still apprear on different interfac=
es.</div>

<div><br>You may=A0refer to the=A0problem analysis discussed and agreed in =
3GPP:<br><a href=3D"http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_85_XiAN/D=
ocs/S2-112902.zip">http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_85_XiAN/Do=
cs/S2-112902.zip</a><br>
</div>
<div>Regards,</div>
<div>=A0</div>
<div>Tao<br></div>
<div class=3D"gmail_quote">On Tue, Nov 22, 2011 at 11:31 PM, Ted Lemon <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com">Ted.Lemon@nominu=
m.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div style=3D"WORD-WRAP: break-word">
<div class=3D"im">
<div>
<div>On Nov 22, 2011, at 8:18 AM, Ole Troan wrote:</div>
<blockquote type=3D"cite"><span style=3D"TEXT-TRANSFORM: none; TEXT-INDENT:=
 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: norma=
l; LETTER-SPACING: normal; WORD-SPACING: 0px">for clarification, that was n=
ot my proposal. my suggestion was to merge all information within one &quot=
;provisioning domain&quot;.</span></blockquote>

<blockquote type=3D"cite"><span style=3D"TEXT-TRANSFORM: none; TEXT-INDENT:=
 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: norma=
l; LETTER-SPACING: normal; WORD-SPACING: 0px">unsure if we will end up with=
 provisioning domain =3D link, as detection of multiple provisioning domain=
s on a single link may not be trivial in all corner cases.</span></blockquo=
te>
</div><br></div>
<div>I agree with you that right now detecting provisioning domains is not =
trivial; indeed, in some cases it&#39;s impossible. =A0 However, if you thi=
nk provisioning domain =3D=3D link, then that&#39;s a problem that needs fi=
xing. =A0 Indeed, that&#39;s *the* problem that needs fixing. =A0 I think w=
e have to fix it; if we punt, we&#39;re going to pay for it later.</div>

<div><br></div></div><br>_______________________________________________<br=
>mif mailing list<br><a href=3D"mailto:mif@ietf.org">mif@ietf.org</a><br><a=
 href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D"_blank">https=
://www.ietf.org/mailman/listinfo/mif</a><br>
<br></blockquote></div><br>

--20cf3071cd00f49f6f04b2f7ed64--

From james.boswell@twcable.com  Wed Nov 30 13:29:41 2011
Return-Path: <james.boswell@twcable.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2643511E80C0 for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 13:29:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6hYQVYqLRwL for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 13:29:40 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 8EDE511E80AF for <ipv6@ietf.org>; Wed, 30 Nov 2011 13:29:40 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,599,1315195200"; d="scan'208";a="288550389"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 30 Nov 2011 16:23:51 -0500
Received: from PRVPEXVS08.corp.twcable.com ([10.136.163.37]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Wed, 30 Nov 2011 16:29:39 -0500
From: "Boswell, James" <james.boswell@twcable.com>
To: Shishio Tsuchiya <shtsuchi@cisco.com>, "brian@innovationslab.net" <brian@innovationslab.net>
Date: Wed, 30 Nov 2011 16:29:39 -0500
Subject: RE: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
Thread-Topic: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
Thread-Index: AcyvfC7XQcPCPr3FQOmT4QkyIrJMpAAKtrtA
Message-ID: <7AB90E1B152E184A92C1FA2DD63E0DC303C1CD3F74@PRVPEXVS08.corp.twcable.com>
References: <4ED4FF87.80703@innovationslab.net> <4ED65813.1000805@cisco.com>
In-Reply-To: <4ED65813.1000805@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 21:29:41 -0000

Support,  and agreed very useful to avoid conflicts for users.


-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Shi=
shio Tsuchiya
Sent: Wednesday, November 30, 2011 11:22 AM
To: brian@innovationslab.net
Cc: 6man-chairs@tools.ietf.org; ipv6@ietf.org
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt

Support!
Thank you for this document.
This is understandable/useful guide line to avoid conflict for users.

Regards,
-Shishio

(2011/11/30 0:51), Brian Haberman wrote:
> All,
> This message starts a two week 6MAN Working Group on advancing:
>
> Title : RFC3627 to Historic status
> Author(s) : Wesley George
> Filename : draft-ietf-6man-3627-historic-00.txt
> Pages : 4
> Date : 2011-11-28
>
> as Informational. Substantive comments and statements of support for
> advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent to the authors. This last call will
> end on December 13, 2011.
>
> Regards,
> Brian Haberman & Bob Hinden
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From narten@us.ibm.com  Wed Nov 30 17:33:31 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0F621F8BFE for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 17:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VqjPlsbQayR9 for <ipv6@ietfa.amsl.com>; Wed, 30 Nov 2011 17:33:30 -0800 (PST)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id 62E5121F8BF9 for <ipv6@ietf.org>; Wed, 30 Nov 2011 17:33:29 -0800 (PST)
Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ipv6@ietf.org> from <narten@us.ibm.com>; Wed, 30 Nov 2011 20:33:28 -0500
Received: from d01relay06.pok.ibm.com (9.56.227.116) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 30 Nov 2011 20:33:26 -0500
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pB11XQc23588346 for <ipv6@ietf.org>; Wed, 30 Nov 2011 20:33:26 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pB11XPdM021052 for <ipv6@ietf.org>; Wed, 30 Nov 2011 20:33:26 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-76-145-54.mts.ibm.com [9.76.145.54]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id pB11XOJY021002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Nov 2011 20:33:25 -0500
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id pB11XNsg032073; Wed, 30 Nov 2011 20:33:24 -0500
Message-Id: <201112010133.pB11XNsg032073@cichlid.raleigh.ibm.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Character set for Line ID
In-reply-to: <4ED6B08A.6090004@ericsson.com>
References: <4ED6B08A.6090004@ericsson.com>
Comments: In-reply-to Suresh Krishnan <suresh.krishnan@ericsson.com> message dated "Wed, 30 Nov 2011 17:39:06 -0500."
Date: Wed, 30 Nov 2011 20:33:23 -0500
From: Thomas Narten <narten@us.ibm.com>
x-cbid: 11120101-9360-0000-0000-0000012204D7
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 01:33:31 -0000

Well, if you want the line ID field to hold a string, to do the right
thing, one probably needs to:

1) make the field be a UTF-8 string

2) have the string contain normalized unicode, so that the "string"
entered on one device correctly matches the "string" entered on the
server (which won't always happen if unnormalized unicode strings are
allowed).

I.e., the kind of stuff that the precis WG does. :)

Thomas

