
From bob.hinden@gmail.com  Thu Dec  1 06:41:33 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 7622821F9220 for <ipv6@ietfa.amsl.com>; Thu,  1 Dec 2011 06:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.681
X-Spam-Level: 
X-Spam-Status: No, score=-102.681 tagged_above=-999 required=5 tests=[AWL=-0.478, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 QdvTqXpJSiv7 for <ipv6@ietfa.amsl.com>; Thu,  1 Dec 2011 06:41:32 -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 DFD1D21F921A for <ipv6@ietf.org>; Thu,  1 Dec 2011 06:41:31 -0800 (PST)
Received: by yenl9 with SMTP id l9so1006997yen.31 for <ipv6@ietf.org>; Thu, 01 Dec 2011 06:41:31 -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=yzlwQRdaV0tPspwLUjqeC/AuCfaH7xCYcWJkbWPOfVw=; b=i2O3KFDo/0rmm+K2NxItFKaUrOLPRvUwBOGqlo5aDNik6kjLeseVISbH8HpJl9KMCh isw34PSXNyHaGWjuQdIvT6eyGBV/TKtAtaVwnk37bpml7s0z24QsIip+yw0A3XrNcp4c dZwvRyw//nbktLaT8NvWqSuIcFPT+nVbX4tz8=
Received: by 10.182.115.106 with SMTP id jn10mr1433469obb.54.1322750491254; Thu, 01 Dec 2011 06:41:31 -0800 (PST)
Received: from [10.0.0.27] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id q10sm4610051obv.1.2011.12.01.06.41.28 (version=SSLv3 cipher=OTHER); Thu, 01 Dec 2011 06:41:29 -0800 (PST)
Subject: Re: Working Group last call for adding RFC6437 Flow Label support to Node Requirements bis document
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: <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.com>
Date: Thu, 1 Dec 2011 06:41:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <202D0F00-988F-4BC2-AD04-736E039C316E@gmail.com>
References: <2129067463716F46AC77A22602E5CB5C01F90D3A@008-AM1MPN1-015.mgdnok.nokia.com> <75BF48A7-D1A1-4F77-8386-1B359EB0EB96@gmail.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, 01 Dec 2011 14:41:33 -0000

This last call was completed on 17 November 2011.  There was no =
objection raised during the last call.  The topic was also discussed at =
the Taipei 6man session.  The minutes show:

 Node Requirements update based on new Flow Label RFC, Chairs, 10 min.
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

 Should this document be updated to reflect the recently published Flow
 Label RFCs?  So a new WG last call has been issued to confirm comfort
 with the changes.  Jari Arkko said not to delay publishing if we cannot
 easily resolve this issue.  Several people spoke in support of getting
 this text into the document now.  Brian Haberman (remote, co-chair)
 strongly urged support for making this change.  Bob Hinden polled the
 room, and there was strong support for the change, and no one indicated
 opposition.

Consequently, the authors should proceed with the change to the =
document.

Bob Hinden / Brian Haberman
6man Chairs



On Nov 10, 2011, at 9:00 AM, 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


From jari.arkko@piuha.net  Thu Dec  1 07:46:15 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 569AA21F9115 for <ipv6@ietfa.amsl.com>; Thu,  1 Dec 2011 07:46:15 -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=[AWL=0.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 uFIq2pkCVisC for <ipv6@ietfa.amsl.com>; Thu,  1 Dec 2011 07:46:15 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 7204321F9106 for <ipv6@ietf.org>; Thu,  1 Dec 2011 07:46:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C17622CC43; Thu,  1 Dec 2011 17:46:09 +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 T4dKUKazud7C; Thu,  1 Dec 2011 17:46:09 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DB1DC2CC31; Thu,  1 Dec 2011 17:46:08 +0200 (EET)
Message-ID: <4ED7A140.8060401@piuha.net>
Date: Thu, 01 Dec 2011 17:46:08 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111110 Thunderbird/8.0
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> <202D0F00-988F-4BC2-AD04-736E039C316E@gmail.com>
In-Reply-To: <202D0F00-988F-4BC2-AD04-736E039C316E@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>, 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, 01 Dec 2011 15:46:15 -0000

Good. Please make sure the RFC Editor gets the final AUTH48 change in e-mail so that I can say "approve"...

Jari


From warren@kumari.net  Thu Dec  1 15:01:54 2011
Return-Path: <warren@kumari.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 2FC001F0CC9 for <ipv6@ietfa.amsl.com>; Thu,  1 Dec 2011 15:01:54 -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 AdUE6XRGDrrU for <ipv6@ietfa.amsl.com>; Thu,  1 Dec 2011 15:01:53 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id A82511F0CC7 for <ipv6@ietf.org>; Thu,  1 Dec 2011 15:01:53 -0800 (PST)
Received: from dhcp-172-19-119-228.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 2D68E1B407B8; Thu,  1 Dec 2011 18:01:51 -0500 (EST)
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4ED4FF87.80703@innovationslab.net>
Date: Thu, 1 Dec 2011 18:01:49 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <2F842780-64BA-4602-9B88-D33872FC911E@kumari.net>
References: <4ED4FF87.80703@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1084)
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: Thu, 01 Dec 2011 23:01:54 -0000

Support.

W
On Nov 29, 2011, at 10:51 AM, 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 gdt@gdt.id.au  Thu Dec  1 22:39:33 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 70F2021F8DFD for <ipv6@ietfa.amsl.com>; Thu,  1 Dec 2011 22:39:33 -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 9Cxa5fXt-Yjq for <ipv6@ietfa.amsl.com>; Thu,  1 Dec 2011 22:39:32 -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 86B1121F8DE0 for <ipv6@ietf.org>; Thu,  1 Dec 2011 22:39:31 -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 pB26dMTb012898 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Dec 2011 17:09:23 +1030
Subject: Re: Character set for Line ID
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: <4ED6B08A.6090004@ericsson.com>
Date: Fri, 2 Dec 2011 17:09:22 +1030
Content-Transfer-Encoding: quoted-printable
Message-Id: <906CC1A7-20AF-4414-93F4-7F234B78F086@gdt.id.au>
References: <4ED6B08A.6090004@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1084)
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: Fri, 02 Dec 2011 06:39:33 -0000

On 01/12/2011, at 9:09 AM, Suresh Krishnan wrote:
> 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).

Is there not also a requirement that the string be able to be expressed =
in a typical router's configuration?

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


From bob.hinden@gmail.com  Fri Dec  2 08:47:42 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 262F521F8C4E for <ipv6@ietfa.amsl.com>; Fri,  2 Dec 2011 08:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.375
X-Spam-Level: 
X-Spam-Status: No, score=-103.375 tagged_above=-999 required=5 tests=[AWL=0.224, 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 cZykMxy6hS38 for <ipv6@ietfa.amsl.com>; Fri,  2 Dec 2011 08:47:41 -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 9946621F8BD3 for <ipv6@ietf.org>; Fri,  2 Dec 2011 08:47:41 -0800 (PST)
Received: by ggnp4 with SMTP id p4so3771349ggn.31 for <ipv6@ietf.org>; Fri, 02 Dec 2011 08:47:41 -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=lvamRnHOwcXT0/yiW+63uk1SeCV9Stf4Sy9RlDI5x8k=; b=mz5gm9jHrl5BLk9W98l/v/pWFaBiiSsU/6HNOQSnZo55GTW/PnBku62za+IUGWSs4z GJ3XdDCz9dTq2EmygMmFK10VdFOL452JhianMr9KhsjsyqTtJUloW7GSmFiKvtEYHstO SacbbPmlHxfUf4iofdKXbaAb1VfuqJBYQGuVg=
Received: by 10.182.188.34 with SMTP id fx2mr2501806obc.31.1322844461117; Fri, 02 Dec 2011 08:47:41 -0800 (PST)
Received: from [10.0.0.27] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id k8sm462105obi.3.2011.12.02.08.47.39 (version=SSLv3 cipher=OTHER); Fri, 02 Dec 2011 08:47:40 -0800 (PST)
Subject: Re: Character set for Line ID
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: <201112010133.pB11XNsg032073@cichlid.raleigh.ibm.com>
Date: Fri, 2 Dec 2011 08:47:38 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3576727F-88A0-4147-9221-17B0D512D73E@gmail.com>
References: <4ED6B08A.6090004@ericsson.com> <201112010133.pB11XNsg032073@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Suresh Krishnan <suresh.krishnan@ericsson.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, 02 Dec 2011 16:47:42 -0000

Thomas,

No hats on.

I assume that if the Line ID is going to be opaque we don't need to =
define how to encode strings in it.  Suresh's email wasn't clear on =
that, if I understood it correctly.

I still would like it to be an opaque field as that keeps it aligned =
with the DHCP option. =20

Bob

 =20
On Nov 30, 2011, at 5:33 PM, Thomas Narten wrote:

> Well, if you want the line ID field to hold a string, to do the right
> thing, one probably needs to:
>=20
> 1) make the field be a UTF-8 string
>=20
> 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).
>=20
> I.e., the kind of stuff that the precis WG does. :)
>=20
> Thomas
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From narten@us.ibm.com  Fri Dec  2 08:53:10 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 9729A11E8080 for <ipv6@ietfa.amsl.com>; Fri,  2 Dec 2011 08:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.166
X-Spam-Level: 
X-Spam-Status: No, score=-106.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 pJIjd2Q8mKxS for <ipv6@ietfa.amsl.com>; Fri,  2 Dec 2011 08:53:09 -0800 (PST)
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) by ietfa.amsl.com (Postfix) with ESMTP id 87FD911E807F for <ipv6@ietf.org>; Fri,  2 Dec 2011 08:53:09 -0800 (PST)
Received: from /spool/local by e2.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>; Fri, 2 Dec 2011 11:53:08 -0500
Received: from d01relay05.pok.ibm.com (9.56.227.237) by e2.ny.us.ibm.com (192.168.1.102) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 2 Dec 2011 11:53:07 -0500
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pB2Gr6R4208840 for <ipv6@ietf.org>; Fri, 2 Dec 2011 11:53:06 -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 pB2Gr5jt014546 for <ipv6@ietf.org>; Fri, 2 Dec 2011 11:53:05 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-65-224-83.mts.ibm.com [9.65.224.83]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id pB2Gr4Q9014433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2011 11:53:05 -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 pB2Gr3CS013762; Fri, 2 Dec 2011 11:53:03 -0500
Message-Id: <201112021653.pB2Gr3CS013762@cichlid.raleigh.ibm.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Character set for Line ID
In-reply-to: <3576727F-88A0-4147-9221-17B0D512D73E@gmail.com>
References: <4ED6B08A.6090004@ericsson.com> <201112010133.pB11XNsg032073@cichlid.raleigh.ibm.com> <3576727F-88A0-4147-9221-17B0D512D73E@gmail.com>
Comments: In-reply-to Bob Hinden <bob.hinden@gmail.com> message dated "Fri, 02 Dec 2011 08:47:38 -0800."
Date: Fri, 02 Dec 2011 11:53:03 -0500
From: Thomas Narten <narten@us.ibm.com>
x-cbid: 11120216-5112-0000-0000-000002AC6FEE
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.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, 02 Dec 2011 16:53:10 -0000

> I assume that if the Line ID is going to be opaque we don't need to
> define how to encode strings in it.  Suresh's email wasn't clear on
> that, if I understood it correctly.

The problem with this is if the field actually holds a string, you
have to define a canonical representation for the  string. It's just
not sufficient to say it is a "string" or a "UTF-8 string", etc. You
won't get interoperability with that.

This is something *ALL* IETF protocols are starting to grapple with,
if they allow protocol fields to hold strings, and one has to compare
those strings for equality.

> I still would like it to be an opaque field as that keeps it aligned
> with the DHCP option.

The DHCP format was specified many years ago... the world is more
complex today...

If we say specifically the opague field is not a "string", this issue
probably goes away. But I think we need to ask the users of this
option whether that is OK.

Thomas


From bob.hinden@gmail.com  Fri Dec  2 11:50:52 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 093DD11E8103 for <ipv6@ietfa.amsl.com>; Fri,  2 Dec 2011 11:50:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.774
X-Spam-Level: 
X-Spam-Status: No, score=-103.774 tagged_above=-999 required=5 tests=[AWL=-0.175, 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 tHTdYhhDK5Vz for <ipv6@ietfa.amsl.com>; Fri,  2 Dec 2011 11:50:51 -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 4C72F11E80FE for <ipv6@ietf.org>; Fri,  2 Dec 2011 11:50:51 -0800 (PST)
Received: by ggnp4 with SMTP id p4so3975509ggn.31 for <ipv6@ietf.org>; Fri, 02 Dec 2011 11:50:49 -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=IduiagI8LvRvOobyxs5EYyLnADb7Ct35HTBKUoo17bo=; b=kDOhGT6R73DQHcjwerouJruko6xSz14oNIAZWLU79Cvndh9WlP8L6h4RyMoWPgf4qZ sla34vBOu59S8fh1K9NyZmP9MKYQzYySckz85Qcv74r0cZdgBJGxdNLj6E/P6CZYD8Lh eCsTwlhGfurEOx9Y4q/L0u/3eKL+9LYEm7aUA=
Received: by 10.182.147.4 with SMTP id tg4mr2638687obb.60.1322855449764; Fri, 02 Dec 2011 11:50:49 -0800 (PST)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id e4sm1181433obd.11.2011.12.02.11.50.48 (version=SSLv3 cipher=OTHER); Fri, 02 Dec 2011 11:50:49 -0800 (PST)
Subject: Re: Character set for Line ID
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: <201112021653.pB2Gr3CS013762@cichlid.raleigh.ibm.com>
Date: Fri, 2 Dec 2011 11:50:47 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1C4A25F-400B-46D9-942B-54E80BA000CB@gmail.com>
References: <4ED6B08A.6090004@ericsson.com> <201112010133.pB11XNsg032073@cichlid.raleigh.ibm.com> <3576727F-88A0-4147-9221-17B0D512D73E@gmail.com> <201112021653.pB2Gr3CS013762@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Suresh Krishnan <suresh.krishnan@ericsson.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, 02 Dec 2011 19:50:52 -0000

Thomas,

On Dec 2, 2011, at 8:53 AM, Thomas Narten wrote:

>> I assume that if the Line ID is going to be opaque we don't need to
>> define how to encode strings in it.  Suresh's email wasn't clear on
>> that, if I understood it correctly.
>=20
> The problem with this is if the field actually holds a string, you
> have to define a canonical representation for the  string. It's just
> not sufficient to say it is a "string" or a "UTF-8 string", etc. You
> won't get interoperability with that.
>=20
> This is something *ALL* IETF protocols are starting to grapple with,
> if they allow protocol fields to hold strings, and one has to compare
> those strings for equality.

Still seems to me that if it's opaque, then it's opaque and we don't =
need to specify rules for it's contents.  If it's not opaque, then we =
should specify rules.

>=20
>> I still would like it to be an opaque field as that keeps it aligned
>> with the DHCP option.
>=20
> The DHCP format was specified many years ago... the world is more
> complex today...

Is anyone asking to change that?  If it's working, then it's not.....

> If we say specifically the opague field is not a "string", this issue
> probably goes away. But I think we need to ask the users of this
> option whether that is OK.

Hopefully they will respond to this thread.

Thanks,
Bob


> Thomas
>=20


From suresh.krishnan@ericsson.com  Sat Dec  3 23:49:49 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 2EB291F0C45 for <ipv6@ietfa.amsl.com>; Sat,  3 Dec 2011 23:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.668
X-Spam-Level: 
X-Spam-Status: No, score=-105.668 tagged_above=-999 required=5 tests=[AWL=0.931, 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 XWgZ+t4OTRfi for <ipv6@ietfa.amsl.com>; Sat,  3 Dec 2011 23:49:48 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id A974B1F0C43 for <ipv6@ietf.org>; Sat,  3 Dec 2011 23:49:48 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pB47ni6q019847; Sun, 4 Dec 2011 01:49:45 -0600
Received: from [164.48.125.32] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.137.0; Sun, 4 Dec 2011 02:49:38 -0500
Message-ID: <4EDB259B.7010503@ericsson.com>
Date: Sun, 4 Dec 2011 02:47:39 -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: Thomas Narten <narten@us.ibm.com>
Subject: Re: Character set for Line ID
References: <4ED6B08A.6090004@ericsson.com> <201112010133.pB11XNsg032073@cichlid.raleigh.ibm.com> <3576727F-88A0-4147-9221-17B0D512D73E@gmail.com> <201112021653.pB2Gr3CS013762@cichlid.raleigh.ibm.com>
In-Reply-To: <201112021653.pB2Gr3CS013762@cichlid.raleigh.ibm.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: IETF IPv6 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: Sun, 04 Dec 2011 07:49:49 -0000

Hi Thomas,

On 12/02/2011 11:53 AM, Thomas Narten wrote:
>> I assume that if the Line ID is going to be opaque we don't need to
>> define how to encode strings in it.  Suresh's email wasn't clear on
>> that, if I understood it correctly.
> 
> The problem with this is if the field actually holds a string, you
> have to define a canonical representation for the  string. It's just
> not sufficient to say it is a "string" or a "UTF-8 string", etc. You
> won't get interoperability with that.

I will try to describe the provisioning procedure a bit. When a
subscriber line is provisioned, the operator will perform the following
steps

a) Configure the Access Node to insert a sequence of bytes into the
line-id field.
b) Configure the AAA server to hand out a given prefix when this exact
sequence of bytes is received in an Access Request.

The edge router will pass on, without inspecting, the line-id received
from the RS and send it off to the AAA server to get the prefix to send
out in the RA.

> 
> This is something *ALL* IETF protocols are starting to grapple with,
> if they allow protocol fields to hold strings, and one has to compare
> those strings for equality.

Right. I was proposing considering this field as an "Absolute
Identifier" as defined in the IAB Identifier comparison draft and the
match policy would be exact match. i.e. The match would fail if any of
the bytes fail to match.

> 
>> I still would like it to be an opaque field as that keeps it aligned
>> with the DHCP option.
> 
> The DHCP format was specified many years ago... the world is more
> complex today...

But the AAA systems that are used, will use the same kind of line-id
(per operator) for both DHCP(v4/v6) and the RS.

Thanks
Suresh




From suresh.krishnan@ericsson.com  Sat Dec  3 23:53:08 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 6161211E808A for <ipv6@ietfa.amsl.com>; Sat,  3 Dec 2011 23:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.726
X-Spam-Level: 
X-Spam-Status: No, score=-105.726 tagged_above=-999 required=5 tests=[AWL=0.873, 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 3M2v60gni2u6 for <ipv6@ietfa.amsl.com>; Sat,  3 Dec 2011 23:53:07 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id CC34B11E8081 for <ipv6@ietf.org>; Sat,  3 Dec 2011 23:53:07 -0800 (PST)
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 pB47r1SK019861; Sun, 4 Dec 2011 01:53:02 -0600
Received: from [164.48.125.32] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.137.0; Sun, 4 Dec 2011 02:52:55 -0500
Message-ID: <4EDB2661.4000505@ericsson.com>
Date: Sun, 4 Dec 2011 02:50:57 -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: Glen Turner <gdt@gdt.id.au>
Subject: Re: Character set for Line ID
References: <4ED6B08A.6090004@ericsson.com> <906CC1A7-20AF-4414-93F4-7F234B78F086@gdt.id.au>
In-Reply-To: <906CC1A7-20AF-4414-93F4-7F234B78F086@gdt.id.au>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Sun, 04 Dec 2011 07:53:08 -0000

Hi Glen,

On 12/02/2011 01:39 AM, Glen Turner wrote:
> 
> On 01/12/2011, at 9:09 AM, Suresh Krishnan wrote:
>> 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).
> 
> Is there not also a requirement that the string be able to be expressed in a typical router's configuration?

In the deployments that I know of, the line-id is not configured on the
router at all. The router just passes through the line-id it received
from the Access Node onto the AAA server.

Thanks
Suresh



From marka@isc.org  Sun Dec  4 21:25:03 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 785DD1F0C3F; Sun,  4 Dec 2011 21:25:03 -0800 (PST)
X-Quarantine-ID: <FCdmdKFfjkdO>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
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 FCdmdKFfjkdO; Sun,  4 Dec 2011 21:25:03 -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 CD5071F0C36; Sun,  4 Dec 2011 21:24:59 -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 50CD15F9906; Mon,  5 Dec 2011 05:24:41 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:fce5:1941:667f:5022]) (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 B6787216C6B; Mon,  5 Dec 2011 05:24:39 +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 C4DA81913544; Mon,  5 Dec 2011 16:24:36 +1100 (EST)
To: "Stephan Lagerholm" <stephan.lagerholm@secure64.com>
From: Mark Andrews <marka@isc.org>
References: <20111204074710.64552.qmail@joyce.lan> <4EDBEA1D.4040806@ogud.com><AA039D53-2F83-40D2-9251-C88D3362F144@vpnc.org> <20111204230152.BF424190D6B3@drugs.dv.isc.org> <DD056A31A84CFC4AB501BD56D1E14BBBB5C0E2@exchange.secure64.com>
Subject: Re: draft-andrews-dnsext-ipv6-fragmentation
In-reply-to: Your message of "Sun, 04 Dec 2011 21:49:30 PDT." <DD056A31A84CFC4AB501BD56D1E14BBBB5C0E2@exchange.secure64.com>
Date: Mon, 05 Dec 2011 16:24:36 +1100
Message-Id: <20111205052436.C4DA81913544@drugs.dv.isc.org>
X-Mailman-Approved-At: Mon, 05 Dec 2011 02:51:39 -0800
Cc: 6man@ietf.org, dnsext@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, 05 Dec 2011 05:25:03 -0000

In message <DD056A31A84CFC4AB501BD56D1E14BBBB5C0E2@exchange.secure64.com>, "Ste
phan Lagerholm" writes:
> Hi Mark,
> 
> You can get blocked ICMP 'packet too big' even if you have the MTU set
> to 1280.=20
> 
> RFC 2460:
> In response to an IPv6 packet that is sent to an IPv4 destination (i.e.,
> a packet that undergoes translation from IPv6=20
> to IPv4), the originating IPv6 node may receive an ICMP Packet Too Big
> message reporting a Next-Hop MTU less than 1280.=20
> In that case, the IPv6 node is not required to reduce the size of
> subsequent packets to less than 1280, but must include=20
> a Fragment header in those packets so that the IPv6-to-IPv4 translating
> router can obtain a suitable Identification=20
> value to use in resulting IPv4 fragments. Note that this means the
> payload may have to be reduced to 1232 octets (1280=20
> minus 40 for the IPv6 header and 8 for the Fragment header), and smaller
> still if additional extension headers are used.

Which just mean that 6man needs to extend the IPv6 socket API so
that the insertion of a fragment header can be signaled.  Or
IPV6_USE_MIN_MTU=1 needs to imply that a fragment header needs to
be added to packets that are not fragmented.  Currently IPV6_USE_MIN_MTU
doesn't quite fully disable PMTUD.

RFC 3542 allows you to turn off adding the adding of Fragment headr
by there is no mechanism to force the adding of a Fragment header.

> /Stephan
> 
> > -----Original Message-----
> > From: dnsext-bounces@ietf.org [mailto:dnsext-bounces@ietf.org] On
> > Behalf Of Mark Andrews
> > Sent: Sunday, December 04, 2011 6:02 PM
> > To: Paul Hoffman
> > Cc: dnsext@ietf.org; Olafur Gudmundsson
> > Subject: Re: [dnsext] draft-levine-dnsextlang-02
> >=20
> > On a similar matter I was in the process of submitting the following.
> > I just needed to address internal comments.  I also think my EDNS
> > expire option still needs to be addressed though I suspect I'll do
> that
> > as a individual submission.
> >=20
> > Mark
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From rja.lists@gmail.com  Tue Dec  6 11:35:43 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 C6FEF21F8BB2 for <ipv6@ietfa.amsl.com>; Tue,  6 Dec 2011 11: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 iAy5lmhZ-nu9 for <ipv6@ietfa.amsl.com>; Tue,  6 Dec 2011 11:35:43 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 35FAA21F8B7C for <ipv6@ietf.org>; Tue,  6 Dec 2011 11:35:43 -0800 (PST)
Received: by qadb12 with SMTP id b12so4546684qad.10 for <ipv6@ietf.org>; Tue, 06 Dec 2011 11:35:42 -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 :to:mime-version:x-mailer; bh=PWStzQ5tXY1MiPOHVskWVngnIqoabQ6zaLDL1+YunYE=; b=UHugPEy2KIg46z8XY5hzbIT5w6vkErKZSbcwuvQMsu+hTm2yTG/kaWsfqx0qdBGl8a V3+VdPQdJBfXdcbX5KNXvO1EvTTitZWfV2WRnL+MQZj1bk/W6YV7ZgWqMoWp+z5AL3J5 ubcFhaznoOgRPHDhJQvYdfcMve69+qHgSvRNE=
Received: by 10.224.217.131 with SMTP id hm3mr13493109qab.81.1323200142708; Tue, 06 Dec 2011 11:35:42 -0800 (PST)
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 z1sm33972058qao.1.2011.12.06.11.35.40 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 06 Dec 2011 11:35:41 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Character set for Line ID
Date: Tue, 6 Dec 2011 14:35:39 -0500
Message-Id: <EAC60EFC-0411-48AE-92D1-7621DCA60CA1@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: Tue, 06 Dec 2011 19:35:43 -0000

Bob,

  My read of the relevant RFCs is that the 
DHCP Line-ID option specifies the use of the "NVT"
character set.  

The character set specification is implicit, applying 
to all DHCP options, rather than having been written
explicitly for this single DHCP option.  One has 
to really study the full set of DHCP RFCs 
(i.e. the full daisy-chain of RFC citations from
the References backwards) to see this, but it is
consistent with every DHCP implementation that 
I can identify.

  I can't find ANY DHCP implementations that permit 
"arbitrary bytes" to be entered into the Line-ID option 
field. I can't think of any DHCP implementation that
permits, for example, LINEFEED or CARRIAGE-RETURN
to be entered into ANY DHCP-related field.  Many
have problems with inputs other than printable
characters from ISO-8859, for example.  

  The word "opaque" in the DHCP Line-ID option
specification refers to the packet processing
for the DHCP packet, not to the contents of
the field or how that field is entered 
(presumably via a CLI or perhaps web page someplace) 
or how that field is to be displayed to humans.

The DHCP Line-ID option does not use the word 
"opaque" to indicate absence of a character set.
That is a mis-reading of the DHCP RFC set.

As a former ISP person, I can assure that the
Line-ID values absolutely DO get displayed
to operators and others in network operations.
It is important to be able to configure the
Line-ID values and to view them in order to
troubleshoot real networks (e.g. a DSL deployment).

So the assumption that the DHCP Line-ID option
does not have any specified character set is
not actually correct.

Now, if one's goal is *strict* compatibility with
the DHCP Line-ID option, then the NVT character
set (originally specified in very early RFCs)
ought to be specified.  

I think, however, it would be reasonable to choose 
some alternative such as US-ASCII, ISO-8859-1, 
or (maybe -- possibly more risky given existing
DHCP implementations -- but more globally suitable)
UTF-8.

Yours,

Ran


From rja.lists@gmail.com  Tue Dec  6 11:43:02 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 50D3821F8C18 for <ipv6@ietfa.amsl.com>; Tue,  6 Dec 2011 11:43:02 -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 60AD67UtSrC1 for <ipv6@ietfa.amsl.com>; Tue,  6 Dec 2011 11:43:01 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 624F821F8C14 for <ipv6@ietf.org>; Tue,  6 Dec 2011 11:43:01 -0800 (PST)
Received: by qcsf15 with SMTP id f15so3086769qcs.31 for <ipv6@ietf.org>; Tue, 06 Dec 2011 11:43:01 -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 :to:mime-version:x-mailer; bh=PusEoJqhsK7J47L+oQcopWj9e1Xf1UK6KfzbjM3fwtQ=; b=GimiUKT9NzyRentq0kveXX+la2gnlK+FLhQbti6De4iyfiOPmTtGwzE2qebahvhpsO JYANEAzIWky4u2Qq/avOtpw8/jfleqHdM35nyDVCg/DOYe3iK7c0yZPkhnVS1z8eFTfh RIOjwFEMhN1nEHl6tWcsaZfmDuqvLi16Y2npo=
Received: by 10.229.66.12 with SMTP id l12mr3401187qci.127.1323200580964; Tue, 06 Dec 2011 11:43:00 -0800 (PST)
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 ed2sm33971702qab.15.2011.12.06.11.42.59 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 06 Dec 2011 11:42:59 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Character set for Line ID
Date: Tue, 6 Dec 2011 14:42:58 -0500
Message-Id: <16950B8E-6F05-4351-8EC5-E191CF7E73A9@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: Tue, 06 Dec 2011 19:43:02 -0000

Earlier, Suresh wrote:
> In the deployments that I know of, the line-id is
> not configured on the router at all. The router
> just passes through the line-id it received
> from the Access Node onto the AAA server.

Some are configured in the router.  Some are not.
In some cases, the router might even be the 
same system as the Access Node.  Regardless,
the quote above misses the original point
about operations.

The LineID value is configured by humans 
(e.g. directly via a CLI or indirectly via a 
provisioning system that was itself configured 
by humans or via some other schema that also
originates with humans) into (various) operational 
systems (e.g. routers, access nodes, AAA server, 
DHCP servers, other boxes) and does not contain
opaque bytes.  It contains printable characters
only.

In the different systems I'm aware of, which are
genetically different from each other, none permit
non-printable characters.  All appear to be limited
to US-ASCII, ISO-646, or ISO-8859.

The word "opaque" in the DHCP Line-ID option
merely meant that one ought not try to be too
smart in packet processing.  The goal of the 
words in that DHCP RFC are ONLY to ensure that 
"Foo" matches "Foo" and does not match (for example) 
"FOO" or "fOO" or "F00".

Yours,

Ran


From bob.hinden@gmail.com  Tue Dec  6 16:47:03 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 E88BA21F8801 for <ipv6@ietfa.amsl.com>; Tue,  6 Dec 2011 16:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.812
X-Spam-Level: 
X-Spam-Status: No, score=-103.812 tagged_above=-999 required=5 tests=[AWL=-0.212, 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 2qC61Ew5105O for <ipv6@ietfa.amsl.com>; Tue,  6 Dec 2011 16:47:03 -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 87BFC21F87FA for <ipv6@ietf.org>; Tue,  6 Dec 2011 16:46:56 -0800 (PST)
Received: by iaek3 with SMTP id k3so11953iae.31 for <ipv6@ietf.org>; Tue, 06 Dec 2011 16:46:56 -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=BL/fRdErnrojWOHU/l6OuUWDr1sNRIzCyOvYR1nHnMg=; b=b6xvHOmDzI/XkxH6SYLtL3uQmo/1cYG2QQu1VM2qiuyOK1kbW5xzMQkxWDvDjRlNx5 zLT0j5v2VFW9lYKa19Lmwi9QJbAYQGe1jp7f4WZa2Y+5CjxnTHhWvoRbnTlG2q3m0g2p aEZk8qSd8Wdo4E4VFPRcJ43Vt/Pea72w7FoNQ=
Received: by 10.42.173.71 with SMTP id q7mr16505162icz.43.1323218814581; Tue, 06 Dec 2011 16:46:54 -0800 (PST)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id ew6sm52719076igc.4.2011.12.06.16.46.53 (version=SSLv3 cipher=OTHER); Tue, 06 Dec 2011 16:46:53 -0800 (PST)
Subject: Re: Character set for Line ID
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: <EAC60EFC-0411-48AE-92D1-7621DCA60CA1@gmail.com>
Date: Tue, 6 Dec 2011 16:46:52 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <300341D2-D253-4AA5-94B0-2D188F8365AF@gmail.com>
References: <EAC60EFC-0411-48AE-92D1-7621DCA60CA1@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: 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, 07 Dec 2011 00:47:04 -0000

Ran,

Thanks.  I was reaching a conclusion based on what someone said at the =
last 6man session.  Given that opaque is not what I thought, your =
suggestion makes sense to me.

Bob

On Dec 6, 2011, at 11:35 AM, RJ Atkinson wrote:

>=20
> Bob,
>=20
>  My read of the relevant RFCs is that the=20
> DHCP Line-ID option specifies the use of the "NVT"
> character set. =20
>=20
> The character set specification is implicit, applying=20
> to all DHCP options, rather than having been written
> explicitly for this single DHCP option.  One has=20
> to really study the full set of DHCP RFCs=20
> (i.e. the full daisy-chain of RFC citations from
> the References backwards) to see this, but it is
> consistent with every DHCP implementation that=20
> I can identify.
>=20
>  I can't find ANY DHCP implementations that permit=20
> "arbitrary bytes" to be entered into the Line-ID option=20
> field. I can't think of any DHCP implementation that
> permits, for example, LINEFEED or CARRIAGE-RETURN
> to be entered into ANY DHCP-related field.  Many
> have problems with inputs other than printable
> characters from ISO-8859, for example. =20
>=20
>  The word "opaque" in the DHCP Line-ID option
> specification refers to the packet processing
> for the DHCP packet, not to the contents of
> the field or how that field is entered=20
> (presumably via a CLI or perhaps web page someplace)=20
> or how that field is to be displayed to humans.
>=20
> The DHCP Line-ID option does not use the word=20
> "opaque" to indicate absence of a character set.
> That is a mis-reading of the DHCP RFC set.
>=20
> As a former ISP person, I can assure that the
> Line-ID values absolutely DO get displayed
> to operators and others in network operations.
> It is important to be able to configure the
> Line-ID values and to view them in order to
> troubleshoot real networks (e.g. a DSL deployment).
>=20
> So the assumption that the DHCP Line-ID option
> does not have any specified character set is
> not actually correct.
>=20
> Now, if one's goal is *strict* compatibility with
> the DHCP Line-ID option, then the NVT character
> set (originally specified in very early RFCs)
> ought to be specified. =20
>=20
> I think, however, it would be reasonable to choose=20
> some alternative such as US-ASCII, ISO-8859-1,=20
> or (maybe -- possibly more risky given existing
> DHCP implementations -- but more globally suitable)
> UTF-8.
>=20
> Yours,
>=20
> Ran
>=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  Wed Dec  7 11:21: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 365D821F8BBF for <ipv6@ietfa.amsl.com>; Wed,  7 Dec 2011 11:21:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.657
X-Spam-Level: 
X-Spam-Status: No, score=-103.657 tagged_above=-999 required=5 tests=[AWL=-0.058, 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 MMhp4P9VU90z for <ipv6@ietfa.amsl.com>; Wed,  7 Dec 2011 11:21:06 -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 3890D21F8BB5 for <ipv6@ietf.org>; Wed,  7 Dec 2011 11:21:06 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so833523vcb.31 for <ipv6@ietf.org>; Wed, 07 Dec 2011 11:21:05 -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=ZOkL7ET4RcQmNnBHeeUPuLmgvHfmnlvsV891ddcHqcA=; b=phr25j+zc0n7PTD3LfZKIbJmxxVXnC67UMh8zCYPetD8/JSakve1dq1glygLGC0hG7 RSN1dM09zz0qKkLBOgz5Gq0bAwLY1LuEWK1MWCn5WYkhT5LX77rJtAZxEX+tdFxplzVE /d6Q3h/izO1rSNarhPulxxm60OOYHXUE3teng=
Received: by 10.52.88.5 with SMTP id bc5mr11848020vdb.15.1323285665746; Wed, 07 Dec 2011 11:21:05 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id l9sm2191294vde.13.2011.12.07.11.21.03 (version=SSLv3 cipher=OTHER); Wed, 07 Dec 2011 11:21:05 -0800 (PST)
Message-ID: <4EDFBC9A.7040503@gmail.com>
Date: Thu, 08 Dec 2011 08:20:58 +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: [Fwd: I-D Action: draft-carpenter-6man-uri-zoneid-00.txt]
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, 07 Dec 2011 19:21:07 -0000

Comments welcome...

-------- Original Message --------
Subject: I-D Action: draft-carpenter-6man-uri-zoneid-00.txt
Date: Tue, 06 Dec 2011 17:27:00 -0800
From: internet-drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Representing IPv6 Zone Identifiers in Uniform Resource Identifiers
	Author(s)       : Brian Carpenter
                          Robert M. Hinden
	Filename        : draft-carpenter-6man-uri-zoneid-00.txt
	Pages           : 6
	Date            : 2011-12-06

   This document describes how the Zone Identifier of an IPv6 scoped
   address can be represented in a Uniform Resource Identifier that
   includes a literal IPv6 address.  It updates RFC 3986 and RFC 4007.


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


From suresh.krishnan@ericsson.com  Wed Dec  7 21:39:44 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 0C4B721F84FB for <ipv6@ietfa.amsl.com>; Wed,  7 Dec 2011 21:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.107
X-Spam-Level: 
X-Spam-Status: No, score=-106.107 tagged_above=-999 required=5 tests=[AWL=0.492, 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 yELQR4nQb1ed for <ipv6@ietfa.amsl.com>; Wed,  7 Dec 2011 21:39:43 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id F08AD21F84FA for <ipv6@ietf.org>; Wed,  7 Dec 2011 21:39:42 -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 pB85dbY5022082 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 Dec 2011 23:39:40 -0600
Received: from [164.48.125.41] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.137.0; Thu, 8 Dec 2011 00:39:36 -0500
Message-ID: <4EE04D22.3050702@ericsson.com>
Date: Thu, 8 Dec 2011 00:37:38 -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: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: Character set for Line ID
References: <EAC60EFC-0411-48AE-92D1-7621DCA60CA1@gmail.com>
In-Reply-To: <EAC60EFC-0411-48AE-92D1-7621DCA60CA1@gmail.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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, 08 Dec 2011 05:39:44 -0000

Hi Ran,
  Thanks for the explanation. It was very useful.

On 12/06/2011 02:35 PM, RJ Atkinson wrote:
> 
> Bob,
> 
>   My read of the relevant RFCs is that the 
> DHCP Line-ID option specifies the use of the "NVT"
> character set.  
> ...
> Now, if one's goal is *strict* compatibility with
> the DHCP Line-ID option, then the NVT character
> set (originally specified in very early RFCs)
> ought to be specified.  

This is not a goal but is certainly a limiting factor. I have checked
with a few BBF operators and they believe that the printable subset of
7-bit ASCII should be sufficient to hold the line ids. From my reading
of RFC854 (is there a more specific reference?) it seems that NVT should
be able to hold all possible line-ids.

Thanks
Suresh

From rja.lists@gmail.com  Thu Dec  8 04:26:15 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 6C82321F8A7D for <ipv6@ietfa.amsl.com>; Thu,  8 Dec 2011 04:26:15 -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 tAlb2cf0tawI for <ipv6@ietfa.amsl.com>; Thu,  8 Dec 2011 04:26:15 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id D5D2921F8A69 for <ipv6@ietf.org>; Thu,  8 Dec 2011 04:26:14 -0800 (PST)
Received: by qadb15 with SMTP id b15so368676qad.10 for <ipv6@ietf.org>; Thu, 08 Dec 2011 04:26:14 -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 :to:mime-version:x-mailer; bh=PS9jebF4wNnOJiP98jkX04FqJyJ4lHG5dI9jxTHRcGc=; b=pGRZ8oMRKSiOoDczOOk54/xK48P+fwcbH5kPEmnp78Qom7zp90p7Gg+ET96dNAPWd6 PKHIJee7bvmgnq8c4GSAGEHEzbCLF3ycWIGiAhU4H8SFymGVIU9rG8r4g7lBvppcsP7h MSOS2+Labdn4TgMA0dMaXOYYKaOjCvgTH6e3A=
Received: by 10.224.18.140 with SMTP id w12mr2558502qaa.60.1323347174365; Thu, 08 Dec 2011 04:26:14 -0800 (PST)
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 du5sm9733172qab.14.2011.12.08.04.26.11 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 08 Dec 2011 04:26:12 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Character set for Line ID
Date: Thu, 8 Dec 2011 07:26:13 -0500
Message-Id: <70703BB1-D8E0-4833-996B-B2F2632C34FF@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: Thu, 08 Dec 2011 12:26:15 -0000

Glen Turner and I expect to post some draft 
candidate text about the character set issue 
to the IPv6 WG list in the next several days.

Ran


From brian@innovationslab.net  Thu Dec  8 06:46:31 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 9FF7721F8AC3 for <ipv6@ietfa.amsl.com>; Thu,  8 Dec 2011 06:46: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 fQZihZLhnROa for <ipv6@ietfa.amsl.com>; Thu,  8 Dec 2011 06:46:31 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3A58321F8AB9 for <ipv6@ietf.org>; Thu,  8 Dec 2011 06:46:31 -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 BD9B9882AA for <ipv6@ietf.org>; Thu,  8 Dec 2011 06:46:30 -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 80834130004 for <ipv6@ietf.org>; Thu,  8 Dec 2011 06:46:30 -0800 (PST)
Message-ID: <4EE0CDC5.6090908@innovationslab.net>
Date: Thu, 08 Dec 2011 09:46:29 -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: [Fwd: I-D Action: draft-carpenter-6man-uri-zoneid-00.txt]
References: <4EDFBC9A.7040503@gmail.com>
In-Reply-To: <4EDFBC9A.7040503@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, 08 Dec 2011 14:46:31 -0000

Brian & Bob,

On 12/7/11 2:20 PM, Brian E Carpenter wrote:
> Comments welcome...
> 
> -------- Original Message --------
> Subject: I-D Action: draft-carpenter-6man-uri-zoneid-00.txt
> Date: Tue, 06 Dec 2011 17:27:00 -0800
> From: internet-drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 	Title           : Representing IPv6 Zone Identifiers in Uniform Resource Identifiers
> 	Author(s)       : Brian Carpenter
>                           Robert M. Hinden
> 	Filename        : draft-carpenter-6man-uri-zoneid-00.txt
> 	Pages           : 6
> 	Date            : 2011-12-06
> 
>    This document describes how the Zone Identifier of an IPv6 scoped
>    address can be represented in a Uniform Resource Identifier that
>    includes a literal IPv6 address.  It updates RFC 3986 and RFC 4007.

If option 2 is preferred as this work moves forward, does there need to
be text on how to handle the addition of a ZoneID to an address that
does not need one (i.e., non-link-local)?

It would probably be useful for the draft to reference RFC 4007 as
guidance on how the ZoneID affects interface/address selection.

Regards,
Brian


From shemant@cisco.com  Thu Dec  8 15:57:15 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 33AF621F84AF for <ipv6@ietfa.amsl.com>; Thu,  8 Dec 2011 15:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.075,  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 DoSR00KptFcO for <ipv6@ietfa.amsl.com>; Thu,  8 Dec 2011 15:57:14 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 324AE21F84A6 for <ipv6@ietf.org>; Thu,  8 Dec 2011 15:57:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=3640; q=dns/txt; s=iport; t=1323388634; x=1324598234; h=mime-version:subject:date:message-id:from:to:cc; bh=yGrS7aOgj8j2Pp0yHqbv/Iw3JJvBoAVN6AywSRNBWoc=; b=M+TYyAxcdNzQbJwKXvUBocDQOIVaLeaBNalQXilPcoSu825LTWpIPeGM rPWuzAX6FhnlgeQvfnGh76uCOIogj0toLtwKLW62Nwsf1XwX/MEdl03rk PHNafNM+Gw8FT35IQ2SejdImRH/rW8zwHmFFn8WXbKZRXdI1WvGljk8lP 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFAIpO4U6tJXHB/2dsb2JhbABDgk2gBwGIFYEFgXQBBBIBCREDSRIBDB4GGAdXAQQbGodtmVoBngCII4I1YwSILp8C
X-IronPort-AV: E=Sophos;i="4.71,322,1320624000"; d="scan'208,217";a="42387913"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 08 Dec 2011 23:57:01 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id pB8Nv0rF026197;  Thu, 8 Dec 2011 23:57:00 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 8 Dec 2011 17:57:00 -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_01CCB605.13870035"
Subject: please review new version of the enhanced-dad draft
Date: Thu, 8 Dec 2011 17:56:59 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303829081@XMB-RCD-109.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: please review new version of the enhanced-dad draft
Thread-Index: Acy2BRMKban3FvkyT6mUtyjFPqUWoQ==
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 08 Dec 2011 23:57:00.0782 (UTC) FILETIME=[13A8C0E0:01CCB605]
Cc: "Howard, Lee" <lee.howard@twcable.com>, Suresh Krishnan <suresh.krishnan@ericsson.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, 08 Dec 2011 23:57:15 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCB605.13870035
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

http://tools.ietf.org/html/draft-hsingh-6man-enhanced-dad-03

=20

The new version incorporate changes after comments during the
presentation at the recent Taipei IETF.   The new version includes a
Change log so that folks can see the gross changes.  Alternatively folks
can use the IETF rfcdiff tool to get the specific change log.=20

=20

Suresh and DmitryA, please see the new Changes to RFC 4862 section.
Lee, please see the updated text for the cable broadband example in the
Introduction section.    Thanks to you all and others for your comments.

=20

Thanks,

=20

Hemant


------_=_NextPart_001_01CCB605.13870035
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)"><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 WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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><a =
href=3D"http://tools.ietf.org/html/draft-hsingh-6man-enhanced-dad-03">htt=
p://tools.ietf.org/html/draft-hsingh-6man-enhanced-dad-03</a><o:p></o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The =
new version incorporate changes after comments during the presentation =
at the recent Taipei IETF.&nbsp;&nbsp; The new version includes a Change =
log so that folks can see the gross changes.&nbsp; Alternatively folks =
can use the IETF rfcdiff tool to get the specific change log. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Suresh and DmitryA, please see the new Changes to RFC =
4862 section. &nbsp;&nbsp;Lee, please see the updated text for the cable =
broadband example in the Introduction section.&nbsp;&nbsp;&nbsp; Thanks =
to you all and others for your comments.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thanks,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Hemant<o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CCB605.13870035--

From jari.arkko@piuha.net  Tue Dec 13 00:50:09 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 5F59321F85C7 for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 00:50:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 E5MGCJSm7BQP for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 00:50:09 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id D8E6F21F85D1 for <ipv6@ietf.org>; Tue, 13 Dec 2011 00:50:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 324DD2CC5A; Tue, 13 Dec 2011 10:50:08 +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 0WWoDLmyZ5tL; Tue, 13 Dec 2011 10:50:07 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 64A7A2CC31; Tue, 13 Dec 2011 10:50:07 +0200 (EET)
Message-ID: <4EE711BE.90600@piuha.net>
Date: Tue, 13 Dec 2011 10:50:06 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111110 Thunderbird/8.0
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
References: <CB0AF0C2.33621%sgundave@cisco.com>
In-Reply-To: <CB0AF0C2.33621%sgundave@cisco.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, 13 Dec 2011 08:50:09 -0000

The new version of this draft looks good to me: http://tools.ietf.org/rfcdiff?url2=draft-gundavelli-v6ops-pmipv6-address-reservations-04.txt

Ready to be approved?

Jari


From john.loughney@nokia.com  Tue Dec 13 09:57:01 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 9061E21F8ACA for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 09:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.104
X-Spam-Level: 
X-Spam-Status: No, score=-97.104 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, DEAR_SOMETHING=1.605, HTML_MESSAGE=0.001, J_CHICKENPOX_102=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_71=0.6, J_CHICKENPOX_82=0.6, 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 d0KRH0p7USEA for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 09:57:00 -0800 (PST)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id DF52121F8A97 for <ipv6@ietf.org>; Tue, 13 Dec 2011 09:56:59 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-sa02.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id pBDHuvhn011259; Tue, 13 Dec 2011 19:56:57 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.56]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Dec 2011 19:56:57 +0200
Received: from 008-AM1MPN1-015.mgdnok.nokia.com ([169.254.5.97]) by 008-AM1MMR1-001.mgdnok.nokia.com ([65.54.30.56]) with mapi id 14.01.0355.003; Tue, 13 Dec 2011 18:56:56 +0100
From: <john.loughney@nokia.com>
To: <zyh1898@gmail.com>
Subject: RE: Mail regarding draft-ietf-6man-node-req-bis
Thread-Topic: Mail regarding draft-ietf-6man-node-req-bis
Thread-Index: AQHMuVQle7KA1FwOC0a1XLi+PJ/+NJXaDjNQ
Date: Tue, 13 Dec 2011 17:56:56 +0000
Message-ID: <2129067463716F46AC77A22602E5CB5C01FF6AA0@008-AM1MPN1-015.mgdnok.nokia.com>
References: <C716BA6AD50D45FA8C5F5BE8561BEC93@zyhPC>
In-Reply-To: <C716BA6AD50D45FA8C5F5BE8561BEC93@zyhPC>
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: VgNFIFU9Hx+/nZJb9Kg7IjV2rptLnNm/Z3hNP38OqfSHS+Ug4NOZ+vXVixUB2KoUA4HxY4kro9OWC/Z/FZ6QfyQBszkK/C7Gj3szRnwjbkJ3wVmfIsVtAR/DepAn25koK2yNCaQW/7YfPgPncXQ9QA4IAWVHnNCGTdw813+412E8tS/vDpy+9JjsyoRXYO1r4cypcDEzXKzAHSD6uXo1nE+Qo2AtzU2qfrFMcId4XGoq3DAOTzsjpRYTL8b0hdVD
x-headerinfofordlp: None
x-originating-ip: [10.243.186.43]
Content-Type: multipart/alternative; boundary="_000_2129067463716F46AC77A22602E5CB5C01FF6AA0008AM1MPN1015mg_"
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Dec 2011 17:56:57.0308 (UTC) FILETIME=[9B0CF9C0:01CCB9C0]
X-Nokia-AV: Clean
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, 13 Dec 2011 17:57:01 -0000

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

I am forwarding this to the IPv6 Maintenance mailing list.  Discussion of t=
his sort can take place on the mailing list.

John

From: ext zyh [mailto:zyh1898@gmail.com]
Sent: Monday, December 12, 2011 8:31 PM
To: draft-ietf-6man-node-req-bis@tools.ietf.org
Subject: Mail regarding draft-ietf-6man-node-req-bis

Dear Sir:


    As a Chinese,I am writing to express my deep concern about the change o=
f IPSEC in IPv6 Node Requirements(draft-ietf-6man-node-req-bis-11).

    Frankly speaking,my country has enforced the world most rigorous censor=
ship on the Internet,so we can not access twitter,Facebook and other world =
famous websites directly.And Google services there is very unstable.The Int=
ernet is becoming almost a intranet there.

    But thanks to the force implementation of IPSEC in IPV6,the government =
is unable to enforce deep packet inspection,so we can easily surf the Inter=
net through IPV6.So  I'm afraid that once the requirement of IPSEC change f=
rom MUST to SHOULD,we will have a bleak future inevitably.

    I believe you will take my concern into account and I will be more than=
 happy to see some changes in this regard soon.



Yours sincerely

zhang yuhao


--_000_2129067463716F46AC77A22602E5CB5C01FF6AA0008AM1MPN1015mg_
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:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;
	mso-fareast-language:ZH-CN;}
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-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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;}
--></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"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I am forwarding this to t=
he IPv6 Maintenance mailing list.&nbsp; Discussion of this sort can take pl=
ace on the mailing list.<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">John<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;"> ext zyh =
[mailto:zyh1898@gmail.com]
<br>
<b>Sent:</b> Monday, December 12, 2011 8:31 PM<br>
<b>To:</b> draft-ietf-6man-node-req-bis@tools.ietf.org<br>
<b>Subject:</b> Mail regarding draft-ietf-6man-node-req-bis<o:p></o:p></spa=
n></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">Dear Sir:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp; As a Chinese,I am writing=
 to express my deep concern about the change of IPSEC in IPv6 Node Requirem=
ents(draft-ietf-6man-node-req-bis-11).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp; Frankly speaking,my count=
ry has enforced the world most rigorous censorship on the Internet,so we ca=
n not access twitter,Facebook and other world famous websites directly.And
 Google services there is very unstable.The Internet is becoming almost a i=
ntranet there.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp; But thanks to the force i=
mplementation of IPSEC in IPV6,the government is unable to enforce deep pac=
ket inspection,so we can easily surf the Internet through IPV6.So&nbsp; I&#=
8217;m
 afraid that once the requirement of IPSEC change from MUST to SHOULD,we wi=
ll have a bleak future inevitably.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp; I believe you will take m=
y concern into account and I will be more than happy to see some changes in=
 this regard soon.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">Yours sincerely<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">zhang yuhao<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_2129067463716F46AC77A22602E5CB5C01FF6AA0008AM1MPN1015mg_--

From Basavaraj.Patil@nokia.com  Tue Dec 13 13:12:43 2011
Return-Path: <Basavaraj.Patil@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 3B9E321F84A7 for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 13:12:43 -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 w1bxdWOxBizw for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 13:12:41 -0800 (PST)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 710CA21F84A4 for <ipv6@ietf.org>; Tue, 13 Dec 2011 13:12:41 -0800 (PST)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-sa02.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id pBDLCW6p027945; Tue, 13 Dec 2011 23:12:32 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.20]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Dec 2011 23:12:31 +0200
Received: from 008-AM1MPN1-073.mgdnok.nokia.com ([169.254.3.69]) by 008-AM1MMR1-011.mgdnok.nokia.com ([65.54.30.20]) with mapi id 14.01.0355.003; Tue, 13 Dec 2011 22:12:31 +0100
From: <Basavaraj.Patil@nokia.com>
To: <jari.arkko@piuha.net>
Subject: Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
Thread-Topic: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
Thread-Index: AQHMudvsb7KLMKzyiUGM5dqBXuo80A==
Date: Tue, 13 Dec 2011 21:12:30 +0000
Message-ID: <CB0D1A10.17060%basavaraj.patil@nokia.com>
In-Reply-To: <4EE711BE.90600@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [172.19.59.133]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B3D1F10AAE49C544948E624793DDB930@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Dec 2011 21:12:31.0886 (UTC) FILETIME=[ED677AE0:01CCB9DB]
X-Nokia-AV: Clean
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, 13 Dec 2011 21:12:43 -0000

A few clarifying questions:

1. Would all the MAGs across different PMIP6 domains be required to use
the same LLA and IID?
As per the proposal a single LLA and IID are being reserved for use by
PMIP6 MAGs.

2. Is it mandatory for the MAGs in a PMIP6 domain to use this LLA and IID?
Or is it simply a recommendation.
Network configuration tools and protocols can ensure that the same LLA and
IID is configured across all MAGs in a PMIP6 domain. Hence assigning a
specific LLA and IID is unnecessary.

3. When a MAG is provisioned it needs to be associated with an LMA and a
security association configured between the MAG and LMA. As a part of that
process, the MAG could obtain the LLA and IID to be used from the LMA
itself. Would this approach not be sufficient?

-Basavaraj

On 12/13/11 2:50 AM, "ext Jari Arkko" <jari.arkko@piuha.net> wrote:

>The new version of this draft looks good to me:
>http://tools.ietf.org/rfcdiff?url2=3Ddraft-gundavelli-v6ops-pmipv6-address=
-r
>eservations-04.txt
>
>Ready to be approved?
>
>Jari
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------


From sgundave@cisco.com  Tue Dec 13 13:29:25 2011
Return-Path: <sgundave@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 3BF9821F86C3 for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 13:29:25 -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 TqElZBM1xiMj for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 13:29:24 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 50CC821F8672 for <ipv6@ietf.org>; Tue, 13 Dec 2011 13:29:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=3182; q=dns/txt; s=iport; t=1323811764; x=1325021364; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=8bbOrrzmMpHYjYTyWwAvlxgFf3uuuhD0cETtPsdCX40=; b=c4paX7xraDI1IVS07uxtTqCJfKTJ3D6Ho10PJklxZWFTaVFOjDnoo5fX aB3qwtne1knWjxcY/PYPrYyAJJUAYvOCJVrP2ePR4Ac5ioBHMCCb99Qhr GYcfW6I9T1Rivv9pXQflNB224qg9bHNmrBi/gbZmEUmcecCGrdonJoSby M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHzD506rRDoJ/2dsb2JhbABDqx+BBYFyAQEBAwEBAQEPAScCATELBQ0BCBgjMjACBAENBSKHWgiXWQGeIotjBIgwjEGSSg
X-IronPort-AV: E=Sophos;i="4.71,348,1320624000"; d="scan'208";a="20583981"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 13 Dec 2011 21:29:24 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pBDLT8cI026271; Tue, 13 Dec 2011 21:29:24 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Dec 2011 13:29:17 -0800
Received: from 10.32.246.213 ([10.32.246.213]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ;  Tue, 13 Dec 2011 21:29:17 +0000
User-Agent: Microsoft-Entourage/12.31.0.110725
Date: Tue, 13 Dec 2011 13:29:08 -0800
Subject: Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
From: Sri Gundavelli <sgundave@cisco.com>
To: <Basavaraj.Patil@nokia.com>, <jari.arkko@piuha.net>
Message-ID: <CB0D03A4.33931%sgundave@cisco.com>
Thread-Topic: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
Thread-Index: AQHMudvsb7KLMKzyiUGM5dqBXuo80JXaSMYC
In-Reply-To: <CB0D1A10.17060%basavaraj.patil@nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 13 Dec 2011 21:29:17.0598 (UTC) FILETIME=[44DAF3E0:01CCB9DE]
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, 13 Dec 2011 21:29:25 -0000

Hi Raj:

Please see inline.


On 12/13/11 1:12 PM, "Basavaraj.Patil@nokia.com" <Basavaraj.Patil@nokia.com>
wrote:

> 
> A few clarifying questions:
> 
> 1. Would all the MAGs across different PMIP6 domains be required to use
> the same LLA and IID?
> As per the proposal a single LLA and IID are being reserved for use by
> PMIP6 MAGs.
> 

We already have this requirement of using a fixed link-layer Id and IPv6
interface id on the MAG-AR interface, within a PMIPv6 domain. We did not do
the allocation of the same values and deployments have to configure these
values across every MAG in a PMIPv6 domain. Given the scope is a localized
domain, we can only specify this requirement for a given domain, along with
the other domain-wide parameters. Generally, requiring the configuration of
a domain wide value is not an issue, but when the values are about
link-layer id, we need a standardized value, and in the absence of that,
administrator will configure some random addresses, as we are noticing,
which can be an issue.



> 2. Is it mandatory for the MAGs in a PMIP6 domain to use this LLA and IID?
> Or is it simply a recommendation.
> Network configuration tools and protocols can ensure that the same LLA and
> IID is configured across all MAGs in a PMIP6 domain. Hence assigning a
> specific LLA and IID is unnecessary.
> 

Yes. With this draft, its requiring these assigned values to be used on the
MN-AR interface, eliminating the need for static CLI-based configuration
across all the MAG's in a domain.


> 3. When a MAG is provisioned it needs to be associated with an LMA and a
> security association configured between the MAG and LMA. As a part of that
> process, the MAG could obtain the LLA and IID to be used from the LMA
> itself. Would this approach not be sufficient?
> 

Its not really tied to the home network. Its more about MAG to MAG roaming,
within a PMIP domain. We required statically configured values in the base
spec, the same is now an IANA allocated fixed value. Sure, it is possible to
extend the message interface and push it from the LMA as well, if we want to
define new option for MAG-LLID on PMIP interface, but allocating fixed
values for the already defined domain-wide parameters is the simplest
option.


Regards
Sri 




> -Basavaraj
> 
> On 12/13/11 2:50 AM, "ext Jari Arkko" <jari.arkko@piuha.net> wrote:
> 
>> The new version of this draft looks good to me:
>> http://tools.ietf.org/rfcdiff?url2=draft-gundavelli-v6ops-pmipv6-address-r
>> eservations-04.txt
>> 
>> Ready to be approved?
>> 
>> Jari
>> 
>> --------------------------------------------------------------------
>> 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 Basavaraj.Patil@nokia.com  Tue Dec 13 14:01:34 2011
Return-Path: <Basavaraj.Patil@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 C824011E809D for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 14:01:34 -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=[AWL=0.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 bJheYpqB8JjU for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 14:01:33 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6F611E809B for <ipv6@ietf.org>; Tue, 13 Dec 2011 14:01:32 -0800 (PST)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id pBDM1QWK006544; Wed, 14 Dec 2011 00:01:29 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.60]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 14 Dec 2011 00:01:28 +0200
Received: from 008-AM1MPN1-073.mgdnok.nokia.com ([169.254.3.69]) by 008-AM1MMR1-005.mgdnok.nokia.com ([65.54.30.60]) with mapi id 14.01.0355.003; Tue, 13 Dec 2011 23:01:28 +0100
From: <Basavaraj.Patil@nokia.com>
To: <sgundave@cisco.com>, <jari.arkko@piuha.net>
Subject: Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
Thread-Topic: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
Thread-Index: AQHMudvsb7KLMKzyiUGM5dqBXuo80JXaSMYC//+TtwA=
Date: Tue, 13 Dec 2011 22:01:25 +0000
Message-ID: <CB0D255B.17078%basavaraj.patil@nokia.com>
In-Reply-To: <CB0D03A4.33931%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [172.19.59.133]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <85949EED05461342AE4217F65269EABB@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Dec 2011 22:01:28.0677 (UTC) FILETIME=[C3DE3950:01CCB9E2]
X-Nokia-AV: Clean
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, 13 Dec 2011 22:01:35 -0000

Hi Sri,

On 12/13/11 3:29 PM, "ext Sri Gundavelli" <sgundave@cisco.com> wrote:

>Hi Raj:
>
>Please see inline.
>
>
>On 12/13/11 1:12 PM, "Basavaraj.Patil@nokia.com"
><Basavaraj.Patil@nokia.com>
>wrote:
>
>>=20
>> A few clarifying questions:
>>=20
>> 1. Would all the MAGs across different PMIP6 domains be required to use
>> the same LLA and IID?
>> As per the proposal a single LLA and IID are being reserved for use by
>> PMIP6 MAGs.
>>=20
>
>We already have this requirement of using a fixed link-layer Id and IPv6
>interface id on the MAG-AR interface, within a PMIPv6 domain. We did not
>do
>the allocation of the same values and deployments have to configure these
>values across every MAG in a PMIPv6 domain. Given the scope is a localized
>domain, we can only specify this requirement for a given domain, along
>with
>the other domain-wide parameters. Generally, requiring the configuration
>of
>a domain wide value is not an issue, but when the values are about
>link-layer id, we need a standardized value, and in the absence of that,
>administrator will configure some random addresses, as we are noticing,
>which can be an issue.

Agree. RFC5213 requires the MAGs in a PMIP6 domain be configured with the
same LLA.=20
Sec 9.3 of RFC5213 defines the parameter:
"FixedMAGLinkLayerAddressOnAllAccessLinks". It would be good to explain
that this I-D obsoletes this parameter or indicate the IANA assigned value
to be now provisioned for the same.
Do you see any concern from security or privacy perspective the use of a
common LLA and IID for all MAGs across multiple PMIP6 domains?

>
>
>
>> 2. Is it mandatory for the MAGs in a PMIP6 domain to use this LLA and
>>IID?
>> Or is it simply a recommendation.
>> Network configuration tools and protocols can ensure that the same LLA
>>and
>> IID is configured across all MAGs in a PMIP6 domain. Hence assigning a
>> specific LLA and IID is unnecessary.
>>=20
>
>Yes. With this draft, its requiring these assigned values to be used on
>the
>MN-AR interface, eliminating the need for static CLI-based configuration
>across all the MAG's in a domain.

Okay. But it is not just w.r.t all MAGs in a single domain; It applies to
all MAGs across domains, right?

>
>
>> 3. When a MAG is provisioned it needs to be associated with an LMA and a
>> security association configured between the MAG and LMA. As a part of
>>that
>> process, the MAG could obtain the LLA and IID to be used from the LMA
>> itself. Would this approach not be sufficient?
>>=20
>
>Its not really tied to the home network. Its more about MAG to MAG
>roaming,
>within a PMIP domain. We required statically configured values in the base
>spec, the same is now an IANA allocated fixed value. Sure, it is possible
>to
>extend the message interface and push it from the LMA as well, if we want
>to
>define new option for MAG-LLID on PMIP interface, but allocating fixed
>values for the already defined domain-wide parameters is the simplest
>option.

Okay. I agree it is easier to have a static configuration value than to
extend the protocol between MAG-LMA with an additional option.

-Raj

>
>
>Regards
>Sri=20
>
>
>
>
>> -Basavaraj
>>=20
>> On 12/13/11 2:50 AM, "ext Jari Arkko" <jari.arkko@piuha.net> wrote:
>>=20
>>> The new version of this draft looks good to me:
>>>=20
>>>http://tools.ietf.org/rfcdiff?url2=3Ddraft-gundavelli-v6ops-pmipv6-addre=
ss
>>>-r
>>> eservations-04.txt
>>>=20
>>> Ready to be approved?
>>>=20
>>> Jari
>>>=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 sgundave@cisco.com  Tue Dec 13 14:07:52 2011
Return-Path: <sgundave@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 A338B11E80A3 for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 14:07:52 -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 rinvC9S-3zjQ for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 14:07:51 -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 BBE8411E809D for <ipv6@ietf.org>; Tue, 13 Dec 2011 14:07:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=4721; q=dns/txt; s=iport; t=1323814071; x=1325023671; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=HCv7jHkMsE+vGtpGW/JsBQ3r5mhJ7XNxXdfiFjzG44g=; b=PtQtUxnLDzxft1skR+VYcnXasCYc1zusehpBQ4ZeLoHOcD5wIF3jb+ju i2LRVzRGjfgZcEQjF70bpbo35Fm8bknPX2QxhWMQkv/npV5DB/QEfLCbN YkjJwiaJsO8/ReE5Mo/Dma6nelKc+9LsnMB64quQOnxRrL/CLHzAq+UxV k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EACvM506rRDoH/2dsb2JhbABDqx+BBYFyAQEBAwEBAQEPAScCATELEgEIGCMyMAIEAQ0FIodaCJduAZ4li2MEiDCMQZJK
X-IronPort-AV: E=Sophos;i="4.71,348,1320624000"; d="scan'208";a="18827627"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 13 Dec 2011 22:07:49 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pBDM7nZx020980; Tue, 13 Dec 2011 22:07:49 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Dec 2011 14:07:49 -0800
Received: from 10.32.246.213 ([10.32.246.213]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ;  Tue, 13 Dec 2011 22:07:48 +0000
User-Agent: Microsoft-Entourage/12.31.0.110725
Date: Tue, 13 Dec 2011 14:07:46 -0800
Subject: Re: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
From: Sri Gundavelli <sgundave@cisco.com>
To: <Basavaraj.Patil@nokia.com>, <jari.arkko@piuha.net>
Message-ID: <CB0D0CB2.3394A%sgundave@cisco.com>
Thread-Topic: Last Call: <draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to Informational RFC
Thread-Index: AQHMudvsb7KLMKzyiUGM5dqBXuo80JXaSMYC//+TtwCAAHcUaw==
In-Reply-To: <CB0D255B.17078%basavaraj.patil@nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 13 Dec 2011 22:07:49.0093 (UTC) FILETIME=[A69D1950:01CCB9E3]
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, 13 Dec 2011 22:07:52 -0000

Hi Raj:

Thanks for your comments.


On 12/13/11 2:01 PM, "Basavaraj.Patil@nokia.com" <Basavaraj.Patil@nokia.com>
wrote:

> 
> Hi Sri,
> 
> On 12/13/11 3:29 PM, "ext Sri Gundavelli" <sgundave@cisco.com> wrote:
> 
>> Hi Raj:
>> 
>> Please see inline.
>> 
>> 
>> On 12/13/11 1:12 PM, "Basavaraj.Patil@nokia.com"
>> <Basavaraj.Patil@nokia.com>
>> wrote:
>> 
>>> 
>>> A few clarifying questions:
>>> 
>>> 1. Would all the MAGs across different PMIP6 domains be required to use
>>> the same LLA and IID?
>>> As per the proposal a single LLA and IID are being reserved for use by
>>> PMIP6 MAGs.
>>> 
>> 
>> We already have this requirement of using a fixed link-layer Id and IPv6
>> interface id on the MAG-AR interface, within a PMIPv6 domain. We did not
>> do
>> the allocation of the same values and deployments have to configure these
>> values across every MAG in a PMIPv6 domain. Given the scope is a localized
>> domain, we can only specify this requirement for a given domain, along
>> with
>> the other domain-wide parameters. Generally, requiring the configuration
>> of
>> a domain wide value is not an issue, but when the values are about
>> link-layer id, we need a standardized value, and in the absence of that,
>> administrator will configure some random addresses, as we are noticing,
>> which can be an issue.
> 
> Agree. RFC5213 requires the MAGs in a PMIP6 domain be configured with the
> same LLA. 
> Sec 9.3 of RFC5213 defines the parameter:
> "FixedMAGLinkLayerAddressOnAllAccessLinks". It would be good to explain
> that this I-D obsoletes this parameter or indicate the IANA assigned value
> to be now provisioned for the same.
> Do you see any concern from security or privacy perspective the use of a
> common LLA and IID for all MAGs across multiple PMIP6 domains?
> 

Ok, I can reflect that point. The security section was updated after IESG
review, reflecting the impact with SEND deployed on the access link.




>> 
>> 
>> 
>>> 2. Is it mandatory for the MAGs in a PMIP6 domain to use this LLA and
>>> IID?
>>> Or is it simply a recommendation.
>>> Network configuration tools and protocols can ensure that the same LLA
>>> and
>>> IID is configured across all MAGs in a PMIP6 domain. Hence assigning a
>>> specific LLA and IID is unnecessary.
>>> 
>> 
>> Yes. With this draft, its requiring these assigned values to be used on
>> the
>> MN-AR interface, eliminating the need for static CLI-based configuration
>> across all the MAG's in a domain.
> 
> Okay. But it is not just w.r.t all MAGs in a single domain; It applies to
> all MAGs across domains, right?
> 
>> 

Yes, the same assigned values will be used on all the MAG-AR links.


>> 
>>> 3. When a MAG is provisioned it needs to be associated with an LMA and a
>>> security association configured between the MAG and LMA. As a part of
>>> that
>>> process, the MAG could obtain the LLA and IID to be used from the LMA
>>> itself. Would this approach not be sufficient?
>>> 
>> 
>> Its not really tied to the home network. Its more about MAG to MAG
>> roaming,
>> within a PMIP domain. We required statically configured values in the base
>> spec, the same is now an IANA allocated fixed value. Sure, it is possible
>> to
>> extend the message interface and push it from the LMA as well, if we want
>> to
>> define new option for MAG-LLID on PMIP interface, but allocating fixed
>> values for the already defined domain-wide parameters is the simplest
>> option.
> 
> Okay. I agree it is easier to have a static configuration value than to
> extend the protocol between MAG-LMA with an additional option.
>

Ok. Thanks



Regards
Sri

 
> -Raj
> 
>> 
>> 
>> Regards
>> Sri 
>> 
>> 
>> 
>> 
>>> -Basavaraj
>>> 
>>> On 12/13/11 2:50 AM, "ext Jari Arkko" <jari.arkko@piuha.net> wrote:
>>> 
>>>> The new version of this draft looks good to me:
>>>> 
>>>> http://tools.ietf.org/rfcdiff?url2=draft-gundavelli-v6ops-pmipv6-address
>>>> -r
>>>> eservations-04.txt
>>>> 
>>>> Ready to be approved?
>>>> 
>>>> Jari
>>>> 
>>>> --------------------------------------------------------------------
>>>> 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 Dec 13 14:15:47 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 09E0921F85A1 for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 14:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.589
X-Spam-Level: 
X-Spam-Status: No, score=-103.589 tagged_above=-999 required=5 tests=[AWL=0.010, 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 fPd+Dm3DsmsL for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 14:15:46 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 873FA21F8593 for <ipv6@ietf.org>; Tue, 13 Dec 2011 14:15:46 -0800 (PST)
Received: by ghrr16 with SMTP id r16so145518ghr.31 for <ipv6@ietf.org>; Tue, 13 Dec 2011 14:15:46 -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=YWQC9bcV+6uRbwHEQsvJU1ZFZh+53qkui7/GRHdcdAc=; b=IXwHq/e0xrxZE/hbzMPg2/fTU8vdPS69b1bGx9zIKE3IV3eQ7IGIyC1ydnFZ7IGseA BqhGftZf2uoFtPJkfeaVF0WfurrhathGX2SHT2YWCDPLvaIbdTKDTkfWjG/334n4z+1B cI67/ED9gHttRv1RkngJRyUjWTmoRjAdFs1x4=
Received: by 10.50.153.133 with SMTP id vg5mr21762921igb.80.1323814545870; Tue, 13 Dec 2011 14:15:45 -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 l28sm1323289ibc.3.2011.12.13.14.15.42 (version=SSLv3 cipher=OTHER); Tue, 13 Dec 2011 14:15:44 -0800 (PST)
Message-ID: <4EE7CE8C.7090204@gmail.com>
Date: Wed, 14 Dec 2011 11:15:40 +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: Brian Haberman <brian@innovationslab.net>
Subject: Re: [Fwd: I-D Action: draft-carpenter-6man-uri-zoneid-00.txt]
References: <4EDFBC9A.7040503@gmail.com> <4EE0CDC5.6090908@innovationslab.net>
In-Reply-To: <4EE0CDC5.6090908@innovationslab.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: Tue, 13 Dec 2011 22:15:47 -0000

On 2011-12-09 03:46, Brian Haberman wrote:
> Brian & Bob,

...
>>    This document describes how the Zone Identifier of an IPv6 scoped
>>    address can be represented in a Uniform Resource Identifier that
>>    includes a literal IPv6 address.  It updates RFC 3986 and RFC 4007.
> 
> If option 2 is preferred as this work moves forward, does there need to
> be text on how to handle the addition of a ZoneID to an address that
> does not need one (i.e., non-link-local)?

Either that, or at least a statement that it's currently undefined.

I imagine that MIF might have an interest in this question.

> 
> It would probably be useful for the draft to reference RFC 4007 as
> guidance on how the ZoneID affects interface/address selection.

Yes, good idea.

Thanks

    Brian C

> 
> Regards,
> Brian
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

From marka@isc.org  Tue Dec 13 21:42:55 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 54F3B1F0C4F for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 21:42:55 -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 5+ulBQUq3gYZ for <ipv6@ietfa.amsl.com>; Tue, 13 Dec 2011 21:42:54 -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 6D56E1F0C57 for <6man@ietf.org>; Tue, 13 Dec 2011 21:42:54 -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 489ECC942D for <6man@ietf.org>; Wed, 14 Dec 2011 05:42:44 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:9dbe:1913:d1c:b98c]) (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 1320C216C6B for <6man@ietf.org>; Wed, 14 Dec 2011 05:42: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 53F6B1A08E7F for <6man@ietf.org>; Wed, 14 Dec 2011 16:42:41 +1100 (EST)
To: 6man@ietf.org
From: Mark Andrews <marka@isc.org>
Subject: draft-andrews-6man-force-fragmentation-00.txt
Date: Wed, 14 Dec 2011 16:42:41 +1100
Message-Id: <20111214054241.53F6B1A08E7F@drugs.dv.isc.org>
X-Mailman-Approved-At: Tue, 13 Dec 2011 21:44:41 -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: Wed, 14 Dec 2011 05:42:55 -0000

	draft-andrews-6man-force-fragmentation-00.txt was just
	submitted.  Comments requested.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE:	+61 2 9871 4742		         INTERNET: marka@isc.org

From internet-drafts@ietf.org  Wed Dec 14 07:34:27 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 B72D621F8B7E; Wed, 14 Dec 2011 07:34:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 C6An+NYSThVu; Wed, 14 Dec 2011 07:34:27 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA1E21F8B39; Wed, 14 Dec 2011 07:34:27 -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-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111214153427.3662.89188.idtracker@ietfa.amsl.com>
Date: Wed, 14 Dec 2011 07:34:27 -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: Wed, 14 Dec 2011 15:34:27 -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-06.txt
	Pages           : 14
	Date            : 2011-12-14

   The RPL protocol includes routing information in data-plane datagrams
   to quickly identify inconsistencies in the routing topology.  This
   document describes the RPL Option for use among RPL routers to
   include such routing information.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-rpl-option-06.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-06.txt


From internet-drafts@ietf.org  Wed Dec 14 07:34:37 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 A97DF21F8BA9; Wed, 14 Dec 2011 07:34:37 -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 KmNeqbcRYbS5; Wed, 14 Dec 2011 07:34:37 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E37D21F8B9B; Wed, 14 Dec 2011 07:34:37 -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-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111214153437.3662.61966.idtracker@ietfa.amsl.com>
Date: Wed, 14 Dec 2011 07:34:37 -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: Wed, 14 Dec 2011 15:34:37 -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-06.txt
	Pages           : 20
	Date            : 2011-12-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-06.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-06.txt


From fgont@si6networks.com  Thu Dec 15 05:04:49 2011
Return-Path: <fgont@si6networks.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 0605121F84AD for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 05:04: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 azxp-qlTCAGl for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 05:04:48 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id B155221F8487 for <ipv6@ietf.org>; Thu, 15 Dec 2011 05:04:48 -0800 (PST)
Received: from [2001:5c0:1000:a::15] by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RbAzO-0005vx-DW; Thu, 15 Dec 2011 14:04:47 +0100
Message-ID: <4EE9F068.70002@si6networks.com>
Date: Thu, 15 Dec 2011 10:04:40 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: New IETF I-D on "Stable Privacy Addresses"
X-Enigmail-Version: 1.1.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: Thu, 15 Dec 2011 13:10:35 -0000

Folks,

We've just published a new IETF I-D entitled "A method for Generating
Stable Privacy-Enhanced Addresses with IPv6 Stateless Address
Autoconfiguration (SLAAC)".

The abstract of the I-D is:
---- cut here ----
   This document specifies a method for generating IPv6 Interface
   Identifiers to be used with IPv6 Stateless Address Autoconfiguration
   (SLAAC), such that addresses configured using this method are stable
   within each subnet, but the Interface Identifier changes when hosts
   move from one network to another.  The aforementioned method is meant
   to be an alternative to generating Interface Identifiers based on
   IEEE identifiers, such that the same manageability benefits can be
   achieved without sacrificing the privacy of users.
---- cut here ----

The aforementioned I-D is available at:
<http://tools.ietf.org/id/draft-gont-6man-stable-privacy-addresses-00.txt>.

Any feedback will be really appreciated.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From fgont@si6networks.com  Thu Dec 15 06:25:15 2011
Return-Path: <fgont@si6networks.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 A539421F86A1 for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 06:25:15 -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 SPKHcZsG8sF2 for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 06:25:15 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id B95B121F8678 for <ipv6@ietf.org>; Thu, 15 Dec 2011 06:25:14 -0800 (PST)
Received: from [2001:5c0:1400:a::1f3] by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RbCFE-0006TT-Ck; Thu, 15 Dec 2011 15:25:13 +0100
Message-ID: <4EEA0342.2040608@si6networks.com>
Date: Thu, 15 Dec 2011 11:25:06 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Fragmentation-related security issues
X-Enigmail-Version: 1.1.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: Thu, 15 Dec 2011 14:25:15 -0000

Folks,

We have published two new IETF I-Ds about fragmentation related security
issues.

The first I-D is entitled "Security Implications of Predictable Fragment
Identification Values"
(http://tools.ietf.org/id/draft-gont-6man-predictable-fragment-id-00.txt).
Its abstract is:

---- cut here ----
   IPv6 specifies the Fragment Header, which is employed for the
   fragmentation and reassembly mechanisms.  The Fragment Header
   contains an "Identification" field which, together with the IPv6
   Source Address and the IPv6 Destination Address of the packet,
   identifies fragments that correspond to the same original datagram,
   such that they can be reassembled together at the receiving host.
   The only requirement for setting the "Identification" value is that
   it must be different than that of any other fragmented packet sent
   recently with the same Source Address and Destination Address.  Some
   implementations simply use a global counter for setting the Fragment
   Identification field, thus leading to predictable values.  This
   document analyzes the security implications of predictable
   Identification values, and updates RFC 2460 specifying additional
   requirements for setting the Fragment Identification, such that the
   aforementioned security implications are mitigated.
---- cut here ----


The second I-D is entitled 'Processing of IPv6 "atomic" fragments'
(http://tools.ietf.org/id/draft-gont-6man-ipv6-atomic-fragments-00.txt).
Its abstract is:

---- cut here ----
   IPv6 allows packets to contain a Fragment Header, without the packet
   being actually fragmented into multiple pieces.  Such packets
   typically result from hosts that have received an ICMPv6 "Packet Too
   Big" error message that advertises a "Next-Hop MTU" smaller than 1280
   bytes, and are currently processed by hosts as "fragmented traffic".
   By forging ICMPv6 "Packet Too Big" error messages an attacker can
   cause hosts to employ "atomic fragments", and the launch any
   fragmentation-based attacks against such traffic.  This document
   discusses the generation of the aforementioned "atomic fragments",
   the corresponding security implications, and formally updates RFC
   2460 and RFC 5722 such that the attack vector based on "atomic
   fragments" is completely eliminated.
---- cut here ----

Any feedback will be very appreciated.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From cgrundemann@gmail.com  Thu Dec 15 08:37:45 2011
Return-Path: <cgrundemann@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 405EF21F86B3 for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 08:37:45 -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 etqDeGwTca-b for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 08:37:44 -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 63C1521F8669 for <ipv6@ietf.org>; Thu, 15 Dec 2011 08:37:42 -0800 (PST)
Received: by wgbdr13 with SMTP id dr13so3351028wgb.13 for <ipv6@ietf.org>; Thu, 15 Dec 2011 08:37:41 -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=W7BQcfObf7XOrB5troOsLzK1PI3V6MzFZtM9j/l8O+0=; b=UcFizRIc856CfYMapMlrCVZdEAj3LUmiZ9MTdR9hj82Hx9k02BpXRfqxG8M669dQlJ Fih7byVfFdXeS623Ba8B0N7cXcluTmF+tPJf/35TsX1NVBgkEJkY6IaJPWSd3LIQVYin IarJBtVmDW9GHqd5vitf596Tcno3cwad+vlOs=
MIME-Version: 1.0
Received: by 10.227.197.10 with SMTP id ei10mr2933054wbb.11.1323967059949; Thu, 15 Dec 2011 08:37:39 -0800 (PST)
Received: by 10.180.93.226 with HTTP; Thu, 15 Dec 2011 08:37:39 -0800 (PST)
In-Reply-To: <4EB3F3D6.4090302@innovationslab.net>
References: <4EB3F3D6.4090302@innovationslab.net>
Date: Thu, 15 Dec 2011 09:37:39 -0700
Message-ID: <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
From: Chris Grundemann <cgrundemann@gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Bob Hinden <bob.hinden@gmail.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, 15 Dec 2011 16:37:45 -0000

Hello and apologies to the list if this is redundant, but what is the
current status of this I-D?

I note that the status page[1] was not updated to reflect this last
call and I do not see any further updates or mention of an -06 or an
IETF last call. Perhaps the authors are working on this off-line?

I am interested in seeing this work completed and am willing to help if nee=
ded.

Thanks!
~Chris

[1] - https://datatracker.ietf.org/doc/draft-ietf-6man-rfc3484-revise/histo=
ry/


On Fri, Nov 4, 2011 at 08:16, Brian Haberman <brian@innovationslab.net> wro=
te:
> All,
> =A0 =A0 This message starts a two week 6MAN Working Group on advancing:
>
> =A0 =A0 Title =A0 =A0 : Update to RFC 3484 Default Address Selection for =
IPv6
> =A0 =A0 Author(s) : Arifumi Matsumoto
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Jun-ya Kato
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Tomohiro Fujisaki
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Tim Chown
> =A0 =A0 Filename =A0: draft-ietf-6man-rfc3484-revise-05.txt
> =A0 =A0 Pages =A0 =A0 : 12
> =A0 =A0 Date =A0 =A0 =A0: 2011-10-31
>
> as a Proposed Standard. =A0Substantive comments and statements of support
> for advancing this document should be directed to the mailing list.
> Editorial suggestions can be sent to the authors. =A0This last call will
> end on November 18, 2011.
>
> Regards,
> Brian Haberman & Bob Hinden
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



--=20
@ChrisGrundemann
weblog.chrisgrundemann.com
www.burningwiththebush.com
www.theIPv6experts.net
www.coisoc.org

From brian@innovationslab.net  Thu Dec 15 10:32: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 25CBB21F8B0E for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 10:32: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 CuoIyzn-sLad for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 10:32:03 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8546821F8B0D for <ipv6@ietf.org>; Thu, 15 Dec 2011 10:32: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 CE0E688277; Thu, 15 Dec 2011 10:32: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 5B0871368104; Thu, 15 Dec 2011 10:32:02 -0800 (PST)
Message-ID: <4EEA3D20.7020603@innovationslab.net>
Date: Thu, 15 Dec 2011 13:32:00 -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: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com>
In-Reply-To: <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com>
X-Enigmail-Version: 1.3.4
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: Thu, 15 Dec 2011 18:32:04 -0000

Hi Chris,
     Unfortunately, the draft is in a limbo state at this point.  The WG
Last Call ended about a month ago with zero comments or statements of
support.  The chairs cannot advance this document without some show of
support by the community.

     I humbly request that members of the working group review this
draft and post their comments, questions, and suggestions to the mailing
list.

Regards,
Brian

On 12/15/11 11:37 AM, Chris Grundemann wrote:
> Hello and apologies to the list if this is redundant, but what is the
> current status of this I-D?
> 
> I note that the status page[1] was not updated to reflect this last
> call and I do not see any further updates or mention of an -06 or an
> IETF last call. Perhaps the authors are working on this off-line?
> 
> I am interested in seeing this work completed and am willing to help if needed.
> 
> Thanks!
> ~Chris
> 
> [1] - https://datatracker.ietf.org/doc/draft-ietf-6man-rfc3484-revise/history/
> 
> 
> On Fri, Nov 4, 2011 at 08:16, Brian Haberman <brian@innovationslab.net> wrote:
>> 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
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> 
> 


From rogerj@gmail.com  Thu Dec 15 11:07:40 2011
Return-Path: <rogerj@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 F041821F8AF0 for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 11:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 C+H6E6hFlrAU for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 11:07:40 -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 3B9BD21F8AF9 for <ipv6@ietf.org>; Thu, 15 Dec 2011 11:07:40 -0800 (PST)
Received: by eaad1 with SMTP id d1so2510165eaa.31 for <ipv6@ietf.org>; Thu, 15 Dec 2011 11:07:39 -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=bjbcaHnbvYuG0lYlWuT7vFfZwtgwo0nuX7oSwV/ZF/0=; b=ZCa1vMimdJG6nKl9QqrDeEr1Qypv2Fp5sWG7Kwzv1PRiZxio6Wg7B5lgHK7EdqjU2u DQ3Xl0MedrrF2+B8BGEihPqXtuXZxXo3UQG0Pr+R5zSwTLsVo/3XM/y6b/x4oTcWNyTb GUYMB+0N7Zn4LKM2N9to91OOB1LNqyim4axpU=
MIME-Version: 1.0
Received: by 10.204.152.140 with SMTP id g12mr2072777bkw.98.1323976059344; Thu, 15 Dec 2011 11:07:39 -0800 (PST)
Received: by 10.204.70.17 with HTTP; Thu, 15 Dec 2011 11:07:39 -0800 (PST)
In-Reply-To: <4EEA3D20.7020603@innovationslab.net>
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net>
Date: Thu, 15 Dec 2011 20:07:39 +0100
Message-ID: <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/alternative; boundary=0015175cfec8b556e404b42632c6
Cc: 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, 15 Dec 2011 19:07:41 -0000

--0015175cfec8b556e404b42632c6
Content-Type: text/plain; charset=ISO-8859-1

On Dec 15, 2011 7:32 PM, "Brian Haberman" <brian@innovationslab.net> wrote:
>
> Hi Chris,
>     Unfortunately, the draft is in a limbo state at this point.  The WG
> Last Call ended about a month ago with zero comments or statements of
> support.  The chairs cannot advance this document without some show of
> support by the community.
>
>     I humbly request that members of the working group review this
> draft and post their comments, questions, and suggestions to the mailing
> list.

Brian Carpenter said it all in this post:

Message-ID: <4EB9D332.1040003@gmail.com>
Date: Wed, 09 Nov 2011 14:11:14 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>

<snip>
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.
</snip>

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

<p><br>
On Dec 15, 2011 7:32 PM, &quot;Brian Haberman&quot; &lt;<a href=3D"mailto:b=
rian@innovationslab.net" target=3D"_blank">brian@innovationslab.net</a>&gt;=
 wrote:<br>
&gt;<br>
&gt; Hi Chris,<br>
&gt; =A0 =A0 Unfortunately, the draft is in a limbo state at this point. =
=A0The WG<br>
&gt; Last Call ended about a month ago with zero comments or statements of<=
br>
&gt; support. =A0The chairs cannot advance this document without some show =
of<br>
&gt; support by the community.<br>
&gt;<br>
&gt; =A0 =A0 I humbly request that members of the working group review this=
<br>
&gt; draft and post their comments, questions, and suggestions to the maili=
ng<br>
&gt; list.<br>
 </p><pre>Brian Carpenter said it all in this post:<br><br>Message-ID: &lt;=
<a href=3D"mailto:4EB9D332.1040003@gmail.com">4EB9D332.1040003@gmail.com</a=
>&gt;
Date: Wed, 09 Nov 2011 14:11:14 +1300
From: Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">=
brian.e.carpenter@gmail.com</a>&gt;<br><br>&lt;snip&gt;<br>Reading this doc=
ument as a proposed standard, I think it will confuse <br>the reader. I thi=
nk that what we actually need is a 100% replacement <br>
of RFC 3484, that can be read on its own.<br>&lt;/snip&gt;<br><br><br><br><=
br></pre>

--0015175cfec8b556e404b42632c6--

From brian@innovationslab.net  Thu Dec 15 12:21: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 01EF511E809D for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 12:21:50 -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=[AWL=0.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 QESqjOkMjPuz for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 12:21:49 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6EEEB11E809C for <ipv6@ietf.org>; Thu, 15 Dec 2011 12:21: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 2813588253 for <ipv6@ietf.org>; Thu, 15 Dec 2011 12:21: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 DD70B136812B for <ipv6@ietf.org>; Thu, 15 Dec 2011 12:21:48 -0800 (PST)
Message-ID: <4EEA56DB.6000906@innovationslab.net>
Date: Thu, 15 Dec 2011 15:21: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: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com>
In-Reply-To: <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com>
X-Enigmail-Version: 1.3.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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, 15 Dec 2011 20:21:50 -0000

On 12/15/11 2:07 PM, Roger Jørgensen wrote:
> On Dec 15, 2011 7:32 PM, "Brian Haberman" <brian@innovationslab.net> wrote:
>>
>> Hi Chris,
>>     Unfortunately, the draft is in a limbo state at this point.  The WG
>> Last Call ended about a month ago with zero comments or statements of
>> support.  The chairs cannot advance this document without some show of
>> support by the community.
>>
>>     I humbly request that members of the working group review this
>> draft and post their comments, questions, and suggestions to the mailing
>> list.
> 
> Brian Carpenter said it all in this post:
> 
> Message-ID: <4EB9D332.1040003@gmail.com>
> Date: Wed, 09 Nov 2011 14:11:14 +1300
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> 
> <snip>
> 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.
> </snip>
> 

Ah, you are correct.  That message ended up in the wrong mailbox and I
missed it when reviewing the state of the draft in response to Chris' query.

Thanks, Roger.

Brian

From brian.e.carpenter@gmail.com  Thu Dec 15 12:24: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 6F9DD11E80A4 for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 12:24:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.421
X-Spam-Level: 
X-Spam-Status: No, score=-103.421 tagged_above=-999 required=5 tests=[AWL=-0.122, 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 DpLZ0RWttIZv for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 12:24:58 -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 AA1C011E809A for <ipv6@ietf.org>; Thu, 15 Dec 2011 12:24:57 -0800 (PST)
Received: by eaad1 with SMTP id d1so2593262eaa.31 for <ipv6@ietf.org>; Thu, 15 Dec 2011 12:24:56 -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=7HcvkdQE3Mvfl5VjH4T9pnE4vI1Rjs4w1XQYQn+OXEc=; b=iFXzw/c9nwwuPrYjF5zzWGrhfXEUllXTXAug7jjoP7c8JGCmL7fhoVWCEfFnkIwcZX VKLF1z3hlJ1id8XUM08dSJJqSahzC5nIX5i4zZomOqiPhj2XxtAxiK8/AhWKR1XF+vg9 IC6P7KxmYSGwiGRw4cIi6vwxNRLj5TdsKzXbA=
Received: by 10.205.130.5 with SMTP id hk5mr2231481bkc.74.1323980696829; Thu, 15 Dec 2011 12:24:56 -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 z7sm17693133bka.1.2011.12.15.12.24.53 (version=SSLv3 cipher=OTHER); Thu, 15 Dec 2011 12:24:56 -0800 (PST)
Message-ID: <4EEA5793.8080800@gmail.com>
Date: Fri, 16 Dec 2011 09:24:51 +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?Um9nZXIgSsO4cmdlbnNlbg==?= <rogerj@gmail.com>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
References: <4EB3F3D6.4090302@innovationslab.net>	<CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com>	<4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com>
In-Reply-To: <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, 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, 15 Dec 2011 20:24:58 -0000

Well, the end of my conversation is at

http://www.ietf.org/mail-archive/web/ipv6/current/msg14948.html

Summary: "an update that makes it easy for the implementer to find the ch=
anges is better."

If it wasn't clear, I believe this document is technically done and needs=

to be advanced, but it does need editorial work as indicated above.

Also there was Dave's review:

http://www.ietf.org/mail-archive/web/ipv6/current/msg14984.html

In IESG parlance that all seems like "new I-D needed" to me.

Regards
   Brian Carpenter


On 2011-12-16 08:07, Roger J=C3=B8rgensen wrote:
> On Dec 15, 2011 7:32 PM, "Brian Haberman" <brian@innovationslab.net> wr=
ote:
>> Hi Chris,
>>     Unfortunately, the draft is in a limbo state at this point.  The W=
G
>> Last Call ended about a month ago with zero comments or statements of
>> support.  The chairs cannot advance this document without some show of=

>> support by the community.
>>
>>     I humbly request that members of the working group review this
>> draft and post their comments, questions, and suggestions to the maili=
ng
>> list.
>=20
> Brian Carpenter said it all in this post:
>=20
> Message-ID: <4EB9D332.1040003@gmail.com>
> Date: Wed, 09 Nov 2011 14:11:14 +1300
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>=20
> <snip>
> 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.
> </snip>
>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From rogerj@gmail.com  Thu Dec 15 13:52:12 2011
Return-Path: <rogerj@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 06BFD11E8096 for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 13:52:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=0.100,  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 D4DrMsiM4o6J for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 13:52:11 -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 D393411E8089 for <ipv6@ietf.org>; Thu, 15 Dec 2011 13:52:10 -0800 (PST)
Received: by eaad1 with SMTP id d1so2665283eaa.31 for <ipv6@ietf.org>; Thu, 15 Dec 2011 13:52:10 -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=xHjKsuK8hQDsQWyVCm+25G64aeaYCvpYsRgHtd9uQt4=; b=hJWuWlCS1lV1Gi81HGGVt//oCD0RdWZ3yM5725dYPB0koAyVjUTlKkg11fwRmh+Eqe UkpHNozPwOchDaUsVlPFIJGTtNEAS8iaPge8FrtkGx7PGTPZMckgyBo8YfxuDBIg108r JYEsrBbK4HmBRekFwDBBoebWn+udRpK4ysOtc=
MIME-Version: 1.0
Received: by 10.204.9.218 with SMTP id m26mr2386307bkm.44.1323985929640; Thu, 15 Dec 2011 13:52:09 -0800 (PST)
Received: by 10.204.70.17 with HTTP; Thu, 15 Dec 2011 13:52:09 -0800 (PST)
In-Reply-To: <4EEA5793.8080800@gmail.com>
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com> <4EEA5793.8080800@gmail.com>
Date: Thu, 15 Dec 2011 22:52:09 +0100
Message-ID: <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, 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, 15 Dec 2011 21:52:12 -0000

On Thu, Dec 15, 2011 at 9:24 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Well, the end of my conversation is at
>
> http://www.ietf.org/mail-archive/web/ipv6/current/msg14948.html
>
> Summary: "an update that makes it easy for the implementer to find the ch=
anges is better."
>
> If it wasn't clear, I believe this document is technically done and needs
> to be advanced, but it does need editorial work as indicated above.

Hmm sorry for being unclear, the technical part looked okay as far as
I could tell, but as the quoted words from you, it will probably be
more confusing to have two documents where the last one update/change
the first one. Would be much better to have just one
replacing/updating the old one.



--- Roger J ---

>
> Also there was Dave's review:
>
> http://www.ietf.org/mail-archive/web/ipv6/current/msg14984.html
>
> In IESG parlance that all seems like "new I-D needed" to me.
>
> Regards
> =A0 Brian Carpenter
>
>
> On 2011-12-16 08:07, Roger J=F8rgensen wrote:
>> On Dec 15, 2011 7:32 PM, "Brian Haberman" <brian@innovationslab.net> wro=
te:
>>> Hi Chris,
>>> =A0 =A0 Unfortunately, the draft is in a limbo state at this point. =A0=
The WG
>>> Last Call ended about a month ago with zero comments or statements of
>>> support. =A0The chairs cannot advance this document without some show o=
f
>>> support by the community.
>>>
>>> =A0 =A0 I humbly request that members of the working group review this
>>> draft and post their comments, questions, and suggestions to the mailin=
g
>>> list.
>>
>> Brian Carpenter said it all in this post:
>>
>> Message-ID: <4EB9D332.1040003@gmail.com>
>> Date: Wed, 09 Nov 2011 14:11:14 +1300
>> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>>
>> <snip>
>> 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.
>> </snip>
>>
>>
>> ------------------------------------------------------------------------
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From brian.e.carpenter@gmail.com  Thu Dec 15 14:56:01 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 3EEE221F84C5 for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 14:56:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.419
X-Spam-Level: 
X-Spam-Status: No, score=-103.419 tagged_above=-999 required=5 tests=[AWL=-0.120, 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 RvGmRicmGYeT for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 14:56:00 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 385D821F84C2 for <ipv6@ietf.org>; Thu, 15 Dec 2011 14:56:00 -0800 (PST)
Received: by werb14 with SMTP id b14so230580wer.31 for <ipv6@ietf.org>; Thu, 15 Dec 2011 14:55: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=xenkIbGSxBE40p1BgP75CNAbTcbuMaaniYkhHefZOCk=; b=fPIkMQDLH+d50/77Fvd57juNhCWHUDrj7LqXGSSRF6uYFQswtcA8oBtiUjma71STPw 7sFqD42SNRbD2Lr8PwiwpHjGH0HesnnC6OMmHUl8thYQ8LNErPT+4cF596jEY+Mg9tDy hAG5oijde0aSjGY81YV53nAceVCte9iGc/H4E=
Received: by 10.216.137.28 with SMTP id x28mr2352537wei.0.1323989758187; Thu, 15 Dec 2011 14:55: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 bl10sm10490809wib.15.2011.12.15.14.55.55 (version=SSLv3 cipher=OTHER); Thu, 15 Dec 2011 14:55:57 -0800 (PST)
Message-ID: <4EEA7AF8.2090508@gmail.com>
Date: Fri, 16 Dec 2011 11:55:52 +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?Um9nZXIgSsO4cmdlbnNlbg==?= <rogerj@gmail.com>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
References: <4EB3F3D6.4090302@innovationslab.net>	<CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com>	<4EEA3D20.7020603@innovationslab.net>	<CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com>	<4EEA5793.8080800@gmail.com> <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com>
In-Reply-To: <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, 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, 15 Dec 2011 22:56:01 -0000

Roger,

On 2011-12-16 10:52, Roger J=C3=B8rgensen wrote:
> On Thu, Dec 15, 2011 at 9:24 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> Well, the end of my conversation is at
>>
>> http://www.ietf.org/mail-archive/web/ipv6/current/msg14948.html
>>
>> Summary: "an update that makes it easy for the implementer to find the=
 changes is better."
>>
>> If it wasn't clear, I believe this document is technically done and ne=
eds
>> to be advanced, but it does need editorial work as indicated above.
>=20
> Hmm sorry for being unclear, the technical part looked okay as far as
> I could tell, but as the quoted words from you, it will probably be
> more confusing to have two documents where the last one update/change
> the first one. Would be much better to have just one
> replacing/updating the old one.

That was my first thought, but then I realised it would cause a lot
of delay, and I think getting these changes deployed is quite urgent.

    Brian

>=20
> --- Roger J ---
>=20
>> Also there was Dave's review:
>>
>> http://www.ietf.org/mail-archive/web/ipv6/current/msg14984.html
>>
>> In IESG parlance that all seems like "new I-D needed" to me.
>>
>> Regards
>>   Brian Carpenter
>>
>>
>> On 2011-12-16 08:07, Roger J=C3=B8rgensen wrote:
>>> On Dec 15, 2011 7:32 PM, "Brian Haberman" <brian@innovationslab.net> =
wrote:
>>>> Hi Chris,
>>>>     Unfortunately, the draft is in a limbo state at this point.  The=
 WG
>>>> Last Call ended about a month ago with zero comments or statements o=
f
>>>> support.  The chairs cannot advance this document without some show =
of
>>>> support by the community.
>>>>
>>>>     I humbly request that members of the working group review this
>>>> draft and post their comments, questions, and suggestions to the mai=
ling
>>>> list.
>>> Brian Carpenter said it all in this post:
>>>
>>> Message-ID: <4EB9D332.1040003@gmail.com>
>>> Date: Wed, 09 Nov 2011 14:11:14 +1300
>>> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>>>
>>> <snip>
>>> 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.
>>> </snip>
>>>
>>>
>>> ---------------------------------------------------------------------=
---
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>=20
>=20
>=20


From cgrundemann@gmail.com  Thu Dec 15 15:16:59 2011
Return-Path: <cgrundemann@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 27BF421F852E for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 15:16:59 -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 U0Ml2amc-e+F for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 15:16:58 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0ED21F8532 for <ipv6@ietf.org>; Thu, 15 Dec 2011 15:16:58 -0800 (PST)
Received: by pbdd12 with SMTP id d12so1929633pbd.31 for <ipv6@ietf.org>; Thu, 15 Dec 2011 15:16:58 -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=6PIbs4AkVGhsx7F9L3EcT24GZpzAlbarw8kwop8SfIg=; b=LUsJ3TlbKWpAXT1NhOgw+dvAbQ30oDSrG2YGUgcl0Ph/oHpB3L63Us/NAGSMgdQGf7 4mCkQWvidcQMihCABcH0hInVv/cyk3MKdhtRYdpiqgoYcJAsBHPT7fuZ3/+GesvOLxCj //woxukfJ1M1VDhixCZyqOtV+g3bRGK9ZrfjI=
MIME-Version: 1.0
Received: by 10.68.196.169 with SMTP id in9mr3095499pbc.54.1323991017130; Thu, 15 Dec 2011 15:16:57 -0800 (PST)
Received: by 10.143.157.12 with HTTP; Thu, 15 Dec 2011 15:16:57 -0800 (PST)
In-Reply-To: <4EEA7AF8.2090508@gmail.com>
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com> <4EEA5793.8080800@gmail.com> <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com> <4EEA7AF8.2090508@gmail.com>
Date: Thu, 15 Dec 2011 16:16:57 -0700
Message-ID: <CAC1-dtn9M8-9cPAmkhCiGV0Gi5+Gfs8GAssTOaA-ZFhyUY3feg@mail.gmail.com>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
From: Chris Grundemann <cgrundemann@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.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: Thu, 15 Dec 2011 23:16:59 -0000

On Thu, Dec 15, 2011 at 15:55, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Roger,
>
> On 2011-12-16 10:52, Roger J=F8rgensen wrote:
>> On Thu, Dec 15, 2011 at 9:24 PM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>>> Well, the end of my conversation is at
>>>
>>> http://www.ietf.org/mail-archive/web/ipv6/current/msg14948.html
>>>
>>> Summary: "an update that makes it easy for the implementer to find the =
changes is better."
>>>
>>> If it wasn't clear, I believe this document is technically done and nee=
ds
>>> to be advanced, but it does need editorial work as indicated above.
>>
>> Hmm sorry for being unclear, the technical part looked okay as far as
>> I could tell, but as the quoted words from you, it will probably be
>> more confusing to have two documents where the last one update/change
>> the first one. Would be much better to have just one
>> replacing/updating the old one.
>
> That was my first thought, but then I realised it would cause a lot
> of delay, and I think getting these changes deployed is quite urgent.

I must agree, there is certainly an urgent need to fix the problems in
the current RFC 3484, particularly around the handling of ULAs, etc.
For one example; I am currently working on sorting out proper IPv6
support in UPnP and DLNA (targeting CE) and we have (effectively)
nothing to point to for dynamic source address selection procedures.
Since there appears to be consensus on the technical changes, is there
a way to make the needed editorial changes and then advance to IETF
last call (or a second WG last call at least)?

~Chris

>
> =A0 =A0Brian
<snip>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



--=20
@ChrisGrundemann
weblog.chrisgrundemann.com
www.burningwiththebush.com
www.theIPv6experts.net
www.coisoc.org

From marka@isc.org  Thu Dec 15 17:20:05 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 917731F0C51 for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 17:20:05 -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 vzG-VX4JZe4o for <ipv6@ietfa.amsl.com>; Thu, 15 Dec 2011 17:20: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 D7C8F1F0C4E for <ipv6@ietf.org>; Thu, 15 Dec 2011 17:20: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 2B92B5F98AF; Fri, 16 Dec 2011 01:19:38 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:15ae:9e88:7399:51d1]) (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 13E5A216C6B; Fri, 16 Dec 2011 01:19:36 +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 C187E1A15E75; Fri, 16 Dec 2011 12:19:29 +1100 (EST)
To: Fernando Gont <fgont@si6networks.com>
From: Mark Andrews <marka@isc.org>
References: <4EEA0342.2040608@si6networks.com>
Subject: Re: Fragmentation-related security issues
In-reply-to: Your message of "Thu, 15 Dec 2011 11:25:06 -0300." <4EEA0342.2040608@si6networks.com>
Date: Fri, 16 Dec 2011 12:19:29 +1100
Message-Id: <20111216011929.C187E1A15E75@drugs.dv.isc.org>
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, 16 Dec 2011 01:20:05 -0000

When thinking about this draft please consider the following:

http://tools.ietf.org/html/draft-andrews-6man-force-fragmentation-00
http://tools.ietf.org/html/draft-andrews-dnsext-udp-fragmentation-00

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From internet-drafts@ietf.org  Thu Dec 15 20:56:28 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 0EEC41F0C72; Thu, 15 Dec 2011 20:56:28 -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=[AWL=0.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 dispdlafAmaI; Thu, 15 Dec 2011 20:56:27 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A121D1F0C35; Thu, 15 Dec 2011 20:56:27 -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-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111216045627.30023.10144.idtracker@ietfa.amsl.com>
Date: Thu, 15 Dec 2011 20:56:27 -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: Fri, 16 Dec 2011 04:56:28 -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-07.txt
	Pages           : 20
	Date            : 2011-12-15

   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-07.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-07.txt


From rogerj@gmail.com  Fri Dec 16 01:38:09 2011
Return-Path: <rogerj@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 DEA1621F8AE9 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 01:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.224
X-Spam-Level: 
X-Spam-Status: No, score=-3.224 tagged_above=-999 required=5 tests=[AWL=0.075,  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 IzM-7nuSI31j for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 01:38:08 -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 60A4521F8A96 for <ipv6@ietf.org>; Fri, 16 Dec 2011 01:38:08 -0800 (PST)
Received: by eaad1 with SMTP id d1so3079870eaa.31 for <ipv6@ietf.org>; Fri, 16 Dec 2011 01:38:07 -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=Jupg5eHx+sOEu3puxDuodZQ38Zq9Zf4Li3kBr1EuXuo=; b=Jzco0nNqbWg9F0J3pygzZ5cQLl6IJmu55rS0aJL3f6Bte5ZmP5B7eal37sd6748DIY JN1o5SpFhttRLhd08duTbmOaBCk6e2XEXwExhUqV5CGwIzy0yXszJWTroFzkS7ZRAf0L 73Fezd9mMMN5o7GInSzdnE65xAvzerOBy1ZHQ=
MIME-Version: 1.0
Received: by 10.204.145.74 with SMTP id c10mr2751337bkv.62.1324028287096; Fri, 16 Dec 2011 01:38:07 -0800 (PST)
Received: by 10.204.70.17 with HTTP; Fri, 16 Dec 2011 01:38:07 -0800 (PST)
In-Reply-To: <4EEA7AF8.2090508@gmail.com>
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com> <4EEA5793.8080800@gmail.com> <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com> <4EEA7AF8.2090508@gmail.com>
Date: Fri, 16 Dec 2011 10:38:07 +0100
Message-ID: <CAKFn1SFp_r7EJ6CpM8EF2zkcJz1z34CdEcRt2i5xcsrWkCBQwQ@mail.gmail.com>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, 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, 16 Dec 2011 09:38:10 -0000

On Thu, Dec 15, 2011 at 11:55 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Roger,
>
> On 2011-12-16 10:52, Roger J=F8rgensen wrote:
>> On Thu, Dec 15, 2011 at 9:24 PM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>>> Well, the end of my conversation is at
>>>
>>> http://www.ietf.org/mail-archive/web/ipv6/current/msg14948.html
>>>
>>> Summary: "an update that makes it easy for the implementer to find the =
changes is better."
>>>
>>> If it wasn't clear, I believe this document is technically done and nee=
ds
>>> to be advanced, but it does need editorial work as indicated above.
>>
>> Hmm sorry for being unclear, the technical part looked okay as far as
>> I could tell, but as the quoted words from you, it will probably be
>> more confusing to have two documents where the last one update/change
>> the first one. Would be much better to have just one
>> replacing/updating the old one.
>
> That was my first thought, but then I realised it would cause a lot
> of delay, and I think getting these changes deployed is quite urgent.

what about doing it in two step? First getting this one out since it fix
something quite broken, and then update the old RFC?



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From tjc@ecs.soton.ac.uk  Fri Dec 16 02:49:17 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 6CF4D21F8A96 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 02:49:17 -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 opaiZiuF98jn for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 02:49:16 -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 4159121F888A for <ipv6@ietf.org>; Fri, 16 Dec 2011 02:49:15 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id pBGAnBjp024852 for <ipv6@ietf.org>; Fri, 16 Dec 2011 10:49:11 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk pBGAnBjp024852
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1324032551; bh=jWwjPK+GFeN7Q3fHxteSqs7vxlM=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=DiiVNp+W1ABRH3zj2Eph3q0vEZGn30eHWCXDeAoRsg0Jej/HlfIpcBUxnq+ttGI3h S4tnXmlcDlTIaU+iUT9Zjl/5kRWqvo+oWR6c8iAiGaSgjRzU+EIbcmCynaLeMuPZZb lNtHi+CTrEnPjkGt3183AmNVYYh1TTPjeHFcSMeY=
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 nBFAnB05437387750q ret-id none; Fri, 16 Dec 2011 10:49:11 +0000
Received: from [IPv6:2001:630:d0:ed03:34fe:49bb:f2b4:c349] ([IPv6:2001:630:d0:ed03:34fe:49bb:f2b4:c349]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id pBGAn4uO021793 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Fri, 16 Dec 2011 10:49:08 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAKFn1SFp_r7EJ6CpM8EF2zkcJz1z34CdEcRt2i5xcsrWkCBQwQ@mail.gmail.com>
Date: Fri, 16 Dec 2011 10:49:05 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|bd681ced736eee0700e443f9acc256d8nBFAnB03tjc|ecs.soton.ac.uk|0D0150C3-9E05-4839-ACF1-0E7196420D2F@ecs.soton.ac.uk>
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com> <4EEA5793.8080800@gmail.com> <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com> <4EEA7AF8.2090508@gmail.com> <CAKFn1SFp_r7EJ6CpM8EF2zkcJz1z34CdEcRt2i5xcsrWkCBQwQ@mail.gmail.com> <0D0150C3-9E05-4839-ACF1-0E7196420D2F@ecs.soton.ac.uk>
To: 6man Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=nBFAnB054373877500; tid=nBFAnB05437387750q; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: pBGAnBjp024852
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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, 16 Dec 2011 10:49:17 -0000

Well, there are two questions here.

One is whether the WG believes the update as described in =
draft-ietf-6man-rfc3484-revise-05 is correct and complete.  I have not =
seen (yet) any significant technical concerns raised.  The last of those =
were discussed and (we believe) resolved in Quebec.  Are there any more?

The other is whether the WG believes we should publish an update, or a =
complete fresh version of RFC3484.  This was discussed previously in the =
WG and the update path preferred.  If a fresh version is now deemed more =
appropriate, I am fine to work on that with the other authors if =
required.

We just need a decision so we can progress this - it's been so close to =
release for a long time.  Many of the changes in the update have been =
implemented in a number of platforms already.

Tim

On 16 Dec 2011, at 09:38, Roger J=F8rgensen wrote:

> On Thu, Dec 15, 2011 at 11:55 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> Roger,
>>=20
>> On 2011-12-16 10:52, Roger J=F8rgensen wrote:
>>> On Thu, Dec 15, 2011 at 9:24 PM, Brian E Carpenter
>>> <brian.e.carpenter@gmail.com> wrote:
>>>> Well, the end of my conversation is at
>>>>=20
>>>> http://www.ietf.org/mail-archive/web/ipv6/current/msg14948.html
>>>>=20
>>>> Summary: "an update that makes it easy for the implementer to find =
the changes is better."
>>>>=20
>>>> If it wasn't clear, I believe this document is technically done and =
needs
>>>> to be advanced, but it does need editorial work as indicated above.
>>>=20
>>> Hmm sorry for being unclear, the technical part looked okay as far =
as
>>> I could tell, but as the quoted words from you, it will probably be
>>> more confusing to have two documents where the last one =
update/change
>>> the first one. Would be much better to have just one
>>> replacing/updating the old one.
>>=20
>> That was my first thought, but then I realised it would cause a lot
>> of delay, and I think getting these changes deployed is quite urgent.
>=20
> what about doing it in two step? First getting this one out since it =
fix
> something quite broken, and then update the old RFC?
>=20
>=20
>=20
> --=20
>=20
> Roger Jorgensen           |
> rogerj@gmail.com          | - IPv6 is The Key!
> http://www.jorgensen.no   | roger@jorgensen.no
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From kpark@ti.com  Fri Dec 16 08:55:34 2011
Return-Path: <kpark@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 9894221F8B58 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 08:55:34 -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 zM22WMoqy1h3 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 08:55:33 -0800 (PST)
Received: from arroyo.ext.ti.com (arroyo.ext.ti.com [192.94.94.40]) by ietfa.amsl.com (Postfix) with ESMTP id B5F0221F8B57 for <ipv6@ietf.org>; Fri, 16 Dec 2011 08:55:33 -0800 (PST)
Received: from dlep26.itg.ti.com ([157.170.170.121]) by arroyo.ext.ti.com (8.13.7/8.13.7) with ESMTP id pBGGtWpL017100 for <ipv6@ietf.org>; Fri, 16 Dec 2011 10:55:33 -0600
Received: from DFLE70.ent.ti.com (localhost [127.0.0.1]) by dlep26.itg.ti.com (8.13.8/8.13.8) with ESMTP id pBGGtWp3011156 for <ipv6@ietf.org>; Fri, 16 Dec 2011 10:55:32 -0600 (CST)
Received: from DLEE10.ent.ti.com ([fe80::843:a4aa:bf01:3f68]) by DFLE70.ent.ti.com ([fe80::db3:609a:aa62:e1ec%22]) with mapi id 14.01.0323.003; Fri, 16 Dec 2011 10:55:33 -0600
From: "Park, Kundok" <kpark@ti.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: I-D Action: draft-ietf-6man-rpl-option-06.txt
Thread-Topic: I-D Action: draft-ietf-6man-rpl-option-06.txt
Thread-Index: AQHMunXknFy7hMAU3Uubz0qSChYYBJXeqvdA
Date: Fri, 16 Dec 2011 16:55:32 +0000
Message-ID: <055FAFECB2B53642884D29B0094D147510980815@DLEE10.ent.ti.com>
References: <20111214153427.3662.89188.idtracker@ietfa.amsl.com>
In-Reply-To: <20111214153427.3662.89188.idtracker@ietfa.amsl.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
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, 16 Dec 2011 16:55:34 -0000

Hi, Jonathan,

I have a question on the following text on version 6, on page 8.

"
   2.  Datagrams destined elsewhere within the same RPL Instance are
       forwarded to the correct interface.

   3.  Datagrams destined to nodes outside the RPL Instance are dropped
       if the outer-most IPv6 header contains a RPL Option not generated
       by the RPL router forwarding the datagram.
"

Can you clarify the meaning of the (same) RPL instance in the above text? I=
s it the RPL instance in the outer-most IPv6 header? For instance, if a RPL=
 packet is tunneled to a RPL router using another RPL instance and the reci=
pient RPL router is the exit point of the outer tunnel, must the router dis=
card such a packet whether the router joined the RPL instance of the inner =
packet or not?
To phrase it differently, can RPL be used in a virtual network over a netwo=
rk which happens to use another RPL instance as an underlying routing proto=
col?

Thank you.

BR,
Kundok Park
Texas Instruments

From fgont@si6networks.com  Fri Dec 16 11:59:38 2011
Return-Path: <fgont@si6networks.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 B0D6921F86A0 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 11:59:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, 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 LfE3vrkdwtpb for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 11:59:38 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 32DFF21F8678 for <ipv6@ietf.org>; Fri, 16 Dec 2011 11:59:37 -0800 (PST)
Received: from [2001:5c0:1000:a::2c3] by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RbdwK-0002Tw-Cc; Fri, 16 Dec 2011 20:59:32 +0100
Message-ID: <4EEB66D6.7070703@si6networks.com>
Date: Fri, 16 Dec 2011 12:42:14 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com> <20111216011929.C187E1A15E75@drugs.dv.isc.org>
In-Reply-To: <20111216011929.C187E1A15E75@drugs.dv.isc.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 16 Dec 2011 19:59:38 -0000

Hi, Mark,

On 12/15/2011 10:19 PM, Mark Andrews wrote:
> When thinking about this draft please consider the following:
> 
> http://tools.ietf.org/html/draft-andrews-6man-force-fragmentation-00
> http://tools.ietf.org/html/draft-andrews-dnsext-udp-fragmentation-00

I've just read both of them. The relationship I've found with these two
and the two I've authored is that your I-D's will lead to an increase of
IPv6 "atomic fragments". This means that:

*
<http://tools.ietf.org/id/draft-gont-6man-ipv6-atomic-fragments-00.txt>
is even more desirable, as it would completely mitigate
fragmentation-related attacks against DNS traffic that is not really
split into several packets (but still contains a Fragment Header.

* Implementation of
<http://tools.ietf.org/id/draft-gont-6man-predictable-fragment-id-00.txt> at
the sending node would help mitigate some fragmentation-related attacks
against receivers that do not yet implement the "atomic packets"
behaviour described above, or in scenarios in which DNS traffic is
really fragmented (i.e., packets are split into multiple pieces).

Does this agree with your assessment? Am I missing something?

P.S.: I'll be sending feedback about your I-Ds in separate e-mails.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From fgont@si6networks.com  Fri Dec 16 11:59:45 2011
Return-Path: <fgont@si6networks.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 136DB21F8AF4 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 11:59:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level: 
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, 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 G-TD5e-GjspR for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 11:59:44 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 499B321F8AF3 for <ipv6@ietf.org>; Fri, 16 Dec 2011 11:59:44 -0800 (PST)
Received: from [2001:5c0:1000:a::2c3] by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RbdwV-0002U3-8C; Fri, 16 Dec 2011 20:59:43 +0100
Message-ID: <4EEB70E7.1050700@si6networks.com>
Date: Fri, 16 Dec 2011 13:25:11 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Some feedback on draft-andrews-6man-force-fragmentation-00
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Mark Andrews <marka@isc.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, 16 Dec 2011 19:59:45 -0000

Mark,

Here's some feedback about the aforementioned I-D:

** Technical: **

Section 1:
>    In order to avoid PMTUD [RFC 1191] in IPv6 an application must not
>    only force packets to be fragmented at the network MTU it must also

s/network MTU/minimum IPv6 MTU/
(note that there are other instances of this throughout the document...
all should be fixed)


Section 1:
>    otherwise PTB ICMPv6 may be sent if the packet goes through a IPv6 to
>    IPv4 translating router [RFC 2460].

Are there any existing devices that exploit this feature? NAT64? Others?


Section 2:
> 2. Extend IPV6_USE_MIN_MTU
> 
> 
>    If IPV6_USE_MIN_MTU is set to 1 then a Fragment header MUST be added
>    to both multicast and unicast packets.
> 
>    If IPV6_USE_MIN_MTU is set to -1 then a Fragment header MUST be added
>    to multicast packets.

I might be missing something, but: the current semantics of the
IPV6_USE_MIN_MTU are that you force the *PMTU* to be 1280, rather than
force the *inclusion* of a fragment header.

Right now, if an app sets IPV6_USE_MIN_MTU, but the packet it sends
equal to or smaller than 1280, a fragment header would *not* be added.
However, with the new semantics you're specifying, it would.

Section 6:
At the risk of sounding my own horn,
draft-gont-6man-predictable-fragment-id may be your friend here.
Additionally, you may note that when a fragment header is included, but
the packet does not actually get fragmented into multiple pieces,
draft-gont-6man-ipv6-atomic-fragments eliminates the
fragmentation-related security issues.


** Editorial **

Abstract: Expand it mentioning at least some scenario where you'd need
this. (trivial: the DNS/UDP scenario).


Section 1:
>    There appears to be 3 viable alternatives. 1) extend IPV6_USE_MIN_MTU
>    to force the inclusion of a Fragment header. 2) extend IPV6_DONTFRAG
>    to signal that a Fragment header needs to be included. 3) add a new
>    socket option like IPV6_DOFRAG.

Have the document focus on only one of them (IMHO, option 3), and simply
put any discussion of "alternative approaches" in an appendix.



** Nits **

Section 1:
>    The Advanced Sockets API for IPv6 [RFC 3542] provides mechanisms to
>    force fragmentation of packet greater than the network MTU
>    (IPV6_USE_MIN_MTU).

s/of packet/of a packet/


Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From jonhui@cisco.com  Fri Dec 16 14:00:25 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 353D01F0C3F for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 14:00:25 -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 rav6FumMDCpa for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 14:00:24 -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 B1CAB1F0C38 for <ipv6@ietf.org>; Fri, 16 Dec 2011 14:00:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=1850; q=dns/txt; s=iport; t=1324072824; x=1325282424; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=/VNpRL2b42buzPPB9x7dPYu4V8v/McKqMb+zT8WsRyI=; b=jqdacqANIThxsNZY60nzcaFxruwSg0pnKAawUCXc1fkxW+Ch8fgIMANm uuoPk2c+ZY0LZn0T5oNwUj4fJOz5hH2OCyd4MtdJIXB32OoM3cbHtaPqi l9nqYkWE8B5Z7/asW80TFN+UVEv02ZNR+mt7CUt/rTu9hCY9qUBiCLbph 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EADu+606rRDoJ/2dsb2JhbABEq1WBBYFyAQEBAwEBAQEPASc0CwULC0YnMAYTIodYCJleAZ4pBIshYwSINIxCkk0
X-IronPort-AV: E=Sophos;i="4.71,365,1320624000"; d="scan'208";a="19476680"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 16 Dec 2011 22:00:24 +0000
Received: from sjc-vpn6-1768.cisco.com (sjc-vpn6-1768.cisco.com [10.21.126.232]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pBGM0NsN003119; Fri, 16 Dec 2011 22:00:23 GMT
Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <055FAFECB2B53642884D29B0094D147510980815@DLEE10.ent.ti.com>
Date: Fri, 16 Dec 2011 14:00:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A4603CA-2BCE-4029-A82E-6169C065D224@cisco.com>
References: <20111214153427.3662.89188.idtracker@ietfa.amsl.com> <055FAFECB2B53642884D29B0094D147510980815@DLEE10.ent.ti.com>
To: "Park, Kundok" <kpark@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: Fri, 16 Dec 2011 22:00:25 -0000

Hi Kundok,

If the RPL router is serves as the tunnel-exit, it falls into case 1 and =
removes the outer-most header in the usual way.  If the IPv6 header =
after decapsulation includes another RPL Option, the router uses the RPL =
Instance of that RPL Option and evaluates the forwarding rules again =
(this time applying case 2 or 3).  RPL can support a hierarchy of RPL =
routing topologies.

Does that help?

--
Jonathan Hui

On Dec 16, 2011, at 8:55 AM, Park, Kundok wrote:

> Hi, Jonathan,
>=20
> I have a question on the following text on version 6, on page 8.
>=20
> "
>   2.  Datagrams destined elsewhere within the same RPL Instance are
>       forwarded to the correct interface.
>=20
>   3.  Datagrams destined to nodes outside the RPL Instance are dropped
>       if the outer-most IPv6 header contains a RPL Option not =
generated
>       by the RPL router forwarding the datagram.
> "
>=20
> Can you clarify the meaning of the (same) RPL instance in the above =
text? Is it the RPL instance in the outer-most IPv6 header? For =
instance, if a RPL packet is tunneled to a RPL router using another RPL =
instance and the recipient RPL router is the exit point of the outer =
tunnel, must the router discard such a packet whether the router joined =
the RPL instance of the inner packet or not?
> To phrase it differently, can RPL be used in a virtual network over a =
network which happens to use another RPL instance as an underlying =
routing protocol?
>=20
> Thank you.
>=20
> BR,
> Kundok Park
> Texas Instruments
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From kpark@ti.com  Fri Dec 16 15:21:29 2011
Return-Path: <kpark@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 713EE11E8073 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 15:21:29 -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 6Z4tWV9i3ug5 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 15:21:28 -0800 (PST)
Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by ietfa.amsl.com (Postfix) with ESMTP id A29E821F8500 for <ipv6@ietf.org>; Fri, 16 Dec 2011 15:21:28 -0800 (PST)
Received: from dlep26.itg.ti.com ([157.170.170.121]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id pBGNLPb4018638; Fri, 16 Dec 2011 17:21:27 -0600
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 pBGNLPuo010392; Fri, 16 Dec 2011 17:21:25 -0600 (CST)
Received: from DLEE10.ent.ti.com ([fe80::843:a4aa:bf01:3f68]) by DLEE74.ent.ti.com ([fe80::a0f1:125b:e7e3:7ed8%18]) with mapi id 14.01.0323.003; Fri, 16 Dec 2011 17:21:25 -0600
From: "Park, Kundok" <kpark@ti.com>
To: Jonathan Hui <jonhui@cisco.com>
Subject: RE: I-D Action: draft-ietf-6man-rpl-option-06.txt
Thread-Topic: I-D Action: draft-ietf-6man-rpl-option-06.txt
Thread-Index: AQHMunXknFy7hMAU3Uubz0qSChYYBJXeqvdAgADA74D//5v7cA==
Date: Fri, 16 Dec 2011 23:21:25 +0000
Message-ID: <055FAFECB2B53642884D29B0094D14751098086E@DLEE10.ent.ti.com>
References: <20111214153427.3662.89188.idtracker@ietfa.amsl.com> <055FAFECB2B53642884D29B0094D147510980815@DLEE10.ent.ti.com> <7A4603CA-2BCE-4029-A82E-6169C065D224@cisco.com>
In-Reply-To: <7A4603CA-2BCE-4029-A82E-6169C065D224@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, 16 Dec 2011 23:21:29 -0000

Hi, Jonathan,

Thanks for your quick reply.

Unfortunately I am still a bit confused.

Based on your reply, I guess that the case 1 is meant only for the case of =
tunnel exit-point being the final RPL router along a path, when the tunnel =
is used.

The same RPL instance mentioned in case 2 perhaps means the RPL instance in=
 the outer header when a tunnel is used and when the RPL router is not the =
final RPL router along a path, and does the case 2 also apply to a case whe=
re RPL router is the final RPL router along a path?

Does the case 3 only apply to the RPL router being the final RPL router alo=
ng a path when tunnel is used but not to the RPL router not being the final=
 router along a path? If the answer is yes, by the outer-most IPv6 header, =
did you mean the outer-most IPv6 header of the inner packet and does RPL In=
stance in this context mean any RPL instance that the RPL router joined?

I'd appreciate if you can clarify furthermore.

BR,
Kundok

> -----Original Message-----
> From: Jonathan Hui [mailto:jonhui@cisco.com]
> Sent: Friday, December 16, 2011 2:00 PM
> To: Park, Kundok
> Cc: ipv6@ietf.org
> Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
>=20
>=20
> Hi Kundok,
>=20
> If the RPL router is serves as the tunnel-exit, it falls into case 1 and
> removes the outer-most header in the usual way.  If the IPv6 header after
> decapsulation includes another RPL Option, the router uses the RPL
> Instance of that RPL Option and evaluates the forwarding rules again (thi=
s
> time applying case 2 or 3).  RPL can support a hierarchy of RPL routing
> topologies.
>=20
> Does that help?
>=20
> --
> Jonathan Hui
>=20
> On Dec 16, 2011, at 8:55 AM, Park, Kundok wrote:
>=20
> > Hi, Jonathan,
> >
> > I have a question on the following text on version 6, on page 8.
> >
> > "
> >   2.  Datagrams destined elsewhere within the same RPL Instance are
> >       forwarded to the correct interface.
> >
> >   3.  Datagrams destined to nodes outside the RPL Instance are dropped
> >       if the outer-most IPv6 header contains a RPL Option not generated
> >       by the RPL router forwarding the datagram.
> > "
> >
> > Can you clarify the meaning of the (same) RPL instance in the above
> text? Is it the RPL instance in the outer-most IPv6 header? For instance,
> if a RPL packet is tunneled to a RPL router using another RPL instance an=
d
> the recipient RPL router is the exit point of the outer tunnel, must the
> router discard such a packet whether the router joined the RPL instance o=
f
> the inner packet or not?
> > To phrase it differently, can RPL be used in a virtual network over a
> network which happens to use another RPL instance as an underlying routin=
g
> protocol?
> >
> > Thank you.
> >
> > BR,
> > Kundok Park
> > Texas Instruments
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------


From marka@isc.org  Fri Dec 16 15:45:47 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 16FA621F87D6 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 15:45:47 -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 Dkl2hN2XhRWq for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 15:45:45 -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 C466121F85EF for <ipv6@ietf.org>; Fri, 16 Dec 2011 15:45:45 -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 069AB5F98B6; Fri, 16 Dec 2011 23:45:31 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:4f4:b290:88dd:9a95]) (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 402F6216C6B; Fri, 16 Dec 2011 23:45:29 +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 0E10E1A1A5CF; Sat, 17 Dec 2011 10:45:25 +1100 (EST)
To: Fernando Gont <fgont@si6networks.com>
From: Mark Andrews <marka@isc.org>
References: <4EEA0342.2040608@si6networks.com> <20111216011929.C187E1A15E75@drugs.dv.isc.org> <4EEB66D6.7070703@si6networks.com>
Subject: Re: Fragmentation-related security issues
In-reply-to: Your message of "Fri, 16 Dec 2011 12:42:14 -0300." <4EEB66D6.7070703@si6networks.com>
Date: Sat, 17 Dec 2011 10:45:24 +1100
Message-Id: <20111216234525.0E10E1A1A5CF@drugs.dv.isc.org>
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, 16 Dec 2011 23:45:47 -0000

In message <4EEB66D6.7070703@si6networks.com>, Fernando Gont writes:
> Hi, Mark,
> 
> On 12/15/2011 10:19 PM, Mark Andrews wrote:
> > When thinking about this draft please consider the following:
> > 
> > http://tools.ietf.org/html/draft-andrews-6man-force-fragmentation-00
> > http://tools.ietf.org/html/draft-andrews-dnsext-udp-fragmentation-00
> 
> I've just read both of them. The relationship I've found with these two
> and the two I've authored is that your I-D's will lead to an increase of
> IPv6 "atomic fragments". This means that:
> 
> *
> <http://tools.ietf.org/id/draft-gont-6man-ipv6-atomic-fragments-00.txt>
> is even more desirable, as it would completely mitigate
> fragmentation-related attacks against DNS traffic that is not really
> split into several packets (but still contains a Fragment Header.
> 
> * Implementation of
> <http://tools.ietf.org/id/draft-gont-6man-predictable-fragment-id-00.txt> at
> the sending node would help mitigate some fragmentation-related attacks
> against receivers that do not yet implement the "atomic packets"
> behaviour described above, or in scenarios in which DNS traffic is
> really fragmented (i.e., packets are split into multiple pieces).
> 
> Does this agree with your assessment? Am I missing something?
> 
> P.S.: I'll be sending feedback about your I-Ds in separate e-mails.
> 
> Thanks!
> 
> Best regards,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

The real worry is the amount of state that busy authoritative servers
will be maintaining.  At 13K+ mostly unique clients a second to answer
that's a lot of state.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From jonhui@cisco.com  Fri Dec 16 15:48:29 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 0337111E8083 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 15:48:29 -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=[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 7M8MxHbwrRqh for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 15:48:28 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 37BBD11E8073 for <ipv6@ietf.org>; Fri, 16 Dec 2011 15:48:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=4191; q=dns/txt; s=iport; t=1324079308; x=1325288908; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=rCq0reSPMRy/jbrhfoMomUGLzYWHkKUCwatPJegBPbM=; b=Fn/ttItBtfryVmKDx9s+YOaILv/+0MzXXZLfWetgvgnnemRd9irPGORY aAKKM9wAdGOzYZPHts3YpDF/5nAxrDXEkBGadihvgZZOe0cgH1yhnPC6O NOpBH0YbIHnKBrXlnksujBgW86jofkszH8aUbdzXkTVWV3WOjbRquTLkg g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtQAAJzX606rRDoG/2dsb2JhbABEmwqQTIEFgXIBAQEDAQEBAQ8BJzQLBQcECxEEAQEBJwcnHwkIBhMih1gImVMBnicEiyFjBIg0jEKSTQ
X-IronPort-AV: E=Sophos;i="4.71,366,1320624000"; d="scan'208";a="21183263"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 16 Dec 2011 23:48:28 +0000
Received: from sjc-vpn5-1371.cisco.com (sjc-vpn5-1371.cisco.com [10.21.93.91]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pBGNmQJM009116; Fri, 16 Dec 2011 23:48:27 GMT
Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <055FAFECB2B53642884D29B0094D14751098086E@DLEE10.ent.ti.com>
Date: Fri, 16 Dec 2011 15:48:31 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <789A0DE4-2534-40DC-961F-4B268C61B0B5@cisco.com>
References: <20111214153427.3662.89188.idtracker@ietfa.amsl.com> <055FAFECB2B53642884D29B0094D147510980815@DLEE10.ent.ti.com> <7A4603CA-2BCE-4029-A82E-6169C065D224@cisco.com> <055FAFECB2B53642884D29B0094D14751098086E@DLEE10.ent.ti.com>
To: "Park, Kundok" <kpark@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: Fri, 16 Dec 2011 23:48:29 -0000

Hi Kundok,

As the processing rules state, Case 1 only occurs when the RPL router is =
the tunnel exit-point.  Case 2 and 3 occur only when the RPL router is =
*not* the tunnel exit-point and is an intermediate hop of a tunnel.

Take the following example of nested tunnels:

| TunnelA | TunnelB | Datagram |

If the RPL router is the exit-point for TunnelA, the RPL router will =
first apply Case 1, decapsulate the packet by removing the TunnelA =
header, and resubmit the datagram for further processing.

The RPL router then applies the processing rules again to the =
resubmitted datagram.  In this case, the outer-most header now refers to =
TunnelB.  If the RPL router is not the exit-point for TunnelB, it =
applies either Case 2 or 3.

This is typically how nested tunnels are handled in IPv6.

--
Jonathan Hui

On Dec 16, 2011, at 3:21 PM, Park, Kundok wrote:

> Hi, Jonathan,
>=20
> Thanks for your quick reply.
>=20
> Unfortunately I am still a bit confused.
>=20
> Based on your reply, I guess that the case 1 is meant only for the =
case of tunnel exit-point being the final RPL router along a path, when =
the tunnel is used.
>=20
> The same RPL instance mentioned in case 2 perhaps means the RPL =
instance in the outer header when a tunnel is used and when the RPL =
router is not the final RPL router along a path, and does the case 2 =
also apply to a case where RPL router is the final RPL router along a =
path?
>=20
> Does the case 3 only apply to the RPL router being the final RPL =
router along a path when tunnel is used but not to the RPL router not =
being the final router along a path? If the answer is yes, by the =
outer-most IPv6 header, did you mean the outer-most IPv6 header of the =
inner packet and does RPL Instance in this context mean any RPL instance =
that the RPL router joined?
>=20
> I'd appreciate if you can clarify furthermore.
>=20
> BR,
> Kundok
>=20
>> -----Original Message-----
>> From: Jonathan Hui [mailto:jonhui@cisco.com]
>> Sent: Friday, December 16, 2011 2:00 PM
>> To: Park, Kundok
>> Cc: ipv6@ietf.org
>> Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
>>=20
>>=20
>> Hi Kundok,
>>=20
>> If the RPL router is serves as the tunnel-exit, it falls into case 1 =
and
>> removes the outer-most header in the usual way.  If the IPv6 header =
after
>> decapsulation includes another RPL Option, the router uses the RPL
>> Instance of that RPL Option and evaluates the forwarding rules again =
(this
>> time applying case 2 or 3).  RPL can support a hierarchy of RPL =
routing
>> topologies.
>>=20
>> Does that help?
>>=20
>> --
>> Jonathan Hui
>>=20
>> On Dec 16, 2011, at 8:55 AM, Park, Kundok wrote:
>>=20
>>> Hi, Jonathan,
>>>=20
>>> I have a question on the following text on version 6, on page 8.
>>>=20
>>> "
>>>  2.  Datagrams destined elsewhere within the same RPL Instance are
>>>      forwarded to the correct interface.
>>>=20
>>>  3.  Datagrams destined to nodes outside the RPL Instance are =
dropped
>>>      if the outer-most IPv6 header contains a RPL Option not =
generated
>>>      by the RPL router forwarding the datagram.
>>> "
>>>=20
>>> Can you clarify the meaning of the (same) RPL instance in the above
>> text? Is it the RPL instance in the outer-most IPv6 header? For =
instance,
>> if a RPL packet is tunneled to a RPL router using another RPL =
instance and
>> the recipient RPL router is the exit point of the outer tunnel, must =
the
>> router discard such a packet whether the router joined the RPL =
instance of
>> the inner packet or not?
>>> To phrase it differently, can RPL be used in a virtual network over =
a
>> network which happens to use another RPL instance as an underlying =
routing
>> protocol?
>>>=20
>>> Thank you.
>>>=20
>>> BR,
>>> Kundok Park
>>> Texas Instruments
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>=20


From fgont@si6networks.com  Fri Dec 16 16:43:44 2011
Return-Path: <fgont@si6networks.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 080E321F847D for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 16:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 ukOUK54brJU5 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 16:43:43 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 36D111F0C50 for <ipv6@ietf.org>; Fri, 16 Dec 2011 16:43:43 -0800 (PST)
Received: from [190.48.203.52] (helo=[192.168.123.102]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RbiNG-0005Ik-Fx; Sat, 17 Dec 2011 01:43:38 +0100
Message-ID: <4EEBE5AD.9080902@si6networks.com>
Date: Fri, 16 Dec 2011 21:43:25 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com> <20111216011929.C187E1A15E75@drugs.dv.isc.org> <4EEB66D6.7070703@si6networks.com> <20111216234525.0E10E1A1A5CF@drugs.dv.isc.org>
In-Reply-To: <20111216234525.0E10E1A1A5CF@drugs.dv.isc.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 17 Dec 2011 00:43:44 -0000

On 12/16/2011 08:45 PM, Mark Andrews wrote:
> The real worry is the amount of state that busy authoritative servers
> will be maintaining.  At 13K+ mostly unique clients a second to answer
> that's a lot of state.

Well, that's assuming the queries are really fragmented into more than
one packet. Is there any data about this? (i.e., size of requests)

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From kpark@ti.com  Fri Dec 16 16:56:38 2011
Return-Path: <kpark@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 312AF21F891D for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 16:56: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 Kn5zRq9lT+-P for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 16:56:37 -0800 (PST)
Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by ietfa.amsl.com (Postfix) with ESMTP id 6686A21F841D for <ipv6@ietf.org>; Fri, 16 Dec 2011 16:56:37 -0800 (PST)
Received: from dlep26.itg.ti.com ([157.170.170.121]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id pBH0uYjE028058; Fri, 16 Dec 2011 18:56:36 -0600
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 pBH0uY3c001846; Fri, 16 Dec 2011 18:56:34 -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; Fri, 16 Dec 2011 18:56:34 -0600
From: "Park, Kundok" <kpark@ti.com>
To: Jonathan Hui <jonhui@cisco.com>
Subject: RE: I-D Action: draft-ietf-6man-rpl-option-06.txt
Thread-Topic: I-D Action: draft-ietf-6man-rpl-option-06.txt
Thread-Index: AQHMunXknFy7hMAU3Uubz0qSChYYBJXeqvdAgADA74D//5v7cIAAgjaA//+duCA=
Date: Sat, 17 Dec 2011 00:56:34 +0000
Message-ID: <055FAFECB2B53642884D29B0094D1475109808B2@DLEE10.ent.ti.com>
References: <20111214153427.3662.89188.idtracker@ietfa.amsl.com> <055FAFECB2B53642884D29B0094D147510980815@DLEE10.ent.ti.com> <7A4603CA-2BCE-4029-A82E-6169C065D224@cisco.com> <055FAFECB2B53642884D29B0094D14751098086E@DLEE10.ent.ti.com> <789A0DE4-2534-40DC-961F-4B268C61B0B5@cisco.com>
In-Reply-To: <789A0DE4-2534-40DC-961F-4B268C61B0B5@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: Sat, 17 Dec 2011 00:56:38 -0000

Hi, Jonathan,

I think I now understand. My understanding is as if the cases 2 and 3 were =
written in the following way:


  2.  Datagrams, which can be forwarded within the same RPL Instance as in
      the RPL Option contained in outer-most IPv6 header inside the
      datagrams, are forwarded to the correct interface.

  3.  Datagrams, which cannot be forwarded within the same RPL Instance
      as in the RPL option contained in the outer-most IPv6 header inside
      the datagrams, are dropped.

  4.  Datagrams, which does not contain a RPL option in the outer-most IPv6
      Header inside the datagrams, can be either forwarded to available
      network or dropped if the next hop cannot be determined.
      RPL router may encapsulate the datagrams using IPv6-in-IPv6 tunneling
      when forwarding them, adding RPL Option to the newly added outer
      IPv6 header.
      Note that, if a datagram, which does not contain a RPL option, was
      delivered to the RPL router using IPv6-in-IPv6 tunneling, and the
      outer IPv6 header contained a RPL option, and the recipient RPL
      router decides to forward the datagram using the same RPL Instance
      as in the processed RPL option, the RPL router encapsulates the
      packet again and include the same RPL Option following the
      requirements mentioned above in this section.


Is my understanding correct?
Thank you.

BR,
Kundok


> -----Original Message-----
> From: Jonathan Hui [mailto:jonhui@cisco.com]
> Sent: Friday, December 16, 2011 3:49 PM
> To: Park, Kundok
> Cc: ipv6@ietf.org
> Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
>=20
>=20
> Hi Kundok,
>=20
> As the processing rules state, Case 1 only occurs when the RPL router is
> the tunnel exit-point.  Case 2 and 3 occur only when the RPL router is
> *not* the tunnel exit-point and is an intermediate hop of a tunnel.
>=20
> Take the following example of nested tunnels:
>=20
> | TunnelA | TunnelB | Datagram |
>=20
> If the RPL router is the exit-point for TunnelA, the RPL router will firs=
t
> apply Case 1, decapsulate the packet by removing the TunnelA header, and
> resubmit the datagram for further processing.
>=20
> The RPL router then applies the processing rules again to the resubmitted
> datagram.  In this case, the outer-most header now refers to TunnelB.  If
> the RPL router is not the exit-point for TunnelB, it applies either Case =
2
> or 3.
>=20
> This is typically how nested tunnels are handled in IPv6.
>=20
> --
> Jonathan Hui
>=20
> On Dec 16, 2011, at 3:21 PM, Park, Kundok wrote:
>=20
> > Hi, Jonathan,
> >
> > Thanks for your quick reply.
> >
> > Unfortunately I am still a bit confused.
> >
> > Based on your reply, I guess that the case 1 is meant only for the case
> of tunnel exit-point being the final RPL router along a path, when the
> tunnel is used.
> >
> > The same RPL instance mentioned in case 2 perhaps means the RPL instanc=
e
> in the outer header when a tunnel is used and when the RPL router is not
> the final RPL router along a path, and does the case 2 also apply to a
> case where RPL router is the final RPL router along a path?
> >
> > Does the case 3 only apply to the RPL router being the final RPL router
> along a path when tunnel is used but not to the RPL router not being the
> final router along a path? If the answer is yes, by the outer-most IPv6
> header, did you mean the outer-most IPv6 header of the inner packet and
> does RPL Instance in this context mean any RPL instance that the RPL
> router joined?
> >
> > I'd appreciate if you can clarify furthermore.
> >
> > BR,
> > Kundok
> >
> >> -----Original Message-----
> >> From: Jonathan Hui [mailto:jonhui@cisco.com]
> >> Sent: Friday, December 16, 2011 2:00 PM
> >> To: Park, Kundok
> >> Cc: ipv6@ietf.org
> >> Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
> >>
> >>
> >> Hi Kundok,
> >>
> >> If the RPL router is serves as the tunnel-exit, it falls into case 1
> and
> >> removes the outer-most header in the usual way.  If the IPv6 header
> after
> >> decapsulation includes another RPL Option, the router uses the RPL
> >> Instance of that RPL Option and evaluates the forwarding rules again
> (this
> >> time applying case 2 or 3).  RPL can support a hierarchy of RPL routin=
g
> >> topologies.
> >>
> >> Does that help?
> >>
> >> --
> >> Jonathan Hui
> >>
> >> On Dec 16, 2011, at 8:55 AM, Park, Kundok wrote:
> >>
> >>> Hi, Jonathan,
> >>>
> >>> I have a question on the following text on version 6, on page 8.
> >>>
> >>> "
> >>>  2.  Datagrams destined elsewhere within the same RPL Instance are
> >>>      forwarded to the correct interface.
> >>>
> >>>  3.  Datagrams destined to nodes outside the RPL Instance are dropped
> >>>      if the outer-most IPv6 header contains a RPL Option not generate=
d
> >>>      by the RPL router forwarding the datagram.
> >>> "
> >>>
> >>> Can you clarify the meaning of the (same) RPL instance in the above
> >> text? Is it the RPL instance in the outer-most IPv6 header? For
> instance,
> >> if a RPL packet is tunneled to a RPL router using another RPL instance
> and
> >> the recipient RPL router is the exit point of the outer tunnel, must
> the
> >> router discard such a packet whether the router joined the RPL instanc=
e
> of
> >> the inner packet or not?
> >>> To phrase it differently, can RPL be used in a virtual network over a
> >> network which happens to use another RPL instance as an underlying
> routing
> >> protocol?
> >>>
> >>> Thank you.
> >>>
> >>> BR,
> >>> Kundok Park
> >>> Texas Instruments
> >>> --------------------------------------------------------------------
> >>> IETF IPv6 working group mailing list
> >>> ipv6@ietf.org
> >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>> --------------------------------------------------------------------
> >


From simon.perreault@viagenie.ca  Wed Dec 14 05:46:53 2011
Return-Path: <simon.perreault@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 43C4721F8B30 for <ipv6@ietfa.amsl.com>; Wed, 14 Dec 2011 05:46:53 -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 ptVEeFyQ0Qx0 for <ipv6@ietfa.amsl.com>; Wed, 14 Dec 2011 05:46:52 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id A339C21F8A6C for <6man@ietf.org>; Wed, 14 Dec 2011 05:46:52 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 0C1DA21CC9; Wed, 14 Dec 2011 08:46:22 -0500 (EST)
Message-ID: <4EE8A8AD.4090802@viagenie.ca>
Date: Wed, 14 Dec 2011 08:46:21 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: draft-andrews-6man-force-fragmentation-00.txt
References: <20111214054241.53F6B1A08E7F@drugs.dv.isc.org>
In-Reply-To: <20111214054241.53F6B1A08E7F@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 16 Dec 2011 17:34:32 -0800
Cc: 6man@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, 14 Dec 2011 13:46:53 -0000

On 2011-12-14 00:42, Mark Andrews wrote:
>
> 	draft-andrews-6man-force-fragmentation-00.txt was just
> 	submitted.  Comments requested.

At first sight I don't like extending IPV6_USE_MIN_MTU because it would change 
current behaviour so it would risk breaking existing applications. The other two 
options look good.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From marka@isc.org  Wed Dec 14 14:27:02 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 B616D11E80CC for <ipv6@ietfa.amsl.com>; Wed, 14 Dec 2011 14:27:02 -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 LWVWPr9TqYlV for <ipv6@ietfa.amsl.com>; Wed, 14 Dec 2011 14:27:02 -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 623BD11E809F for <6man@ietf.org>; Wed, 14 Dec 2011 14:27:01 -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 7F07F5F98B1; Wed, 14 Dec 2011 22:26:47 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:822:436a:c9fe:719]) (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 7CAB4216C6D; Wed, 14 Dec 2011 22:26:45 +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 B13A91A0BC48; Thu, 15 Dec 2011 09:26:41 +1100 (EST)
To: Simon Perreault <simon.perreault@viagenie.ca>
From: Mark Andrews <marka@isc.org>
References: <20111214054241.53F6B1A08E7F@drugs.dv.isc.org> <4EE8A8AD.4090802@viagenie.ca>
Subject: Re: draft-andrews-6man-force-fragmentation-00.txt
In-reply-to: Your message of "Wed, 14 Dec 2011 08:46:21 CDT." <4EE8A8AD.4090802@viagenie.ca>
Date: Thu, 15 Dec 2011 09:26:41 +1100
Message-Id: <20111214222641.B13A91A0BC48@drugs.dv.isc.org>
X-Mailman-Approved-At: Fri, 16 Dec 2011 17:34:32 -0800
Cc: 6man@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, 14 Dec 2011 22:27:02 -0000

In message <4EE8A8AD.4090802@viagenie.ca>, Simon Perreault writes:
> On 2011-12-14 00:42, Mark Andrews wrote:
> >
> > 	draft-andrews-6man-force-fragmentation-00.txt was just
> > 	submitted.  Comments requested.
> 
> At first sight I don't like extending IPV6_USE_MIN_MTU because it would chang
> e 
> current behaviour so it would risk breaking existing applications. The other 
> two 
> options look good.

We could also just add 2 and -2 to IPV6_USE_MIN_MTU to indicate the
forced addition of a Fragment header in addition to limiting the
mtu size.  This should not break existing applications and support
would be detectable at run time.  Try with 2 (or -2) and if that
fails use 1 (or -1).

I'll add this to the next I-D.

> Simon
> -- 
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From jonhui@cisco.com  Fri Dec 16 17:52:18 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 CD5A61F0C57 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 17:52:18 -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 CUsidjBw7Ijb for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 17:52:17 -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 D21731F0C4D for <ipv6@ietf.org>; Fri, 16 Dec 2011 17:52:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=6659; q=dns/txt; s=iport; t=1324086737; x=1325296337; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=CrIDCfRzYk2Err2n+lwtu/3+TVZyFXUdHoTHouI2JXo=; b=alsxQnD81YzMG3ednUTs2GOqjXR1U+/zsqpqCk2obmi2kLhkbkiOQK4w GuBzCpGfDVI21i6AV64H40zsPgT9V2pPVvax2x/8wuedZBT+FX8UGGjY/ tI3wUz3RpQB0cTuwmjLZP26jQC8XkyzJX9mDAJk8vm7mBBjOU/41LvMR+ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtQAAOH0606rRDoJ/2dsb2JhbABEmwqQTIEFgXIBAQEDAQEBAQ8BJzQLBQcECxEEAQEBJwcnHwkIBhMih1gImTgBnicEiyFjBIg0jEKFTox/
X-IronPort-AV: E=Sophos;i="4.71,366,1320624000"; d="scan'208";a="19508524"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 17 Dec 2011 01:52:05 +0000
Received: from [10.21.86.244] ([10.21.86.244]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pBH1q0Is029181; Sat, 17 Dec 2011 01:52:02 GMT
Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <055FAFECB2B53642884D29B0094D1475109808B2@DLEE10.ent.ti.com>
Date: Fri, 16 Dec 2011 17:52:05 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <52723601-7577-4A81-98BC-9741BBA563D8@cisco.com>
References: <20111214153427.3662.89188.idtracker@ietfa.amsl.com> <055FAFECB2B53642884D29B0094D147510980815@DLEE10.ent.ti.com> <7A4603CA-2BCE-4029-A82E-6169C065D224@cisco.com> <055FAFECB2B53642884D29B0094D14751098086E@DLEE10.ent.ti.com> <789A0DE4-2534-40DC-961F-4B268C61B0B5@cisco.com> <055FAFECB2B53642884D29B0094D1475109808B2@DLEE10.ent.ti.com>
To: "Park, Kundok" <kpark@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: Sat, 17 Dec 2011 01:52:18 -0000

Hi Kundok,

Your description is correct.  The processing rules in the draft do not =
apply if the packet does not contain a RPL Option.  If no RPL Option =
exists, then the RPL router should process the datagram like any other =
datagram it may receive from a node not running RPL.

--
Jonathan Hui

On Dec 16, 2011, at 4:56 PM, Park, Kundok wrote:

> Hi, Jonathan,
>=20
> I think I now understand. My understanding is as if the cases 2 and 3 =
were written in the following way:
>=20
>=20
>  2.  Datagrams, which can be forwarded within the same RPL Instance as =
in
>      the RPL Option contained in outer-most IPv6 header inside the
>      datagrams, are forwarded to the correct interface.
>=20
>  3.  Datagrams, which cannot be forwarded within the same RPL Instance
>      as in the RPL option contained in the outer-most IPv6 header =
inside
>      the datagrams, are dropped.
>=20
>  4.  Datagrams, which does not contain a RPL option in the outer-most =
IPv6
>      Header inside the datagrams, can be either forwarded to available
>      network or dropped if the next hop cannot be determined.
>      RPL router may encapsulate the datagrams using IPv6-in-IPv6 =
tunneling
>      when forwarding them, adding RPL Option to the newly added outer
>      IPv6 header.
>      Note that, if a datagram, which does not contain a RPL option, =
was
>      delivered to the RPL router using IPv6-in-IPv6 tunneling, and the
>      outer IPv6 header contained a RPL option, and the recipient RPL
>      router decides to forward the datagram using the same RPL =
Instance
>      as in the processed RPL option, the RPL router encapsulates the
>      packet again and include the same RPL Option following the
>      requirements mentioned above in this section.
>=20
>=20
> Is my understanding correct?
> Thank you.
>=20
> BR,
> Kundok
>=20
>=20
>> -----Original Message-----
>> From: Jonathan Hui [mailto:jonhui@cisco.com]
>> Sent: Friday, December 16, 2011 3:49 PM
>> To: Park, Kundok
>> Cc: ipv6@ietf.org
>> Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
>>=20
>>=20
>> Hi Kundok,
>>=20
>> As the processing rules state, Case 1 only occurs when the RPL router =
is
>> the tunnel exit-point.  Case 2 and 3 occur only when the RPL router =
is
>> *not* the tunnel exit-point and is an intermediate hop of a tunnel.
>>=20
>> Take the following example of nested tunnels:
>>=20
>> | TunnelA | TunnelB | Datagram |
>>=20
>> If the RPL router is the exit-point for TunnelA, the RPL router will =
first
>> apply Case 1, decapsulate the packet by removing the TunnelA header, =
and
>> resubmit the datagram for further processing.
>>=20
>> The RPL router then applies the processing rules again to the =
resubmitted
>> datagram.  In this case, the outer-most header now refers to TunnelB. =
 If
>> the RPL router is not the exit-point for TunnelB, it applies either =
Case 2
>> or 3.
>>=20
>> This is typically how nested tunnels are handled in IPv6.
>>=20
>> --
>> Jonathan Hui
>>=20
>> On Dec 16, 2011, at 3:21 PM, Park, Kundok wrote:
>>=20
>>> Hi, Jonathan,
>>>=20
>>> Thanks for your quick reply.
>>>=20
>>> Unfortunately I am still a bit confused.
>>>=20
>>> Based on your reply, I guess that the case 1 is meant only for the =
case
>> of tunnel exit-point being the final RPL router along a path, when =
the
>> tunnel is used.
>>>=20
>>> The same RPL instance mentioned in case 2 perhaps means the RPL =
instance
>> in the outer header when a tunnel is used and when the RPL router is =
not
>> the final RPL router along a path, and does the case 2 also apply to =
a
>> case where RPL router is the final RPL router along a path?
>>>=20
>>> Does the case 3 only apply to the RPL router being the final RPL =
router
>> along a path when tunnel is used but not to the RPL router not being =
the
>> final router along a path? If the answer is yes, by the outer-most =
IPv6
>> header, did you mean the outer-most IPv6 header of the inner packet =
and
>> does RPL Instance in this context mean any RPL instance that the RPL
>> router joined?
>>>=20
>>> I'd appreciate if you can clarify furthermore.
>>>=20
>>> BR,
>>> Kundok
>>>=20
>>>> -----Original Message-----
>>>> From: Jonathan Hui [mailto:jonhui@cisco.com]
>>>> Sent: Friday, December 16, 2011 2:00 PM
>>>> To: Park, Kundok
>>>> Cc: ipv6@ietf.org
>>>> Subject: Re: I-D Action: draft-ietf-6man-rpl-option-06.txt
>>>>=20
>>>>=20
>>>> Hi Kundok,
>>>>=20
>>>> If the RPL router is serves as the tunnel-exit, it falls into case =
1
>> and
>>>> removes the outer-most header in the usual way.  If the IPv6 header
>> after
>>>> decapsulation includes another RPL Option, the router uses the RPL
>>>> Instance of that RPL Option and evaluates the forwarding rules =
again
>> (this
>>>> time applying case 2 or 3).  RPL can support a hierarchy of RPL =
routing
>>>> topologies.
>>>>=20
>>>> Does that help?
>>>>=20
>>>> --
>>>> Jonathan Hui
>>>>=20
>>>> On Dec 16, 2011, at 8:55 AM, Park, Kundok wrote:
>>>>=20
>>>>> Hi, Jonathan,
>>>>>=20
>>>>> I have a question on the following text on version 6, on page 8.
>>>>>=20
>>>>> "
>>>>> 2.  Datagrams destined elsewhere within the same RPL Instance are
>>>>>     forwarded to the correct interface.
>>>>>=20
>>>>> 3.  Datagrams destined to nodes outside the RPL Instance are =
dropped
>>>>>     if the outer-most IPv6 header contains a RPL Option not =
generated
>>>>>     by the RPL router forwarding the datagram.
>>>>> "
>>>>>=20
>>>>> Can you clarify the meaning of the (same) RPL instance in the =
above
>>>> text? Is it the RPL instance in the outer-most IPv6 header? For
>> instance,
>>>> if a RPL packet is tunneled to a RPL router using another RPL =
instance
>> and
>>>> the recipient RPL router is the exit point of the outer tunnel, =
must
>> the
>>>> router discard such a packet whether the router joined the RPL =
instance
>> of
>>>> the inner packet or not?
>>>>> To phrase it differently, can RPL be used in a virtual network =
over a
>>>> network which happens to use another RPL instance as an underlying
>> routing
>>>> protocol?
>>>>>=20
>>>>> Thank you.
>>>>>=20
>>>>> BR,
>>>>> Kundok Park
>>>>> Texas Instruments
>>>>> =
--------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list
>>>>> ipv6@ietf.org
>>>>> Administrative Requests: =
https://www.ietf.org/mailman/listinfo/ipv6
>>>>> =
--------------------------------------------------------------------
>>>=20
>=20


From marka@isc.org  Fri Dec 16 18:03:24 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 8F30A21F8490 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 18:03:24 -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 WdwFomBJFoYy for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 18:03:24 -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 1C09E21F848F for <ipv6@ietf.org>; Fri, 16 Dec 2011 18:03:24 -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 78D39C9463; Sat, 17 Dec 2011 02:03:11 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:4f4:b290:88dd:9a95]) (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 24462216C6A; Sat, 17 Dec 2011 02:03:11 +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 DE9821A1B446; Sat, 17 Dec 2011 13:03:06 +1100 (EST)
To: Fernando Gont <fgont@si6networks.com>
From: Mark Andrews <marka@isc.org>
References: <4EEA0342.2040608@si6networks.com> <20111216011929.C187E1A15E75@drugs.dv.isc.org> <4EEB66D6.7070703@si6networks.com> <20111216234525.0E10E1A1A5CF@drugs.dv.isc.org> <4EEBE5AD.9080902@si6networks.com>
Subject: Re: Fragmentation-related security issues
In-reply-to: Your message of "Fri, 16 Dec 2011 21:43:25 -0300." <4EEBE5AD.9080902@si6networks.com>
Date: Sat, 17 Dec 2011 13:03:06 +1100
Message-Id: <20111217020306.DE9821A1B446@drugs.dv.isc.org>
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, 17 Dec 2011 02:03:24 -0000

In message <4EEBE5AD.9080902@si6networks.com>, Fernando Gont writes:
> On 12/16/2011 08:45 PM, Mark Andrews wrote:
> > The real worry is the amount of state that busy authoritative servers
> > will be maintaining.  At 13K+ mostly unique clients a second to answer
> > that's a lot of state.
> 
> Well, that's assuming the queries are really fragmented into more than
> one packet. Is there any data about this? (i.e., size of requests)

It's the state on the sending side I'm worried about.  You are
adding ~13K entries a second to the destination cache it will
soon get large as *every* DNS/UDP response has a fragmentation
header.

Instead of maintainin a counter on a per-destination basis, hash
the source and destination and use a pool of fragment counters
possibly using differently seeded lsfr.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From fgont@si6networks.com  Fri Dec 16 19:12:20 2011
Return-Path: <fgont@si6networks.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 EE28021F86A5 for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 19:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 X3UvyPhHzXUC for <ipv6@ietfa.amsl.com>; Fri, 16 Dec 2011 19:12:20 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 1698A21F86A4 for <ipv6@ietf.org>; Fri, 16 Dec 2011 19:12:20 -0800 (PST)
Received: from [190.48.203.52] (helo=[192.168.123.102]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1Rbkh4-0006sY-AW; Sat, 17 Dec 2011 04:12:14 +0100
Message-ID: <4EEC0884.3050101@si6networks.com>
Date: Sat, 17 Dec 2011 00:12:04 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com> <20111216011929.C187E1A15E75@drugs.dv.isc.org> <4EEB66D6.7070703@si6networks.com> <20111216234525.0E10E1A1A5CF@drugs.dv.isc.org> <4EEBE5AD.9080902@si6networks.com> <20111217020306.DE9821A1B446@drugs.dv.isc.org>
In-Reply-To: <20111217020306.DE9821A1B446@drugs.dv.isc.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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, 17 Dec 2011 03:12:21 -0000

On 12/16/2011 11:03 PM, Mark Andrews wrote:
>> Well, that's assuming the queries are really fragmented into more than
>> one packet. Is there any data about this? (i.e., size of requests)
> 
> It's the state on the sending side I'm worried about.  You are
> adding ~13K entries a second to the destination cache it will
> soon get large as *every* DNS/UDP response has a fragmentation
> header.

Well, the problem you mention with the destinations cache is not really
introduced by this algorithm -- the Destinations Cache is there anyway
(it is not created because of this).

If the Destinations Cache gets too big, you prune part of the entries,
and then the worst thing that can happen is that when the Fragment ID is
reinitialized with a random number for a future communication instance,
there's a Fragment ID collision, and the corresponding fragments get
discarded.

However,since the Identification field of the IPv6 Fragment Header is
much larger than that of IPv4, I'd argue that collisions are rather
unlikely (for instance, the reason for which we're proposing the
algorithm we¿re proposing rather than simply randomizing the Fragment ID
for each packet is to avoid collisions when two systems are transferring
a lot of data, at a high rate.... since in those scenarios, and with the
ever increasing data rates, there might be collisions)


> Instead of maintainin a counter on a per-destination basis, hash
> the source and destination and use a pool of fragment counters
> possibly using differently seeded lsfr.

FWIW, Linux and Solaris have already implemented this algorithm.

IIRC, an earlier version of this document proposed something along the
lines of what you mention. But IIRC we abandonded the idea because
implementers were concerned about computing a hash for each outgoing
packet.

That aside, one should be careful with the approach you're describing.
Unless the number of counters is really large, then it wouldn't be hard
to learn the current value of all counters -- after all, you have 64
bits in the Interface ID to play with, which could possibly let you
learn the current value of all the "Fragment ID" counters (i.e., not as
bad as a global counter, but still not good enough).

All the above said, take this as "brainstorming"... if we conclude that
it would be best to provide a number of alternative algorithms, or even
change the currently recommended algorithm, I'd have no problems with that.

(the current one is the result of discussions with the v6 developers of
a number of OSes... but there's always room for improvement)

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From internet-drafts@ietf.org  Mon Dec 19 10:41:59 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 6F05511E809F; Mon, 19 Dec 2011 10:41:59 -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=[AWL=0.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 tuSHoobzoQz3; Mon, 19 Dec 2011 10:41:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9C2E11E8080; Mon, 19 Dec 2011 10:41:58 -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-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111219184158.18497.33256.idtracker@ietfa.amsl.com>
Date: Mon, 19 Dec 2011 10:41:58 -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, 19 Dec 2011 18:41:59 -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-01.txt
	Pages           : 4
	Date            : 2011-12-19

   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-01.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-01.txt


From wesley.george@twcable.com  Mon Dec 19 10:43:51 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 D7D0511E809C for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 10:43:51 -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 UxMBXXtuiWsu for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 10:43:51 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 46C4B11E8080 for <ipv6@ietf.org>; Mon, 19 Dec 2011 10:43:51 -0800 (PST)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.71,377,1320642000"; d="scan'208";a="297148004"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 19 Dec 2011 13:43:19 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Mon, 19 Dec 2011 13:43:41 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Date: Mon, 19 Dec 2011 13:43: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: AcyuruE5Oa4uaJvDRSqZmxfznwKTDwPzxulA
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791736C47A44@PRVPEXVS03.corp.twcable.com>
References: <4ED4FF87.80703@innovationslab.net>
In-Reply-To: <4ED4FF87.80703@innovationslab.net>
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 <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: Mon, 19 Dec 2011 18:43:52 -0000

I just posted an updated version (-01) of this draft that clears the IDNits=
, but I received no other substantive feedback at last call, so I think it'=
s ready to proceed.

Thanks,

Wes

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian Haberman
> Sent: Tuesday, November 29, 2011 10:52 AM
> To: ipv6@ietf.org
> Cc: 6man Chairs
> Subject: 6MAN WG Last Call: draft-ietf-6man-3627-historic-00.txt
>
> 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
> --------------------------------------------------------------------

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 kpark@ti.com  Mon Dec 19 13:17:35 2011
Return-Path: <kpark@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 A071011E8080 for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 13:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[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 jnSF5iBji3Ou for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 13:17:34 -0800 (PST)
Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by ietfa.amsl.com (Postfix) with ESMTP id 782EA21F84D8 for <ipv6@ietf.org>; Mon, 19 Dec 2011 13:17:34 -0800 (PST)
Received: from dlep26.itg.ti.com ([157.170.170.121]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id pBJLHXtN031625 for <ipv6@ietf.org>; Mon, 19 Dec 2011 15:17:33 -0600
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 pBJLHXQ3018280 for <ipv6@ietf.org>; Mon, 19 Dec 2011 15:17:33 -0600 (CST)
Received: from DLEE10.ent.ti.com ([fe80::843:a4aa:bf01:3f68]) by DLEE74.ent.ti.com ([fe80::a0f1:125b:e7e3:7ed8%18]) with mapi id 14.01.0323.003; Mon, 19 Dec 2011 15:17:33 -0600
From: "Park, Kundok" <kpark@ti.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: draft-ietf-6man-rpl-routing-header-07
Thread-Topic: draft-ietf-6man-rpl-routing-header-07
Thread-Index: Acy+k55tWNpb7VPsS9WuATHFu4Tpyw==
Date: Mon, 19 Dec 2011 21:17:33 +0000
Message-ID: <055FAFECB2B53642884D29B0094D14751098099F@DLEE10.ent.ti.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: multipart/alternative; boundary="_000_055FAFECB2B53642884D29B0094D14751098099FDLEE10entticom_"
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, 19 Dec 2011 21:17:35 -0000

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

It seems that the following text on page 10 has some slight oversights:

"

   In order to respect the IPv6 Hop Limit value of the original

   datagram, a RPL router generating an SRH MUST set the Segments Left

   to no greater than the original datagram's IPv6 Hop Limit value upon

   forwarding.
"

should have been as follows:

"

   In order to respect the IPv6 Hop Limit value of the original

   datagram, a RPL router generating an SRH in an IPv6-in-IPv6 tunnel

   MUST set the Segments Left to less than the original datagram's IPv6

   Hop Limit value upon forwarding.
"

If the Segments Left is equal to Hop Limit value, the source route includes=
 one more hop than the hop limit, which is not intended here.
The other change is to make clear that the above phrase does not apply to t=
he case where the SRH is directly included within the original packet.

As a side note, the traceroute application doesn't seem to be able to handl=
e the case with no tunnel use, because the original datagram destination ad=
dress alters when SRH is added, unless, I guess, traceroute application is =
re-written to handle source routing in returned ICMPv6 error messages. Perh=
aps, that recommended direct inclusion of SRH should be removed?

Best Regards,
Kundok


--_000_055FAFECB2B53642884D29B0094D14751098099FDLEE10entticom_
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=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 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">It seems that the following text on page 10 has some sli=
ght oversights:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;<o:p></o:p></span></font></p>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; In order to respect the IPv6 Hop Limit value of the original<=
o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; datagram, a RPL router generating an SRH MUST set the Segment=
s Left<o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; to <u>no greater</u> than the original datagram's IPv6 Hop Li=
mit value upon<o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; forwarding.<o:p></o:p></span></font></pre>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">should have been as follows:<o:p></o:p></span></font></p=
>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;<o:p></o:p></span></font></p>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; In order to respect the IPv6 Hop Limit value of the original<=
o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; datagram, a RPL router generating an SRH <u>in an IPv6-in-IPv=
6 tunnel</u><o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; MUST set the Segments Left to <u>less</u> than the original d=
atagram's IPv6<o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp; &nbsp;Hop Limit value upon forwarding.<o:p></o:p></span></font></pr=
e>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">If the Segments Left is equal to Hop Limit value, the so=
urce route includes one more hop than the hop limit, which is not intended =
here.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">The other change is to make clear that the above phrase =
does not apply to the case where the SRH is directly included within the or=
iginal packet.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">As a side note, the traceroute application doesn&#8217;t=
 seem to be able to handle the case with no tunnel use, because the origina=
l datagram destination address alters
 when SRH is added, unless, I guess, traceroute application is re-written t=
o handle source routing in returned ICMPv6 error messages. Perhaps, that re=
commended direct inclusion of SRH should be removed?<o:p></o:p></span></fon=
t></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">Best Regards,<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">Kundok<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
</div>
</body>
</html>

--_000_055FAFECB2B53642884D29B0094D14751098099FDLEE10entticom_--

From ghanashyam_satpathy@yahoo.com  Sun Dec 18 03:14:22 2011
Return-Path: <ghanashyam_satpathy@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 5D83121F850B for <ipv6@ietfa.amsl.com>; Sun, 18 Dec 2011 03:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.001
X-Spam-Level: **
X-Spam-Status: No, score=2.001 tagged_above=-999 required=5 tests=[BAYES_80=2,  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 sO041LAwkXia for <ipv6@ietfa.amsl.com>; Sun, 18 Dec 2011 03:14:22 -0800 (PST)
Received: from nm28-vm1.bullet.mail.ne1.yahoo.com (nm28-vm1.bullet.mail.ne1.yahoo.com [98.138.91.35]) by ietfa.amsl.com (Postfix) with SMTP id D5BF421F8507 for <ipv6@ietf.org>; Sun, 18 Dec 2011 03:14:21 -0800 (PST)
Received: from [98.138.90.52] by nm28.bullet.mail.ne1.yahoo.com with NNFMP; 18 Dec 2011 11:14:15 -0000
Received: from [98.138.87.5] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 18 Dec 2011 11:14:15 -0000
Received: from [127.0.0.1] by omp1005.mail.ne1.yahoo.com with NNFMP; 18 Dec 2011 11:14:15 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 695896.75635.bm@omp1005.mail.ne1.yahoo.com
Received: (qmail 73452 invoked by uid 60001); 18 Dec 2011 11:14:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1324206855; bh=GGnkU810fAzZenyAPHnhBheShkkFnmMBhZPVlD7t8UU=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=YLe/pJYzo0XLKLJEvL+jEw2vEt6PdHk2z9uz9ZFqKKyUtlvcWMGQvPosyHGTRQR0ur86/eO3hd0rqVts6dIhquLCS43cuWyjCiTLE90W/S3L9T1pa7kdz1w7SXbId1c2tNms3h1Jl+Fz6/uW+o/VZkbyEjSaxncV26Awi9uK2Q4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=49fYtVt4Oq/lidWhqLfGhRezJmMpHwaQ1vgpk6Ggpt3ZuZMaOMhAbpZ4LwmvrjkJmK+VbCUilYYxxAZ86WnxzbIn+FDjvPgLGM/1ATB8sIowFPpJjMgpJ66iWTymQVtRidzv5xneCbtpNdx018cPmCt4TcEz0KPKjMADZdcKv5g=;
X-YMail-OSG: EJQE0FUVM1m6i2_HAH6V5Ud42ia9rLAAx2REcggXWVuaQxB B1uW1e81kFws5uyficxyyoTWEFZRPGD1hXPMVfDFSxe7fzKj_F8QvNsx7fSC V1gFU0YFNeWUYhxpIymtWhydA3bn7qs9pLhGxvQokXAQ24UMMm7nOaYBJsxl HxWy9dxKKZ7O3uNJ_2_i6siWOMK5IKtmGJ38C5_iSriPTf9GrHaobYlCdRkh 8C5MSAHcao.P5dKqas.uI7Szr9Vwvy5Z7M.q4i2YnLPNIwtqbapGe_7cRa2C Ouiiv8pfRnr7QTePgNfSP2fcm3NCop70yjF3YngmD9O08xFy2wgO79qBN03h gO2Zw0flO0AC3xA0jk4f9A5I9JTb5zaIwk5GRzN6wKSPGw1zYcPMOOtmAG_X LYeEzSIh8lOMjQDQQu62LmDdKcTGk8MxDUH8Gsob.mBbkQPCxNuM7CWYfGQ- -
Received: from [182.71.249.226] by web121801.mail.ne1.yahoo.com via HTTP; Sun, 18 Dec 2011 03:14:15 PST
X-Mailer: YahooMailWebService/0.8.115.331698
Message-ID: <1324206855.51664.YahooMailNeo@web121801.mail.ne1.yahoo.com>
Date: Sun, 18 Dec 2011 03:14:15 -0800 (PST)
From: Ghanashyam Satpathy <ghanashyam_satpathy@yahoo.com>
Subject: Question on IPV4/IPV6 Multicast interoperability
To: "ipv6@ietf.org" <ipv6@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-433406958-229466137-1324206855=:51664"
X-Mailman-Approved-At: Mon, 19 Dec 2011 14:23:01 -0800
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ghanashyam Satpathy <ghanashyam_satpathy@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: Sun, 18 Dec 2011 11:15:43 -0000

---433406958-229466137-1324206855=:51664
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,=0A=A0=0AI have a question on IPV4/IPV6 Multicast interoperability. W=
e have succesfully upgraded our application(Windows Based)=A0to support IPV=
6 and faced issue on multicast interoperability. Multicast messages sent by=
 a IPV6 server is successfully receved by a client running on IPV6. But any=
 client running on IPV4 is not able to receive the message.=0A=A0=0AQuite a=
 no. of things I tried like using IPV4 mapped IPV6 address and V4 embeded V=
6 adress.But nothing seems to be working.Would like to know an unified way =
so that one multicast message sent by an IPV6 server should be received by =
both V6 and V4 client.=0A=A0=0AWould be great if somebody can send some cod=
e snippet(C/C++) on it.=0A=A0=0AThanks.=0A=A0=0AGhanashyam
---433406958-229466137-1324206855=:51664
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt"><div style=3D"RIGHT: =
auto">Hello,</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">I have a question on IPV4/IPV6 Multicast interop=
erability. We have succesfully upgraded our application(Windows Based)&nbsp=
;to support IPV6 and faced issue on multicast interoperability. Multicast m=
essages sent by a IPV6 server is successfully receved by a client running o=
n IPV6. But any client running on IPV4 is not able to receive the message.<=
/div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">Quite a no. of things I tried like using IPV4 ma=
pped IPV6 address and V4 embeded V6 adress.But nothing seems to be working.=
Would like to know an unified way so that one multicast message sent by an =
IPV6 server should be received by both V6 and V4 client.</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">Would be great if somebody can send some code sn=
ippet(C/C++)<VAR id=3Dyui-ie-cursor></VAR> on it.</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">Thanks.</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">Ghanashyam</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">&nbsp;</div></div></body></html>
---433406958-229466137-1324206855=:51664--

From kpark@ti.com  Mon Dec 19 15:59:16 2011
Return-Path: <kpark@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 4633621F8505 for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 15:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[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 spmMh9x+2b4e for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 15:59:14 -0800 (PST)
Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by ietfa.amsl.com (Postfix) with ESMTP id 82A2521F8500 for <ipv6@ietf.org>; Mon, 19 Dec 2011 15:59:14 -0800 (PST)
Received: from dlep26.itg.ti.com ([157.170.170.121]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id pBJNxCrR020426 for <ipv6@ietf.org>; Mon, 19 Dec 2011 17:59:14 -0600
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 pBJNxBdZ023151 for <ipv6@ietf.org>; Mon, 19 Dec 2011 17:59:12 -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; Mon, 19 Dec 2011 17:59:12 -0600
From: "Park, Kundok" <kpark@ti.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-6man-rpl-routing-header-07
Thread-Topic: draft-ietf-6man-rpl-routing-header-07
Thread-Index: Acy+k55tWNpb7VPsS9WuATHFu4TpywAE+ODQ
Date: Mon, 19 Dec 2011 23:59:11 +0000
Message-ID: <055FAFECB2B53642884D29B0094D1475109809D8@DLEE10.ent.ti.com>
References: <055FAFECB2B53642884D29B0094D14751098099F@DLEE10.ent.ti.com>
In-Reply-To: <055FAFECB2B53642884D29B0094D14751098099F@DLEE10.ent.ti.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: multipart/alternative; boundary="_000_055FAFECB2B53642884D29B0094D1475109809D8DLEE10entticom_"
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, 19 Dec 2011 23:59:16 -0000

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

As another side note, this new draft revision creates a situation where the=
 hop limit from the RPL router performing source routing may be one and hen=
ce it cannot use SRH (because Segments Left becomes zero and no address can=
 be included). In order to make it appear as if it tried the source routing=
 with one hop, I think the RPL router must forward the packet to the next h=
op that it should normally pick for a source routing without modifying the =
original packet (that is, the destination address remains the same as the f=
inal destination). I don't think this requires any change to the draft beca=
use the RPL router in this case is not using SRH and hence out of scope of =
this draft.

BR,
Kundok

________________________________
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Par=
k, Kundok
Sent: Monday, December 19, 2011 1:18 PM
To: ipv6@ietf.org
Subject: draft-ietf-6man-rpl-routing-header-07

It seems that the following text on page 10 has some slight oversights:

"

   In order to respect the IPv6 Hop Limit value of the original

   datagram, a RPL router generating an SRH MUST set the Segments Left

   to no greater than the original datagram's IPv6 Hop Limit value upon

   forwarding.
"

should have been as follows:

"

   In order to respect the IPv6 Hop Limit value of the original

   datagram, a RPL router generating an SRH in an IPv6-in-IPv6 tunnel

   MUST set the Segments Left to less than the original datagram's IPv6

   Hop Limit value upon forwarding.
"

If the Segments Left is equal to Hop Limit value, the source route includes=
 one more hop than the hop limit, which is not intended here.
The other change is to make clear that the above phrase does not apply to t=
he case where the SRH is directly included within the original packet.

As a side note, the traceroute application doesn't seem to be able to handl=
e the case with no tunnel use, because the original datagram destination ad=
dress alters when SRH is added, unless, I guess, traceroute application is =
re-written to handle source routing in returned ICMPv6 error messages. Perh=
aps, that recommended direct inclusion of SRH should be removed?

Best Regards,
Kundok


--_000_055FAFECB2B53642884D29B0094D1475109809D8DLEE10entticom_
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=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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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"><font size=3D"2" color=3D"blue" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:blue">As another side note, this new draft r=
evision creates a situation where the hop limit from the RPL router perform=
ing source routing may
 be one and hence it cannot use SRH (because Segments Left becomes zero and=
 no address can be included). In order to make it appear as if it tried the=
 source routing with one hop, I think the RPL router must forward the packe=
t to the next hop that it should
 normally pick for a source routing without modifying the original packet (=
that is, the destination address remains the same as the final destination)=
. I don&#8217;t think this requires any change to the draft because the RPL=
 router in this case is not using SRH
 and hence out of scope of this draft.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"blue" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:blue"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"blue" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:blue">BR,<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"blue" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:blue">Kundok<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"blue" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:blue"><o:p>&nbsp;</o:p></span></font></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center" tabindex=3D"-1">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span style=3D"f=
ont-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font size=3D"2=
" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font-family:Tahoma"> ipv6=
-bounces@ietf.org [mailto:ipv6-bounces@ietf.org]
<b><span style=3D"font-weight:
bold">On Behalf Of </span></b>Park, Kundok<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Monday, December 19, 2=
011 1:18 PM<br>
<b><span style=3D"font-weight:bold">To:</span></b> ipv6@ietf.org<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> draft-ietf-6man-rpl=
-routing-header-07</span></font><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">It seems that the following text on page 10 has some sli=
ght oversights:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;<o:p></o:p></span></font></p>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; In order to respect the IPv6 Hop Limit value of the original<=
o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; datagram, a RPL router generating an SRH MUST set the Segment=
s Left<o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; to <u>no greater</u> than the original datagram's IPv6 Hop Li=
mit value upon<o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; forwarding.<o:p></o:p></span></font></pre>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">should have been as follows:<o:p></o:p></span></font></p=
>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;<o:p></o:p></span></font></p>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; In order to respect the IPv6 Hop Limit value of the original<=
o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; datagram, a RPL router generating an SRH <u>in an IPv6-in-IPv=
6 tunnel</u><o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp;&nbsp; MUST set the Segments Left to <u>less</u> than the original d=
atagram's IPv6<o:p></o:p></span></font></pre>
<pre><font size=3D"2" face=3D"Courier New"><span style=3D"font-size:10.0pt"=
>&nbsp; &nbsp;Hop Limit value upon forwarding.<o:p></o:p></span></font></pr=
e>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">If the Segments Left is equal to Hop Limit value, the so=
urce route includes one more hop than the hop limit, which is not intended =
here.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">The other change is to make clear that the above phrase =
does not apply to the case where the SRH is directly included within the or=
iginal packet.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">As a side note, the traceroute application doesn&#8217;t=
 seem to be able to handle the case with no tunnel use, because the origina=
l datagram destination address alters
 when SRH is added, unless, I guess, traceroute application is re-written t=
o handle source routing in returned ICMPv6 error messages. Perhaps, that re=
commended direct inclusion of SRH should be removed?<o:p></o:p></span></fon=
t></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">Best Regards,<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">Kundok<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
</div>
</div>
</body>
</html>

--_000_055FAFECB2B53642884D29B0094D1475109809D8DLEE10entticom_--

From Tina.Tsou.Zouting@huawei.com  Mon Dec 19 16:39:21 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 5E9A621F8477; Mon, 19 Dec 2011 16:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[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 5TJN6S-0X4WY; Mon, 19 Dec 2011 16:39:20 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 1E73821F8462; Mon, 19 Dec 2011 16:39:20 -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 <0LWH001ZY8HBIM@szxga04-in.huawei.com>; Tue, 20 Dec 2011 08:39:11 +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 <0LWH002WD8HA1Q@szxga04-in.huawei.com>; Tue, 20 Dec 2011 08:39:11 +0800 (CST)
Received: from szxeml206-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFU52928; Tue, 20 Dec 2011 08:39:10 +0800
Received: from SZXEML416-HUB.china.huawei.com (10.82.67.155) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 20 Dec 2011 08:39:08 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.37]) by szxeml416-hub.china.huawei.com ([10.82.67.155]) with mapi id 14.01.0323.003; Tue, 20 Dec 2011 08:39:03 +0800
Date: Tue, 20 Dec 2011 00:39:02 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: RE: Question on IPV4/IPV6 Multicast interoperability
In-reply-to: <1324206855.51664.YahooMailNeo@web121801.mail.ne1.yahoo.com>
X-Originating-IP: [10.193.34.145]
To: Ghanashyam Satpathy <ghanashyam_satpathy@yahoo.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C22F04F@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_f/BsSJ6RYBqOdKm0ahN7+w)"
Content-language: en-US
Accept-Language: en-US, zh-CN
Thread-topic: Question on IPV4/IPV6 Multicast interoperability
Thread-index: AQHMvpzl8eODnaBst02N8+9ZmITwy5Xj4SAA
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <1324206855.51664.YahooMailNeo@web121801.mail.ne1.yahoo.com>
Cc: MBONED WG <mboned@ietf.org>, "multrans@ietf.org" <multrans@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, 20 Dec 2011 00:39:21 -0000

--Boundary_(ID_f/BsSJ6RYBqOdKm0ahN7+w)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Ghanashyam,
http://datatracker.ietf.org/doc/draft-tsou-multrans-addr-acquisition/
http://datatracker.ietf.org/doc/draft-zhou-multrans-af1-specification/
Running code exists.
Hope it helps.

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html

From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Ghanashyam Satpathy
Sent: Sunday, December 18, 2011 3:14 AM
To: ipv6@ietf.org
Subject: Question on IPV4/IPV6 Multicast interoperability

Hello,

I have a question on IPV4/IPV6 Multicast interoperability. We have succesfully upgraded our application(Windows Based) to support IPV6 and faced issue on multicast interoperability. Multicast messages sent by a IPV6 server is successfully receved by a client running on IPV6. But any client running on IPV4 is not able to receive the message.

Quite a no. of things I tried like using IPV4 mapped IPV6 address and V4 embeded V6 adress.But nothing seems to be working.Would like to know an unified way so that one multicast message sent by an IPV6 server should be received by both V6 and V4 client.

Would be great if somebody can send some code snippet(C/C++) on it.

Thanks.

Ghanashyam





--Boundary_(ID_f/BsSJ6RYBqOdKm0ahN7+w)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 12">
<meta name="Originator" content="Microsoft Word 12">
<link rel="File-List" href="cid:filelist.xml@01CCBE6C.B53C6000"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
<o:TargetScreenSize>1024x768</o:TargetScreenSize>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>210</w:Zoom>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>ZH-CN</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:DontVertAlignCellWithSp/>
<w:DontBreakConstrainedForcedTables/>
<w:DontVertAlignInTxbx/>
<w:Word11KerningPairs/>
<w:CachedColBalance/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="&#45;-"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true" DefSemiHidden="true" DefQFormat="false" DefPriority="99" LatentStyleCount="267">
<w:LsdException Locked="false" Priority="0" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" Priority="39" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" Name="toc 9"/>
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" Priority="10" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" Priority="11" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" Priority="22" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" Priority="59" SemiHidden="false" UnhideWhenUsed="false" Name="Table Grid"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:SimSun;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-alt:"Calisto MT";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1107304683 0 0 159 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-alt:"Times New Roman";
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1610611985 1073750139 0 0 159 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-alt:Verdana;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:1627400839 -2147483648 8 0 66047 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:???????????????????????????????;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:SimSun;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:SimSun;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="tab-interval:.5in">
<div class="WordSection1">
<p class="MsoNormal" style="background:white"><span class="SpellE"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">Ghanashyam</span></span><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D"><a href="http://datatracker.ietf.org/doc/draft-tsou-multrans-addr-acquisition/">http://datatracker.ietf.org/doc/draft-tsou-multrans-addr-acquisition/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D"><a href="http://datatracker.ietf.org/doc/draft-zhou-multrans-af1-specification/">http://datatracker.ietf.org/doc/draft-zhou-multrans-af1-specification/</a><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D;mso-no-proof:yes">Running code exists.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D;mso-no-proof:yes">Hope it helps.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D;mso-no-proof:yes"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D;mso-no-proof:yes">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D;mso-no-proof:yes">Tina TSOU<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D;mso-no-proof:yes">http://tinatsou.weebly.com/contact.html<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:&quot;Times New Roman&quot;">From:</span></b><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:&quot;Times New Roman&quot;"> ipv6-bounces@ietf.org
 [mailto:ipv6-bounces@ietf.org] <b>On Behalf Of </b>Ghanashyam Satpathy<br>
<b>Sent:</b> Sunday, December 18, 2011 3:14 AM<br>
<b>To:</b> ipv6@ietf.org<br>
<b>Subject:</b> Question on IPV4/IPV6 Multicast interoperability<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">Hello,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">I have a question on IPV4/IPV6 Multicast interoperability. We have succesfully upgraded our application(Windows Based)&nbsp;to support IPV6 and faced
 issue on multicast interoperability. Multicast messages sent by a IPV6 server is successfully receved by a client running on IPV6. But any client running on IPV4 is not able to receive the message.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">Quite a no. of things I tried like using IPV4 mapped IPV6 address and V4 embeded V6 adress.But nothing seems to be working.Would like to know an
 unified way so that one multicast message sent by an IPV6 server should be received by both V6 and V4 client.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">Would be great if somebody can send some code snippet(C/C&#43;&#43;) on it.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">Thanks.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">Ghanashyam<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="mso-fareast-font-family:&quot;Times New Roman&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--Boundary_(ID_f/BsSJ6RYBqOdKm0ahN7+w)--

From brian.e.carpenter@gmail.com  Mon Dec 19 17:22:28 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 3713021F84A3 for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 17:22:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.358
X-Spam-Level: 
X-Spam-Status: No, score=-103.358 tagged_above=-999 required=5 tests=[AWL=0.241, 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 XfMEOuIlLZj4 for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 17:22:26 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id A19AA21F84A2 for <ipv6@ietf.org>; Mon, 19 Dec 2011 17:22:26 -0800 (PST)
Received: by werb14 with SMTP id b14so1942338wer.31 for <ipv6@ietf.org>; Mon, 19 Dec 2011 17:22:24 -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=2jBm/PA+/Se2WeCeVQNfMGblpfPSoUhKwk832Pipk/w=; b=DY8M/EQEYI/aeNKYttgiLTeyyJoaF/IbMbNKQy4hiK+oh7lja6gTuZeTi1fJ5NN+ET UtkX7RYGyYZxkjtDJHYovZcNsFezSR5qZ+rbhYlrAJ5b2i7+3Gg9gG+7l7iukn2gSOhv WNlKn478v6qvLBFuNjlA3a1cZecnjJD4A3cKA=
Received: by 10.216.131.141 with SMTP id m13mr5476860wei.30.1324344143580; Mon, 19 Dec 2011 17:22:23 -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 em4sm18104wbb.20.2011.12.19.17.22.20 (version=SSLv3 cipher=OTHER); Mon, 19 Dec 2011 17:22:22 -0800 (PST)
Message-ID: <4EEFE34A.4010408@gmail.com>
Date: Tue, 20 Dec 2011 14:22: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: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
References: <4EB3F3D6.4090302@innovationslab.net>	<CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com>	<4EEA3D20.7020603@innovationslab.net>	<CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com>	<4EEA5793.8080800@gmail.com>	<CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com>	<4EEA7AF8.2090508@gmail.com>	<CAKFn1SFp_r7EJ6CpM8EF2zkcJz1z34CdEcRt2i5xcsrWkCBQwQ@mail.gmail.com>	<0D0150C3-9E05-4839-ACF1-0E7196420D2F@ecs.soton.ac.uk> <EMEW3|bd681ced736eee0700e443f9acc256d8nBFAnB03tjc|ecs.soton.ac.uk|0D0150C3-9E05-4839-ACF1-0E7196420D2F@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|bd681ced736eee0700e443f9acc256d8nBFAnB03tjc|ecs.soton.ac.uk|0D0150C3-9E05-4839-ACF1-0E7196420D2F@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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: Tue, 20 Dec 2011 01:22:28 -0000

Seems to me we all agree on this much:

>> First getting this one out since it fix something quite broken,

Regards
   Brian

On 2011-12-16 23:49, Tim Chown wrote:
> Well, there are two questions here.
>=20
> One is whether the WG believes the update as described in draft-ietf-6m=
an-rfc3484-revise-05 is correct and complete.  I have not seen (yet) any =
significant technical concerns raised.  The last of those were discussed =
and (we believe) resolved in Quebec.  Are there any more?
>=20
> The other is whether the WG believes we should publish an update, or a =
complete fresh version of RFC3484.  This was discussed previously in the =
WG and the update path preferred.  If a fresh version is now deemed more =
appropriate, I am fine to work on that with the other authors if required=
=2E
>=20
> We just need a decision so we can progress this - it's been so close to=
 release for a long time.  Many of the changes in the update have been im=
plemented in a number of platforms already.
>=20
> Tim
>=20
> On 16 Dec 2011, at 09:38, Roger J=C3=B8rgensen wrote:
>=20
>> On Thu, Dec 15, 2011 at 11:55 PM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>>> Roger,
>>>
>>> On 2011-12-16 10:52, Roger J=C3=B8rgensen wrote:
>>>> On Thu, Dec 15, 2011 at 9:24 PM, Brian E Carpenter
>>>> <brian.e.carpenter@gmail.com> wrote:
>>>>> Well, the end of my conversation is at
>>>>>
>>>>> http://www.ietf.org/mail-archive/web/ipv6/current/msg14948.html
>>>>>
>>>>> Summary: "an update that makes it easy for the implementer to find =
the changes is better."
>>>>>
>>>>> If it wasn't clear, I believe this document is technically done and=
 needs
>>>>> to be advanced, but it does need editorial work as indicated above.=

>>>> Hmm sorry for being unclear, the technical part looked okay as far a=
s
>>>> I could tell, but as the quoted words from you, it will probably be
>>>> more confusing to have two documents where the last one update/chang=
e
>>>> the first one. Would be much better to have just one
>>>> replacing/updating the old one.
>>> That was my first thought, but then I realised it would cause a lot
>>> of delay, and I think getting these changes deployed is quite urgent.=

>> what about doing it in two step? First getting this one out since it f=
ix
>> something quite broken, and then update the old RFC?
>>
>>
>>
>> --=20
>>
>> Roger Jorgensen           |
>> rogerj@gmail.com          | - IPv6 is The Key!
>> http://www.jorgensen.no   | roger@jorgensen.no
>> --------------------------------------------------------------------
>> 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


From manav.bhatia@alcatel-lucent.com  Mon Dec 19 17:24:00 2011
Return-Path: <manav.bhatia@alcatel-lucent.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 60BF821F84D8 for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 17:24: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 bS8OwTYVzKao for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 17:24:00 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id D424421F84D4 for <ipv6@ietf.org>; Mon, 19 Dec 2011 17:23:59 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id pBK1Ntl1004319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ipv6@ietf.org>; Mon, 19 Dec 2011 19:23:58 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBK1Nt0A012508 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <ipv6@ietf.org>; Tue, 20 Dec 2011 06:53:55 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Tue, 20 Dec 2011 06:53:55 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: 6man Mailing List <ipv6@ietf.org>
Date: Tue, 20 Dec 2011 06:54:01 +0530
Subject: IPv6 Router Advertisement Option for NTP Server Configuration 
Thread-Topic: IPv6 Router Advertisement Option for NTP Server Configuration 
Thread-Index: Acy+tg3VjAjJ4WUEQsObyt9zgXl5RA==
Message-ID: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.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-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
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, 20 Dec 2011 01:24:00 -0000

Hi,

We have posted a new draft that extends Router Advertisements to include in=
formation about the one or more NTP servers present in the network. This is=
 useful where the delays in acquiring server addresses and communicating wi=
th the servers are critical (mobile environment for example).=20

http://www.ietf.org/internet-drafts/draft-bcd-6man-ntp-server-ra-opt-00.txt=
=20

Would be great to get some feedback from the WG.

We will also be soliciting comments from the NTP and the TICTOC WGs.

Cheers, Manav=

From ghanashyam_satpathy@yahoo.com  Mon Dec 19 19:51:34 2011
Return-Path: <ghanashyam_satpathy@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 9FF4711E80C3 for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 19:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.982
X-Spam-Level: ***
X-Spam-Status: No, score=3.982 tagged_above=-999 required=5 tests=[AWL=-2.867,  BAYES_20=-0.74, FRT_STOCK2=3.988, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_64=0.6, J_CHICKENPOX_66=0.6, J_CHICKENPOX_73=0.6, J_CHICKENPOX_84=0.6]
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 unnqCMvyLRyX for <ipv6@ietfa.amsl.com>; Mon, 19 Dec 2011 19:51:33 -0800 (PST)
Received: from nm35-vm2.bullet.mail.ne1.yahoo.com (nm35-vm2.bullet.mail.ne1.yahoo.com [98.138.229.98]) by ietfa.amsl.com (Postfix) with SMTP id 9471D11E80B6 for <ipv6@ietf.org>; Mon, 19 Dec 2011 19:51:32 -0800 (PST)
Received: from [98.138.90.55] by nm35.bullet.mail.ne1.yahoo.com with NNFMP; 20 Dec 2011 03:51:26 -0000
Received: from [98.138.89.168] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 20 Dec 2011 03:51:26 -0000
Received: from [127.0.0.1] by omp1024.mail.ne1.yahoo.com with NNFMP; 20 Dec 2011 03:51:26 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 294836.93835.bm@omp1024.mail.ne1.yahoo.com
Received: (qmail 78162 invoked by uid 60001); 20 Dec 2011 03:51:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1324353086; bh=tVTec2s28AQa3/QsjxPGPm9YPXhZlQ6VAesGyuC1Heo=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=LQi7H/dnqrhxBLKfWen0Q2IrrwD2kZ0DlpJU9XAdUII1lfXn9svV2OLPPPAL1R3qaY9ICj9YAbX1MFvYBo0Td6yxN3Y+kTQezH9ODf1cx0hW7g9iWwhtIBhcB/f+jNv0aR/tu78SgX3RAZGHIGtD6ZMIc5ScK3xhNFufRACf/os=
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; b=pOaMMYq16VRlLrmPsIvl8l6ehujSAW8ud+MDfq3xrObo/vfRkfLIdOilwB863sQDLB3gz2Yl9s2AaIZwQL3UyjJIuLp/ibf6inkgjGVCCjTC9n6SovXQsi6z673Sj/wTcIDmRB/02WKZJkrAbRxL/AyzOXgcaUIVApaPhNW6t9I=;
X-YMail-OSG: XiNNfEcVM1k9Crh1mn4PlW8HUtEXZZz47Svozma0JiwGiO2 J030tGCUK6kDXRymmKTYlxaA4Lt9j_AxY1bQ8LXnbJbqJgY9yPE8DnSsQkgT QvjOJs6wUWxYYwmYcn8l6_F1woMjhW2X0uhQLlY300pOhHa2FsVokaeImqjV BCkFPxJffn0cEbWkfejKds0DinTg8jyPBra0tZY9HrYhkRTfk0nUdqELQIcz fKs.VNka2bBUlyLLpukRkp71LuGMdsgwhxLYF0oc4vA6h8E5nAv6dujdg71x ybos10Bc6HgrY4fXIjOA0cwtCwv3tAa2ykY6sl1j3yK8dHPA8MtxDP167PHg x4dGLzsRyjzhEA83fEolwhUhSXnA6vZJBeE59F6qhXbR1vmwgNEnXafYcmw5 o035XNpnkP8X3jWHq4Y7rRU.eJwkYvCnSaVltBl6lc09nVgOkuvu9wHVWLQS jbyiVIdVzsJ5FeiZ6h._ATZ3tiWoXbs_T8YQxkdlqGcfMdY9UfYW3GVOIgnr SK7xLca8dy2BfEzx0xC0CBCRlf3eVOx5FujPlxT7pQRuqPNqZOEnO2B8-
Received: from [182.71.249.226] by web121803.mail.ne1.yahoo.com via HTTP; Mon, 19 Dec 2011 19:51:25 PST
X-Mailer: YahooMailWebService/0.8.115.331698
References: <1324206855.51664.YahooMailNeo@web121801.mail.ne1.yahoo.com> <C0E0A32284495243BDE0AC8A066631A80C22F04F@szxeml526-mbx.china.huawei.com>
Message-ID: <1324353085.77877.YahooMailNeo@web121803.mail.ne1.yahoo.com>
Date: Mon, 19 Dec 2011 19:51:25 -0800 (PST)
From: Ghanashyam Satpathy <ghanashyam_satpathy@yahoo.com>
Subject: Re: Question on IPV4/IPV6 Multicast interoperability
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "ipv6@ietf.org" <ipv6@ietf.org>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C22F04F@szxeml526-mbx.china.huawei.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-877950688-1063082605-1324353085=:77877"
X-Mailman-Approved-At: Tue, 20 Dec 2011 01:16:21 -0800
Cc: MBONED WG <mboned@ietf.org>, "multrans@ietf.org" <multrans@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ghanashyam Satpathy <ghanashyam_satpathy@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, 20 Dec 2011 03:51:34 -0000

---877950688-1063082605-1324353085=:77877
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Tina,=0A=A0=0AThanks for the reply and understands the theory but una=
ble to make it in my code.=0A=A0=0AHere is my server and client=A0code,=A0b=
oth can be compiled as a console app in windows.And run as =0A=A0=0Amultica=
st_server 224.0.22.1 9210 HelloIPv4World=0Amulticast_server ff15::1 2001 He=
lloIPv6World=0A=A0=0Amulticast_client 224.0.22.1 9210=0Amulticast_client ff=
15::1 2001=0A=0AFor the sample code if the server runs as IPV6 (multicast_s=
erver ff15::1 2001 HelloIPv6World)=A0then cleint running in IPV6 (multicast=
_client ff15::1 2001) receives the multicast message.But the client running=
 in IPV4 does not receive the multicast message.=0A=A0=0AI want to run the =
server so that both IPV4 and IPV6 client can receive the multicast messages=
.How to do that ,some C/C++ code sample will be great.=0A=A0=0AThanks=0A=A0=
=0AGhanashyam=0A=A0=0A=A0=0A=A0=0A=A0=0A// server.cpp : Defines the entry p=
oint for the console application.=0A//=0A/* multicast_server.c=0A=A0* This =
sample demonstrates a Windows multicast server that works with either=0A=A0=
* IPv4 or IPv6, depending on the multicast address given.=0A=A0* Requires W=
indows XP+/Use MSVC and platform SDK to compile.=0A=A0* Troubleshoot: Make =
sure you have the IPv6 stack installed by running=0A=A0*=A0=A0=A0=A0 >ipv6 =
install=0A=A0*=0A=A0* Usage:=0A=A0*=A0=A0=A0=A0 multicast_server multicasti=
p port data [ttl]=0A=A0*=0A=A0* Examples:=0A=A0*=A0=A0=A0=A0 >multicast_ser=
ver 224.0.22.1 9210 HelloIPv4World=0A=A0*=A0=A0=A0=A0 >multicast_server ff1=
5::1 2001 HelloIPv6World=0A=A0*=0A#include <stdio.h>=A0=A0=A0=A0=A0 /* for =
fprintf() */=0A=A0#include <winsock2.h> /* for socket(), connect(), send(),=
 and recv() */=0A#include <ws2tcpip.h>=A0=A0 /* for ip options */=0A#includ=
e <stdlib.h>=A0=A0=A0=A0 /* for atoi() and exit() */=0A=0A#if defined(_MSC_=
VER)=0A#pragma comment(lib, "ws2_32.lib")=0A#endif=0A=0A=0Astatic void DieW=
ithError(char* errorMessage)=0A{=0A=A0=A0=A0 fprintf(stderr, "%s\n", errorM=
essage);=0A=A0=A0=A0 exit(EXIT_FAILURE);=0A}=0A=0A=0Aint main(int argc, cha=
r *argv[])=0A{=0A=A0=A0=A0 SOCKET=A0=A0=A0 sock;=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Socket */=0A=A0=A0=A0 WSADATA=A0=A0 wsaData;=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* For WSAStartup */=0A=A0=A0=
=A0 char*=A0=A0=A0=A0 multicastIP;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Arg:=
 IP Multicast address */=0A=A0=A0=A0 char*=A0=A0=A0=A0 multicastPort;=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 /* Arg: Server port */=0A=A0=A0=A0 char*=A0=A0=A0=A0 =
sendString;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Arg: String to multicast=
 */=0A=A0=A0=A0 size_t=A0=A0=A0 sendStringLen;=A0=A0=A0=A0=A0=A0=A0=A0=A0 /=
* Length of string to multicast */=0A=A0=A0=A0 DWORD=A0=A0=A0=A0 multicastT=
TL;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Arg: TTL of multicast packets */=0A=A0=
=A0=A0 ADDRINFO* multicastAddr;=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Multicast add=
ress */=0A=A0=A0=A0 ADDRINFO=A0 hints=A0=A0=A0=A0=A0=A0=A0=A0=A0 =3D { 0 };=
 /* Hints for name lookup */=0A=0A=A0=A0=A0 if ( WSAStartup(MAKEWORD(2, 2),=
 &wsaData) !=3D 0)=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 DieWithError("WSAS=
tartup() failed");=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 if ( argc < 4 || argc > 5 )=
=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 fprintf(stderr, "Usage:=A0 %s <Multi=
cast Address> <Port> <Send String> [<TTL>]\n", argv[0]);=0A=A0=A0=A0=A0=A0=
=A0=A0 exit(EXIT_FAILURE);=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 multicastIP=A0=A0 =
=3D argv[1];=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* First arg:=A0=A0 multic=
ast IP address */=0A=A0=A0=A0 multicastPort =3D argv[2];=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 /* Second arg:=A0 multicast port */=0A=A0=A0=A0 sendStri=
ng=A0=A0=A0 =3D argv[3];=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Third arg:=
=A0=A0 String to multicast */=0A=A0=A0=A0 multicastTTL=A0 =3D (argc =3D=3D =
5 ?=A0=A0=A0=A0=A0=A0=A0=A0 /* Fourth arg:=A0 If supplied, use command-line=
 */=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 atoi(arg=
v[4]) : 1); /* specified TTL, else use default TTL of 1 */=0A=A0=A0=A0 send=
StringLen =3D strlen(sendString);=A0 /* Find length of sendString */=0A=0A=
=A0=A0=A0 /* Resolve destination address for multicast datagrams */=0A=A0=
=A0=A0 hints.ai_family=A0=A0 =3D PF_UNSPEC;=0A=A0=A0=A0 hints.ai_socktype =
=3D SOCK_DGRAM;=0A=A0=A0=A0 hints.ai_flags=A0=A0=A0 =3D AI_NUMERICHOST;=0A=
=A0=A0=A0 if ( getaddrinfo(multicastIP, multicastPort, &hints, &multicastAd=
dr) !=3D 0 )=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 DieWithError("getaddrinf=
o() failed");=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 printf("Using %s\n", multicastAd=
dr->ai_family =3D=3D PF_INET6 ? "IPv6" : "IPv4");=0A=0A=A0=A0=A0 /* Create =
socket for sending multicast datagrams */=0A=A0=A0=A0 if ( (sock =3D socket=
(multicastAddr->ai_family, multicastAddr->ai_socktype, 0)) =3D=3D INVALID_S=
OCKET )=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 DieWithError("socket() failed=
");=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 /* Set TTL of multicast packet */=0A=A0=A0=
=A0 if ( setsockopt(sock,=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 multicastAddr->ai_family =3D=3D PF_INET6 ? IPPROTO_IPV6=A0=A0=
=A0=A0=A0=A0=A0 : IPPROTO_IP,=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 multicastAddr->ai_family =3D=3D PF_INET6 ? IPV6_MULTICAST_H=
OPS : IP_MULTICAST_TTL,=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 (char*) &multicastTTL, sizeof(multicastTTL)) !=3D 0 )=0A=A0=A0=A0=
 {=0A=A0=A0=A0=A0=A0=A0=A0 DieWithError("setsockopt() failed");=0A=A0=A0=A0=
 }=0A=0A=A0=A0=A0 for (;;) /* Run forever */=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=
=A0=A0=A0 if ( sendto(sock, sendString, sendStringLen, 0,=0A=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 multicastAddr->ai_addr, multicas=
tAddr->ai_addrlen) !=3D sendStringLen )=0A=A0=A0=A0=A0=A0=A0=A0 {=0A=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0 DieWithError("sendto() sent a different number =
of bytes than expected");=0A=A0=A0=A0=A0=A0=A0=A0 }=0A=0A=A0=A0=A0=A0=A0=A0=
=A0 Sleep(3000); /* Multicast sendString in datagram to clients every 3 sec=
onds */=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 /* NOT REACHED */=0A=A0=A0=A0 freeaddr=
info(multicastAddr);=0A=A0=A0=A0 closesocket(sock);=0A=A0=A0=A0 return 0;=
=0A} =0A=A0=0A=A0=0A// client.cpp : Defines the entry point for the console=
 application.=0A//=0A=A0=0A=0A/* multicast_client.c=0A=A0* This sample demo=
nstrates a Windows multicast client that works with either=0A=A0* IPv4 or I=
Pv6, depending on the multicast address given.=0A=A0* Requires Windows XP+/=
Use MSVC and platform SDK to compile.=0A=A0* Troubleshoot: Make sure you ha=
ve the IPv6 stack installed by running=0A=A0*=A0=A0=A0=A0 >ipv6 install=0A=
=A0*=0A=A0* Usage:=0A=A0*=A0=A0=A0=A0 multicast_client multicastip port=0A=
=A0*=0A=A0* Examples:=0A=A0*=A0=A0=A0=A0 >multicast_client 224.0.22.1 9210=
=0A=A0*=A0=A0=A0=A0 >multicast_client ff15::1 2001=0A=A0*=0A=A0#include <st=
dio.h>=A0=A0=A0=A0=A0 /* for printf() and fprintf() */=0A#include <winsock2=
.h>=A0=A0 /* for socket(), connect(), sendto(), and recvfrom() */=0A#includ=
e <ws2tcpip.h>=A0=A0 /* for ip_mreq */=0A#include <stdlib.h>=A0=A0=A0=A0 /*=
 for atoi() and exit() */=0A#include <string.h>=A0=A0=A0=A0 /* for memset()=
 */=0A#include <time.h>=A0=A0=A0=A0=A0=A0 /* for timestamps */=0A=0A#if def=
ined(_MSC_VER)=0A#pragma comment(lib, "ws2_32.lib")=0A#endif=0A=0A=0Avoid D=
ieWithError(char* errorMessage)=0A{=0A=A0=A0=A0 fprintf(stderr, "%s\n", err=
orMessage);=0A=A0=A0=A0 exit(EXIT_FAILURE);=0A}=0A=0A=0Aint main(int argc, =
char* argv[])=0A{=0A=A0=A0=A0 SOCKET=A0=A0=A0=A0 sock;=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Socket */=0A=A0=A0=A0 WSADATA=A0=
=A0=A0 wsaData;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* For W=
SAStartup */=0A=A0=A0=A0 char*=A0=A0=A0=A0=A0 multicastIP;=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 /* Arg: IP Multicast Address */=0A=A0=A0=A0 char*=
=A0=A0=A0=A0=A0 multicastPort;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Arg: Por=
t */=0A=A0=A0=A0 ADDRINFO*=A0 multicastAddr;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 /* Multicast Address */=0A=A0=A0=A0 ADDRINFO*=A0 localAddr;=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* Local address to bind to */=0A=A0=A0=
=A0 ADDRINFO=A0=A0 hints=A0=A0=A0=A0=A0=A0=A0=A0=A0 =3D { 0 };=A0=A0 /* Hin=
ts for name lookup */=0A=0A=A0=A0=A0 if ( WSAStartup(MAKEWORD(2, 2), &wsaDa=
ta) !=3D 0)=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 DieWithError("WSAStartup(=
) failed");=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 if ( argc !=3D 3 )=0A=A0=A0=A0 {=
=0A=A0=A0=A0=A0=A0=A0=A0 fprintf(stderr,"Usage: %s <Multicast IP> <Multicas=
t Port>\n", argv[0]);=0A=A0=A0=A0=A0=A0=A0=A0 exit(EXIT_FAILURE);=0A=A0=A0=
=A0 }=0A=0A=A0=A0=A0 multicastIP=A0=A0 =3D argv[1];=A0=A0=A0=A0=A0 /* First=
 arg:=A0 Multicast IP address */=0A=A0=A0=A0 multicastPort =3D argv[2];=A0=
=A0=A0=A0=A0 /* Second arg: Multicast port */=0A=0A=A0=A0=A0 /* Resolve the=
 multicast group address */ hints.ai_family =3D PF_UNSPEC; hints.ai_flags =
=3D AI_NUMERICHOST; if ( getaddrinfo(multicastIP, NULL, &hints, &multicastA=
ddr) !=3D 0 ) { DieWithError("getaddrinfo() failed"); } printf("Using %s\n"=
, multicastAddr->ai_family =3D=3D PF_INET6 ? "IPv6" : "IPv4"); /* Get a loc=
al address with the same family (IPv4 or IPv6) as our multicast group */=0A=
=A0=A0=A0 hints.ai_family=A0=A0 =3D multicastAddr->ai_family;=0A=A0=A0=A0 h=
ints.ai_socktype =3D SOCK_DGRAM;=0A=A0=A0=A0 hints.ai_flags=A0=A0=A0 =3D AI=
_PASSIVE; /* Return an address we can bind to */=0A=A0=A0=A0 if ( getaddrin=
fo(NULL, multicastPort, &hints, &localAddr) !=3D 0 )=0A=A0=A0=A0 {=0A=A0=A0=
=A0=A0=A0=A0=A0 DieWithError("getaddrinfo() failed");=0A=A0=A0=A0 }=0A=0A=
=A0=A0=A0 /* Create socket for receiving datagrams */=0A=A0=A0=A0 if ( (soc=
k =3D socket(localAddr->ai_family, localAddr->ai_socktype, 0)) =3D=3D INVAL=
ID_SOCKET )=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 DieWithError("socket() fa=
iled");=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 /* Bind to the multicast port */=0A=A0=
=A0=A0 if ( bind(sock, localAddr->ai_addr, localAddr->ai_addrlen) !=3D 0 )=
=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 DieWithError("bind() failed");=0A=A0=
=A0=A0 }=0A=0A=A0=A0=A0 /* Join the multicast group. We do this seperately =
depending on whether we=0A=A0=A0=A0=A0 * are using IPv4 or IPv6. WSAJoinLea=
f is supposed to be IP version agnostic=0A=A0=A0=A0=A0 * but it looks more =
complex than just duplicating the required code. */=0A=A0=A0=A0 if ( multic=
astAddr->ai_family=A0 =3D=3D PF_INET &&=A0 =0A=A0=A0=A0=A0=A0=A0=A0=A0 mult=
icastAddr->ai_addrlen =3D=3D sizeof(struct sockaddr_in) ) /* IPv4 */=0A=A0=
=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 struct ip_mreq multicastRequest;=A0 /* Mul=
ticast address join structure */=0A=0A=A0=A0=A0=A0=A0=A0=A0 /* Specify the =
multicast group */=0A=A0=A0=A0=A0=A0=A0=A0 memcpy(&multicastRequest.imr_mul=
tiaddr,=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 &((struct sockaddr_in*=
)(multicastAddr->ai_addr))->sin_addr,=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 sizeof(multicastRequest.imr_multiaddr));=0A=0A=A0=A0=A0=A0=A0=A0=
=A0 /* Accept multicast from any interface */=0A=A0=A0=A0=A0=A0=A0=A0 multi=
castRequest.imr_interface.s_addr =3D htonl(INADDR_ANY);=0A=0A=A0=A0=A0=A0=
=A0=A0=A0 /* Join the multicast address */=0A=A0=A0=A0=A0=A0=A0=A0 if ( set=
sockopt(sock, IPPROTO_IP, IP_ADD_MEMBERSHIP, (char*) &multicastRequest, siz=
eof(multicastRequest)) !=3D 0 )=0A=A0=A0=A0=A0=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 DieWithError("setsockopt() failed");=0A=A0=A0=A0=A0=A0=
=A0=A0 }=0A=A0=A0=A0 }=0A=A0=A0=A0 else if ( multicastAddr->ai_family=A0 =
=3D=3D PF_INET6 &&=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 multicastAddr-=
>ai_addrlen =3D=3D sizeof(struct sockaddr_in6) ) /* IPv6 */=0A=A0=A0=A0 {=
=0A=A0=A0=A0=A0=A0=A0=A0 struct ipv6_mreq multicastRequest;=A0 /* Multicast=
 address join structure */=0A=0A=A0=A0=A0=A0=A0=A0=A0 /* Specify the multic=
ast group */=0A=A0=A0=A0=A0=A0=A0=A0 memcpy(&multicastRequest.ipv6mr_multia=
ddr,=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 &((struct sockaddr_in6*)(=
multicastAddr->ai_addr))->sin6_addr,=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 sizeof(multicastRequest.ipv6mr_multiaddr));=0A=0A=A0=A0=A0=A0=A0=A0=
=A0 /* Accept multicast from any interface */=0A=A0=A0=A0=A0=A0=A0=A0 multi=
castRequest.ipv6mr_interface =3D 0;=0A=0A=A0=A0=A0=A0=A0=A0=A0 /* Join the =
multicast address */=0A=A0=A0=A0=A0=A0=A0=A0 if ( setsockopt(sock, IPPROTO_=
IPV6, IPV6_ADD_MEMBERSHIP, (char*) &multicastRequest, sizeof(multicastReque=
st)) !=3D 0 )=0A=A0=A0=A0=A0=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
 DieWithError("setsockopt() failed");=0A=A0=A0=A0=A0=A0=A0=A0 }=0A=A0=A0=A0=
 }=0A=A0=A0=A0 else=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 DieWithError("Nei=
ther IPv4 or IPv6");=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 freeaddrinfo(localAddr);=
=0A=A0=A0=A0 freeaddrinfo(multicastAddr);=0A=0A=A0=A0=A0 for (;;) /* Run fo=
rever */=0A=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0 time_t timer;=0A=A0=A0=A0=A0=
=A0=A0=A0 char=A0=A0 recvString[500];=A0=A0=A0=A0=A0 /* Buffer for received=
 string */=0A=A0=A0=A0=A0=A0=A0=A0 int=A0=A0=A0 recvStringLen;=A0=A0=A0=A0=
=A0=A0=A0 /* Length of received string */=0A=0A=A0=A0=A0=A0=A0=A0=A0 /* Rec=
eive a single datagram from the server */=0A=A0=A0=A0=A0=A0=A0=A0 if ( (rec=
vStringLen =3D recvfrom(sock, recvString, sizeof(recvString) - 1, 0, NULL, =
0)) < 0 )=0A=A0=A0=A0=A0=A0=A0=A0 {=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Die=
WithError("recvfrom() failed");=0A=A0=A0=A0=A0=A0=A0=A0 }=0A=0A=A0=A0=A0=A0=
=A0=A0=A0 recvString[recvStringLen] =3D '\0';=0A=0A=A0=A0=A0=A0=A0=A0=A0 /*=
 Print the received string */=0A=A0=A0=A0=A0=A0=A0=A0 time(&timer);=A0 /* g=
et time stamp to print with recieved data */=0A=A0=A0=A0=A0=A0=A0=A0 printf=
("Time Received: %.*s : %s\n", strlen(ctime(&timer)) - 1, ctime(&timer), re=
cvString);=0A=A0=A0=A0 }=0A=0A=A0=A0=A0 /* NOT REACHED */=0A=A0=A0=A0 close=
socket(sock);=0A=A0=A0=A0 exit(EXIT_SUCCESS);=0A}=0AFrom: Tina TSOU <Tina.T=
sou.Zouting@huawei.com>=0ATo: Ghanashyam Satpathy <ghanashyam_satpathy@yaho=
o.com>; "ipv6@ietf.org" <ipv6@ietf.org> =0ACc: "multrans@ietf.org" <multran=
s@ietf.org>; MBONED WG <mboned@ietf.org> =0ASent: Tuesday, December 20, 201=
1 6:09 AM=0ASubject: RE: Question on IPV4/IPV6 Multicast interoperability=
=0A=0A=0AGhanashyam,=0Ahttp://datatracker.ietf.org/doc/draft-tsou-multrans-=
addr-acquisition/=0Ahttp://datatracker.ietf.org/doc/draft-zhou-multrans-af1=
-specification/=0ARunning code exists.=0AHope it helps.=0A=A0=0ABest Regard=
s,=0ATina TSOU=0Ahttp://tinatsou.weebly.com/contact.html=0A=A0=0AFrom:ipv6-=
bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Ghanashyam Sat=
pathy=0ASent: Sunday, December 18, 2011 3:14 AM=0ATo: ipv6@ietf.org=0ASubje=
ct: Question on IPV4/IPV6 Multicast interoperability=0A=A0=0AHello,=0A=A0=
=0AI have a question on IPV4/IPV6 Multicast interoperability. We have succe=
sfully upgraded our application(Windows Based)=A0to support IPV6 and faced =
issue on multicast interoperability. Multicast messages sent by a IPV6 serv=
er is successfully receved by a client running on IPV6. But any client runn=
ing on IPV4 is not able to receive the message.=0A=A0=0AQuite a no. of thin=
gs I tried like using IPV4 mapped IPV6 address and V4 embeded V6 adress.But=
 nothing seems to be working.Would like to know an unified way so that one =
multicast message sent by an IPV6 server should be received by both V6 and =
V4 client.=0A=A0=0AWould be great if somebody can send some code snippet(C/=
C++) on it.=0A=A0=0AThanks.=0A=A0=0AGhanashyam
---877950688-1063082605-1324353085=:77877
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt"><div style=3D"RIGHT: =
auto"><SPAN style=3D"RIGHT: auto">Hello Tina,</SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">Thanks for the reply=
 and understands the theory but unable to make it in my code.</SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">Here is my server an=
d client&nbsp;code,&nbsp;both can be compiled as a console app in windows.A=
nd run as </SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">multicast_server 224=
.0.22.1 9210 HelloIPv4World<BR>multicast_server ff15::1 2001 HelloIPv6World=
</SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">multicast_client 224=
.0.22.1 9210<BR>multicast_client ff15::1 2001<BR></SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">For the sample code =
if the server runs as IPV6 (multicast_server ff15::1 2001 HelloIPv6World)&n=
bsp;then cleint running in IPV6 (multicast_client ff15::1 2001) receives th=
e multicast message.But the client running in IPV4 does not receive the mul=
ticast message.</SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">&nbsp;</SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">I want to run the se=
rver so that both IPV4 and IPV6 client can receive the multicast messages.H=
ow to do that ,some C/C++ code sample will be great.</SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">Thanks</SPAN></div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">Ghanashyam<VAR id=3D=
yui-ie-cursor></VAR></div></SPAN>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">&nbsp;</div></SPAN>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN>&nbsp;</div>
<div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">// server.cpp : Defi=
nes the entry point for the console application.<BR>//</SPAN></div><SPAN st=
yle=3D"RIGHT: auto">
<div style=3D"RIGHT: auto"><BR style=3D"RIGHT: auto">/* multicast_server.c<=
BR>&nbsp;* This sample demonstrates a Windows multicast server that works w=
ith either<BR>&nbsp;* IPv4 or IPv6, depending on the multicast address give=
n.<BR>&nbsp;* Requires Windows XP+/Use MSVC and platform SDK to compile.<BR=
>&nbsp;* Troubleshoot: Make sure you have the IPv6 stack installed by runni=
ng<BR>&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp; &gt;ipv6 install<BR>&nbsp;*<BR>&nbsp;=
* Usage:<BR>&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp; multicast_server multicastip po=
rt data [ttl]<BR>&nbsp;*<BR>&nbsp;* Examples:<BR>&nbsp;*&nbsp;&nbsp;&nbsp;&=
nbsp; &gt;multicast_server 224.0.22.1 9210 HelloIPv4World<BR>&nbsp;*&nbsp;&=
nbsp;&nbsp;&nbsp; &gt;multicast_server ff15::1 2001 HelloIPv6World<BR>&nbsp=
;*<BR>#include &lt;stdio.h&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT style=3D=
"RIGHT: auto" color=3Ddarkgreen>/* for fprintf() */</FONT></div>
<div style=3D"RIGHT: auto"><FONT color=3D#006400></FONT>&nbsp;</div>
#include &lt;winsock2.h&gt;   <FONT color=3Ddarkgreen>/* for socket(), conn=
ect(), send(), and recv() */</FONT><BR>#include &lt;ws2tcpip.h&gt;&nbsp;&nb=
sp; <FONT color=3Ddarkgreen>/* for ip options */</FONT><BR>#include &lt;std=
lib.h&gt;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* for atoi() and=
 exit() */</FONT><BR><BR>#if defined(_MSC_VER)<BR>#pragma comment(lib, "ws2=
_32.lib")<BR>#endif<BR><BR><BR>static void DieWithError(char* errorMessage)=
<BR>{<BR>&nbsp;&nbsp;&nbsp; fprintf(stderr, "%s\n", errorMessage);<BR>&nbsp=
;&nbsp;&nbsp; exit(EXIT_FAILURE);<BR>}<BR><BR><BR>int main(int argc, char *=
argv[])<BR>{<BR>&nbsp;&nbsp;&nbsp; SOCKET&nbsp;&nbsp;&nbsp; sock;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Socket */</FONT><BR>&nbs=
p;&nbsp;&nbsp; WSADATA&nbsp;&nbsp; wsaData;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT
 color=3Ddarkgreen>/* For WSAStartup */</FONT><BR>&nbsp;&nbsp;&nbsp; char*&=
nbsp;&nbsp;&nbsp;&nbsp; multicastIP;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Arg: IP Multicast ad=
dress */</FONT><BR>&nbsp;&nbsp;&nbsp; char*&nbsp;&nbsp;&nbsp;&nbsp; multica=
stPort;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=
=3Ddarkgreen>/* Arg: Server port */</FONT><BR>&nbsp;&nbsp;&nbsp; char*&nbsp=
;&nbsp;&nbsp;&nbsp; sendString;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Arg: String to mult=
icast */</FONT><BR>&nbsp;&nbsp;&nbsp; size_t&nbsp;&nbsp;&nbsp; sendStringLe=
n;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddark=
green>/* Length of string to multicast */</FONT><BR>&nbsp;&nbsp;&nbsp; DWOR=
D&nbsp;&nbsp;&nbsp;&nbsp; multicastTTL;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Arg: TTL of multicast p=
ackets
 */</FONT><BR>&nbsp;&nbsp;&nbsp; ADDRINFO* multicastAddr;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Multicast a=
ddress */</FONT><BR>&nbsp;&nbsp;&nbsp; ADDRINFO&nbsp; hints&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D { 0 }; <FONT color=3Ddarkgreen>/=
* Hints for name lookup */</FONT><BR><BR>&nbsp;&nbsp;&nbsp; if ( WSAStartup=
(MAKEWORD(2, 2), &amp;wsaData) !=3D 0)<BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("WSAStartup() failed");<BR>&=
nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; if ( argc &lt; 4 || argc &gt;=
 5 )<BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
fprintf(stderr, "Usage:&nbsp; %s &lt;Multicast Address&gt; &lt;Port&gt; &lt=
;Send String&gt; [&lt;TTL&gt;]\n", argv[0]);<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; exit(EXIT_FAILURE);<BR>&nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&n=
bsp;&nbsp; multicastIP&nbsp;&nbsp; =3D
 argv[1];&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; <FONT color=3Ddarkgreen>/* First arg:&nbsp;&nbsp; multicast IP addre=
ss */</FONT><BR>&nbsp;&nbsp;&nbsp; multicastPort =3D argv[2];&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Dda=
rkgreen>/* Second arg:&nbsp; multicast port */</FONT><BR>&nbsp;&nbsp;&nbsp;=
 sendString&nbsp;&nbsp;&nbsp; =3D argv[3];&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Third ar=
g:&nbsp;&nbsp; String to multicast */</FONT><BR>&nbsp;&nbsp;&nbsp; multicas=
tTTL&nbsp; =3D (argc =3D=3D 5 ?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; <FONT color=3Ddarkgreen>/* Fourth arg:&nbsp; If supplied, use command-=
line */</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; atoi(argv[4=
]) : 1); <FONT color=3Ddarkgreen>/* specified TTL, else use default TTL of =
1
 */</FONT><BR>&nbsp;&nbsp;&nbsp; sendStringLen =3D strlen(sendString);&nbsp=
; <FONT color=3Ddarkgreen>/* Find length of sendString */</FONT><BR><BR>&nb=
sp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Resolve destination address for =
multicast datagrams */</FONT><BR>&nbsp;&nbsp;&nbsp; hints.ai_family&nbsp;&n=
bsp; =3D PF_UNSPEC;<BR>&nbsp;&nbsp;&nbsp; hints.ai_socktype =3D SOCK_DGRAM;=
<BR>&nbsp;&nbsp;&nbsp; hints.ai_flags&nbsp;&nbsp;&nbsp; =3D AI_NUMERICHOST;=
<BR>&nbsp;&nbsp;&nbsp; if ( getaddrinfo(multicastIP, multicastPort, &amp;hi=
nts, &amp;multicastAddr) !=3D 0 )<BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("getaddrinfo() failed");<BR>&nbsp=
;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; printf("Using %s\n", multicastAdd=
r-&gt;ai_family =3D=3D PF_INET6 ? "IPv6" : "IPv4");<BR><BR>&nbsp;&nbsp;&nbs=
p; <FONT color=3Ddarkgreen>/* Create socket for sending multicast datagrams=
 */</FONT><BR>&nbsp;&nbsp;&nbsp; if ( (sock =3D socket(multicastAddr-&gt;ai=
_family,
 multicastAddr-&gt;ai_socktype, 0)) =3D=3D INVALID_SOCKET )<BR>&nbsp;&nbsp;=
&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("socket=
() failed");<BR>&nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; <FONT color=
=3Ddarkgreen>/* Set TTL of multicast packet */</FONT><BR>&nbsp;&nbsp;&nbsp;=
 if ( setsockopt(sock,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast=
Addr-&gt;ai_family =3D=3D PF_INET6 ? IPPROTO_IPV6&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; : IPPROTO_IP,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=
ulticastAddr-&gt;ai_family =3D=3D PF_INET6 ? IPV6_MULTICAST_HOPS : IP_MULTI=
CAST_TTL,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (char*) &amp;multicast=
TTL, sizeof(multicastTTL)) !=3D 0 )<BR>&nbsp;&nbsp;&nbsp;
 {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("setsockopt()=
 failed");<BR>&nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; for (;;) <FONT=
 color=3Ddarkgreen>/* Run forever */</FONT><BR>&nbsp;&nbsp;&nbsp; {<BR>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if ( sendto(sock, sendString, sendSt=
ringLen, 0,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicastAddr-&gt;ai=
_addr, multicastAddr-&gt;ai_addrlen) !=3D sendStringLen )<BR>&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("sendto() sent a different number of=
 bytes than expected");<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<BR>=
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sleep(3000); <FONT color=3Dd=
arkgreen>/* Multicast sendString in datagram to clients every 3 seconds */<=
/FONT><BR>&nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; <FONT
 color=3Ddarkgreen>/* NOT REACHED */</FONT><BR>&nbsp;&nbsp;&nbsp; freeaddri=
nfo(multicastAddr);<BR>&nbsp;&nbsp;&nbsp; closesocket(sock);<BR>&nbsp;&nbsp=
;&nbsp; return 0;<BR>}
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto">// client.cpp : Defines the entry point for the =
console application.<BR>//</div>
<div style=3D"RIGHT: auto">&nbsp;</div>
<div style=3D"RIGHT: auto"><BR>/* multicast_client.c<BR>&nbsp;* This sample=
 demonstrates a Windows multicast client that works with either<BR>&nbsp;* =
IPv4 or IPv6, depending on the multicast address given.<BR>&nbsp;* Requires=
 Windows XP+/Use MSVC and platform SDK to compile.<BR>&nbsp;* Troubleshoot:=
 Make sure you have the IPv6 stack installed by running<BR>&nbsp;*&nbsp;&nb=
sp;&nbsp;&nbsp; &gt;ipv6 install<BR>&nbsp;*<BR>&nbsp;* Usage:<BR>&nbsp;*&nb=
sp;&nbsp;&nbsp;&nbsp; multicast_client multicastip port<BR>&nbsp;*<BR>&nbsp=
;* Examples:<BR>&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp; &gt;multicast_client 224.0.=
22.1 9210<BR>&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp; &gt;multicast_client ff15::1 2=
001<BR>&nbsp;*<BR>&nbsp;#include &lt;stdio.h&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; <FONT color=3Ddarkgreen>/* for printf() and fprintf() */</FONT><BR>#inc=
lude &lt;winsock2.h&gt;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* for socket()=
, connect(), sendto(), and recvfrom() */</FONT><BR>#include
 &lt;ws2tcpip.h&gt;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* for ip_mreq */</=
FONT><BR>#include &lt;stdlib.h&gt;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Dda=
rkgreen>/* for atoi() and exit() */</FONT><BR>#include &lt;string.h&gt;&nbs=
p;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* for memset() */</FONT><BR>#=
include &lt;time.h&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Dda=
rkgreen>/* for timestamps */</FONT><BR><BR>#if defined(_MSC_VER)<BR>#pragma=
 comment(lib, "ws2_32.lib")<BR>#endif<BR><BR><BR>void DieWithError(char* er=
rorMessage)<BR>{<BR>&nbsp;&nbsp;&nbsp; fprintf(stderr, "%s\n", errorMessage=
);<BR>&nbsp;&nbsp;&nbsp; exit(EXIT_FAILURE);<BR>}<BR><BR><BR>int main(int a=
rgc, char* argv[])<BR>{<BR>&nbsp;&nbsp;&nbsp; SOCKET&nbsp;&nbsp;&nbsp;&nbsp=
; sock;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgree=
n>/* Socket */</FONT><BR>&nbsp;&nbsp;&nbsp; WSADATA&nbsp;&nbsp;&nbsp;
 wsaData;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* For WSAStar=
tup */</FONT><BR>&nbsp;&nbsp;&nbsp; char*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mul=
ticastIP;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Arg: IP Multicast Address */</FONT>=
<BR>&nbsp;&nbsp;&nbsp; char*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicastPort;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT colo=
r=3Ddarkgreen>/* Arg: Port */</FONT><BR>&nbsp;&nbsp;&nbsp; ADDRINFO*&nbsp; =
multicastAddr;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; <FONT color=3Ddarkgreen>/* Multicast Address */</FONT><BR>&nbsp;&nbsp=
;&nbsp; ADDRINFO*&nbsp; localAddr;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/=
* Local address to bind to */</FONT><BR>&nbsp;&nbsp;&nbsp;
 ADDRINFO&nbsp;&nbsp; hints&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; =3D { 0 };&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Hints for name loo=
kup */</FONT><BR><BR>&nbsp;&nbsp;&nbsp; if ( WSAStartup(MAKEWORD(2, 2), &am=
p;wsaData) !=3D 0)<BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; DieWithError("WSAStartup() failed");<BR>&nbsp;&nbsp;&nbsp; }<=
BR><BR>&nbsp;&nbsp;&nbsp; if ( argc !=3D 3 )<BR>&nbsp;&nbsp;&nbsp; {<BR>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fprintf(stderr,"Usage: %s &lt;Multi=
cast IP&gt; &lt;Multicast Port&gt;\n", argv[0]);<BR>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; exit(EXIT_FAILURE);<BR>&nbsp;&nbsp;&nbsp; }<BR><BR>&nbs=
p;&nbsp;&nbsp; multicastIP&nbsp;&nbsp; =3D argv[1];&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; <FONT color=3Ddarkgreen>/* First arg:&nbsp; Multicast IP address */<=
/FONT><BR>&nbsp;&nbsp;&nbsp; multicastPort =3D argv[2];&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; <FONT color=3Ddarkgreen>/* Second arg: Multicast port
 */</FONT><BR><BR>&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Resolve the=
 multicast group address */</FONT>
    hints.ai_family =3D PF_UNSPEC;    hints.ai_flags  =3D AI_NUMERICHOST;
    if ( getaddrinfo(multicastIP, NULL, &amp;hints, &amp;multicastAddr) !=
=3D 0 )
    {        DieWithError("getaddrinfo() failed");    }
    printf("Using %s\n", multicastAddr-&gt;ai_family =3D=3D PF_INET6 ? "IPv=
6" : "IPv4");
    <FONT color=3Ddarkgreen>/* Get a local address with the same family (IP=
v4 or IPv6) as our multicast group */</FONT><BR>&nbsp;&nbsp;&nbsp; hints.ai=
_family&nbsp;&nbsp; =3D multicastAddr-&gt;ai_family;<BR>&nbsp;&nbsp;&nbsp; =
hints.ai_socktype =3D SOCK_DGRAM;<BR>&nbsp;&nbsp;&nbsp; hints.ai_flags&nbsp=
;&nbsp;&nbsp; =3D AI_PASSIVE; <FONT color=3Ddarkgreen>/* Return an address =
we can bind to */</FONT><BR>&nbsp;&nbsp;&nbsp; if ( getaddrinfo(NULL, multi=
castPort, &amp;hints, &amp;localAddr) !=3D 0 )<BR>&nbsp;&nbsp;&nbsp; {<BR>&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("getaddrinfo() faile=
d");<BR>&nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgr=
een>/* Create socket for receiving datagrams */</FONT><BR>&nbsp;&nbsp;&nbsp=
; if ( (sock =3D socket(localAddr-&gt;ai_family, localAddr-&gt;ai_socktype,=
 0)) =3D=3D INVALID_SOCKET )<BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; DieWithError("socket() failed");<BR>&nbsp;&nbsp;&nb=
sp;
 }<BR><BR>&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Bind to the multica=
st port */</FONT><BR>&nbsp;&nbsp;&nbsp; if ( bind(sock, localAddr-&gt;ai_ad=
dr, localAddr-&gt;ai_addrlen) !=3D 0 )<BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("bind() failed");<BR>&nbsp;&=
nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Join the=
 multicast group. We do this seperately depending on whether we<BR>&nbsp;&n=
bsp;&nbsp;&nbsp; * are using IPv4 or IPv6. WSAJoinLeaf is supposed to be IP=
 version agnostic<BR>&nbsp;&nbsp;&nbsp;&nbsp; * but it looks more complex t=
han just duplicating the required code. */</FONT><BR>&nbsp;&nbsp;&nbsp; if =
( multicastAddr-&gt;ai_family&nbsp; =3D=3D PF_INET &amp;&amp;&nbsp; <BR>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicastAddr-&gt;ai_addrlen =
=3D=3D sizeof(struct sockaddr_in) ) <FONT color=3Ddarkgreen>/* IPv4 */</FON=
T><BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; st=
ruct
 ip_mreq multicastRequest;&nbsp; <FONT color=3Ddarkgreen>/* Multicast addre=
ss join structure */</FONT><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; <FONT color=3Ddarkgreen>/* Specify the multicast group */</FONT><BR>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; memcpy(&amp;multicastRequest.imr_mul=
tiaddr,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; &amp;((struct sockaddr_in*)(multicastAddr-&gt;ai_addr)=
)-&gt;sin_addr,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; sizeof(multicastRequest.imr_multiaddr));<BR><B=
R>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Acc=
ept multicast from any interface */</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; multicastRequest.imr_interface.s_addr =3D htonl(INADDR_ANY);<=
BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/=
* Join the multicast address
 */</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if ( setsockopt(so=
ck, IPPROTO_IP, IP_ADD_MEMBERSHIP, (char*) &amp;multicastRequest, sizeof(mu=
lticastRequest)) !=3D 0 )<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {<B=
R>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DieWit=
hError("setsockopt() failed");<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; }<BR>&nbsp;&nbsp;&nbsp; }<BR>&nbsp;&nbsp;&nbsp; else if ( multicastAddr-&=
gt;ai_family&nbsp; =3D=3D PF_INET6 &amp;&amp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicastAddr-&gt;ai_a=
ddrlen =3D=3D sizeof(struct sockaddr_in6) ) <FONT color=3Ddarkgreen>/* IPv6=
 */</FONT><BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; struct ipv6_mreq multicastRequest;&nbsp; <FONT color=3Ddarkgreen>/* M=
ulticast address join structure */</FONT><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Specify the multicast group
 */</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; memcpy(&amp;multic=
astRequest.ipv6mr_multiaddr,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &amp;((struct sockaddr_in6*)(mult=
icastAddr-&gt;ai_addr))-&gt;sin6_addr,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sizeof(multicastRequest=
.ipv6mr_multiaddr));<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FON=
T color=3Ddarkgreen>/* Accept multicast from any interface */</FONT><BR>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicastRequest.ipv6mr_interface =
=3D 0;<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddark=
green>/* Join the multicast address */</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; if ( setsockopt(sock, IPPROTO_IPV6, IPV6_ADD_MEMBERSHIP, (=
char*) &amp;multicastRequest, sizeof(multicastRequest)) !=3D 0 )<BR>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Di=
eWithError("setsockopt() failed");<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; }<BR>&nbsp;&nbsp;&nbsp; }<BR>&nbsp;&nbsp;&nbsp; else<BR>&nbsp;&nbsp;&=
nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("Neither=
 IPv4 or IPv6");<BR>&nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; freeaddr=
info(localAddr);<BR>&nbsp;&nbsp;&nbsp; freeaddrinfo(multicastAddr);<BR><BR>=
&nbsp;&nbsp;&nbsp; for (;;) <FONT color=3Ddarkgreen>/* Run forever */</FONT=
><BR>&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tim=
e_t timer;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; char&nbsp;&nbsp; r=
ecvString[500];&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Bu=
ffer for received string */</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; int&nbsp;&nbsp;&nbsp; recvStringLen;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; <FONT color=3Ddarkgreen>/* Length of received string
 */</FONT><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT color=3D=
darkgreen>/* Receive a single datagram from the server */</FONT><BR>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if ( (recvStringLen =3D recvfrom(sock, =
recvString, sizeof(recvString) - 1, 0, NULL, 0)) &lt; 0 )<BR>&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; DieWithError("recvfrom() failed");<BR>&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; recvString[recvStringLen] =3D '\0';<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; <FONT color=3Ddarkgreen>/* Print the received string */=
</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; time(&amp;timer);&nbs=
p; <FONT color=3Ddarkgreen>/* get time stamp to print with recieved data */=
</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; printf("Time Received=
: %.*s : %s\n", strlen(ctime(&amp;timer)) - 1, ctime(&amp;timer),
 recvString);<BR>&nbsp;&nbsp;&nbsp; }<BR><BR>&nbsp;&nbsp;&nbsp; <FONT color=
=3Ddarkgreen>/* NOT REACHED */</FONT><BR>&nbsp;&nbsp;&nbsp; closesocket(soc=
k);<BR>&nbsp;&nbsp;&nbsp; exit(EXIT_SUCCESS);<BR>}</SPAN><BR></div>
<DIV style=3D"FONT-FAMILY: times new roman, new york, times, serif; FONT-SI=
ZE: 12pt">
<DIV style=3D"FONT-FAMILY: times new roman, new york, times, serif; FONT-SI=
ZE: 12pt"><FONT size=3D2 face=3DArial>
<DIV style=3D"BORDER-BOTTOM: #ccc 1px solid; BORDER-LEFT: #ccc 1px solid; P=
ADDING-BOTTOM: 0px; LINE-HEIGHT: 0; MARGIN: 5px 0px; PADDING-LEFT: 0px; PAD=
DING-RIGHT: 0px; HEIGHT: 0px; FONT-SIZE: 0px; BORDER-TOP: #ccc 1px solid; B=
ORDER-RIGHT: #ccc 1px solid; PADDING-TOP: 0px" class=3Dhr readonly=3D"true"=
 contenteditable=3D"false"></DIV><B><SPAN style=3D"FONT-WEIGHT: bold">From:=
</SPAN></B> Tina TSOU &lt;Tina.Tsou.Zouting@huawei.com&gt;<BR><B><SPAN styl=
e=3D"FONT-WEIGHT: bold">To:</SPAN></B> Ghanashyam Satpathy &lt;ghanashyam_s=
atpathy@yahoo.com&gt;; "ipv6@ietf.org" &lt;ipv6@ietf.org&gt; <BR><B><SPAN s=
tyle=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> "multrans@ietf.org" &lt;multrans@=
ietf.org&gt;; MBONED WG &lt;mboned@ietf.org&gt; <BR><B><SPAN style=3D"FONT-=
WEIGHT: bold">Sent:</SPAN></B> Tuesday, December 20, 2011 6:09 AM<BR><B><SP=
AN style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: Question on IPV4/IPV=
6 Multicast interoperability<BR></FONT><BR>
<DIV id=3Dyiv822834594>
<STYLE><!--=0A#yiv822834594  =0A _filtered #yiv822834594 {font-family:SimSu=
n;panose-1:2 1 6 0 3 1 1 1 1 1;}=0A _filtered #yiv822834594 {font-family:"C=
ambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;}=0A _filtered #yiv822834594 {fon=
t-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}=0A _filtered #yiv822834594=
 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}=0A _filtered #yiv82283=
4594 {font-family:SimSun;panose-1:2 1 6 0 3 1 1 1 1 1;}=0A#yiv822834594  =
=0A#yiv822834594 p.yiv822834594MsoNormal, #yiv822834594 li.yiv822834594MsoN=
ormal, #yiv822834594 div.yiv822834594MsoNormal=0A=09{margin:0in;margin-bott=
om:.0001pt;font-size:12.0pt;font-family:"serif";}=0A#yiv822834594 a:link, #=
yiv822834594 span.yiv822834594MsoHyperlink=0A=09{color:blue;text-decoration=
:underline;}=0A#yiv822834594 a:visited, #yiv822834594 span.yiv822834594MsoH=
yperlinkFollowed=0A=09{color:purple;text-decoration:underline;}=0A#yiv82283=
4594 span.yiv822834594EmailStyle18=0A=09{font-family:"sans-serif";color:#1F=
497D;}=0A#yiv822834594 span.yiv822834594SpellE=0A=09{}=0A#yiv822834594 .yiv=
822834594MsoChpDefault=0A=09{font-size:10.0pt;}=0A _filtered #yiv822834594 =
{margin:1.0in 1.25in 1.0in 1.25in;}=0A#yiv822834594 div.yiv822834594WordSec=
tion1=0A=09{}=0A--></STYLE>

<DIV>
<DIV class=3Dyiv822834594WordSection1>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN class=
=3Dyiv822834594SpellE><SPAN style=3D"COLOR: black">Ghanashyam</SPAN></SPAN>=
<SPAN style=3D"COLOR: black">,</SPAN></div>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">http://datatracker.ietf.org/doc/draft-tsou-multrans-addr-acquisitio=
n/</SPAN></div>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">http://datatracker.ietf.org/doc/draft-zhou-multrans-af1-specificati=
on/</SPAN></div>
<DIV>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">Running code exists.</SPAN></div>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">Hope it helps.</SPAN></div>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">&nbsp;</SPAN></div>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">Best Regards,</SPAN></div>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">Tina TSOU</SPAN></div>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">http://tinatsou.weebly.com/contact.html</SPAN></div></DIV>
<div class=3Dyiv822834594MsoNormal><SPAN style=3D"COLOR: #1f497d; FONT-SIZE=
: 11pt">&nbsp;</SPAN></div>
<DIV>
<DIV style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING=
-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1p=
t solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<div class=3Dyiv822834594MsoNormal><B><SPAN style=3D"FONT-SIZE: 10pt">From:=
</SPAN></B><SPAN style=3D"FONT-SIZE: 10pt"> ipv6-bounces@ietf.org [mailto:i=
pv6-bounces@ietf.org] <B>On Behalf Of </B>Ghanashyam Satpathy<BR><B>Sent:</=
B> Sunday, December 18, 2011 3:14 AM<BR><B>To:</B> ipv6@ietf.org<BR><B>Subj=
ect:</B> Question on IPV4/IPV6 Multicast interoperability</SPAN></div></DIV=
></DIV>
<div class=3Dyiv822834594MsoNormal>&nbsp;</div>
<DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">Hello,</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">I have a question on IPV4/IPV6 Multicast interoperability=
. We have succesfully upgraded our application(Windows Based)&nbsp;to suppo=
rt IPV6 and faced issue on multicast interoperability. Multicast messages s=
ent by a IPV6 server is successfully receved by a client running on IPV6. B=
ut any client running on IPV4 is not able to receive the message.</SPAN></d=
iv></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">Quite a no. of things I tried like using IPV4 mapped IPV6=
 address and V4 embeded V6 adress.But nothing seems to be working.Would lik=
e to know an unified way so that one multicast message sent by an IPV6 serv=
er should be received by both V6 and V4 client.</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">Would be great if somebody can send some code snippet(C/C=
++) on it.</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">Thanks.</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">Ghanashyam</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV>
<DIV>
<div style=3D"BACKGROUND: white" class=3Dyiv822834594MsoNormal><SPAN style=
=3D"COLOR: black">&nbsp;</SPAN></div></DIV></DIV></DIV></DIV></DIV><BR><BR>=
</DIV></DIV></div></body></html>
---877950688-1063082605-1324353085=:77877--

From fweimer@bfk.de  Tue Dec 20 02:00:58 2011
Return-Path: <fweimer@bfk.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 DA26421F8B0F for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 02:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.782
X-Spam-Level: 
X-Spam-Status: No, score=-0.782 tagged_above=-999 required=5 tests=[AWL=1.467,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 WOY+p6C+Twip for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 02:00:58 -0800 (PST)
Received: from mx01.bfk.de (mx01.bfk.de [193.227.124.2]) by ietfa.amsl.com (Postfix) with ESMTP id 00D7221F8A91 for <ipv6@ietf.org>; Tue, 20 Dec 2011 02:00:57 -0800 (PST)
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1RcwVE-0005F5-NK; Tue, 20 Dec 2011 10:00:56 +0000
Received: by bfk.de with local id 1RcwVE-0007vj-Ii; Tue, 20 Dec 2011 10:00:56 +0000
From: Florian Weimer <fweimer@bfk.de>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com>
Date: Tue, 20 Dec 2011 10:00:56 +0000
In-Reply-To: <4EEA0342.2040608@si6networks.com> (Fernando Gont's message of "Thu, 15 Dec 2011 11:25:06 -0300")
Message-ID: <82fwgfk1ev.fsf@mid.bfk.de>
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
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, 20 Dec 2011 10:00:59 -0000

* Fernando Gont:

> The second I-D is entitled 'Processing of IPv6 "atomic" fragments'
> (http://tools.ietf.org/id/draft-gont-6man-ipv6-atomic-fragments-00.txt).
> Its abstract is:
>
> ---- cut here ----
>    IPv6 allows packets to contain a Fragment Header, without the packet
>    being actually fragmented into multiple pieces.  Such packets
>    typically result from hosts that have received an ICMPv6 "Packet Too
>    Big" error message that advertises a "Next-Hop MTU" smaller than 1280
>    bytes, and are currently processed by hosts as "fragmented
>    traffic".

Does such traffic actually occur in the wild, or would it only be used
in attacks?

>    By forging ICMPv6 "Packet Too Big" error messages an attacker can
>    cause hosts to employ "atomic fragments", and the launch any
>    fragmentation-based attacks against such traffic.  This document
>    discusses the generation of the aforementioned "atomic fragments",
>    the corresponding security implications, and formally updates RFC
>    2460 and RFC 5722 such that the attack vector based on "atomic
>    fragments" is completely eliminated.

My feeling is that such atomic fragments should be dropped from the
protocol.

Per previous WG discussion, when reassembling such atomic fragments,
IPv6 implementations must ignore the upper 16 bits of the fragment ID
(otherwise the stateless v4/v6 gateways won't work).  Clearly, this is
not desirable.

--=20
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstra=DFe 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

From sthaug@nethelp.no  Tue Dec 20 03:45:03 2011
Return-Path: <sthaug@nethelp.no>
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 C6D0421F8A56 for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 03:45:03 -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 WNVwBi1BDqSc for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 03:45:03 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 6EB9F21F867F for <ipv6@ietf.org>; Tue, 20 Dec 2011 03:45:02 -0800 (PST)
Received: (qmail 91941 invoked from network); 20 Dec 2011 11:44:58 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 20 Dec 2011 11:44:58 -0000
Date: Tue, 20 Dec 2011 12:44:58 +0100 (CET)
Message-Id: <20111220.124458.41706285.sthaug@nethelp.no>
To: fweimer@bfk.de
Subject: Re: Fragmentation-related security issues
From: sthaug@nethelp.no
In-Reply-To: <82fwgfk1ev.fsf@mid.bfk.de>
References: <4EEA0342.2040608@si6networks.com> <82fwgfk1ev.fsf@mid.bfk.de>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
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: Tue, 20 Dec 2011 11:45:03 -0000

> >    IPv6 allows packets to contain a Fragment Header, without the packet
> >    being actually fragmented into multiple pieces.  Such packets
> >    typically result from hosts that have received an ICMPv6 "Packet Too
> >    Big" error message that advertises a "Next-Hop MTU" smaller than 1280
> >    bytes, and are currently processed by hosts as "fragmented
> >    traffic".
> 
> Does such traffic actually occur in the wild, or would it only be used
> in attacks?

Such traffic absolutely occurs in the wild. I have three reasonably
busy name servers where this is logged as an error from the ipfw code,
e.g.

Dec 16 14:04:04 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 17 00:27:20 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 18 07:53:10 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 18 23:21:37 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 19 03:07:43 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 19 05:09:45 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 19 21:47:46 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 20 08:10:59 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 20 08:59:21 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
Dec 20 11:25:59 slem kernel: IPFW2: IPV6 - Invalid Fragment Header

This is because these name servers haven't (yet) been upgraded to a
FreeBSD version where bug report kern/145733 haven't been fixed. It
*is* fixed in newer FreeBSD versions, e.g. 8.2-STABLE.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From iesg-secretary@ietf.org  Tue Dec 20 07:44:39 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 D632D21F8770; Tue, 20 Dec 2011 07:44:39 -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 fsTyUJeVyHUW; Tue, 20 Dec 2011 07:44:39 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C90A21F8A66; Tue, 20 Dec 2011 07:44:39 -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: Protocol Action: 'RPL Option for Carrying RPL Information in Data-Plane Datagrams' to Proposed Standard (draft-ietf-6man-rpl-option-06.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111220154439.30639.36955.idtracker@ietfa.amsl.com>
Date: Tue, 20 Dec 2011 07:44:39 -0800
Cc: 6man chair <6man-chairs@tools.ietf.org>, 6man mailing list <ipv6@ietf.org>, RFC Editor <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, 20 Dec 2011 15:44:40 -0000

The IESG has approved the following document:
- 'RPL Option for Carrying RPL Information in Data-Plane Datagrams'
  (draft-ietf-6man-rpl-option-06.txt) as a Proposed Standard

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

The IESG contact persons are Jari Arkko and Ralph Droms.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-option/




    Technical Summary 
        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 within a RPL domain.

    Working Group Summary 
        This document was reviewed by the 6man and RPL WGs and
        represents the consensus of those groups.

    Document Quality 
        Several external groups have indicated their plans to
        carry out large-scale deployments using the RPL option
        defined in this document.

Personnel

   The responsible Area Director is Jari Arkko. Brian Haberman (brian@innovationslab.net)
   is the document shepherd




From iesg-secretary@ietf.org  Tue Dec 20 07:47:06 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 995A921F8569; Tue, 20 Dec 2011 07:47:06 -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 skiVs2lH1DtU; Tue, 20 Dec 2011 07:47:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9FD121F85EF; Tue, 20 Dec 2011 07:47:05 -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: Protocol Action: 'An IPv6 Routing Header for Source Routes with RPL' to Proposed Standard (draft-ietf-6man-rpl-routing-header-07.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111220154705.31809.94941.idtracker@ietfa.amsl.com>
Date: Tue, 20 Dec 2011 07:47:05 -0800
Cc: 6man chair <6man-chairs@tools.ietf.org>, 6man mailing list <ipv6@ietf.org>, RFC Editor <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, 20 Dec 2011 15:47:06 -0000

The IESG has approved the following document:
- 'An IPv6 Routing Header for Source Routes with RPL'
  (draft-ietf-6man-rpl-routing-header-07.txt) as a Proposed Standard

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

The IESG contact persons are Jari Arkko and Ralph Droms.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-routing-header/




  Technical Summary 

        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 domain.

    Working Group Summary 

        This document was reviewed by the 6man and RPL WGs and
        represents the consensus of those groups.

    Document Quality 

        Several external groups have indicated their plans to
        carry out large-scale deployments using the RPL option
        defined in this document.

   Personnel

       Brian Haberman (brian@innovationslab.net) is the document shepherd.
       Jari Arkko is the responsible Area Director.

RFC Editor Note

  In the IANA consideration section, please remove the duplicated "assigned assigned":

   This document defines a new IPv6 Routing Type, the "RPL Source Route
   Header", and hass been assigned assigned number TBD by IANA.




From prvs=3280cf979=mukul@uwm.edu  Tue Dec 20 08:14:22 2011
Return-Path: <prvs=3280cf979=mukul@uwm.edu>
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 BDCC321F8B8A; Tue, 20 Dec 2011 08:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.74
X-Spam-Level: 
X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 r67z-Dkyn9r3; Tue, 20 Dec 2011 08:14:22 -0800 (PST)
Received: from ip1mta.uwm.edu (ip1mta.uwm.edu [129.89.7.18]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8C821F8B7D; Tue, 20 Dec 2011 08:14:21 -0800 (PST)
Received: from localhost (HELO mta04.pantherlink.uwm.edu) ([127.0.0.1]) by ip1mta.uwm.edu with ESMTP; 20 Dec 2011 10:14:21 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta04.pantherlink.uwm.edu (Postfix) with ESMTP id ECD0F2B3EDA; Tue, 20 Dec 2011 10:12:34 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta04.pantherlink.uwm.edu
Received: from mta04.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta04.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SzcRm0EmTauY; Tue, 20 Dec 2011 10:12:34 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta04.pantherlink.uwm.edu (Postfix) with ESMTP id C2CBD2B3ED8; Tue, 20 Dec 2011 10:12:34 -0600 (CST)
Date: Tue, 20 Dec 2011 10:14:21 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Jonathan Hui <jonhui@cisco.com>
Message-ID: <1076398681.709387.1324397661047.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <055FAFECB2B53642884D29B0094D14751098099F@DLEE10.ent.ti.com>
Subject: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll <roll@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, 20 Dec 2011 16:14:22 -0000

Jonathan

The IESG-approved draft refers to the RPL instance as the scope where the routing header can be used. How would this routing header be used for general source routing (across RPL instances) in an LLN? How would a node use this routing header if it wants to travel along a source route discovered using P2P-RPL?

Thanks
Mukul


From rja.lists@gmail.com  Tue Dec 20 09:07:30 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 8421321F84E5 for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 09:07: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 R4o90lBxf9qS for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 09:07:29 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7D19E21F8508 for <ipv6@ietf.org>; Tue, 20 Dec 2011 09:07:29 -0800 (PST)
Received: by qcsf15 with SMTP id f15so4761047qcs.31 for <ipv6@ietf.org>; Tue, 20 Dec 2011 09:07:29 -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 :to:mime-version:x-mailer; bh=UpTBOJEFCiEuJj07pSGzQeyzGOvm25KCTD0RtpSvI8o=; b=hJ5o2hVvP3azHIXzDpQ2BQcDETjbvNrFaPhEq1Xi7JbUj5PaM3q1jqI8+bpJHWUXp1 Jo0u2mW+EWiStjNHyIYmUM56NVPTVWtIdoBpD9OHO/XiRTH8bf1Wb4wM1mVRNHfRLssp XoPKlr7A3Vvw0/FPzofFuyCc3yM8g2wstq7us=
Received: by 10.224.116.144 with SMTP id m16mr3964297qaq.19.1324400848989; Tue, 20 Dec 2011 09:07:28 -0800 (PST)
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 z1sm4720570qao.1.2011.12.20.09.07.25 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Dec 2011 09:07:27 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Fragmentation-related security issues
Date: Tue, 20 Dec 2011 12:07:24 -0500
Message-Id: <C288ACA0-E09B-4F23-800C-294E4BADE00F@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: Tue, 20 Dec 2011 17:07:30 -0000

Earlier, Florian Weimer wrote, in part:
> Does such traffic actually occur in the wild, 
> or would it only be used in attacks?

It does occur in the wild in situations where
it is functionally required and is NOT any
kind of attack.

I think there are at least 2 circumstances for
this.  

I believe that scenario relates to DNS/UDP packets 
-- and one might want to read the recent I-Ds (plural)
from Mark Andrews for more details -- see this
email to the IPv6 list for example:

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

Another scenario relates to several kinds of
RF/wireless links that only support smaller
link MTUs and are relatively low bandwidth.

Other legitimate deployment scenarios for these
IPv6 packets are likely to exist.

Also, Steinar Haug wrote, in part:
> This is because these name servers haven't (yet)
> been upgraded to a FreeBSD version where bug report
> kern/145733 haven't been fixed. It *is* fixed in
> newer FreeBSD versions, e.g. 8.2-STABLE.

Multiple shipping OSs understand the legitimacy
of IPv6 packets with a Fragment Header without
multiple fragments.  So FreeBSD-current is not 
alone in handling these correctly.


MORE GENERALLY:

We need to AVOID falling into the trap that things 
not explicitly allowed are always security 
vulnerabilities and lack legitimate reasons to exist.  
IPv6 is not "done" -- any useful deployed protocol 
will evolve over time.

So it is not helpful to publish documents that 
advise firewall/middlebox/router vendors to filter out 
"unknown" behaviour or "curious" packet patterns or 
unrecognised options.  

For example, if a firewall doesn't recognise
(e.g. due to lack of firewall firmware update) 
some new IPv6 option (e.g. carried in an IPv6 
Destination Header), the firewall ought NOT
filter/drop packets with that new/unrecognised 
option.

Over time, probably slowly, new IPv6 options
(i.e. inside existing IPv6 headers) will be 
defined that have legitimate (often new) uses.  

We do NOT want to close the door on IPv6 (or IPv4 
or TCP or UDP or ...) evolution.  Proscriptive and
paranoid recommendations to implementers WILL and
DO close the door on evolution -- and hence can be
harmful to the Internet.

Yours,

Ran

PS:  Many people here are already on holiday, or will 
     begin their holiday soon.  So I hope we will avoid 
     drawing any conclusions prior to early January 2012.  
     I'll be very substantially offline starting in 
     a few hours, until early January, for example.



From fgont@si6networks.com  Tue Dec 20 14:49:35 2011
Return-Path: <fgont@si6networks.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 AEC4311E8095 for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 14:49:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
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 2WZ+EzqbXqHe for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 14:49:35 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id F163F11E808A for <ipv6@ietf.org>; Tue, 20 Dec 2011 14:49:34 -0800 (PST)
Received: from [190.48.235.151] (helo=[192.168.123.102]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1Rd8V2-0007eU-1r; Tue, 20 Dec 2011 23:49:32 +0100
Message-ID: <4EF06D47.2060202@si6networks.com>
Date: Tue, 20 Dec 2011 08:11:03 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: New IETF I-D on IPv6 smurf amplifiers
X-Enigmail-Version: 1.1.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: Tue, 20 Dec 2011 22:49:35 -0000

Folks,

We have published a new IETF I-D on "IPv6 smurf amplifiers". The I-D is
available at:
<http://tools.ietf.org/id/draft-gont-6man-ipv6-smurf-amplifier-00.txt>.

This may be an issue when BC38 is not deployed, or when the BCP38
implementation is buggy (yes, there have been instances of this).

Note: This vector can also be exploited with normal link-local multicast
addresses, but for obvious reasons it becomes a more important issue
with non-local multicast.

Abstract:
---- cut here ----
   When an IPv6 node processing an IPv6 packet does not support an IPv6
   option whose two-highest-order bits of the Option Type are '10', it
   is required to respond with an ICMPv6 Parameter Problem error
   message, even if the Destination Address of the packet was a
   multicast address.  This feature provides an amplification vector,
   opening the door to an IPv6 version of the 'Smurf' Denial-of-Service
   (DoS) attack found in IPv4 networks.  This document discusses the
   security implications of the aforementioned options, and formally
   updates RFC 2460 such that this attack vector is eliminated.
   Additionally, it describes a number of operational mitigations that
   could be deployed against this attack vector.
---- cut here ----

Any feedback will be welcome.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From fernando.gont.netbook.win@gmail.com  Tue Dec 20 14:49:39 2011
Return-Path: <fernando.gont.netbook.win@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 ABB5511E80A1 for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 14:49:39 -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 tadfmqnVYHwo for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 14:49:39 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id E12FB11E809F for <ipv6@ietf.org>; Tue, 20 Dec 2011 14:49:38 -0800 (PST)
Received: by ghbg18 with SMTP id g18so1425514ghb.31 for <ipv6@ietf.org>; Tue, 20 Dec 2011 14:49:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=SBAe/Esz7OakLNEueUtjH0HZmnGaFNXrdiyp/ymaZtY=; b=YP7KIQ0PaEZImcH5IXZ3rhMFciOXfE6+IYY4neAdXfn5ZL8HUAoAwg98sYKrsw0Edn ooXXEZX5DrDadHIN6WG1pAXJIJa//vzo/O+jhzIXPhDtvb+lxl+Lw48okGsxw5FVxltE 7/Ic6FKSx4sfzK8Og2wi46xZWTFno2z9YDMmI=
Received: by 10.236.155.194 with SMTP id j42mr6916213yhk.34.1324421378572; Tue, 20 Dec 2011 14:49:38 -0800 (PST)
Received: from [192.168.123.102] ([190.48.235.151]) by mx.google.com with ESMTPS id i32sm9123610anm.6.2011.12.20.14.49.35 (version=SSLv3 cipher=OTHER); Tue, 20 Dec 2011 14:49:37 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4EF0FFDF.6010703@gont.com.ar>
Date: Tue, 20 Dec 2011 18:36:31 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: Florian Weimer <fweimer@bfk.de>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com> <82fwgfk1ev.fsf@mid.bfk.de>
In-Reply-To: <82fwgfk1ev.fsf@mid.bfk.de>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 20 Dec 2011 22:49:39 -0000

Hello, Florian,

On 12/20/2011 07:00 AM, Florian Weimer wrote:
>> ---- cut here ----
>>    IPv6 allows packets to contain a Fragment Header, without the packet
>>    being actually fragmented into multiple pieces.  Such packets
>>    typically result from hosts that have received an ICMPv6 "Packet Too
>>    Big" error message that advertises a "Next-Hop MTU" smaller than 1280
>>    bytes, and are currently processed by hosts as "fragmented
>>    traffic".
> 
> Does such traffic actually occur in the wild, or would it only be used
> in attacks?

They have been seen in the wild. That aside, I don't know whether e.g.
NAT64 or the like used this (.e.g, whether they are used for transition
technologies as envisioned in RFC 2460). However, it might also be the
case that such "atomic fragments" are generated when communicating
through networks that do not really have a MTU >= 1280. In such
scenarios there might be some for of gateway that sends the ICMPv6 PTB
advertising a Next-Hop MTU smaller than 1280, thus resulting in atomic
fragments (such that it's easier for the "gateway" to fragment the IPv6
packets).

BTW, I seem to recall that when doing some testing, Linux doesn't react
to ICMPv6 PTB < 1280 as indicated in the specs. Can you confirm this?
ANd, if so, if this a bug, or "intented" behavior?


>>    By forging ICMPv6 "Packet Too Big" error messages an attacker can
>>    cause hosts to employ "atomic fragments", and the launch any
>>    fragmentation-based attacks against such traffic.  This document
>>    discusses the generation of the aforementioned "atomic fragments",
>>    the corresponding security implications, and formally updates RFC
>>    2460 and RFC 5722 such that the attack vector based on "atomic
>>    fragments" is completely eliminated.
> 
> My feeling is that such atomic fragments should be dropped from the
> protocol.

There seems to be stuff relying on them....

That aside, there's the proposal by Mark Andrews which would add yet
another use case for these atomic fragments.


> Per previous WG discussion, when reassembling such atomic fragments,
> IPv6 implementations must ignore the upper 16 bits of the fragment ID
> (otherwise the stateless v4/v6 gateways won't work).  Clearly, this is
> not desirable.

I may be missing something, but: when sending from the v6 side to the v4
side, we can probably assume that only the low order 16 bits of the
Fragment Identification field are used (whether you set the rest of the
bits or not, it doesn't matter -- particularly if the Fragment
Identification for each destination is a linear function (as e.g. in the
algorithm proposed in the I-D)). That is, you don't really need to do
anything special with the high order bits.

Am I missing something?

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fgont@si6networks.com  Tue Dec 20 20:57:01 2011
Return-Path: <fgont@si6networks.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 A85C221F8431 for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 20:57:01 -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 H9KTYO8IAYfy for <ipv6@ietfa.amsl.com>; Tue, 20 Dec 2011 20:57:01 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id E86F721F846B for <ipv6@ietf.org>; Tue, 20 Dec 2011 20:57:00 -0800 (PST)
Received: from [209.13.155.122] (helo=[192.168.1.8]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RdEEV-0003HE-VF; Wed, 21 Dec 2011 05:56:56 +0100
Message-ID: <4EF14D5F.9030802@si6networks.com>
Date: Wed, 21 Dec 2011 00:07:11 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: Fragmentation-related security issues
References: <C288ACA0-E09B-4F23-800C-294E4BADE00F@gmail.com>
In-Reply-To: <C288ACA0-E09B-4F23-800C-294E4BADE00F@gmail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 21 Dec 2011 04:57:01 -0000

Hi, Ran,

On 12/20/2011 02:07 PM, RJ Atkinson wrote:
> MORE GENERALLY:
> 
> We need to AVOID falling into the trap that things 
> not explicitly allowed are always security 
> vulnerabilities and lack legitimate reasons to exist.  
> IPv6 is not "done" -- any useful deployed protocol 
> will evolve over time.

FWIW, draft-gont-6man-ipv6-atomic-fragments avoid the security
implications while still allowing the use of the aforementioned packets.
Actually, one might even argue that trying to "reassemble" an atomic
packet with any other fragment is rather non-sensical...


> So it is not helpful to publish documents that 
> advise firewall/middlebox/router vendors to filter out 
> "unknown" behaviour or "curious" packet patterns or 
> unrecognised options.  
> 
> For example, if a firewall doesn't recognise
> (e.g. due to lack of firewall firmware update) 
> some new IPv6 option (e.g. carried in an IPv6 
> Destination Header), the firewall ought NOT
> filter/drop packets with that new/unrecognised 
> option.

While I understand your concern, from the firewall perspective things
generally are "whatever I have not explicitly allowed, is blocked".

There are understandable arguments both ways. From a networking point of
view, the aforementioned behaviour hurts protocol evolution and
extensibility. From a security point of view, you only allow what you
really need (i.e. "need to pass" basis ;-) ).


> We do NOT want to close the door on IPv6 (or IPv4 
> or TCP or UDP or ...) evolution.  Proscriptive and
> paranoid recommendations to implementers WILL and
> DO close the door on evolution -- and hence can be
> harmful to the Internet.

Just to clarify on this point, I don't think any of these 6man I-Ds I've
published last week fall into this category. In particular, the
fragmentation-related ones aim at mitigating security implications
without any impact on protocol evolution.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From robert.cragie@gridmerge.com  Wed Dec 21 05:25:26 2011
Return-Path: <robert.cragie@gridmerge.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 E47C821F8A62 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 05:25:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 5009HXEBV88n for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 05:25:23 -0800 (PST)
Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by ietfa.amsl.com (Postfix) with ESMTP id 9C07921F8A56 for <ipv6@ietf.org>; Wed, 21 Dec 2011 05:25:22 -0800 (PST)
Received: from client-82-27-15-3.pete.adsl.virginmedia.com ([82.27.15.3] helo=[192.168.0.2]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) id 1RdMAM-0003gH-KU for ipv6@ietf.org; Wed, 21 Dec 2011 13:25:08 +0000
Message-ID: <4EF1DE4A.2080104@gridmerge.com>
Date: Wed, 21 Dec 2011 13:25:30 +0000
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: draft-ietf-6man-rpl-routing-header-07
References: <055FAFECB2B53642884D29B0094D14751098099F@DLEE10.ent.ti.com> <055FAFECB2B53642884D29B0094D1475109809D8@DLEE10.ent.ti.com>
In-Reply-To: <055FAFECB2B53642884D29B0094D1475109809D8@DLEE10.ent.ti.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030205010703050302070000"
X-Authenticated-As: robert.cragie@gridmerge.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.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, 21 Dec 2011 13:25:27 -0000

This is a cryptographically signed message in MIME format.

--------------ms030205010703050302070000
Content-Type: multipart/alternative;
 boundary="------------020208020905090209000300"

This is a multi-part message in MIME format.
--------------020208020905090209000300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Looks like I missed the boat, but I also had some comments on=20
draft-ietf-6man-rpl-routing-header-07:

_More significant comments_

p7: RPL Instance ID - why is this needed for source routing? RPL is not=20
even used for source routing. This flavors the SRH unnecessarily and the =

processing does not use it. If the reason is for checking entering and=20
exiting a RPL domain, this processing needs to be stated.

p10: "In order to respect the IPv6 Hop Limit value of the original=20
datagram, a RPL router generating an SRH MUST set the Segments Left to=20
no greater than the original datagram's IPv6 Hop Limit value upon=20
forwarding.". This language is confusing. 'upon forwarding' suggests=20
that it is the 'IPv6 Hop Limit - 1' value, and again only if it is=20
forwarded, but it is not clear. Also, an 'original datagram' may not=20
always be *forwarded*, i.e. if it originates on the RPL router itself.

p10: "In the case that the source route is longer than the original=20
datagram's IPv6 Hop Limit, only the initial hops (determined by the=20
original datagram's IPv6 Hop Limit) should be included in the SRH.".=20
This means it is unlikely to reach its destination, so why bother?

p10: "If the RPL router is not the source of the original datagram, the=20
original datagram's IPv6 Hop Limit field is decremented before=20
generating the SRH." If this were placed the the beginning of the=20
paragraph, it might be clearer.

p10: "After generating the SRH, the RPL router decrements the original=20
datagram's IPv6 Hop Limit value by the SRH Segments Left value. =20
Processing the SRH Segments Left and original datagram's IPv6 Hop Limit=20
fields in this way ensures that ICMPv6 Time Exceeded errors occur as=20
would be expected on more traditional IPv6 networks that forward=20
datagrams without tunneling." It's not really a tunnel then as defined=20
by RFC 2473 and somewhat conflicts with what's written in RFC 2473.=20
Also, you don't want to do this when the packet is not tunneled or you=20
will be double counting.

_Minor (use of language) comments:_

Throughout: Inconsistent use of:

1. 'router'
2. 'RPL router'
3. 'RPL Router'

(3) (note capitalization) is a defined term. (1) and (2) are used=20
generally but inconsistently. Use 'RPL router' to mean a 'RPL Border=20
Router' or a 'RPL Router' throughout. Use 'a RPL router' as introductory =

to a sentence and, if necessary, 'the router' only to refer to the=20
introduced RPL router, although 'the RPL router' is generally better.=20
This would make the document clearer in places.

p1: "or few routers" -> "or a few routers". Reason for change: 'few=20
routers' on its own implies 'not many routers'.

p6: "In the scenarios above, R may indicate a RPL Border Router (when=20
connecting to other routing domains) or a RPL Router" -> "In the=20
scenarios above, the RPL router R may indicate a RPL Border Router (when =

connecting to other routing domains) or a RPL Router". Reason for=20
change: This introduces the term 'RPL router' as either a 'RPL Border=20
Router' or a 'RPL Router' (note both are defined terms) correctly for=20
the subsequent paragraph.

p6: "One such use case with RPL is to have all RPL traffic flow through=20
a Border Router and have the Border Router use source routes to deliver=20
datagrams to their final destination.  When including the SRH using=20
tunneled mode, the Border Router would encapsulate the received datagram =

unmodified using IPv6-in-IPv6 and include a SRH in the outer IPv6=20
header." -> "One such use case with RPL is to have all RPL traffic flow=20
through a RPL Border Router and have the RPL Border Router use source=20
routes to deliver datagrams to their final destination.  When including=20
the SRH using tunneled mode, the RPL Border Router would encapsulate the =

received datagram unmodified using IPv6-in-IPv6 and include a SRH in the =

outer IPv6 header." Reason for change: Uses the correct terminology.

p6: "In the above scenario, datagrams travel from S to D through LBR" -> =

"In the above scenario, datagrams travel from S to D through the RPL=20
Border Router LBR (referred to as LBRs in [I-D.ietf-roll-terminology])". =

Reason for change: Clarify what LBR is.

Robert


On 19/12/2011 11:59 PM, Park, Kundok wrote:
>
> As another side note, this new draft revision creates a situation=20
> where the hop limit from the RPL router performing source routing may=20
> be one and hence it cannot use SRH (because Segments Left becomes zero =

> and no address can be included). In order to make it appear as if it=20
> tried the source routing with one hop, I think the RPL router must=20
> forward the packet to the next hop that it should normally pick for a=20
> source routing without modifying the original packet (that is, the=20
> destination address remains the same as the final destination). I=20
> don't think this requires any change to the draft because the RPL=20
> router in this case is not using SRH and hence out of scope of this dra=
ft.
>
> BR,
>
> Kundok
>
> -----------------------------------------------------------------------=
-
>
> *From:*ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] *On Behalf =

> Of *Park, Kundok
> *Sent:* Monday, December 19, 2011 1:18 PM
> *To:* ipv6@ietf.org
> *Subject:* draft-ietf-6man-rpl-routing-header-07
>
> It seems that the following text on page 10 has some slight oversights:=

>
> "
>
>     In order to respect the IPv6 Hop Limit value of the original
>     datagram, a RPL router generating an SRH MUST set the Segments Left=

>     to_no greater_  than the original datagram's IPv6 Hop Limit value u=
pon
>     forwarding.
>
> "
>
> should have been as follows:
>
> "
>
>     In order to respect the IPv6 Hop Limit value of the original
>     datagram, a RPL router generating an SRH_in an IPv6-in-IPv6 tunnel_=

>     MUST set the Segments Left to_less_  than the original datagram's I=
Pv6
>     Hop Limit value upon forwarding.
>
> "
>
> If the Segments Left is equal to Hop Limit value, the source route=20
> includes one more hop than the hop limit, which is not intended here.
>
> The other change is to make clear that the above phrase does not apply =

> to the case where the SRH is directly included within the original pack=
et.
>
> As a side note, the traceroute application doesn't seem to be able to=20
> handle the case with no tunnel use, because the original datagram=20
> destination address alters when SRH is added, unless, I guess,=20
> traceroute application is re-written to handle source routing in=20
> returned ICMPv6 error messages. Perhaps, that recommended direct=20
> inclusion of SRH should be removed?
>
> Best Regards,
>
> Kundok
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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

<html>
  <head>
    <meta content=3D"text/html; charset=3DISO-8859-1"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    Looks like I missed the boat, but I also had some comments on
    draft-ietf-6man-rpl-routing-header-07:<br>
    <br>
    _More significant comments_<br>
    <br>
    p7: RPL Instance ID - why is this needed for source routing? RPL is
    not even used for source routing. This flavors the SRH unnecessarily
    and the processing does not use it. If the reason is for checking
    entering and exiting a RPL domain, this processing needs to be
    stated.<br>
    <br>
    p10: "In order to respect the IPv6 Hop Limit value of the original
    datagram, a RPL router generating an SRH MUST set the Segments Left
    to no greater than the original datagram's IPv6 Hop Limit value upon
    forwarding.". This language is confusing. 'upon forwarding' suggests
    that it is the 'IPv6 Hop Limit - 1' value, and again only if it is
    forwarded, but it is not clear. Also, an 'original datagram' may not
    always be *forwarded*, i.e. if it originates on the RPL router
    itself.<br>
    <br>
    p10: "In the case that the source route is longer than the original
    datagram's IPv6 Hop Limit, only the initial hops (determined by the
    original datagram's IPv6 Hop Limit) should be included in the SRH.".
    This means it is unlikely to reach its destination, so why bother?<br=
>
    <br>
    p10: "If the RPL router is not the source of the original datagram,
    the original datagram's IPv6 Hop Limit field is decremented before
    generating the SRH." If this were placed the the beginning of the
    paragraph, it might be clearer.<br>
    <br>
    p10: "After generating the SRH, the RPL router decrements the
    original datagram's IPv6 Hop Limit value by the SRH Segments Left
    value.&nbsp; Processing the SRH Segments Left and original datagram's=

    IPv6 Hop Limit fields in this way ensures that ICMPv6 Time Exceeded
    errors occur as would be expected on more traditional IPv6 networks
    that forward datagrams without tunneling." It's not really a tunnel
    then as defined by RFC 2473 and somewhat conflicts with what's
    written in RFC 2473. Also, you don't want to do this when the packet
    is not tunneled or you will be double counting.<br>
    <br>
    _Minor (use of language) comments:_<br>
    <br>
    Throughout: Inconsistent use of:<br>
    <br>
    1. 'router'<br>
    2. 'RPL router'<br>
    3. 'RPL Router'<br>
    <br>
    (3) (note capitalization) is a defined term. (1) and (2) are used
    generally but inconsistently. Use 'RPL router' to mean a 'RPL Border
    Router' or a 'RPL Router' throughout. Use 'a RPL router' as
    introductory to a sentence and, if necessary, 'the router' only to
    refer to the introduced RPL router, although 'the RPL router' is
    generally better. This would make the document clearer in places.<br>=

    <br>
    p1: "or few routers" -&gt; "or a few routers". Reason for change:
    'few routers' on its own implies 'not many routers'.<br>
    <br>
    p6: "In the scenarios above, R may indicate a RPL Border Router
    (when connecting to other routing domains) or a RPL Router" -&gt;
    "In the scenarios above, the RPL router R may indicate a RPL Border
    Router (when connecting to other routing domains) or a RPL Router".
    Reason for change: This introduces the term 'RPL router' as either a
    'RPL Border Router' or a 'RPL Router' (note both are defined terms)
    correctly for the subsequent paragraph.<br>
    <br>
    p6: "One such use case with RPL is to have all RPL traffic flow
    through a Border Router and have the Border Router use source routes
    to deliver datagrams to their final destination.&nbsp; When including=
 the
    SRH using tunneled mode, the Border Router would encapsulate the
    received datagram unmodified using IPv6-in-IPv6 and include a SRH in
    the outer IPv6 header." -&gt; "One such use case with RPL is to have
    all RPL traffic flow through a RPL Border Router and have the RPL
    Border Router use source routes to deliver datagrams to their final
    destination.&nbsp; When including the SRH using tunneled mode, the RP=
L
    Border Router would encapsulate the received datagram unmodified
    using IPv6-in-IPv6 and include a SRH in the outer IPv6 header."
    Reason for change: Uses the correct terminology.<br>
    <br>
    p6: "In the above scenario, datagrams travel from S to D through
    LBR" -&gt; "In the above scenario, datagrams travel from S to D
    through the RPL Border Router LBR (referred to as LBRs in
    [I-D.ietf-roll-terminology])". Reason for change: Clarify what LBR
    is.<br>
    <br>
    Robert<br>
    <br>
    <br>
    On 19/12/2011 11:59 PM, Park, Kundok wrote:
    <blockquote
      cite=3D"mid:055FAFECB2B53642884D29B0094D1475109809D8@DLEE10.ent.ti.=
com"
      type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html;
        charset=3DISO-8859-1">
      <meta name=3D"Generator" content=3D"Microsoft Word 11 (filtered
        medium)">
      <!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
=2Eshape {behavior:url(#default#VML);}
</style>
<![endif]-->
      <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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]-->
      <div class=3D"Section1">
        <p class=3D"MsoNormal"><font color=3D"blue" face=3D"Arial" size=3D=
"2"><span
              style=3D"font-size:
              10.0pt;font-family:Arial;color:blue">As another side note,
              this new draft revision creates a situation where the hop
              limit from the RPL router performing source routing may be
              one and hence it cannot use SRH (because Segments Left
              becomes zero and no address can be included). In order to
              make it appear as if it tried the source routing with one
              hop, I think the RPL router must forward the packet to the
              next hop that it should normally pick for a source routing
              without modifying the original packet (that is, the
              destination address remains the same as the final
              destination). I don&#8217;t think this requires any change =
to
              the draft because the RPL router in this case is not using
              SRH and hence out of scope of this draft.<o:p></o:p></span>=
</font></p>
        <p class=3D"MsoNormal"><font color=3D"blue" face=3D"Arial" size=3D=
"2"><span
              style=3D"font-size:
              10.0pt;font-family:Arial;color:blue"><o:p>&nbsp;</o:p></spa=
n></font></p>
        <p class=3D"MsoNormal"><font color=3D"blue" face=3D"Arial" size=3D=
"2"><span
              style=3D"font-size:
              10.0pt;font-family:Arial;color:blue">BR,<o:p></o:p></span><=
/font></p>
        <p class=3D"MsoNormal"><font color=3D"blue" face=3D"Arial" size=3D=
"2"><span
              style=3D"font-size:
              10.0pt;font-family:Arial;color:blue">Kundok<o:p></o:p></spa=
n></font></p>
        <p class=3D"MsoNormal"><font color=3D"blue" face=3D"Arial" size=3D=
"2"><span
              style=3D"font-size:
              10.0pt;font-family:Arial;color:blue"><o:p>&nbsp;</o:p></spa=
n></font></p>
        <div style=3D"border:none;border-left:solid blue 1.5pt;padding:0i=
n
          0in 0in 4.0pt">
          <div>
            <div class=3D"MsoNormal" style=3D"text-align:center"
              align=3D"center"><font face=3D"Times New Roman" size=3D"3">=
<span
                  style=3D"font-size:12.0pt">
                  <hr tabindex=3D"-1" align=3D"center" size=3D"2" width=3D=
"100%">
                </span></font></div>
            <p class=3D"MsoNormal"><b><font face=3D"Tahoma" size=3D"2"><s=
pan
                    style=3D"font-size:10.0pt;
                    font-family:Tahoma;font-weight:bold">From:</span></fo=
nt></b><font
                face=3D"Tahoma" size=3D"2"><span
                  style=3D"font-size:10.0pt;font-family:Tahoma">
                  <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:ip=
v6-bounces@ietf.org">ipv6-bounces@ietf.org</a> [<a class=3D"moz-txt-link-=
freetext" href=3D"mailto:ipv6-bounces@ietf.org">mailto:ipv6-bounces@ietf.=
org</a>]
                  <b><span style=3D"font-weight:
                      bold">On Behalf Of </span></b>Park, Kundok<br>
                  <b><span style=3D"font-weight:bold">Sent:</span></b>
                  Monday, December 19, 2011 1:18 PM<br>
                  <b><span style=3D"font-weight:bold">To:</span></b>
                  <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:ip=
v6@ietf.org">ipv6@ietf.org</a><br>
                  <b><span style=3D"font-weight:bold">Subject:</span></b>=

                  draft-ietf-6man-rpl-routing-header-07</span></font><o:p=
></o:p></p>
          </div>
          <p class=3D"MsoNormal"><font face=3D"Times New Roman" size=3D"3=
"><span
                style=3D"font-size:
                12.0pt"><o:p>&nbsp;</o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">It seems that the following text on
                page 10 has some slight oversights:<o:p></o:p></span></fo=
nt></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">&#8220;<o:p></o:p></span></font></p>
          <pre><font face=3D"Courier New" size=3D"2"><span style=3D"font-=
size:10.0pt">&nbsp;&nbsp; In order to respect the IPv6 Hop Limit value of=
 the original<o:p></o:p></span></font></pre>
          <pre><font face=3D"Courier New" size=3D"2"><span style=3D"font-=
size:10.0pt">&nbsp;&nbsp; datagram, a RPL router generating an SRH MUST s=
et the Segments Left<o:p></o:p></span></font></pre>
          <pre><font face=3D"Courier New" size=3D"2"><span style=3D"font-=
size:10.0pt">&nbsp;&nbsp; to <u>no greater</u> than the original datagram=
's IPv6 Hop Limit value upon<o:p></o:p></span></font></pre>
          <pre><font face=3D"Courier New" size=3D"2"><span style=3D"font-=
size:10.0pt">&nbsp;&nbsp; forwarding.<o:p></o:p></span></font></pre>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">&#8220;<o:p></o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">should have been as follows:<o:p></o:p=
></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">&#8220;<o:p></o:p></span></font></p>
          <pre><font face=3D"Courier New" size=3D"2"><span style=3D"font-=
size:10.0pt">&nbsp;&nbsp; In order to respect the IPv6 Hop Limit value of=
 the original<o:p></o:p></span></font></pre>
          <pre><font face=3D"Courier New" size=3D"2"><span style=3D"font-=
size:10.0pt">&nbsp;&nbsp; datagram, a RPL router generating an SRH <u>in =
an IPv6-in-IPv6 tunnel</u><o:p></o:p></span></font></pre>
          <pre><font face=3D"Courier New" size=3D"2"><span style=3D"font-=
size:10.0pt">&nbsp;&nbsp; MUST set the Segments Left to <u>less</u> than =
the original datagram's IPv6<o:p></o:p></span></font></pre>
          <pre><font face=3D"Courier New" size=3D"2"><span style=3D"font-=
size:10.0pt">&nbsp; &nbsp;Hop Limit value upon forwarding.<o:p></o:p></sp=
an></font></pre>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">&#8220;<o:p></o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">If the Segments Left is equal to Hop
                Limit value, the source route includes one more hop than
                the hop limit, which is not intended here.<o:p></o:p></sp=
an></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">The other change is to make clear
                that the above phrase does not apply to the case where
                the SRH is directly included within the original packet.<=
o:p></o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">As a side note, the traceroute
                application doesn&#8217;t seem to be able to handle the c=
ase
                with no tunnel use, because the original datagram
                destination address alters when SRH is added, unless, I
                guess, traceroute application is re-written to handle
                source routing in returned ICMPv6 error messages.
                Perhaps, that recommended direct inclusion of SRH should
                be removed?<o:p></o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">Best Regards,<o:p></o:p></span></font>=
</p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial">Kundok<o:p></o:p></span></font></p>
          <p class=3D"MsoNormal"><font face=3D"Arial" size=3D"2"><span
                style=3D"font-size:10.0pt;
                font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
        </div>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">----------------------------------------------------=
----------------
IETF IPv6 working group mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:ipv6@ietf.org">ipv6@=
ietf.org</a>
Administrative Requests: <a class=3D"moz-txt-link-freetext" href=3D"https=
://www.ietf.org/mailman/listinfo/ipv6">https://www.ietf.org/mailman/listi=
nfo/ipv6</a>
--------------------------------------------------------------------
</pre>
    </blockquote>
  </body>
</html>

--------------020208020905090209000300--

--------------ms030205010703050302070000
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIP3jCC
BIowggNyoAMCAQICECf06hH0eobEbp27bqkXBwcwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UE
BhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5h
bCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0w
NTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMC
VVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5l
dHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVN
NRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQy
lbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXq
vgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6
hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu
9mIwFIws6wIDAQABo4HhMIHeMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0G
A1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/
BAUwAwEB/zB7BgNVHR8EdDByMDigNqA0hjJodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9BZGRU
cnVzdEV4dGVybmFsQ0FSb290LmNybDA2oDSgMoYwaHR0cDovL2NybC5jb21vZG8ubmV0L0Fk
ZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQAZ2IkRbyispgCi
54fBm5AD236hEv0e8+LwAamUVEJrmgnEoG3XkJIEA2Z5Q3H8+G+v23ZF4jcaPd3kWQR4rBz0
g0bzes9bhHIt5UbBuhgRKfPLSXmHPLptBZ2kbWhPrXIUNqi5sf2/z3/wpGqUNVCPz4FtVbHd
WTBK322gnGQfSXzvNrv042n0+DmPWq1LhTq3Du3Tzw1EovsEv+QvcI4l+1pUBrPQxLxtjftz
Mizpm4QkLdZ/kXpoAlAfDj9N6cz1u2fo3BwuO/xOzf4CjuOoEwqlJkRl6RDyTVKnrtw+ymsy
XEFs/vVdoOr/0fqbhlhtPZZH5f4ulQTCAMyOofK7MIIFGjCCBAKgAwIBAgIQbRnqpxlPajMi
5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcw
FQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3Jr
MSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VS
Rmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMTA0MjgwMDAwMDBa
Fw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tXmNReL4uk4UDIo1NY
X2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vxaa7lIBvky2NeYMqi
QfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrlVICv2HEKHTcKAlBT
bJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+OsvxQ7sCVxaD30D9YX
WEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hRmWONGoulzEKbm30i
Y9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0jBBgwFoAUiYJnfcSd
JnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8ecV7MA4GA1UdDwEB
/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYEVR0gADBYBgNVHR8E
UTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVTRVJGaXJzdC1DbGll
bnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRoMGYwPQYIKwYBBQUH
MAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENsaWVudF9DQS5jcnQw
JQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQEFBQAD
ggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtzbj7pJnzmTJjBMCjf
y/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqTecr+4pEeVnSy+I3T
4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPNM1+b0L1garM7/vrU
yTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZhtZdVwcbpzC+S0lE
uJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/bucwggYuMIIFFqAD
AgECAhBcMVDbxC2oy5hyHl/adO9mMA0GCSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEb
MBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQK
ExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDkwMjAwMDAwMFoXDTE0MDkwMTIzNTk1
OVowggE3MQswCQYDVQQGEwJHQjEQMA4GA1UEERMHV0Y0IDRXQTEXMBUGA1UECBMOV2VzdCBZ
b3Jrc2hpcmUxEjAQBgNVBAcTCVdha2VmaWVsZDEUMBIGA1UECRMLR3JhbmdlIE1vb3IxHzAd
BgNVBAkTFjg5IEdyZWVuZmllbGQgQ3Jlc2NlbnQxFzAVBgNVBAoTDkdyaWRtZXJnZSBMdGQu
MTQwMgYDVQQLEytJc3N1ZWQgdGhyb3VnaCBHcmlkbWVyZ2UgTHRkLiBFLVBLSSBNYW5hZ2Vy
MR8wHQYDVQQLExZDb3Jwb3JhdGUgU2VjdXJlIEVtYWlsMRYwFAYDVQQDEw1Sb2JlcnQgQ3Jh
Z2llMSowKAYJKoZIhvcNAQkBFhtyb2JlcnQuY3JhZ2llQGdyaWRtZXJnZS5jb20wggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxOGq8t5ZTVDVkmadv7ZRBLA5ApaiTcDUzCTn
zYB2/BoBDIEWWI/InSRcmq3A0Ghm+T7dYmvRADllGv4nTHexdWlzFp2iM/Yc3PLWCyAO0gYb
yW2hTi+ZfUDwFOU4hRP4+Dyn9tKu7FXS/PQJHyGjaGxHRmLm9T6tAo2ZuC59uRaGVCcwRiOS
d6axwtB/DVhnP3S1rrt2g0O6MXLr5fojToemO52AxjHxt2w1LnFUUXC4EDV6o1Ctr7EvOEI5
5f088H/Mrryp02GueLdY9gb0SFK3gPOT7EjP2GPvCtRkhVcNM+xjyptRIFWnCbMjmUIc+DO6
sfU4rtbCCkNKyXmnAgMBAAGjggHVMIIB0TAfBgNVHSMEGDAWgBR6E04AdFvGeGNkJ8Ev4qBb
vHnFezAdBgNVHQ4EFgQUEI5c0f6UObxT2DLdvdtG+vG8qCswDgYDVR0PAQH/BAQDAgWgMAwG
A1UdEwEB/wQCMAAwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMEYGA1UdIAQ/MD0w
OwYMKwYBBAGyMQECAQMFMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5u
ZXQvQ1BTMFcGA1UdHwRQME4wTKBKoEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9E
T0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEB
BHwwejBSBggrBgEFBQcwAoZGaHR0cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50
QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDov
L29jc3AuY29tb2RvY2EuY29tMCYGA1UdEQQfMB2BG3JvYmVydC5jcmFnaWVAZ3JpZG1lcmdl
LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAPpv87QuQ9q+RHhmeirGDQB3szd24Obi7N+uVfh5y
CrnoJx3B37dNrLPsTB6PfTChUyZMqQD80pFoJ3TBUz3yx4X+hmNco7ujVIfbuKBGcZJaMKhZ
ex3AkZ9ltie9wgiGGzEmgI81t5JHsLQ8AUMqw/fGsnIwcyWMgmyhFtm79+dg3IVaH05d/t9g
k4aYoMoCFJptQZ+Fju6a9T139hOqjTZDpjMLt3jM80bVrvkC4dIRyF/oZ0qrJwbfwjnL2OUN
ph9eymhLc+VM0Ih5k41s5IxmB+2c0RUqr5JbK0WrIb/z53Cmb9rXYox7HknyIfBpQqP77Y7a
sAU2MMOpel4RijGCBAwwggQIAgEBMIGoMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3Jl
YXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0Eg
TGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2Vj
dXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMAkGBSsOAwIaBQCgggI4MBgGCSqGSIb3
DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTIyMTEzMjUzMFowIwYJKoZI
hvcNAQkEMRYEFNmSWlr1ZTeHYmdxlmOqmLjWHNo5MF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDCBuQYJKwYBBAGCNxAEMYGrMIGoMIGTMQswCQYDVQQGEwJH
QjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYD
VQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMIG7BgsqhkiG
9w0BCRACCzGBq6CBqDCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hl
c3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3
BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBD
QQIQXDFQ28QtqMuYch5f2nTvZjANBgkqhkiG9w0BAQEFAASCAQCZK+oj5wCmULlw4KSZqkKq
NJ0XUEzSiMPI81zMCTO3bCACjj948vJs828GwBQgaqAJO05gQ6xaMY8DOkNkj10ZXZWzE6cf
pt5JnxlQmrNaz6ofefLPkqVp+4ZskTcbc8RlxJJnvXs/yCIGDyFWg+NzLHDJbqaOhHx7QiQF
LBA0/jcxHeHbOGNuREtfBfG2cTbcokgy8ROepjZNQAYusQIv9PkmSbsahQQpyzxDCRqgS9/l
ngGDmRKI+vX1xNWS5pKYeFStzsLiE4fb0UVl1z6TEUbcMVEia7YvyOE1CggLpiNQhefGuGIz
BaADlNIYcpFVvEEYV31w7CuTfyPtAHmnAAAAAAAA
--------------ms030205010703050302070000--

From marka@isc.org  Wed Dec 21 06:03:11 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 3C5C611E8093 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 06:03:11 -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 rdXYUOwLgMX7 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 06:03:10 -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 A2C9811E808A for <ipv6@ietf.org>; Wed, 21 Dec 2011 06:03:10 -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 77EC65F98B9; Wed, 21 Dec 2011 14:02:46 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:1cf7:c90d:8e34:7b4f]) (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 6B178216C6A; Wed, 21 Dec 2011 14:02: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 3259D1A6F096; Thu, 22 Dec 2011 01:02:41 +1100 (EST)
To: sthaug@nethelp.no
From: Mark Andrews <marka@isc.org>
References: <4EEA0342.2040608@si6networks.com> <82fwgfk1ev.fsf@mid.bfk.de> <20111220.124458.41706285.sthaug@nethelp.no>
Subject: Re: Fragmentation-related security issues
In-reply-to: Your message of "Tue, 20 Dec 2011 12:44:58 BST." <20111220.124458.41706285.sthaug@nethelp.no>
Date: Thu, 22 Dec 2011 01:02:41 +1100
Message-Id: <20111221140241.3259D1A6F096@drugs.dv.isc.org>
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: Wed, 21 Dec 2011 14:03:11 -0000

In message <20111220.124458.41706285.sthaug@nethelp.no>, sthaug@nethelp.no writes:
> > >    IPv6 allows packets to contain a Fragment Header, without the packet
> > >    being actually fragmented into multiple pieces.  Such packets
> > >    typically result from hosts that have received an ICMPv6 "Packet Too
> > >    Big" error message that advertises a "Next-Hop MTU" smaller than 1280
> > >    bytes, and are currently processed by hosts as "fragmented
> > >    traffic".
> > 
> > Does such traffic actually occur in the wild, or would it only be used
> > in attacks?
> 
> Such traffic absolutely occurs in the wild. I have three reasonably
> busy name servers where this is logged as an error from the ipfw code,
> e.g.
> 
> Dec 16 14:04:04 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 17 00:27:20 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 18 07:53:10 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 18 23:21:37 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 19 03:07:43 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 19 05:09:45 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 19 21:47:46 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 20 08:10:59 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 20 08:59:21 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> Dec 20 11:25:59 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> 
> This is because these name servers haven't (yet) been upgraded to a
> FreeBSD version where bug report kern/145733 haven't been fixed. It
> *is* fixed in newer FreeBSD versions, e.g. 8.2-STABLE.

Not yet.
http://svnweb.freebsd.org/base/stable/8/sys/netinet/ipfw/ip_fw2.c?view=log
 
> Steinar Haug, Nethelp consulting, sthaug@nethelp.no
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From brian@innovationslab.net  Wed Dec 21 07:12:31 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 723D921F849C for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 07:12: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 1nBNcduxy+PV for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 07:12:30 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 777F521F8496 for <ipv6@ietf.org>; Wed, 21 Dec 2011 07:12:30 -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 3FC8988218 for <ipv6@ietf.org>; Wed, 21 Dec 2011 07:12:30 -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 EFC7E130004 for <ipv6@ietf.org>; Wed, 21 Dec 2011 07:12:29 -0800 (PST)
Message-ID: <4EF1F75B.6060009@innovationslab.net>
Date: Wed, 21 Dec 2011 10:12:27 -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: 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; 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: Wed, 21 Dec 2011 15:12:31 -0000

All,
      The WG Last Call has ended with a strong show of support.

Wes,
      Are there any editorial changes that need to be made prior to 
advancement?

Regards,
Brian

On 11/29/11 10:51 AM, 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 sthaug@nethelp.no  Wed Dec 21 07:16:10 2011
Return-Path: <sthaug@nethelp.no>
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 B516821F85B1 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 07:16:10 -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 Nhud4JZWIh48 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 07:16:10 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 8CC1D11E8073 for <ipv6@ietf.org>; Wed, 21 Dec 2011 07:16:09 -0800 (PST)
Received: (qmail 83550 invoked from network); 21 Dec 2011 15:16:07 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 21 Dec 2011 15:16:07 -0000
Date: Wed, 21 Dec 2011 16:16:07 +0100 (CET)
Message-Id: <20111221.161607.74682637.sthaug@nethelp.no>
To: marka@isc.org
Subject: Re: Fragmentation-related security issues
From: sthaug@nethelp.no
In-Reply-To: <20111221140241.3259D1A6F096@drugs.dv.isc.org>
References: <82fwgfk1ev.fsf@mid.bfk.de> <20111220.124458.41706285.sthaug@nethelp.no> <20111221140241.3259D1A6F096@drugs.dv.isc.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
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: Wed, 21 Dec 2011 15:16:10 -0000

> > This is because these name servers haven't (yet) been upgraded to a
> > FreeBSD version where bug report kern/145733 haven't been fixed. It
> > *is* fixed in newer FreeBSD versions, e.g. 8.2-STABLE.
> 
> Not yet.
> http://svnweb.freebsd.org/base/stable/8/sys/netinet/ipfw/ip_fw2.c?view=log

Sorry, you're right. I had patched it on my own 8.2-STABLE servers and
forgotten all about it (since the error messages stopped).

Hopefully this will be merged to 8.2-STABLE soon.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From jonhui@cisco.com  Wed Dec 21 07:51:34 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 DDCD011E808A for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 07:51:34 -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 w6DJydmyD8jD for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 07:51:34 -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 1A28721F8ABE for <ipv6@ietf.org>; Wed, 21 Dec 2011 07:51:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=5295; q=dns/txt; s=iport; t=1324482694; x=1325692294; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=pVptHrfyoSJViig4Bq2YrD4OtaMyrBdNVCgEXwl6ozg=; b=UkbRd1K3TPZBR33tnsCd456csRL92+VVGY4s4aX6w1IH5XCLzlVIa9sI gCX4wn5+1ZQJkVUpkajQ6nKi8J7Q+C7ndFWCKGn1X+FoIpkBtj9d/R6ZV ghWQ/ckhDdedhqCvaMuI7Z6Dc8i+Lo+sZmUvIeNkxDFfIyGCY3qS7VrmN c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAJD/8U6rRDoJ/2dsb2JhbABDrBqBBYFyAQEBAwESARQTPwULC0ZXO4dYmQwBnlGLLGMEiDeMSJJT
X-IronPort-AV: E=Sophos;i="4.71,388,1320624000"; d="scan'208";a="20188363"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 21 Dec 2011 15:51:33 +0000
Received: from dhcp-128-107-155-213.cisco.com (dhcp-128-107-155-213.cisco.com [128.107.155.213]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pBLFpXpH021109; Wed, 21 Dec 2011 15:51:33 GMT
Subject: Re: draft-ietf-6man-rpl-routing-header-07
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <4EF1DE4A.2080104@gridmerge.com>
Date: Wed, 21 Dec 2011 07:51:33 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <439AF687-83D0-4581-A4EB-13104047B41C@cisco.com>
References: <055FAFECB2B53642884D29B0094D14751098099F@DLEE10.ent.ti.com> <055FAFECB2B53642884D29B0094D1475109809D8@DLEE10.ent.ti.com> <4EF1DE4A.2080104@gridmerge.com>
To: robert.cragie@gridmerge.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: Wed, 21 Dec 2011 15:51:35 -0000

Hi Robert,

Thanks for your review.  We'll try to address what we can in the next =
revision.  See below:

On Dec 21, 2011, at 5:25 AM, Robert Cragie wrote:

> Looks like I missed the boat, but I also had some comments on =
draft-ietf-6man-rpl-routing-header-07:
>=20
> _More significant comments_
>=20
> p7: RPL Instance ID - why is this needed for source routing? RPL is =
not even used for source routing. This flavors the SRH unnecessarily and =
the processing does not use it. If the reason is for checking entering =
and exiting a RPL domain, this processing needs to be stated.

Page 12 describes processing rules intended to keep the SRH within a RPL =
Instance.

> p10: "In order to respect the IPv6 Hop Limit value of the original =
datagram, a RPL router generating an SRH MUST set the Segments Left to =
no greater than the original datagram's IPv6 Hop Limit value upon =
forwarding.". This language is confusing. 'upon forwarding' suggests =
that it is the 'IPv6 Hop Limit - 1' value, and again only if it is =
forwarded, but it is not clear. Also, an 'original datagram' may not =
always be *forwarded*, i.e. if it originates on the RPL router itself.

"Upon forwarding" was intended to indicate "upon submitting to the =
proper interface for forwarding".  Would you prefer the RFC 2473 =
language: "during forwarding"?  We purposely did not indicate that it is =
the IPv6 Hop Limit - 1 value because, as you indicate, the original =
datagram may  originate on the router itself.

> p10: "In the case that the source route is longer than the original =
datagram's IPv6 Hop Limit, only the initial hops (determined by the =
original datagram's IPv6 Hop Limit) should be included in the SRH.". =
This means it is unlikely to reach its destination, so why bother?

To support traceroute, which was an application that ZigBee/IP members =
indicated was important.

> p10: "If the RPL router is not the source of the original datagram, =
the original datagram's IPv6 Hop Limit field is decremented before =
generating the SRH." If this were placed the the beginning of the =
paragraph, it might be clearer.

Agree.

> p10: "After generating the SRH, the RPL router decrements the original =
datagram's IPv6 Hop Limit value by the SRH Segments Left value.  =
Processing the SRH Segments Left and original datagram's IPv6 Hop Limit =
fields in this way ensures that ICMPv6 Time Exceeded errors occur as =
would be expected on more traditional IPv6 networks that forward =
datagrams without tunneling." It's not really a tunnel then as defined =
by RFC 2473 and somewhat conflicts with what's written in RFC 2473. =
Also, you don't want to do this when the packet is not tunneled or you =
will be double counting.

Agree that this is in conflict with RFC 2473, but necessary to support =
traceroute as requested by ZigBee/IP members.  We can add text that =
clearly states this difference with RFC 2473.

> _Minor (use of language) comments:_
>=20
> Throughout: Inconsistent use of:
>=20
> 1. 'router'
> 2. 'RPL router'
> 3. 'RPL Router'
>=20
> (3) (note capitalization) is a defined term. (1) and (2) are used =
generally but inconsistently. Use 'RPL router' to mean a 'RPL Border =
Router' or a 'RPL Router' throughout. Use 'a RPL router' as introductory =
to a sentence and, if necessary, 'the router' only to refer to the =
introduced RPL router, although 'the RPL router' is generally better. =
This would make the document clearer in places.

Agree.

> p1: "or few routers" -> "or a few routers". Reason for change: 'few =
routers' on its own implies 'not many routers'.

Agree.

> p6: "In the scenarios above, R may indicate a RPL Border Router (when =
connecting to other routing domains) or a RPL Router" -> "In the =
scenarios above, the RPL router R may indicate a RPL Border Router (when =
connecting to other routing domains) or a RPL Router". Reason for =
change: This introduces the term 'RPL router' as either a 'RPL Border =
Router' or a 'RPL Router' (note both are defined terms) correctly for =
the subsequent paragraph.

Agree.

> p6: "One such use case with RPL is to have all RPL traffic flow =
through a Border Router and have the Border Router use source routes to =
deliver datagrams to their final destination.  When including the SRH =
using tunneled mode, the Border Router would encapsulate the received =
datagram unmodified using IPv6-in-IPv6 and include a SRH in the outer =
IPv6 header." -> "One such use case with RPL is to have all RPL traffic =
flow through a RPL Border Router and have the RPL Border Router use =
source routes to deliver datagrams to their final destination.  When =
including the SRH using tunneled mode, the RPL Border Router would =
encapsulate the received datagram unmodified using IPv6-in-IPv6 and =
include a SRH in the outer IPv6 header." Reason for change: Uses
> the correct terminology.

Agree.

> p6: "In the above scenario, datagrams travel from S to D through LBR" =
-> "In the above scenario, datagrams travel from S to D through the RPL =
Border Router LBR (referred to as LBRs in [I-
> D.ietf-roll-terminology])". Reason for change: Clarify what LBR is.

Agree.

Thanks again.

--
Jonathan Hui


From evyncke@cisco.com  Wed Dec 21 08:56:30 2011
Return-Path: <evyncke@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 E95E91F0C52 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 08:56:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 uEOVpOAlrcks for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 08:56:30 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 093D91F0C3B for <ipv6@ietf.org>; Wed, 21 Dec 2011 08:56:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=evyncke@cisco.com; l=2870; q=dns/txt; s=iport; t=1324486590; x=1325696190; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=q5KwBYK13kE1QZsPFTlcztHnljAIkmnfmvV8Hu+ZeUE=; b=k6JvhCKDzghfnOtplLOulLA9Lj3KSQ6hGuERE7/dBqiodC+IPW2mvmPe tiQGiiTbQ1N+0AUIglHCvBc5e4/QyabmT1fXNf+4Nsf0E2nCWIT4M8jmB BriiUU97s2YIDu0phtSH8Kv0GEB3p+/uxtiRSY/F/XJPN5S35tcjOvCrW c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAKUO8k6Q/khN/2dsb2JhbABDrBuBBYFyAQEBBAEBAQ8BHT4XBAIBCA4DBAEBCwYXAQYBJh8JCAEBBAESCBqHYJkVAZ5UiyxjBIgEny4
X-IronPort-AV: E=Sophos;i="4.71,389,1320624000"; d="scan'208";a="124394580"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 21 Dec 2011 16:56:29 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pBLGuTwj018276; Wed, 21 Dec 2011 16:56:29 GMT
Received: from xmb-ams-110.cisco.com ([144.254.74.85]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 21 Dec 2011 17:56:28 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: New IETF I-D on IPv6 smurf amplifiers
Date: Wed, 21 Dec 2011 17:56:27 +0100
Message-ID: <317616CE96204D49B5A1811098BA89500614FBF5@XMB-AMS-110.cisco.com>
In-Reply-To: <4EF06D47.2060202@si6networks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New IETF I-D on IPv6 smurf amplifiers
Thread-Index: Acy/abBTDhrQv2CFRZqu3pZLAcGukwAlw6pw
References: <4EF06D47.2060202@si6networks.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Fernando Gont" <fgont@si6networks.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 21 Dec 2011 16:56:28.0974 (UTC) FILETIME=[7BB324E0:01CCC001]
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, 21 Dec 2011 16:56:31 -0000

My usual recommendations about this issue (and the related =
packet-too-big sent to a mcast group) are quite commonly accepted and =
are described in your I-D in 2.2:
- RPF for all traffic
- rate limit per node the ICMP generation
- rate limit per router the ICMP traffic to a 100-1000 pps

I would rather be reluctant to change RFC 2460/4443 even if there =
appears to currently have no valid use of option type 10xxxxxx because =
who knows in the future? And getting an error message is quite =
important.

The above counter-measures also mitigate the risk of reflection attacks =
and not only smurf-like amplification attacks. So, this should be the =
only recommended approach (i.e. remove 2.1 from your I-D)

Hope it helps

-=E9ric


> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf =
Of
> Fernando Gont
> Sent: mardi 20 d=E9cembre 2011 12:11
> To: ipv6@ietf.org
> Subject: New IETF I-D on IPv6 smurf amplifiers
>=20
> Folks,
>=20
> We have published a new IETF I-D on "IPv6 smurf amplifiers". The I-D =
is
> available at:
> =
<http://tools.ietf.org/id/draft-gont-6man-ipv6-smurf-amplifier-00.txt>.
>=20
> This may be an issue when BC38 is not deployed, or when the BCP38
> implementation is buggy (yes, there have been instances of this).
>=20
> Note: This vector can also be exploited with normal link-local =
multicast
> addresses, but for obvious reasons it becomes a more important issue
> with non-local multicast.
>=20
> Abstract:
> ---- cut here ----
>    When an IPv6 node processing an IPv6 packet does not support an =
IPv6
>    option whose two-highest-order bits of the Option Type are '10', it
>    is required to respond with an ICMPv6 Parameter Problem error
>    message, even if the Destination Address of the packet was a
>    multicast address.  This feature provides an amplification vector,
>    opening the door to an IPv6 version of the 'Smurf' =
Denial-of-Service
>    (DoS) attack found in IPv4 networks.  This document discusses the
>    security implications of the aforementioned options, and formally
>    updates RFC 2460 such that this attack vector is eliminated.
>    Additionally, it describes a number of operational mitigations that
>    could be deployed against this attack vector.
> ---- cut here ----
>=20
> Any feedback will be welcome.
>=20
> Thanks!
>=20
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From wwwrun@rfc-editor.org  Wed Dec 21 09:01:44 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 C2AAF1F0C52; Wed, 21 Dec 2011 09:01:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.273
X-Spam-Level: 
X-Spam-Status: No, score=-102.273 tagged_above=-999 required=5 tests=[AWL=0.327, 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 pCbBs2CvhNHH; Wed, 21 Dec 2011 09:01:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0A31F0C50; Wed, 21 Dec 2011 09:01:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B25A572E004; Wed, 21 Dec 2011 09:00:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6434 on IPv6 Node Requirements
From: rfc-editor@rfc-editor.org
Message-Id: <20111221170018.B25A572E004@rfc-editor.org>
Date: Wed, 21 Dec 2011 09:00:18 -0800 (PST)
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: Wed, 21 Dec 2011 17:01:44 -0000

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

        
        RFC 6434

        Title:      IPv6 Node Requirements 
        Author:     E. Jankiewicz, J. Loughney,
                    T. Narten
        Status:     Informational
        Stream:     IETF
        Date:       December 2011
        Mailbox:    edward.jankiewicz@sri.com, 
                    john.loughney@nokia.com, 
                    narten@us.ibm.com
        Pages:      30
        Characters: 64407
        Obsoletes:  RFC4294

        I-D Tag:    draft-ietf-6man-node-req-bis-11.txt

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

This document defines requirements for IPv6 nodes.  It is expected
that IPv6 will be deployed in a wide range of devices and situations.
Specifying the requirements for IPv6 nodes allows IPv6 to function
well and interoperate in a large number of situations and
deployments.  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 prvs=329774bb4=mukul@uwm.edu  Wed Dec 21 09:24:29 2011
Return-Path: <prvs=329774bb4=mukul@uwm.edu>
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 513C511E8098; Wed, 21 Dec 2011 09:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=0.929,  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 eGXDLnYc8BxE; Wed, 21 Dec 2011 09:24:28 -0800 (PST)
Received: from ip2mta.uwm.edu (smtp.uwm.edu [129.89.7.20]) by ietfa.amsl.com (Postfix) with ESMTP id 426D511E8094; Wed, 21 Dec 2011 09:24:28 -0800 (PST)
Received: from localhost (HELO mta04.pantherlink.uwm.edu) ([127.0.0.1]) by ip2mta.uwm.edu with ESMTP; 21 Dec 2011 11:24:27 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta04.pantherlink.uwm.edu (Postfix) with ESMTP id 84EEA2B3EDD; Wed, 21 Dec 2011 11:22:40 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta04.pantherlink.uwm.edu
Received: from mta04.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta04.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id icawGKjDVtOb; Wed, 21 Dec 2011 11:22:40 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta04.pantherlink.uwm.edu (Postfix) with ESMTP id 54F872B3EDA; Wed, 21 Dec 2011 11:22:40 -0600 (CST)
Date: Wed, 21 Dec 2011 11:24:27 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Jonathan Hui <jonhui@cisco.com>
Message-ID: <2121048960.723525.1324488267237.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <439AF687-83D0-4581-A4EB-13104047B41C@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll <roll@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, 21 Dec 2011 17:24:29 -0000

Hi Jonathan

I have serious issues with the use of RPL Instance as the domain for SRH.

>>[R Cragie]
>> p7: RPL Instance ID - why is this needed for source routing? RPL is not even used for source routing. This flavors the SRH unnecessarily and the processing does not use it. If the reason is for checking entering and exiting a RPL domain, this processing needs to be stated.

>[J Hui]
>Page 12 describes processing rules intended to keep the SRH within a RPL Instance.


Page 12 has no mention of RPL Instance. Page 13 does mention RPL Instance in the following rules:

   2.  Datagrams destined elsewhere within the same RPL Instance are
       forwarded to the correct interface.

   3.  Datagrams destined to nodes outside the RPL Instance are dropped
       if the outer-most IPv6 header contains a SRH not generated by the
       RPL router forwarding the datagram.

My question is how does a router know whether the next hop is within the same RPL Instance or not? A router has no idea what RPL Instances its neighbors belong to. 

It seems that a router, that receives a packet with a SRH, does not need to check if it belongs to the RPL Instance mentioned in the SRH. It just needs to check if the next hop belongs to that RPL Instance or not. And as I said in the prev para, I am not sure how would the router make that check.

It would be a problem if the router were required to check its own membership in the RPL Instance in order to accept a packet with SRH. Routers part of a source route should not need to maintain any state about it. 

Thanks
Mukul

From prvs=329774bb4=mukul@uwm.edu  Wed Dec 21 09:26:59 2011
Return-Path: <prvs=329774bb4=mukul@uwm.edu>
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 7607111E8098; Wed, 21 Dec 2011 09:26:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.134
X-Spam-Level: 
X-Spam-Status: No, score=-6.134 tagged_above=-999 required=5 tests=[AWL=0.465,  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 kg1ZV6O+VsZa; Wed, 21 Dec 2011 09:26:59 -0800 (PST)
Received: from ip2mta.uwm.edu (smtp.uwm.edu [129.89.7.20]) by ietfa.amsl.com (Postfix) with ESMTP id DC92D11E8094; Wed, 21 Dec 2011 09:26:58 -0800 (PST)
Received: from localhost (HELO mta02.pantherlink.uwm.edu) ([127.0.0.1]) by ip2mta.uwm.edu with ESMTP; 21 Dec 2011 11:26:42 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.pantherlink.uwm.edu (Postfix) with ESMTP id 0303A12E3CC; Wed, 21 Dec 2011 11:26:43 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta02.pantherlink.uwm.edu
Received: from mta02.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta02.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ua8IxB6ARJzZ; Wed, 21 Dec 2011 11:26:42 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta02.pantherlink.uwm.edu (Postfix) with ESMTP id C73C612E3CD; Wed, 21 Dec 2011 11:26:42 -0600 (CST)
Date: Wed, 21 Dec 2011 11:26:42 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Jonathan Hui <jonhui@cisco.com>
Message-ID: <557570317.723557.1324488402749.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <B28ACA7A-EBCD-426E-B9E3-F3979E8F7101@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll <roll@ietf.org>, 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: Wed, 21 Dec 2011 17:26:59 -0000

Jonathan

I described the problem in the message I sent just now. I think RPL Instance is not the correct scope for SRH. It has to be a RPL domain to be defined as we discussed some time back on the ROLL list.

Thanks
Mukul

----- Original Message -----
From: "Jonathan Hui" <jonhui@cisco.com>
To: "Mukul Goyal" <mukul@uwm.edu>
Cc: "roll" <roll@ietf.org>
Sent: Tuesday, December 20, 2011 10:27:29 AM
Subject: Re: draft-ietf-6man-rpl-routing-header-07


Mukul,

As defined in the draft today, you cannot use a RPL routing header to cross RPL Instances.  My understanding is that roll-p2p-rpl makes use of local RPL instances.  Can you describe the issue you are concerned about?

--
Jonathan Hui

On Dec 20, 2011, at 8:14 AM, Mukul Goyal wrote:

> Jonathan
> 
> The IESG-approved draft refers to the RPL instance as the scope where the routing header can be used. How would this routing header be used for general source routing (across RPL instances) in an LLN? How would a node use this routing header if it wants to travel along a source route discovered using P2P-RPL?
> 
> Thanks
> Mukul
> 


From jonhui@cisco.com  Wed Dec 21 10:07:11 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 D5F6121F8491; Wed, 21 Dec 2011 10:07:11 -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 nzhRcYRawQ7d; Wed, 21 Dec 2011 10:07:11 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 505C121F841B; Wed, 21 Dec 2011 10:07:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=3021; q=dns/txt; s=iport; t=1324490831; x=1325700431; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=BFwNogzvgSia6ijRzKNdlZ4L861D9pBqfbOgkGOCahA=; b=KgFNH7BYtMKmJQPpwqxB2rbk/1MBwx+wNdZUgX4J3OY7GSegSF1cyT3k CM0EYhqg5eTtbAYr51Il3DTEnqzXUmr9VzZBT37C0MMzCnCuxJDXJSbrj K3mUeojyNUGmj4m8OUPRUjyGvCFtj0nNOCywJLH+HanT0nuzM9BQxPFoS E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EALof8k6rRDoI/2dsb2JhbABDDqwPgQWBcgEBAQMBEgEnPwULC0ZXBjWHWJkzAZ5MiyxjBIg3jEiRe1g
X-IronPort-AV: E=Sophos;i="4.71,389,1320624000"; d="scan'208";a="21936825"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 21 Dec 2011 18:07:09 +0000
Received: from dhcp-128-107-155-213.cisco.com (dhcp-128-107-155-213.cisco.com [128.107.155.213]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pBLI79gQ021997; Wed, 21 Dec 2011 18:07:09 GMT
Subject: Re: draft-ietf-6man-rpl-routing-header-07
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <2121048960.723525.1324488267237.JavaMail.root@mail17.pantherlink.uwm.edu>
Date: Wed, 21 Dec 2011 10:07:09 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <55AAC580-DC07-4DAC-BAB0-A3DF27A11565@cisco.com>
References: <2121048960.723525.1324488267237.JavaMail.root@mail17.pantherlink.uwm.edu>
To: Mukul Goyal <mukul@uwm.edu>
X-Mailer: Apple Mail (2.1084)
Cc: roll <roll@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, 21 Dec 2011 18:07:12 -0000

On Dec 21, 2011, at 9:24 AM, Mukul Goyal wrote:

>>> [R Cragie]
>>> p7: RPL Instance ID - why is this needed for source routing? RPL is =
not even used for source routing. This flavors the SRH unnecessarily and =
the processing does not use it. If the reason is for checking entering =
and exiting a RPL domain, this processing needs to be stated.
>=20
>> [J Hui]
>> Page 12 describes processing rules intended to keep the SRH within a =
RPL Instance.

Oops, typo.  s/12/13/

> Page 12 has no mention of RPL Instance. Page 13 does mention RPL =
Instance in the following rules:
>=20
>   2.  Datagrams destined elsewhere within the same RPL Instance are
>       forwarded to the correct interface.
>=20
>   3.  Datagrams destined to nodes outside the RPL Instance are dropped
>       if the outer-most IPv6 header contains a SRH not generated by =
the
>       RPL router forwarding the datagram.
>=20
> My question is how does a router know whether the next hop is within =
the same RPL Instance or not? A router has no idea what RPL Instances =
its neighbors belong to.=20
>=20
> It seems that a router, that receives a packet with a SRH, does not =
need to check if it belongs to the RPL Instance mentioned in the SRH. It =
just needs to check if the next hop belongs to that RPL Instance or not. =
And as I said in the prev para, I am not sure how would the router make =
that check.

It knows whether or not RPL is running on an interface.  It could at =
least check that.  By the same argument, how do you propose we limit =
packets to a RPL routing domain?  If we have no good way of limiting =
packets, then the stated security considerations do not apply.

> It would be a problem if the router were required to check its own =
membership in the RPL Instance in order to accept a packet with SRH. =
Routers part of a source route should not need to maintain any state =
about it.=20

Note that in draft-ietf-roll-rpl, RPL routers do maintain such state =
already.  I agree the issue comes up with P2P.

Remember that the original purpose of the RPL Instance is to support =
MTR.  The RPL Instance identifies what routing topology to use.  This is =
important especially if the SRH does not specify the entire path to the =
destination.  How does the tunnel exit-point know what routing topology =
to use to reach the destination?

The lack of and need for the RPL Instance identifier was raised during =
IESG review.  The options are (1) to require inclusion a RPL Option in =
addition to the RPL routing header or (2) add a RPL Instance field in =
the RPL routing header itself.  I doubt that you would prefer option 1.

If the RPL router has no idea of the RPL Instance when forwarding, it =
can choose to forward the packet along anyway.  At the very least, the =
tunnel exit-point should enforce the use of the RPL Instance.  Surely =
the end-points of a source route should at least know what RPL Instance =
they are in...

--
Jonathan Hui


From jonhui@cisco.com  Wed Dec 21 10:22:12 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 C303D21F8540; Wed, 21 Dec 2011 10:22:12 -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 ZnopPf3DU5rv; Wed, 21 Dec 2011 10:22:12 -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 2447F21F849C; Wed, 21 Dec 2011 10:22:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=1752; q=dns/txt; s=iport; t=1324491732; x=1325701332; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=cOqcNIutCIUJceOtJipDBranyoErRV2aUvaBcj6CyAk=; b=J4QTPBW+T+3rNJoztOt6iIvH6Yjc4opMZq8apkzegQINkdLkysV+I7Fl GZdYp57nYa2NRNm60sPvSD/XRwuk11Qo4NeJLMljib6Rje+KX3Ld1RIO/ kNBR7ghmDqJyBUelACrolgCa7phtcp+HpZ7p0oVLgakQo12tbmzwP+fRX o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AooAALYi8k6rRDoJ/2dsb2JhbABDDps4kFeBBYFyAQEBAwESASc/BQcECxEEAQEBLk8IBgESIodYmS4BnkyLLGMEiDeMSJF7WA
X-IronPort-AV: E=Sophos;i="4.71,389,1320624000"; d="scan'208";a="20223423"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 21 Dec 2011 18:22:11 +0000
Received: from dhcp-128-107-155-213.cisco.com (dhcp-128-107-155-213.cisco.com [128.107.155.213]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pBLIMBIo024547; Wed, 21 Dec 2011 18:22:11 GMT
Subject: Re: draft-ietf-6man-rpl-routing-header-07
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <557570317.723557.1324488402749.JavaMail.root@mail17.pantherlink.uwm.edu>
Date: Wed, 21 Dec 2011 10:22:11 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A89D3D3-1DA6-4698-BC4A-B8AEBE397906@cisco.com>
References: <557570317.723557.1324488402749.JavaMail.root@mail17.pantherlink.uwm.edu>
To: Mukul Goyal <mukul@uwm.edu>, Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1084)
Cc: roll WG <roll@ietf.org>, 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: Wed, 21 Dec 2011 18:22:12 -0000

Personally, I am OK changing the scope to a RPL routing domain rather =
than a RPL Instance.  If one really wants to limit to a RPL Instance, =
then they can also include a RPL Option.  This is what we originally had =
in rpl-routing-header-05.  This change was made late during the IESG =
review process.

Jari, would you support reverting the scope of the RPL SRH to a RPL =
routing domain rather than a RPL Instance?

Thanks.

--
Jonathan Hui

On Dec 21, 2011, at 9:26 AM, Mukul Goyal wrote:

> Jonathan
>=20
> I described the problem in the message I sent just now. I think RPL =
Instance is not the correct scope for SRH. It has to be a RPL domain to =
be defined as we discussed some time back on the ROLL list.
>=20
> Thanks
> Mukul
>=20
> ----- Original Message -----
> From: "Jonathan Hui" <jonhui@cisco.com>
> To: "Mukul Goyal" <mukul@uwm.edu>
> Cc: "roll" <roll@ietf.org>
> Sent: Tuesday, December 20, 2011 10:27:29 AM
> Subject: Re: draft-ietf-6man-rpl-routing-header-07
>=20
>=20
> Mukul,
>=20
> As defined in the draft today, you cannot use a RPL routing header to =
cross RPL Instances.  My understanding is that roll-p2p-rpl makes use of =
local RPL instances.  Can you describe the issue you are concerned =
about?
>=20
> --
> Jonathan Hui
>=20
> On Dec 20, 2011, at 8:14 AM, Mukul Goyal wrote:
>=20
>> Jonathan
>>=20
>> The IESG-approved draft refers to the RPL instance as the scope where =
the routing header can be used. How would this routing header be used =
for general source routing (across RPL instances) in an LLN? How would a =
node use this routing header if it wants to travel along a source route =
discovered using P2P-RPL?
>>=20
>> Thanks
>> Mukul
>>=20
>=20


From dougb@dougbarton.us  Wed Dec 21 10:38:04 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 3887921F8549 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 10:38:04 -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 I01k4bE0DEr2 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 10:38:03 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 5999C21F8551 for <ipv6@ietf.org>; Wed, 21 Dec 2011 10:38:03 -0800 (PST)
Received: (qmail 2163 invoked by uid 399); 21 Dec 2011 18:38:01 -0000
Received: from unknown (HELO ?172.17.198.245?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 21 Dec 2011 18:38:01 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4EF22786.2070908@dougbarton.us>
Date: Wed, 21 Dec 2011 10:37:58 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com>
X-Enigmail-Version: 1.3.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Wed, 21 Dec 2011 18:38:04 -0000

On 12/19/2011 5:24 PM, Bhatia, Manav (Manav) wrote:
> Hi,
> 
> We have posted a new draft that extends Router Advertisements to
> include information about the one or more NTP servers present in the
> network. This is useful where the delays in acquiring server
> addresses and communicating with the servers are critical (mobile
> environment for example).

Sort of surprised that no one else has responded so far, but I'll bite.
Quite simply, "no." Slightly less simply, "use DHCP since that's what
it's for."

I'm happy to expound on the evils of "camel's nose already too far under
the tent," etc.


Doug

-- 

		[^L]

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


From brian.e.carpenter@gmail.com  Wed Dec 21 11:45:11 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 4A20321F8AF1 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 11:45:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.449
X-Spam-Level: 
X-Spam-Status: No, score=-103.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 xNI6o5-kK-6D for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 11:45:10 -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 95A1321F8AB8 for <ipv6@ietf.org>; Wed, 21 Dec 2011 11:45:10 -0800 (PST)
Received: by eaak10 with SMTP id k10so791287eaa.31 for <ipv6@ietf.org>; Wed, 21 Dec 2011 11:45:09 -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=pzbbjBRWQfBCtUlZ/HEomwlvOwKqjWbSyHGcUTvvHH8=; b=IoLKogTZxiJgtQL1UDMq3kjTnq/lf3ZwMX6wpZPZb/N07i9CjEv+fKQ6jtzr3Lg0s4 WTOPhZWmJBrRs+gKXYG+aeB5phjFcnJGhX2THQSqRsYGlwHCj2QrnYz8pZqLlkoy4gUv Voh/8f3fS/FAXZrkPYSKJ2otifVYd5//5a0Jw=
Received: by 10.204.130.145 with SMTP id t17mr2549623bks.60.1324496709362; Wed, 21 Dec 2011 11:45:09 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id zv9sm13224309bkb.0.2011.12.21.11.45.06 (version=SSLv3 cipher=OTHER); Wed, 21 Dec 2011 11:45:08 -0800 (PST)
Message-ID: <4EF2373B.6060905@gmail.com>
Date: Thu, 22 Dec 2011 08:44: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: Doug Barton <dougb@dougbarton.us>
Subject: IPv6 Router Advertisement Option for Foobar Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us>
In-Reply-To: <4EF22786.2070908@dougbarton.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Wed, 21 Dec 2011 19:45:11 -0000

On 2011-12-22 07:37, Doug Barton wrote:
> On 12/19/2011 5:24 PM, Bhatia, Manav (Manav) wrote:
>> Hi,
>>
>> We have posted a new draft that extends Router Advertisements to
>> include information about the one or more NTP servers present in the
>> network. This is useful where the delays in acquiring server
>> addresses and communicating with the servers are critical (mobile
>> environment for example).
> 
> Sort of surprised that no one else has responded so far, but I'll bite.
> Quite simply, "no." Slightly less simply, "use DHCP since that's what
> it's for."
> 
> I'm happy to expound on the evils of "camel's nose already too far under
> the tent," etc.

There is of course a broader issue here, illustrated by the endless loop
over in MIF about draft-ietf-mif-dhcpv6-route-option.

What is the intended scope of the RA mechanism?

I was a strong proponent of standardising the DNS server option
in RA, because it is an absolute requirement for even the most
minimal host to get onto the Internet. But I am also a strong
proponent of -dhcpv6-route-option, because it seems clear that
more complex environments will inevitably require the extensibility
that comes with DHCPv6.

I think we need a standards track document that defines the maximum
scope of the RA mechanism once and for all. Personally I would
probably freeze it where it is today, but we need a reasoned
architectural decision about this.

   Brian

From fgont@si6networks.com  Wed Dec 21 11:59:09 2011
Return-Path: <fgont@si6networks.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 4CBC221F84DC for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 11:59:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, 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 cZs0ygU+cRb8 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 11:59:09 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 09EE221F8AFB for <ipv6@ietf.org>; Wed, 21 Dec 2011 11:59:07 -0800 (PST)
Received: from [2001:5c0:1000:a::595] by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RdSJZ-0008WU-4i; Wed, 21 Dec 2011 20:59:01 +0100
Message-ID: <4EF20BEB.8070209@si6networks.com>
Date: Wed, 21 Dec 2011 13:40:11 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com> <82fwgfk1ev.fsf@mid.bfk.de>	<20111220.124458.41706285.sthaug@nethelp.no> <20111221140241.3259D1A6F096@drugs.dv.isc.org>
In-Reply-To: <20111221140241.3259D1A6F096@drugs.dv.isc.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 21 Dec 2011 19:59:09 -0000

Hi, Mark,

On 12/21/2011 11:02 AM, Mark Andrews wrote:
>> Such traffic absolutely occurs in the wild. I have three reasonably
>> busy name servers where this is logged as an error from the ipfw code,
>> e.g.
>>
>> Dec 16 14:04:04 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
>> Dec 17 00:27:20 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
[....]
>>
>> This is because these name servers haven't (yet) been upgraded to a
>> FreeBSD version where bug report kern/145733 haven't been fixed. It
>> *is* fixed in newer FreeBSD versions, e.g. 8.2-STABLE.
> 
> Not yet.
> http://svnweb.freebsd.org/base/stable/8/sys/netinet/ipfw/ip_fw2.c?view=log

Is the aforementioned traffic the result of an implementation of your
proposal for for DNS/UDP?

If that's the case, what's the interface that you use for forcing the
atomic fragments?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From fgont@si6networks.com  Wed Dec 21 11:59:24 2011
Return-Path: <fgont@si6networks.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 0A45921F8AF9 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 11:59:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.022,  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 CvarXcjoxsTb for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 11:59:23 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 677CB11E80BA for <ipv6@ietf.org>; Wed, 21 Dec 2011 11:59:23 -0800 (PST)
Received: from [2001:5c0:1000:a::595] by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RdSJr-00005A-3F; Wed, 21 Dec 2011 20:59:19 +0100
Message-ID: <4EF21809.2090501@si6networks.com>
Date: Wed, 21 Dec 2011 14:31:53 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Subject: Re: New IETF I-D on IPv6 smurf amplifiers
References: <4EF06D47.2060202@si6networks.com> <317616CE96204D49B5A1811098BA89500614FBF5@XMB-AMS-110.cisco.com>
In-Reply-To: <317616CE96204D49B5A1811098BA89500614FBF5@XMB-AMS-110.cisco.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 21 Dec 2011 19:59:24 -0000

Hi, Eric,

Thanks so much for your comments. Please find my responses inline...

On 12/21/2011 01:56 PM, Eric Vyncke (evyncke) wrote:
> My usual recommendations about this issue (and the related
> packet-too-big sent to a mcast group) are quite commonly accepted and
> are described in your I-D in 2.2: - RPF for all traffic - rate limit
> per node the ICMP generation - rate limit per router the ICMP traffic
> to a 100-1000 pps

Note that this limit might kill other stuff -- just blindly limiting
ICMPv6 traffic might e.g. introduce PMTUD blackholes.



> I would rather be reluctant to change RFC 2460/4443 even if there
> appears to currently have no valid use of option type 10xxxxxx
> because who knows in the future? And getting an error message is
> quite important.

The v6 specs carefully eliminate other potential smurf amplifiers. --
But this one was "left in". Getting an error from multiple destination
hosts doesn't look like a good idea. -- but I'll let others weigh in...

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From dougb@dougbarton.us  Wed Dec 21 12:22:40 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 079751F0C56 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 12:22:40 -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 eGzteHcB2NeL for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 12:22:39 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id EB8DF1F0C4D for <ipv6@ietf.org>; Wed, 21 Dec 2011 12:22:38 -0800 (PST)
Received: (qmail 13719 invoked by uid 399); 21 Dec 2011 20:22:32 -0000
Received: from unknown (HELO ?172.17.198.245?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 21 Dec 2011 20:22:32 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4EF24007.3030300@dougbarton.us>
Date: Wed, 21 Dec 2011 12:22:31 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: IPv6 Router Advertisement Option for Foobar Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <4EF2373B.6060905@gmail.com>
In-Reply-To: <4EF2373B.6060905@gmail.com>
X-Enigmail-Version: 1.3.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Wed, 21 Dec 2011 20:22:40 -0000

On 12/21/2011 11:44 AM, Brian E Carpenter wrote:
> On 2011-12-22 07:37, Doug Barton wrote:
>> On 12/19/2011 5:24 PM, Bhatia, Manav (Manav) wrote:
>>> Hi,
>>>
>>> We have posted a new draft that extends Router Advertisements to
>>> include information about the one or more NTP servers present in the
>>> network. This is useful where the delays in acquiring server
>>> addresses and communicating with the servers are critical (mobile
>>> environment for example).
>>
>> Sort of surprised that no one else has responded so far, but I'll bite.
>> Quite simply, "no." Slightly less simply, "use DHCP since that's what
>> it's for."
>>
>> I'm happy to expound on the evils of "camel's nose already too far under
>> the tent," etc.
> 
> There is of course a broader issue here, illustrated by the endless loop
> over in MIF about draft-ietf-mif-dhcpv6-route-option.

... or the endless loop of "we need DNS info in RA" until it finally got
adopted.

> What is the intended scope of the RA mechanism?
> 
> I was a strong proponent of standardising the DNS server option
> in RA, because it is an absolute requirement for even the most
> minimal host to get onto the Internet. But I am also a strong
> proponent of -dhcpv6-route-option, because it seems clear that
> more complex environments will inevitably require the extensibility
> that comes with DHCPv6.

So, expound it is. :)

When I first got interested in IPv6 protocol work back in 2000 or so I
was curious about this "RA" thing. Given that DHCP was already widely
deployed and successful in the IPv4 world I wondered why such a thing
was necessary/useful.* I was told at the time that a key feature of IPv6
was going to be the ability to bring "dumb" devices onto the network
that only needed to be addressable (light switches were a commonly used
example). The RA mechanism was perfect for this as it involved no state,
and anything that needed to be even slightly "smart" would use DHCPv6.
As much as I was dubious about it at the time, I accepted that
explanation at face value.

Then someone realized that RA was great for getting a thing on the
network, but at that point the thing wasn't really all that useful. So
the logical next step was to extend RA to allow for sending out
resolving DNS info. The point I (and others) tried to make at the time
went something like this (I will use the first person so as to take 100%
of the blame, but that's not meant to exclude the others who made
significant contributions to the line of argument that I support):

Me:	Um, if it's not a dumb device, why can't it use DHCP?
Them:	DHCP is too heavy-weight. We just need one more piece of
information provided by RA and then we'll have a fully-functional client
without the need for DHCP at all, isn't that great!
Me:	Um, well, I see what you're saying, but doesn't that sort of open
the door for adding more things down the road? And as both a system
administrator and an operating system developer I have serious concerns
about having to support 2 different host configuration protocols. It
will inevitably lead to problems, and ...
Them:	No no no, don't be silly! We JUST want to add this ONE little
thing. After that we promise, no more!
Me:	I just think it's a bad precedent. Besides, adding only the
nameserver info isn't enough, you also need the domain and/or search
string to make it useful.
Them:	*snap* Oh, right! Thanks for pointing that out. Ok, we'll add that
too, but after that, NO MORE. I PROMISE!
Me:	Um ....

> I think we need a standards track document that defines the maximum
> scope of the RA mechanism once and for all. Personally I would
> probably freeze it where it is today, but we need a reasoned
> architectural decision about this.

Given that using RA for DNS info isn't widely deployed yet, I would vote
for rolling RA back to its originally designed purpose, THEN saying "no
more, really, I mean it." But I doubt that either of those options will
be successful. I would be ecstatic to be proven wrong however.


Doug

* I realize that when RA was first conceived DHCP wasn't that well
established yet, and furthermore I understand that some people disagree
on how well established it was even as late as 2000. My experience at
the time was that DHCP was already widely used in both the SOHO and
large enterprise markets. In any case I don't think anyone can argue
that in the last 11 years it hasn't been firmly established. Failure to
recognize why DHCP is popular, and why RA isn't, is a bug in the
protocol development process.

-- 

		[^L]

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


From simon.perreault@viagenie.ca  Wed Dec 21 12:30:39 2011
Return-Path: <simon.perreault@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 74FFA1F0C63; Wed, 21 Dec 2011 12:30:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 VvipybCpKewh; Wed, 21 Dec 2011 12:30:38 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id 962F11F0C61; Wed, 21 Dec 2011 12:30:38 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id CB09720DC3; Wed, 21 Dec 2011 15:30:07 -0500 (EST)
Message-ID: <4EF241CF.4050902@viagenie.ca>
Date: Wed, 21 Dec 2011 15:30:07 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0
MIME-Version: 1.0
To: Ghanashyam Satpathy <ghanashyam_satpathy@yahoo.com>
Subject: Re: Question on IPV4/IPV6 Multicast interoperability
References: <1324206855.51664.YahooMailNeo@web121801.mail.ne1.yahoo.com> <C0E0A32284495243BDE0AC8A066631A80C22F04F@szxeml526-mbx.china.huawei.com> <1324353085.77877.YahooMailNeo@web121803.mail.ne1.yahoo.com>
In-Reply-To: <1324353085.77877.YahooMailNeo@web121803.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: MBONED WG <mboned@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "multrans@ietf.org" <multrans@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, 21 Dec 2011 20:30:39 -0000

On 2011-12-19 22:51, Ghanashyam Satpathy wrote:
> Thanks for the reply and understands the theory but unable to make it in my code.

Your code might not need any modification at all...

Normally, IPv4 multicast and IPv6 multicast are incompatible.
a) An IPv4-only listener can receive multicast from an IPv4 source.
b) An IPv6-only listener can receive multicast from an IPv6 source.
c) A dual-stack listener can receive multicast from both IPv4 and IPv6 sources.
d) But an IPvX-only listener cannot receive multicast from an IPvY-only source.

To be able to do d), you need something between the listener and the source, what 
these days gets called an "adaptation function". It typically does not require 
code changes on the source or listener.

There is currently an effort in the IETF called "multrans" trying to standardize 
methods and protocols to do that. Some vendors already have "running code" that 
can translate between IPv4 and IPv6 multicast.

Simon


> *From:* Tina TSOU <Tina.Tsou.Zouting@huawei.com>
> *To:* Ghanashyam Satpathy <ghanashyam_satpathy@yahoo.com>; "ipv6@ietf.org"
> <ipv6@ietf.org>
> *Cc:* "multrans@ietf.org" <multrans@ietf.org>; MBONED WG <mboned@ietf.org>
> *Sent:* Tuesday, December 20, 2011 6:09 AM
> *Subject:* RE: Question on IPV4/IPV6 Multicast interoperability
>
> Ghanashyam,
> http://datatracker.ietf.org/doc/draft-tsou-multrans-addr-acquisition/
> http://datatracker.ietf.org/doc/draft-zhou-multrans-af1-specification/
> Running code exists.
> Hope it helps.
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
> *From:*ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] *On Behalf Of
> *Ghanashyam Satpathy
> *Sent:* Sunday, December 18, 2011 3:14 AM
> *To:* ipv6@ietf.org
> *Subject:* Question on IPV4/IPV6 Multicast interoperability
> Hello,
> I have a question on IPV4/IPV6 Multicast interoperability. We have succesfully
> upgraded our application(Windows Based) to support IPV6 and faced issue on
> multicast interoperability. Multicast messages sent by a IPV6 server is
> successfully receved by a client running on IPV6. But any client running on IPV4
> is not able to receive the message.
> Quite a no. of things I tried like using IPV4 mapped IPV6 address and V4 embeded
> V6 adress.But nothing seems to be working.Would like to know an unified way so
> that one multicast message sent by an IPV6 server should be received by both V6
> and V4 client.
> Would be great if somebody can send some code snippet(C/C++) on it.
> Thanks.
> Ghanashyam
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From brian.e.carpenter@gmail.com  Wed Dec 21 14:07:44 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 40A921F0C4D for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 14:07:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.468
X-Spam-Level: 
X-Spam-Status: No, score=-103.468 tagged_above=-999 required=5 tests=[AWL=0.132, 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 7vZiac8ndEv5 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 14:07:43 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2E74721F8545 for <ipv6@ietf.org>; Wed, 21 Dec 2011 14:07:43 -0800 (PST)
Received: by eekc14 with SMTP id c14so6676576eek.31 for <ipv6@ietf.org>; Wed, 21 Dec 2011 14:07:42 -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=050SPX+0XWAv1F5jBw4QoV8ZC9+YtJ91q392O8u2F98=; b=rmMVBmcicRjvVXajQ9vAosVNl1XrHQMcGo6ovVoY+RLsNl4EmY4AR8rKruBd6scBZk jDd3dHl+ddoXb22LKj/oxy4Ls1xHUajbMLX48ftdErhbTQ7GbqkV4lCqL26mFeB+QiFj yfG8cLLI3J5EJ/gXn6DJJX+lZYIsmbpz+YLDg=
Received: by 10.213.28.11 with SMTP id k11mr1682089ebc.101.1324505262323; Wed, 21 Dec 2011 14:07:42 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id z54sm25739261eeh.5.2011.12.21.14.07.39 (version=SSLv3 cipher=OTHER); Wed, 21 Dec 2011 14:07:41 -0800 (PST)
Message-ID: <4EF258A5.1040106@gmail.com>
Date: Thu, 22 Dec 2011 11:07:33 +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: Doug Barton <dougb@dougbarton.us>
Subject: Re: IPv6 Router Advertisement Option for Foobar Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <4EF2373B.6060905@gmail.com> <4EF24007.3030300@dougbarton.us>
In-Reply-To: <4EF24007.3030300@dougbarton.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Wed, 21 Dec 2011 22:07:44 -0000

Doug,

Excuse front posting, but I think there's another aspect to this,
which is that the Service Location Protocol (RFC 2165) was
standardised in 1997, when DHCP was still a newcomer, and it
offers a multicast service discovery mechanism that doesn't
need *any* central server (the SLP Directory Agent is optional).

A combination of basic RA plus directory-less SLP would be
necessary and sufficient for small unmanaged networks, I think.

Regards
   Brian

On 2011-12-22 09:22, Doug Barton wrote:
> On 12/21/2011 11:44 AM, Brian E Carpenter wrote:
>> On 2011-12-22 07:37, Doug Barton wrote:
>>> On 12/19/2011 5:24 PM, Bhatia, Manav (Manav) wrote:
>>>> Hi,
>>>>
>>>> We have posted a new draft that extends Router Advertisements to
>>>> include information about the one or more NTP servers present in the
>>>> network. This is useful where the delays in acquiring server
>>>> addresses and communicating with the servers are critical (mobile
>>>> environment for example).
>>> Sort of surprised that no one else has responded so far, but I'll bite.
>>> Quite simply, "no." Slightly less simply, "use DHCP since that's what
>>> it's for."
>>>
>>> I'm happy to expound on the evils of "camel's nose already too far under
>>> the tent," etc.
>> There is of course a broader issue here, illustrated by the endless loop
>> over in MIF about draft-ietf-mif-dhcpv6-route-option.
> 
> ... or the endless loop of "we need DNS info in RA" until it finally got
> adopted.
> 
>> What is the intended scope of the RA mechanism?
>>
>> I was a strong proponent of standardising the DNS server option
>> in RA, because it is an absolute requirement for even the most
>> minimal host to get onto the Internet. But I am also a strong
>> proponent of -dhcpv6-route-option, because it seems clear that
>> more complex environments will inevitably require the extensibility
>> that comes with DHCPv6.
> 
> So, expound it is. :)
> 
> When I first got interested in IPv6 protocol work back in 2000 or so I
> was curious about this "RA" thing. Given that DHCP was already widely
> deployed and successful in the IPv4 world I wondered why such a thing
> was necessary/useful.* I was told at the time that a key feature of IPv6
> was going to be the ability to bring "dumb" devices onto the network
> that only needed to be addressable (light switches were a commonly used
> example). The RA mechanism was perfect for this as it involved no state,
> and anything that needed to be even slightly "smart" would use DHCPv6.
> As much as I was dubious about it at the time, I accepted that
> explanation at face value.
> 
> Then someone realized that RA was great for getting a thing on the
> network, but at that point the thing wasn't really all that useful. So
> the logical next step was to extend RA to allow for sending out
> resolving DNS info. The point I (and others) tried to make at the time
> went something like this (I will use the first person so as to take 100%
> of the blame, but that's not meant to exclude the others who made
> significant contributions to the line of argument that I support):
> 
> Me:	Um, if it's not a dumb device, why can't it use DHCP?
> Them:	DHCP is too heavy-weight. We just need one more piece of
> information provided by RA and then we'll have a fully-functional client
> without the need for DHCP at all, isn't that great!
> Me:	Um, well, I see what you're saying, but doesn't that sort of open
> the door for adding more things down the road? And as both a system
> administrator and an operating system developer I have serious concerns
> about having to support 2 different host configuration protocols. It
> will inevitably lead to problems, and ...
> Them:	No no no, don't be silly! We JUST want to add this ONE little
> thing. After that we promise, no more!
> Me:	I just think it's a bad precedent. Besides, adding only the
> nameserver info isn't enough, you also need the domain and/or search
> string to make it useful.
> Them:	*snap* Oh, right! Thanks for pointing that out. Ok, we'll add that
> too, but after that, NO MORE. I PROMISE!
> Me:	Um ....
> 
>> I think we need a standards track document that defines the maximum
>> scope of the RA mechanism once and for all. Personally I would
>> probably freeze it where it is today, but we need a reasoned
>> architectural decision about this.
> 
> Given that using RA for DNS info isn't widely deployed yet, I would vote
> for rolling RA back to its originally designed purpose, THEN saying "no
> more, really, I mean it." But I doubt that either of those options will
> be successful. I would be ecstatic to be proven wrong however.
> 
> 
> Doug
> 
> * I realize that when RA was first conceived DHCP wasn't that well
> established yet, and furthermore I understand that some people disagree
> on how well established it was even as late as 2000. My experience at
> the time was that DHCP was already widely used in both the SOHO and
> large enterprise markets. In any case I don't think anyone can argue
> that in the last 11 years it hasn't been firmly established. Failure to
> recognize why DHCP is popular, and why RA isn't, is a bug in the
> protocol development process.
> 

From marka@isc.org  Wed Dec 21 14:39:36 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 1F0B511E80B5 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 14:39:36 -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 VoHU0ISQLYdx for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 14:39:35 -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 6908711E8096 for <ipv6@ietf.org>; Wed, 21 Dec 2011 14:39:35 -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 BC30AC9465; Wed, 21 Dec 2011 22:39:16 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:f938:b621:e161:a433]) (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 7C25B216C6E; Wed, 21 Dec 2011 22:39:16 +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 A881B1A703DC; Thu, 22 Dec 2011 09:39:16 +1100 (EST)
To: Fernando Gont <fgont@si6networks.com>
From: Mark Andrews <marka@isc.org>
References: <4EEA0342.2040608@si6networks.com> <82fwgfk1ev.fsf@mid.bfk.de> <20111220.124458.41706285.sthaug@nethelp.no> <20111221140241.3259D1A6F096@drugs.dv.isc.org> <4EF20BEB.8070209@si6networks.com>
Subject: Re: Fragmentation-related security issues
In-reply-to: Your message of "Wed, 21 Dec 2011 13:40:11 -0300." <4EF20BEB.8070209@si6networks.com>
Date: Thu, 22 Dec 2011 09:39:16 +1100
Message-Id: <20111221223916.A881B1A703DC@drugs.dv.isc.org>
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: Wed, 21 Dec 2011 22:39:36 -0000

In message <4EF20BEB.8070209@si6networks.com>, Fernando Gont writes:
> Hi, Mark,
> 
> On 12/21/2011 11:02 AM, Mark Andrews wrote:
> >> Such traffic absolutely occurs in the wild. I have three reasonably
> >> busy name servers where this is logged as an error from the ipfw code,
> >> e.g.
> >>
> >> Dec 16 14:04:04 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> >> Dec 17 00:27:20 slem kernel: IPFW2: IPV6 - Invalid Fragment Header
> [....]
> >>
> >> This is because these name servers haven't (yet) been upgraded to a
> >> FreeBSD version where bug report kern/145733 haven't been fixed. It
> >> *is* fixed in newer FreeBSD versions, e.g. 8.2-STABLE.
> > 
> > Not yet.
> > http://svnweb.freebsd.org/base/stable/8/sys/netinet/ipfw/ip_fw2.c?view=log
> 
> Is the aforementioned traffic the result of an implementation of your
> proposal for for DNS/UDP?

No. I haven't fiddled with any kernel code to do this.  I could do
it with raw sockets but I havn't done so.  The following should
work.  Bind to a socket so reply traffic is handled then use that
socket's port and address to construct a packet with a fragment
header to send using the raw socket.

My main worry is getting DNS/UDP fragmented at IPv6 minumum MTU as
that is not being done today despite the being a API to do it and
as a result I'm seeing lookup failures.  Forcing the addition of a
fragment header is dotting the i's and crossing the t's.

The above fix should have been merged by now if the MFC in 2 weeks
had been heeded.  8-stable is still FreeBSD's latest stable branch.
9.0 is still at release candidate.

Mark

> If that's the case, what's the interface that you use for forcing the
> atomic fragments?
> 
> Thanks,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From fgont@si6networks.com  Wed Dec 21 15:44:38 2011
Return-Path: <fgont@si6networks.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 3C88411E80D0 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 15:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.011,  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 eJYWaq+kawxT for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 15:44:37 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id A67FE11E8096 for <ipv6@ietf.org>; Wed, 21 Dec 2011 15:44:37 -0800 (PST)
Received: from [2001:5c0:1000:a::4fb] by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RdVpq-0002Rd-22; Thu, 22 Dec 2011 00:44:34 +0100
Message-ID: <4EF26F52.2090502@si6networks.com>
Date: Wed, 21 Dec 2011 20:44:18 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com> <82fwgfk1ev.fsf@mid.bfk.de> <20111220.124458.41706285.sthaug@nethelp.no> <20111221140241.3259D1A6F096@drugs.dv.isc.org> <4EF20BEB.8070209@si6networks.com> <20111221223916.A881B1A703DC@drugs.dv.isc.org>
In-Reply-To: <20111221223916.A881B1A703DC@drugs.dv.isc.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 21 Dec 2011 23:44:38 -0000

On 12/21/2011 07:39 PM, Mark Andrews wrote:
>> Is the aforementioned traffic the result of an implementation of your
>> proposal for for DNS/UDP?
> 
> No. I haven't fiddled with any kernel code to do this.

So,,, any idea about what is actually producing these atomic packets?



> My main worry is getting DNS/UDP fragmented at IPv6 minumum MTU as
> that is not being done today despite the being a API to do it and
> as a result I'm seeing lookup failures.  Forcing the addition of a
> fragment header is dotting the i's and crossing the t's.

Sorry: I understand the potential problem with sending packets >1280.

But doesn't sending 1280-sized packets solve the problem? i.e., what are
the boxes that currently implement the RFC2460-specified behavior of
"translating devices wshi leverage the IPv6 fragment header to fragment
an IPv6 packet into the ipv4 world"?

NAT64? The link-radios that RJA mentioned? Anything else?

For the most part, I'm curious about what is generating them....

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From manav.bhatia@alcatel-lucent.com  Wed Dec 21 15:52:19 2011
Return-Path: <manav.bhatia@alcatel-lucent.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 AA0541F0C4D for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 15:52:19 -0800 (PST)
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 XucuHrZ7Yw8C for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 15:52:18 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id C6F5E1F0C35 for <ipv6@ietf.org>; Wed, 21 Dec 2011 15:52:18 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id pBLNqD6a007473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2011 17:52:16 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBLNqCWQ022928 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Dec 2011 05:22:13 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Thu, 22 Dec 2011 05:22:12 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Doug Barton <dougb@dougbarton.us>
Date: Thu, 22 Dec 2011 05:22:10 +0530
Subject: RE: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Topic: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Index: AczAD66ZLf6rWMMSThaCvh5yEKRnIQAKUXMQ
Message-ID: <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us>
In-Reply-To: <4EF22786.2070908@dougbarton.us>
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-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
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: Wed, 21 Dec 2011 23:52:19 -0000

Hi Doug,
=20
>=20
> Sort of surprised that no one else has responded so far, but=20
> I'll bite.
> Quite simply, "no." Slightly less simply, "use DHCP since=20
> that's what it's for."
>=20

I wish it were this simple.

Different operators have different requirements and preferences based on th=
eir environments. I have seen deployments where SLAAC is much more useful t=
han DHCPv6. I've seen deployments where DHCPv6 is needed. So both have a pl=
ace and we should let the operators decide what they want to use. Environme=
nts with 4 to 20 devices in them (small businesses) may not want the comple=
xity of setting up a central server. Those environments are probably more s=
uited for SLAAC.

We have heard customers asking SLAAC to be extended to support NTP, "boot-f=
ile", "next-server" and a few other things that are currently only availabl=
e with DHCP.=20

Currently, operators need to use both SLAAC and DHCP to run their networks.=
 This is far from ideal. Far better for organizations to look at 2 complete=
 solutions and pick the solution that works best for them in their environm=
ent.

Today, we can get NTP server information only with DHCP. DHCP only works af=
ter RAs have been processed. In some environments (mobile IPv6) delays in a=
cquiring NTP and other servers information is critical and waiting for DHCP=
 to come up is NOT an ideal solution.

Cheers, Manav





From samita.chakrabarti@ericsson.com  Wed Dec 21 16:45:30 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 F0F9811E80B5 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 16:45:30 -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 u0ZGlCM8DahW for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 16:45:30 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 64BED11E8096 for <ipv6@ietf.org>; Wed, 21 Dec 2011 16:45:30 -0800 (PST)
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 pBM0jNKk018142; Wed, 21 Dec 2011 18:45:26 -0600
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.30]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Wed, 21 Dec 2011 19:44:47 -0500
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, Doug Barton <dougb@dougbarton.us>
Date: Wed, 21 Dec 2011 19:44:46 -0500
Subject: RE: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Topic: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Index: AczAD66ZLf6rWMMSThaCvh5yEKRnIQAKUXMQAAJSHIA=
Message-ID: <16D60F43CA0B724F8052D7E9323565D7278983ACE8@EUSAACMS0715.eamcs.ericsson.se>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.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 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, 22 Dec 2011 00:45:31 -0000

=20
Agree with Manav on the usecases.

Adhoc type of networks, m2m IoT networks and some home networks benefit fro=
m SLAAC where DHCP Service may not make sense or may be an overhead to main=
tain.

-Samita
-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Bha=
tia, Manav (Manav)
Sent: Wednesday, December 21, 2011 3:52 PM
To: Doug Barton
Cc: 6man Mailing List
Subject: RE: IPv6 Router Advertisement Option for NTP Server Configuration

Hi Doug,
=20
>=20
> Sort of surprised that no one else has responded so far, but I'll=20
> bite.
> Quite simply, "no." Slightly less simply, "use DHCP since that's what=20
> it's for."
>=20

I wish it were this simple.

Different operators have different requirements and preferences based on th=
eir environments. I have seen deployments where SLAAC is much more useful t=
han DHCPv6. I've seen deployments where DHCPv6 is needed. So both have a pl=
ace and we should let the operators decide what they want to use. Environme=
nts with 4 to 20 devices in them (small businesses) may not want the comple=
xity of setting up a central server. Those environments are probably more s=
uited for SLAAC.

We have heard customers asking SLAAC to be extended to support NTP, "boot-f=
ile", "next-server" and a few other things that are currently only availabl=
e with DHCP.=20

Currently, operators need to use both SLAAC and DHCP to run their networks.=
 This is far from ideal. Far better for organizations to look at 2 complete=
 solutions and pick the solution that works best for them in their environm=
ent.

Today, we can get NTP server information only with DHCP. DHCP only works af=
ter RAs have been processed. In some environments (mobile IPv6) delays in a=
cquiring NTP and other servers information is critical and waiting for DHCP=
 to come up is NOT an ideal solution.

Cheers, Manav




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From hingkam16@gmail.com  Wed Dec 21 17:14:37 2011
Return-Path: <hingkam16@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 0F0C211E80DA for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 17:14:37 -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 ydyds7PE21zZ for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 17:14:36 -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 34CC511E80D9 for <ipv6@ietf.org>; Wed, 21 Dec 2011 17:14:36 -0800 (PST)
Received: by iaen33 with SMTP id n33so4731353iae.31 for <ipv6@ietf.org>; Wed, 21 Dec 2011 17:14:34 -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=GtjM3aZK4bpTSHZMPfQ720d1kIDXLSXknHjb1QRFMdQ=; b=mIYh+kRyBDFipI++Xsc4QMOKynR3rOvFSKiG9hyeNFlN723LGpEk3tiXmFVybcGNQq /p7t4ko6qN7RXLj81BukF+gQEAWcXzqogCdMAObXvYtbeP6rkRZ36YIX9tyHE/K7fuAY C1EvaxTBs1WS4aA2pxW+bqT29q9beUxFsZmZ0=
MIME-Version: 1.0
Received: by 10.50.193.229 with SMTP id hr5mr6312496igc.15.1324516474766; Wed, 21 Dec 2011 17:14:34 -0800 (PST)
Received: by 10.50.57.130 with HTTP; Wed, 21 Dec 2011 17:14:34 -0800 (PST)
In-Reply-To: <16D60F43CA0B724F8052D7E9323565D7278983ACE8@EUSAACMS0715.eamcs.ericsson.se>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <16D60F43CA0B724F8052D7E9323565D7278983ACE8@EUSAACMS0715.eamcs.ericsson.se>
Date: Thu, 22 Dec 2011 06:44:34 +0530
Message-ID: <CAEFnT+yXqQB+NvA8Rs1NhKOu5nhKk72QF+hPJSE+itijbHYO3Q@mail.gmail.com>
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
From: "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>
To: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 22 Dec 2011 01:14:37 -0000

Yes, i agree with Manav and Samita. There are networks where SLAAC is
essential and NTP being a core component, must get extended.

Kam

On Thu, Dec 22, 2011 at 6:14 AM, Samita Chakrabarti
<samita.chakrabarti@ericsson.com> wrote:
>
> Agree with Manav on the usecases.
>
> Adhoc type of networks, m2m IoT networks and some home networks benefit f=
rom SLAAC where DHCP Service may not make sense or may be an overhead to ma=
intain.
>
> -Samita
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of B=
hatia, Manav (Manav)
> Sent: Wednesday, December 21, 2011 3:52 PM
> To: Doug Barton
> Cc: 6man Mailing List
> Subject: RE: IPv6 Router Advertisement Option for NTP Server Configuratio=
n
>
> Hi Doug,
>
>>
>> Sort of surprised that no one else has responded so far, but I'll
>> bite.
>> Quite simply, "no." Slightly less simply, "use DHCP since that's what
>> it's for."
>>
>
> I wish it were this simple.
>
> Different operators have different requirements and preferences based on =
their environments. I have seen deployments where SLAAC is much more useful=
 than DHCPv6. I've seen deployments where DHCPv6 is needed. So both have a =
place and we should let the operators decide what they want to use. Environ=
ments with 4 to 20 devices in them (small businesses) may not want the comp=
lexity of setting up a central server. Those environments are probably more=
 suited for SLAAC.
>
> We have heard customers asking SLAAC to be extended to support NTP, "boot=
-file", "next-server" and a few other things that are currently only availa=
ble with DHCP.
>
> Currently, operators need to use both SLAAC and DHCP to run their network=
s. This is far from ideal. Far better for organizations to look at 2 comple=
te solutions and pick the solution that works best for them in their enviro=
nment.
>
> Today, we can get NTP server information only with DHCP. DHCP only works =
after RAs have been processed. In some environments (mobile IPv6) delays in=
 acquiring NTP and other servers information is critical and waiting for DH=
CP to come up is NOT an ideal solution.
>
> Cheers, Manav
>
>
>
>
> --------------------------------------------------------------------
> 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 prvs=3304ccdf4=mukul@uwm.edu  Wed Dec 21 18:10:36 2011
Return-Path: <prvs=3304ccdf4=mukul@uwm.edu>
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 5A5B421F84B0; Wed, 21 Dec 2011 18:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.367
X-Spam-Level: 
X-Spam-Status: No, score=-6.367 tagged_above=-999 required=5 tests=[AWL=0.232,  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 BxP9p2YyAvTv; Wed, 21 Dec 2011 18:10:35 -0800 (PST)
Received: from ip2mta.uwm.edu (ip2mta.uwm.edu [129.89.7.20]) by ietfa.amsl.com (Postfix) with ESMTP id A786F21F8491; Wed, 21 Dec 2011 18:10:35 -0800 (PST)
Received: from localhost (HELO mta02.pantherlink.uwm.edu) ([127.0.0.1]) by ip2mta.uwm.edu with ESMTP; 21 Dec 2011 20:10:28 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.pantherlink.uwm.edu (Postfix) with ESMTP id B304E12E3CC; Wed, 21 Dec 2011 20:10:28 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta02.pantherlink.uwm.edu
Received: from mta02.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta02.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dFZQ646I298h; Wed, 21 Dec 2011 20:10:28 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta02.pantherlink.uwm.edu (Postfix) with ESMTP id 799CF12E3CA; Wed, 21 Dec 2011 20:10:28 -0600 (CST)
Date: Wed, 21 Dec 2011 20:10:28 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Jonathan Hui <jonhui@cisco.com>
Message-ID: <181400612.729968.1324519828382.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <55AAC580-DC07-4DAC-BAB0-A3DF27A11565@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll <roll@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, 22 Dec 2011 02:10:36 -0000

Hi Jonathan

>It knows whether or not RPL is running on an interface.  It could at least check that.  By the same argument, how do you propose we limit packets to a RPL routing domain?  If we have no good way of limiting packets, then the stated security considerations do not apply.

Just the knowledge that the router is part of a particular RPL instance via a particular interface is no guarantee that all the neighbors reachable via that interface belong to the same RPL instance. On the other hand, a router would clearly know whether its particular interface belongs to the RPL domain or not. A packet wont be sent down an interface if that interface is not part of the RPL domain. Here, I am assuming that the RPL domain is defined in the manner you had suggested (analogous to the definition of a routing domain in Section 1.2 of RFC 1195).

>> It would be a problem if the router were required to check its own membership in the RPL Instance in order to accept a packet with SRH. Routers part of a source route should not need to maintain any state about it. 

>Note that in draft-ietf-roll-rpl, RPL routers do maintain such state already.  I agree the issue comes up with P2P.

Indeed, this would be a big problem for P2P-RPL.

>Remember that the original purpose of the RPL Instance is to support MTR.  The RPL Instance identifies what routing topology to use.  This is important especially if the SRH does not specify the entire path to the destination.  How does the tunnel exit-point know what routing topology to use to reach the destination?

There is no mention of MTR in the RPL specs. As far as RPL spec goes, an RPL Instance is simply a group of DAGs using the same OF. You can not assume that a tunnel exit-point would get any information from RPL Instance ID regarding how to reach the ultimate destination of the packet. That information would probably come from the routing table (which may be getting information via several routing protocols).

>The lack of and need for the RPL Instance identifier was raised during IESG review.  The options are (1) to require inclusion a RPL Option in addition to the RPL routing header or (2) add a RPL Instance field in the RPL routing header itself.  I doubt that you would prefer option 1.

I will try to go back and find the IESG review you have mentioned. If you could quickly direct me to right place, that will be helpful. But, at the moment, it is truly mind-boggling for me that RPL instance id is required to be specified in the source routing header. 

>If the RPL router has no idea of the RPL Instance when forwarding, it can choose to forward the packet along anyway.

Doing that would break the rules in SRH draft.

>  At the very least, the tunnel exit-point should enforce the use of the RPL Instance.  Surely the end-points of a source route should at least know what RPL Instance they are in...

Yes, this RPL Instance is a local instance which has no significance associated. I think you are trying to assign a meaning to RPL Instance ID which it does not currently have under RPL core spec.

Thanks
Mukul



From prvs=3304ccdf4=mukul@uwm.edu  Wed Dec 21 18:13:48 2011
Return-Path: <prvs=3304ccdf4=mukul@uwm.edu>
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 6F35C21F8593; Wed, 21 Dec 2011 18:13:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 4l7C0bEurgwZ; Wed, 21 Dec 2011 18:13:47 -0800 (PST)
Received: from ip1mta.uwm.edu (ip1mta.uwm.edu [129.89.7.18]) by ietfa.amsl.com (Postfix) with ESMTP id C646721F84C5; Wed, 21 Dec 2011 18:13:47 -0800 (PST)
Received: from localhost (HELO mta02.pantherlink.uwm.edu) ([127.0.0.1]) by ip1mta.uwm.edu with ESMTP; 21 Dec 2011 20:13:47 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.pantherlink.uwm.edu (Postfix) with ESMTP id 4CB6312E3CD; Wed, 21 Dec 2011 20:13:47 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta02.pantherlink.uwm.edu
Received: from mta02.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta02.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4klshojtMWTM; Wed, 21 Dec 2011 20:13:46 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta02.pantherlink.uwm.edu (Postfix) with ESMTP id CEBAC12E3CC; Wed, 21 Dec 2011 20:13:46 -0600 (CST)
Date: Wed, 21 Dec 2011 20:13:46 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Jonathan Hui <jonhui@cisco.com>
Message-ID: <1603574399.729992.1324520026797.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <7A89D3D3-1DA6-4698-BC4A-B8AEBE397906@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll WG <roll@ietf.org>, 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, 22 Dec 2011 02:13:48 -0000

>Personally, I am OK changing the scope to a RPL routing domain rather than a RPL Instance.  If one really wants to limit to a RPL Instance, then they can also include a RPL Option.  This is what we originally had in rpl-routing-header-05.  This change was made late during the IESG review process.

I support this.

Thanks
Mukul

----- Original Message -----
From: "Jonathan Hui" <jonhui@cisco.com>
To: "Mukul Goyal" <mukul@uwm.edu>, "Jari Arkko" <jari.arkko@piuha.net>
Cc: "roll WG" <roll@ietf.org>, "ipv6" <ipv6@ietf.org>
Sent: Wednesday, December 21, 2011 12:22:11 PM
Subject: Re: draft-ietf-6man-rpl-routing-header-07


Personally, I am OK changing the scope to a RPL routing domain rather than a RPL Instance.  If one really wants to limit to a RPL Instance, then they can also include a RPL Option.  This is what we originally had in rpl-routing-header-05.  This change was made late during the IESG review process.

Jari, would you support reverting the scope of the RPL SRH to a RPL routing domain rather than a RPL Instance?

Thanks.

--
Jonathan Hui

On Dec 21, 2011, at 9:26 AM, Mukul Goyal wrote:

> Jonathan
> 
> I described the problem in the message I sent just now. I think RPL Instance is not the correct scope for SRH. It has to be a RPL domain to be defined as we discussed some time back on the ROLL list.
> 
> Thanks
> Mukul
> 
> ----- Original Message -----
> From: "Jonathan Hui" <jonhui@cisco.com>
> To: "Mukul Goyal" <mukul@uwm.edu>
> Cc: "roll" <roll@ietf.org>
> Sent: Tuesday, December 20, 2011 10:27:29 AM
> Subject: Re: draft-ietf-6man-rpl-routing-header-07
> 
> 
> Mukul,
> 
> As defined in the draft today, you cannot use a RPL routing header to cross RPL Instances.  My understanding is that roll-p2p-rpl makes use of local RPL instances.  Can you describe the issue you are concerned about?
> 
> --
> Jonathan Hui
> 
> On Dec 20, 2011, at 8:14 AM, Mukul Goyal wrote:
> 
>> Jonathan
>> 
>> The IESG-approved draft refers to the RPL instance as the scope where the routing header can be used. How would this routing header be used for general source routing (across RPL instances) in an LLN? How would a node use this routing header if it wants to travel along a source route discovered using P2P-RPL?
>> 
>> Thanks
>> Mukul
>> 
> 


From jonhui@cisco.com  Wed Dec 21 18:42:28 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 85F4211E807F; Wed, 21 Dec 2011 18:42:28 -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 LVUMQNEeuWlb; Wed, 21 Dec 2011 18:42:27 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id C0F7221F8B1D; Wed, 21 Dec 2011 18:42:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=4126; q=dns/txt; s=iport; t=1324521747; x=1325731347; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=E3JqyJuNt7dk3EnL7CMhothIaop81qxVi6iDs6mWQXY=; b=nAuTOzpYoLGKe5aBGymlXaKnJ1jBkff90x1F1kXXc70CzjUnhhbffhgU ZRNlPubeNGq7hkgxbfubd4iVD22rIgLbqmkE4yDoQgh/tpDrVhd+5ezXm j4TGam0OKl/YXkETX+xMiT2tXYaacmdJhFJuYw+7lnk1vqtnBigtJALgV k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EADmY8k6rRDoI/2dsb2JhbAA4Cg6sGYEFgXIBAQECAQESASc/BQsLRlcGHBmHWAiZBAGeMohWglZjBIg3jEiRfFg
X-IronPort-AV: E=Sophos;i="4.71,391,1320624000"; d="scan'208";a="21996853"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 22 Dec 2011 02:42:26 +0000
Received: from sjc-vpn2-370.cisco.com (sjc-vpn2-370.cisco.com [10.21.113.114]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pBM2gPqx002262; Thu, 22 Dec 2011 02:42:25 GMT
Subject: Re: draft-ietf-6man-rpl-routing-header-07
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <181400612.729968.1324519828382.JavaMail.root@mail17.pantherlink.uwm.edu>
Date: Wed, 21 Dec 2011 18:42:25 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <04F68F74-2053-4902-AB99-BDE5FD65FCCF@cisco.com>
References: <181400612.729968.1324519828382.JavaMail.root@mail17.pantherlink.uwm.edu>
To: Mukul Goyal <mukul@uwm.edu>
X-Mailer: Apple Mail (2.1084)
Cc: roll <roll@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, 22 Dec 2011 02:42:28 -0000

On Dec 21, 2011, at 6:10 PM, Mukul Goyal wrote:

> Just the knowledge that the router is part of a particular RPL =
instance via a particular interface is no guarantee that all the =
neighbors reachable via that interface belong to the same RPL instance. =
On the other hand, a router would clearly know whether its particular =
interface belongs to the RPL domain or not. A packet wont be sent down =
an interface if that interface is not part of the RPL domain. Here, I am =
assuming that the RPL domain is defined in the manner you had suggested =
(analogous to the definition of a routing domain in Section 1.2 of RFC =
1195).

And by the same logic, when forwarding a message, there is no guarantee =
that all neighboring nodes reachable via an interface belong to the same =
RPL routing domain.

>> Remember that the original purpose of the RPL Instance is to support =
MTR.  The RPL Instance identifies what routing topology to use.  This is =
important especially if the SRH does not specify the entire path to the =
destination.  How does the tunnel exit-point know what routing topology =
to use to reach the destination?
>=20
> There is no mention of MTR in the RPL specs. As far as RPL spec goes, =
an RPL Instance is simply a group of DAGs using the same OF. You can not =
assume that a tunnel exit-point would get any information from RPL =
Instance ID regarding how to reach the ultimate destination of the =
packet. That information would probably come from the routing table =
(which may be getting information via several routing protocols).

The *entire* point of the RPL Instance concept is to support MTR.  The =
RPL Instance is used to distinguish between different DODAGs from the =
same root.  It gives you the ability to have multiple different routes =
to the same destination (e.g. one that minimizes latency vs. one that =
minimizes energy consumption).  If you don't have the RPL Instance =
information when forwarding a packet, how do you know whether to forward =
along the path that minimizes latency vs. the path that minimizes =
energy?

See slide 18 of =
http://www.iab.org/wp-content/IAB-uploads/2011/04/Vasseur.pdf if you =
want one such reference of MTR and RPL Instances.

>> The lack of and need for the RPL Instance identifier was raised =
during IESG review.  The options are (1) to require inclusion a RPL =
Option in addition to the RPL routing header or (2) add a RPL Instance =
field in the RPL routing header itself.  I doubt that you would prefer =
option 1.
>=20
> I will try to go back and find the IESG review you have mentioned. If =
you could quickly direct me to right place, that will be helpful. But, =
at the moment, it is truly mind-boggling for me that RPL instance id is =
required to be specified in the source routing header.=20

Not so mind boggling if you consider MTR.

>> If the RPL router has no idea of the RPL Instance when forwarding, it =
can choose to forward the packet along anyway.
>=20
> Doing that would break the rules in SRH draft.

Of course.  I was making a proposal that we could relax the processing =
rules to end-points of the SRH.

>> At the very least, the tunnel exit-point should enforce the use of =
the RPL Instance.  Surely the end-points of a source route should at =
least know what RPL Instance they are in...
>=20
> Yes, this RPL Instance is a local instance which has no significance =
associated. I think you are trying to assign a meaning to RPL Instance =
ID which it does not currently have under RPL core spec.


As I mentioned above, the RPL Instance allows you to have multiple =
distinct paths towards the same destination.  The RPL hop-by-hop option =
includes a RPL Instance ID so that a forwarding node knows which routing =
topology to use.  If RPL did not allow multiple routes to the same =
destination, then why bother having a RPL Instance?  You would only need =
the DODAGID to uniquely identify a DODAG (whereas the existing =
definition is the "tuple (RPLInstanceID, DODAGID) uniquely identifies a =
DODAG".

--
Jonathan Hui


From Carl.Wuyts@technicolor.com  Wed Dec 21 23:24:23 2011
Return-Path: <Carl.Wuyts@technicolor.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 E686621F8BA0 for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 23:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  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 dvbj0osJ6kFe for <ipv6@ietfa.amsl.com>; Wed, 21 Dec 2011 23:24:23 -0800 (PST)
Received: from na3sys009aog106.obsmtp.com (na3sys009aob106.obsmtp.com [74.125.149.76]) by ietfa.amsl.com (Postfix) with ESMTP id EE9D421F8B9F for <ipv6@ietf.org>; Wed, 21 Dec 2011 23:24:19 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob106.postini.com ([74.125.148.12]) with SMTP ID DSNKTvLbETWzmEDVMvlgOzmQaUT1cQicCFjO@postini.com; Wed, 21 Dec 2011 23:24:22 PST
Received: from MOPESMAILHC01.eu.thmulti.com (141.11.100.25) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Thu, 22 Dec 2011 08:19:16 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC01.eu.thmulti.com ([141.11.100.25]) with mapi; Thu, 22 Dec 2011 08:19:23 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>, Samita Chakrabarti <samita.chakrabarti@ericsson.com>
Date: Thu, 22 Dec 2011 08:19:19 +0100
Subject: RE: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Topic: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Index: AczARxgzXoT7LoWhQL+MZgtH5VdKywAMjeJg
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB45026D4@MOPESMBX01.eu.thmulti.com>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <16D60F43CA0B724F8052D7E9323565D7278983ACE8@EUSAACMS0715.eamcs.ericsson.se> <CAEFnT+yXqQB+NvA8Rs1NhKOu5nhKk72QF+hPJSE+itijbHYO3Q@mail.gmail.com>
In-Reply-To: <CAEFnT+yXqQB+NvA8Rs1NhKOu5nhKk72QF+hPJSE+itijbHYO3Q@mail.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-Mailman-Approved-At: Thu, 22 Dec 2011 00:28:46 -0800
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, 22 Dec 2011 07:24:24 -0000

I agree that one could benefit in some cases from NTP through RA's, however=
 I don't see any info on "cooperation" between DHCPv6 and RA in your draft,=
 i.e. what is you get your NTP through both channels (both RA and DHCPv6) ?=
  What if content is different on these 2 channels ?  What if (if received =
on both channels) the content of one of them is not available anymore at so=
me point in time ? ...,
Apart from that, we now have DNS support in RA, you're adding NTP, what's n=
ext ... ?  If more info gets sent through RA, more clashes are possible in =
case the info is also present though DHCPv6, hence the more complex it'll g=
et letting them work together.

regs

Carl Wuyts




-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Hin=
g-Kam (Kam) Lam
Sent: donderdag 22 december 2011 2:15
To: Samita Chakrabarti
Cc: 6man Mailing List
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration

Yes, i agree with Manav and Samita. There are networks where SLAAC is essen=
tial and NTP being a core component, must get extended.

Kam

On Thu, Dec 22, 2011 at 6:14 AM, Samita Chakrabarti <samita.chakrabarti@eri=
csson.com> wrote:
>
> Agree with Manav on the usecases.
>
> Adhoc type of networks, m2m IoT networks and some home networks benefit f=
rom SLAAC where DHCP Service may not make sense or may be an overhead to ma=
intain.
>
> -Samita
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf=20
> Of Bhatia, Manav (Manav)
> Sent: Wednesday, December 21, 2011 3:52 PM
> To: Doug Barton
> Cc: 6man Mailing List
> Subject: RE: IPv6 Router Advertisement Option for NTP Server=20
> Configuration
>
> Hi Doug,
>
>>
>> Sort of surprised that no one else has responded so far, but I'll=20
>> bite.
>> Quite simply, "no." Slightly less simply, "use DHCP since that's what=20
>> it's for."
>>
>
> I wish it were this simple.
>
> Different operators have different requirements and preferences based on =
their environments. I have seen deployments where SLAAC is much more useful=
 than DHCPv6. I've seen deployments where DHCPv6 is needed. So both have a =
place and we should let the operators decide what they want to use. Environ=
ments with 4 to 20 devices in them (small businesses) may not want the comp=
lexity of setting up a central server. Those environments are probably more=
 suited for SLAAC.
>
> We have heard customers asking SLAAC to be extended to support NTP, "boot=
-file", "next-server" and a few other things that are currently only availa=
ble with DHCP.
>
> Currently, operators need to use both SLAAC and DHCP to run their network=
s. This is far from ideal. Far better for organizations to look at 2 comple=
te solutions and pick the solution that works best for them in their enviro=
nment.
>
> Today, we can get NTP server information only with DHCP. DHCP only works =
after RAs have been processed. In some environments (mobile IPv6) delays in=
 acquiring NTP and other servers information is critical and waiting for DH=
CP to come up is NOT an ideal solution.
>
> Cheers, Manav
>
>
>
>
> --------------------------------------------------------------------
> 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 zhangdacheng@huawei.com  Thu Dec 22 00:55:49 2011
Return-Path: <zhangdacheng@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 B13DD21F8B45 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 00:55:49 -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 zW3v77pR+a+8 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 00:55:49 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 9EBB121F8B09 for <ipv6@ietf.org>; Thu, 22 Dec 2011 00:55:48 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWL00DRXKR2ZY@szxga03-in.huawei.com> for ipv6@ietf.org; Thu, 22 Dec 2011 16:54:38 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWL00GETKQZF1@szxga03-in.huawei.com> for ipv6@ietf.org; Thu, 22 Dec 2011 16:54:38 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFZ10504; Thu, 22 Dec 2011 16:54:38 +0800
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 22 Dec 2011 16:54:33 +0800
Received: from SZXEML528-MBX.china.huawei.com ([169.254.4.248]) by szxeml405-hub.china.huawei.com ([10.82.67.60]) with mapi id 14.01.0323.003; Thu, 22 Dec 2011 16:54:35 +0800
Date: Thu, 22 Dec 2011 08:54:35 +0000
From: "Dacheng Zhang(Dacheng)" <zhangdacheng@huawei.com>
Subject: re: IPv6 Router Advertisement Option for NTP Server Configuration
In-reply-to: <867F4B6A1672E541A94676D556793ACD0CB45026D4@MOPESMBX01.eu.thmulti.com>
X-Originating-IP: [10.108.4.62]
To: Wuyts Carl <Carl.Wuyts@technicolor.com>, "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>, Samita Chakrabarti <samita.chakrabarti@ericsson.com>
Message-id: <C72CBD9FE3CA604887B1B3F1D145D05E0122EE4B@szxeml528-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-index: AczARxgzLf6rWMMSThaCvh5yEKRnIQAMjeJgAALInHA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <16D60F43CA0B724F8052D7E9323565D7278983ACE8@EUSAACMS0715.eamcs.ericsson.se> <CAEFnT+yXqQB+NvA8Rs1NhKOu5nhKk72QF+hPJSE+itijbHYO3Q@mail.gmail.com> <867F4B6A1672E541A94676D556793ACD0CB45026D4@MOPESMBX01.eu.thmulti.com>
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, 22 Dec 2011 08:55:49 -0000

>> I agree that one could benefit in some cases from NTP through RA's, however
>> I don't see any info on "cooperation" between DHCPv6 and RA in your draft,
>> i.e. what is you get your NTP through both channels (both RA and DHCPv6) ?
>> What if content is different on these 2 channels ?  What if (if received on both
>> channels) the content of one of them is not available anymore at some point in
>> time ? ...,
[Dacheng Zhang] 
We originally intend to provide a mechanism which is complementary to the solution using DHCP. So basically, we just consider the scenarios where DHCP is not deployed. But your comments are very interesting, we should consider them in the next version of the draft. 
>> Apart from that, we now have DNS support in RA, you're adding NTP, what's
>> next ... ?  
[Dacheng Zhang] 
That is a very good question. Maybe NTP can be the last one, maybe not. I think this issue is worthwhile for us to spend more time on it.


>> case the info is also present though DHCPv6, hence the more complex it'll get
>> letting them work together.
>> 
[Dacheng Zhang] 
If there is already a DHCPv6 server where users can learn where to find a NTP server, then we may not have to provide the NTP server information in RAes. As what I have said above, we expect to provide a way to locate NTP servers when SLAAC is employed.
>> 
>> regs
>> 
>> Carl Wuyts
>> 
>> 
>> 
>> 
>> -----Original Message-----
>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
>> Hing-Kam (Kam) Lam
>> Sent: donderdag 22 december 2011 2:15
>> To: Samita Chakrabarti
>> Cc: 6man Mailing List
>> Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
>> 
>> Yes, i agree with Manav and Samita. There are networks where SLAAC is
>> essential and NTP being a core component, must get extended.
>> 
>> Kam
>> 
>> On Thu, Dec 22, 2011 at 6:14 AM, Samita Chakrabarti
>> <samita.chakrabarti@ericsson.com> wrote:
>> >
>> > Agree with Manav on the usecases.
>> >
>> > Adhoc type of networks, m2m IoT networks and some home networks
>> benefit from SLAAC where DHCP Service may not make sense or may be an
>> overhead to maintain.
>> >
>> > -Samita
>> > -----Original Message-----
>> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
>> > Of Bhatia, Manav (Manav)
>> > Sent: Wednesday, December 21, 2011 3:52 PM
>> > To: Doug Barton
>> > Cc: 6man Mailing List
>> > Subject: RE: IPv6 Router Advertisement Option for NTP Server
>> > Configuration
>> >
>> > Hi Doug,
>> >
>> >>
>> >> Sort of surprised that no one else has responded so far, but I'll
>> >> bite.
>> >> Quite simply, "no." Slightly less simply, "use DHCP since that's what
>> >> it's for."
>> >>
>> >
>> > I wish it were this simple.
>> >
>> > Different operators have different requirements and preferences based on
>> their environments. I have seen deployments where SLAAC is much more
>> useful than DHCPv6. I've seen deployments where DHCPv6 is needed. So both
>> have a place and we should let the operators decide what they want to use.
>> Environments with 4 to 20 devices in them (small businesses) may not want
>> the complexity of setting up a central server. Those environments are
>> probably more suited for SLAAC.
>> >
>> > We have heard customers asking SLAAC to be extended to support NTP,
>> "boot-file", "next-server" and a few other things that are currently only
>> available with DHCP.
>> >
>> > Currently, operators need to use both SLAAC and DHCP to run their
>> networks. This is far from ideal. Far better for organizations to look at 2
>> complete solutions and pick the solution that works best for them in their
>> environment.
>> >
>> > Today, we can get NTP server information only with DHCP. DHCP only works
>> after RAs have been processed. In some environments (mobile IPv6) delays in
>> acquiring NTP and other servers information is critical and waiting for DHCP to
>> come up is NOT an ideal solution.
>> >
>> > Cheers, Manav
>> >
>> >
>> >
>> >
>> > --------------------------------------------------------------------
>> > 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
>> --------------------------------------------------------------------
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------

From sander@steffann.nl  Thu Dec 22 01:04:15 2011
Return-Path: <sander@steffann.nl>
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 24C3521F8B2B for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 01:04:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.89
X-Spam-Level: **
X-Spam-Status: No, score=2.89 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_IP_ADDR=1.119, HOST_EQ_NL=1.545, HOST_EQ_STATIC=1.172]
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 b3-vEZ3MLEMW for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 01:04:14 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id A3DE621F8B2A for <ipv6@ietf.org>; Thu, 22 Dec 2011 01:04:14 -0800 (PST)
Received: from [172.18.1.219] (095-097-083-090.static.chello.nl [95.97.83.90]) by mail.sintact.nl (Postfix) with ESMTP id 08391200E; Thu, 22 Dec 2011 10:04:11 +0100 (CET)
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com>
Date: Thu, 22 Dec 2011 10:04:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D532F72-52D3-47D2-B206-6A724ADC8AC3@steffann.nl>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1251.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, 22 Dec 2011 09:04:15 -0000

Hi,

> Different operators have different requirements and preferences based =
on their environments. I have seen deployments where SLAAC is much more =
useful than DHCPv6. I've seen deployments where DHCPv6 is needed. So =
both have a place and we should let the operators decide what they want =
to use. Environments with 4 to 20 devices in them (small businesses) may =
not want the complexity of setting up a central server. Those =
environments are probably more suited for SLAAC.

SLAAC + Stateless DHCPv6. I agree that a central Stateful DHCPv6 server =
is too complex for such a situation, but come on: a stateless DHCPv6 =
server is simple=85.

- Sander


From zhangdacheng@huawei.com  Thu Dec 22 01:15:13 2011
Return-Path: <zhangdacheng@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 966F421F8BB5 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 01:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[AWL=-4.694, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 41DACgxAD1y4 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 01:15:13 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id DB3ED21F8BA9 for <ipv6@ietf.org>; Thu, 22 Dec 2011 01:15:12 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWL003JTLNAJA@szxga03-in.huawei.com> for ipv6@ietf.org; Thu, 22 Dec 2011 17:13:58 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWL00FS3LNAFI@szxga03-in.huawei.com> for ipv6@ietf.org; Thu, 22 Dec 2011 17:13:58 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFZ12073; Thu, 22 Dec 2011 17:13:58 +0800
Received: from SZXEML415-HUB.china.huawei.com (10.82.67.154) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 22 Dec 2011 17:13:53 +0800
Received: from SZXEML528-MBX.china.huawei.com ([169.254.4.248]) by szxeml415-hub.china.huawei.com ([10.82.67.154]) with mapi id 14.01.0323.003; Thu, 22 Dec 2011 17:13:54 +0800
Date: Thu, 22 Dec 2011 09:13:54 +0000
From: "Dacheng Zhang(Dacheng)" <zhangdacheng@huawei.com>
Subject: =?gb2312?B?tPC4tDogSVB2NiBSb3V0ZXIgQWR2ZXJ0aXNlbWVudCBPcHRpb24gZm9yIE5U?= =?gb2312?Q?P_Server_Configuration?=
In-reply-to: <0D532F72-52D3-47D2-B206-6A724ADC8AC3@steffann.nl>
X-Originating-IP: [10.108.4.62]
To: Sander Steffann <sander@steffann.nl>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Message-id: <C72CBD9FE3CA604887B1B3F1D145D05E0122EE6C@szxeml528-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-index: AQHMwIirLf6rWMMSThaCvh5yEKRnIZXnkRHg
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <0D532F72-52D3-47D2-B206-6A724ADC8AC3@steffann.nl>
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, 22 Dec 2011 09:15:13 -0000

DQoNCj4+IC0tLS0t08q8/tStvP4tLS0tLQ0KPj4gt6K8/sjLOiBpcHY2LWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzppcHY2LWJvdW5jZXNAaWV0Zi5vcmddILT6se0gU2FuZGVyDQo+PiBTdGVmZmFu
bg0KPj4gt6LLzcqxvOQ6IDIwMTHE6jEy1MIyMsjVIDE3OjA0DQo+PiDK1bz+yMs6IEJoYXRpYSwg
TWFuYXYgKE1hbmF2KQ0KPj4gs63LzTogNm1hbiBNYWlsaW5nIExpc3QNCj4+INb3zOI6IFJlOiBJ
UHY2IFJvdXRlciBBZHZlcnRpc2VtZW50IE9wdGlvbiBmb3IgTlRQIFNlcnZlciBDb25maWd1cmF0
aW9uDQo+PiANCj4+IEhpLA0KPj4gDQo+PiA+IERpZmZlcmVudCBvcGVyYXRvcnMgaGF2ZSBkaWZm
ZXJlbnQgcmVxdWlyZW1lbnRzIGFuZCBwcmVmZXJlbmNlcyBiYXNlZCBvbg0KPj4gdGhlaXIgZW52
aXJvbm1lbnRzLiBJIGhhdmUgc2VlbiBkZXBsb3ltZW50cyB3aGVyZSBTTEFBQyBpcyBtdWNoIG1v
cmUNCj4+IHVzZWZ1bCB0aGFuIERIQ1B2Ni4gSSd2ZSBzZWVuIGRlcGxveW1lbnRzIHdoZXJlIERI
Q1B2NiBpcyBuZWVkZWQuIFNvIGJvdGgNCj4+IGhhdmUgYSBwbGFjZSBhbmQgd2Ugc2hvdWxkIGxl
dCB0aGUgb3BlcmF0b3JzIGRlY2lkZSB3aGF0IHRoZXkgd2FudCB0byB1c2UuDQo+PiBFbnZpcm9u
bWVudHMgd2l0aCA0IHRvIDIwIGRldmljZXMgaW4gdGhlbSAoc21hbGwgYnVzaW5lc3NlcykgbWF5
IG5vdCB3YW50DQo+PiB0aGUgY29tcGxleGl0eSBvZiBzZXR0aW5nIHVwIGEgY2VudHJhbCBzZXJ2
ZXIuIFRob3NlIGVudmlyb25tZW50cyBhcmUNCj4+IHByb2JhYmx5IG1vcmUgc3VpdGVkIGZvciBT
TEFBQy4NCj4+IA0KPj4gU0xBQUMgKyBTdGF0ZWxlc3MgREhDUHY2LiBJIGFncmVlIHRoYXQgYSBj
ZW50cmFsIFN0YXRlZnVsIERIQ1B2NiBzZXJ2ZXIgaXMNCj4+IHRvbyBjb21wbGV4IGZvciBzdWNo
IGEgc2l0dWF0aW9uLCBidXQgY29tZSBvbjogYSBzdGF0ZWxlc3MgREhDUHY2IHNlcnZlciBpcw0K
Pj4gc2ltcGxloa0uDQo+PiANCltEYWNoZW5nIFpoYW5nXSANCkJ1dCBpbiB0aGlzIGNhc2UsIHdl
IHN0aWxsIG5lZWQgdG8gZGVwbG95IGEgc2VydmVyLi4uIElmIHdlIGNhbiB1c2UgUkFzIGluIHN1
Y2ggZW52aXJvbm1lbnRzLCBldmVuIGEgc3RhdGVsZXNzIERIQ1Agc2VydmVyIGlzIG5vdCBuZWNl
c3NhcnkuIFBsZWFzZSBjb3JyZWN0IG1lIGlmIEkgYW0gd3Jvbmcgb3IgbWlzcyBhbnl0aGluZy4g
DQo+PiAtIFNhbmRlcg0KPj4gDQo+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4gSUVURiBJUHY2IHdvcmtpbmcg
Z3JvdXAgbWFpbGluZyBsaXN0DQo+PiBpcHY2QGlldGYub3JnDQo+PiBBZG1pbmlzdHJhdGl2ZSBS
ZXF1ZXN0czogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHY2DQo+PiAt
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0K

From sander@steffann.nl  Thu Dec 22 01:34:20 2011
Return-Path: <sander@steffann.nl>
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 CDD3A21F8BA7 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 01:34:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.89
X-Spam-Level: **
X-Spam-Status: No, score=2.89 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_IP_ADDR=1.119, HOST_EQ_NL=1.545, HOST_EQ_STATIC=1.172]
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 ytudRKBg4-03 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 01:34:20 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADED21F8BA2 for <ipv6@ietf.org>; Thu, 22 Dec 2011 01:34:19 -0800 (PST)
Received: from [172.18.1.100] (095-097-083-091.static.chello.nl [95.97.83.91]) by mail.sintact.nl (Postfix) with ESMTP id 0E1282003; Thu, 22 Dec 2011 10:34:18 +0100 (CET)
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/signed; boundary="Apple-Mail=_A346E531-8454-41E1-9734-A4183749A760"; protocol="application/pkcs7-signature"; micalg=sha1
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <C72CBD9FE3CA604887B1B3F1D145D05E0122EE6C@szxeml528-mbx.china.huawei.com>
Date: Thu, 22 Dec 2011 10:34:18 +0100
Message-Id: <941C720A-5AB8-46DF-B41C-E13ADAC6EA5E@steffann.nl>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <0D532F72-52D3-47D2-B206-6A724ADC8AC3@steffann.nl> <C72CBD9FE3CA604887B1B3F1D145D05E0122EE6C@szxeml528-mbx.china.huawei.com>
To: "Dacheng Zhang(Dacheng)" <zhangdacheng@huawei.com>
X-Mailer: Apple Mail (2.1251.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, 22 Dec 2011 09:34:20 -0000

--Apple-Mail=_A346E531-8454-41E1-9734-A4183749A760
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312

Hi,

>>> SLAAC + Stateless DHCPv6. I agree that a central Stateful DHCPv6 =
server is
>>> too complex for such a situation, but come on: a stateless DHCPv6 =
server is
>>> simple=A1=AD.
> [Dacheng Zhang]=20
> But in this case, we still need to deploy a server... If we can use =
RAs in such environments, even a stateless DHCP server is not necessary. =
Please correct me if I am wrong or miss anything.=20

Depends on how you see 'deploying a server'. Your router can easily =
perform the stateless DHCPv6 server function. Even tiny CPEs can do that =
these days, and Cisco has been doing that for ages.

- Sander


--Apple-Mail=_A346E531-8454-41E1-9734-A4183749A760
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFSDCCBUQw
ggMsoAMCAQICAQIwDQYJKoZIhvcNAQEFBQAwdjELMAkGA1UEBhMCTkwxEjAQBgNVBAcTCUFwZWxk
b29ybjEVMBMGA1UEChMMU0pNIFN0ZWZmYW5uMR0wGwYDVQQDExRTSk0gU3RlZmZhbm4gUm9vdCBD
QTEdMBsGCSqGSIb3DQEJARYOY2FAc3RlZmZhbm4ubmwwHhcNMTEwODA5MTczMjE2WhcNMTIwODA4
MTczMjE2WjB1MQswCQYDVQQGEwJOTDESMBAGA1UEBxMJQXBlbGRvb3JuMRUwEwYDVQQKEwxTSk0g
U3RlZmZhbm4xGDAWBgNVBAMTD1NhbmRlciBTdGVmZmFubjEhMB8GCSqGSIb3DQEJARYSc2FuZGVy
QHN0ZWZmYW5uLm5sMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC9b7oVFaA35FKgKq2dZXbh
X1kQl2mgPnaI3OurSyefZ6dyv8JFNM6CAA77kb/Gh5FXVDEJujcRPnE93Lmvmx+82J140WSiTpez
7QY8oBYNDCRP0KksXzwfClZjrG2Afw8S1jH14ymK0HufZ9kEkSWD5WzrxEDSqwnQTyFhsGCrbQID
AQABo4IBYDCCAVwwCQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBLAwKwYJYIZIAYb4QgENBB4W
HFRpbnlDQSBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFMBr5zy4rYkQJ/JeoU3+6lnw
Ebd5MIGoBgNVHSMEgaAwgZ2AFOH79lsAHFEBG+6Vrq192mCYPEg6oXqkeDB2MQswCQYDVQQGEwJO
TDESMBAGA1UEBxMJQXBlbGRvb3JuMRUwEwYDVQQKEwxTSk0gU3RlZmZhbm4xHTAbBgNVBAMTFFNK
TSBTdGVmZmFubiBSb290IENBMR0wGwYJKoZIhvcNAQkBFg5jYUBzdGVmZmFubi5ubIIJALBR3gny
oySYMBkGA1UdEgQSMBCBDmNhQHN0ZWZmYW5uLm5sMB0GA1UdEQQWMBSBEnNhbmRlckBzdGVmZmFu
bi5ubDALBgNVHQ8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAIOE9ZBvSzDEUrBsMvN3cdkcyywn
mbZhsZhXJrjEsKSEzbDfoyS/gQzX2cN6jwWNMMN34q8nvy3/cMtYxupjL4LfXitPjVSk+C69jaA1
/SNwLpHFAXbW9ikM3deEtJJJcs1t/OvKHa/mGuWq6MHjAOhKqm2ei2L5WLj5sBkFb7o7BeCh6AzL
RWMwYLBpw0xjwxthFsmRC8q4eWFUT+kSMBHSl2EoKBqaYWfxI7oQ/obWAt4OncylGbDKWDQiwW+O
VPFJKe2fHMFp0v/f4+u1NDTUmyjZ+Lxw+4ABZ0pmAjuceN/zrO4IRU/dpHMs38+Wn5glDmDNkSpE
74ropT+BZhMeSpF2fACVtuk/2Wf+0whB1KzUCMZHiCT/UJp5C2pM0kqVE1EjKRAVRTirjf8O2aHr
A5Yn5o80MQKZ9X1UWvUaIMAxbjWQGCX+qD5NmjxptMHPMtj/mVAa1oS1PC87pk5ca9kht1KGGKBX
Pp8wrGIdXRhIGsh4Y6TW6eYVmIgb8WqLqpV5qg4y/irukcxq7Y0DcDv8dRY9Qvr0kJgU1lHV36Vr
kFYJ2+RZFxYKQeS1/KkN33qng79VNsDejVx9jc1XmEgIRkR+3ou6yfBrG6iQrb9DziD4EFZg4sCk
DifH+Am6d7h21ayiHRT+zyqrqIBrgG1e1O+sL8HGKIZN7QioMYICnjCCApoCAQEwezB2MQswCQYD
VQQGEwJOTDESMBAGA1UEBxMJQXBlbGRvb3JuMRUwEwYDVQQKEwxTSk0gU3RlZmZhbm4xHTAbBgNV
BAMTFFNKTSBTdGVmZmFubiBSb290IENBMR0wGwYJKoZIhvcNAQkBFg5jYUBzdGVmZmFubi5ubAIB
AjAJBgUrDgMCGgUAoIIBeTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xMTEyMjIwOTM0MTlaMCMGCSqGSIb3DQEJBDEWBBSvfzFyUNjWqy1BRAE8DgHAoedyZjCBigYJ
KwYBBAGCNxAEMX0wezB2MQswCQYDVQQGEwJOTDESMBAGA1UEBxMJQXBlbGRvb3JuMRUwEwYDVQQK
EwxTSk0gU3RlZmZhbm4xHTAbBgNVBAMTFFNKTSBTdGVmZmFubiBSb290IENBMR0wGwYJKoZIhvcN
AQkBFg5jYUBzdGVmZmFubi5ubAIBAjCBjAYLKoZIhvcNAQkQAgsxfaB7MHYxCzAJBgNVBAYTAk5M
MRIwEAYDVQQHEwlBcGVsZG9vcm4xFTATBgNVBAoTDFNKTSBTdGVmZmFubjEdMBsGA1UEAxMUU0pN
IFN0ZWZmYW5uIFJvb3QgQ0ExHTAbBgkqhkiG9w0BCQEWDmNhQHN0ZWZmYW5uLm5sAgECMA0GCSqG
SIb3DQEBAQUABIGAqTt8s5hKQ6WpDXWcFMKz4UFpLGgKfiHbmoZ9tWILknJe74oT0uh5CUZ+7pkW
kFsZXTqkcaiviEkf9qqxxeETtQZp5azw2NzHFaTBGZaYBtcvMhuiQPW6NsbzgbGSvfvSn91qsXH/
mS6MdV915lL7zuxq06jR0UUYOgXVoDjSl3MAAAAAAAA=

--Apple-Mail=_A346E531-8454-41E1-9734-A4183749A760--

From evyncke@cisco.com  Thu Dec 22 04:27:19 2011
Return-Path: <evyncke@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 87B0821F853B for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 04:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 lX8nTWRJoM0y for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 04:27:18 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3985F21F853A for <ipv6@ietf.org>; Thu, 22 Dec 2011 04:27:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=evyncke@cisco.com; l=4965; q=dns/txt; s=iport; t=1324556838; x=1325766438; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=nwZ3xtIHTwH/HJ1EF1CdBxPBB453OaCt59c2I3EZBMQ=; b=f+wqYcxPCBFEWz+B9T4NI6PdZGh42pBV8KUypQdtPIXZpsjrc6RZwKqs Cx/I58GnCcVTfTljcEhYl5bcKKsOPcca7GPwvRlsAzdfFFIGm5Lpv87mV tPLiw0l7uHln75QSNXJb4CauzV5Ic9P8x32pL1zEdEm8CcegRq/TLwNsj I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0AAPsg806Q/khL/2dsb2JhbABDm1GQWoEFgXIBAQEEAQEBDwEdPgsMBAIBCBEEAQEBCgYXAQYBJh8JCAEBBBMIEweHYJhtAZ4vBIssYwSIBJ8w
X-IronPort-AV: E=Sophos;i="4.71,392,1320624000"; d="scan'208";a="124479098"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 22 Dec 2011 12:27:16 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pBMCRGV4009178; Thu, 22 Dec 2011 12:27:16 GMT
Received: from xmb-ams-110.cisco.com ([144.254.74.85]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 22 Dec 2011 13:27:16 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: IPv6 Router Advertisement Option for NTP Server Configuration
Date: Thu, 22 Dec 2011 13:27:04 +0100
Message-ID: <317616CE96204D49B5A1811098BA89500625B4AE@XMB-AMS-110.cisco.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB45026D4@MOPESMBX01.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Index: AczARxgzXoT7LoWhQL+MZgtH5VdKywAMjeJgAAroFYA=
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com><4EF22786.2070908@dougbarton.us><7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com><16D60F43CA0B724F8052D7E9323565D7278983ACE8@EUSAACMS0715.eamcs.ericsson.se><CAEFnT+yXqQB+NvA8Rs1NhKOu5nhKk72QF+hPJSE+itijbHYO3Q@mail.gmail.com> <867F4B6A1672E541A94676D556793ACD0CB45026D4@MOPESMBX01.eu.thmulti.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Samita Chakrabarti" <samita.chakrabarti@ericsson.com>
X-OriginalArrivalTime: 22 Dec 2011 12:27:16.0117 (UTC) FILETIME=[0A428450:01CCC0A5]
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, 22 Dec 2011 12:27:19 -0000

And then the next one, and the next one, until packet size is > 1280 and =
other horror stories begin :-O

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf =
Of
> Wuyts Carl
> Sent: jeudi 22 d=E9cembre 2011 08:19
> To: Hing-Kam (Kam) Lam; Samita Chakrabarti
> Cc: 6man Mailing List
> Subject: RE: IPv6 Router Advertisement Option for NTP Server =
Configuration
>=20
> I agree that one could benefit in some cases from NTP through RA's, =
however
> I don't see any info on "cooperation" between DHCPv6 and RA in your =
draft,
> i.e. what is you get your NTP through both channels (both RA and =
DHCPv6) ?
> What if content is different on these 2 channels ?  What if (if =
received on
> both channels) the content of one of them is not available anymore at =
some
> point in time ? ...,
> Apart from that, we now have DNS support in RA, you're adding NTP, =
what's
> next ... ?  If more info gets sent through RA, more clashes are =
possible in
> case the info is also present though DHCPv6, hence the more complex =
it'll
> get letting them work together.
>=20
>=20
> regs
>=20
> Carl Wuyts
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf =
Of
> Hing-Kam (Kam) Lam
> Sent: donderdag 22 december 2011 2:15
> To: Samita Chakrabarti
> Cc: 6man Mailing List
> Subject: Re: IPv6 Router Advertisement Option for NTP Server =
Configuration
>=20
> Yes, i agree with Manav and Samita. There are networks where SLAAC is
> essential and NTP being a core component, must get extended.
>=20
> Kam
>=20
> On Thu, Dec 22, 2011 at 6:14 AM, Samita Chakrabarti
> <samita.chakrabarti@ericsson.com> wrote:
> >
> > Agree with Manav on the usecases.
> >
> > Adhoc type of networks, m2m IoT networks and some home networks =
benefit
> from SLAAC where DHCP Service may not make sense or may be an overhead =
to
> maintain.
> >
> > -Samita
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> > Of Bhatia, Manav (Manav)
> > Sent: Wednesday, December 21, 2011 3:52 PM
> > To: Doug Barton
> > Cc: 6man Mailing List
> > Subject: RE: IPv6 Router Advertisement Option for NTP Server
> > Configuration
> >
> > Hi Doug,
> >
> >>
> >> Sort of surprised that no one else has responded so far, but I'll
> >> bite.
> >> Quite simply, "no." Slightly less simply, "use DHCP since that's =
what
> >> it's for."
> >>
> >
> > I wish it were this simple.
> >
> > Different operators have different requirements and preferences =
based on
> their environments. I have seen deployments where SLAAC is much more =
useful
> than DHCPv6. I've seen deployments where DHCPv6 is needed. So both =
have a
> place and we should let the operators decide what they want to use.
> Environments with 4 to 20 devices in them (small businesses) may not =
want
> the complexity of setting up a central server. Those environments are
> probably more suited for SLAAC.
> >
> > We have heard customers asking SLAAC to be extended to support NTP, =
"boot-
> file", "next-server" and a few other things that are currently only
> available with DHCP.
> >
> > Currently, operators need to use both SLAAC and DHCP to run their
> networks. This is far from ideal. Far better for organizations to look =
at 2
> complete solutions and pick the solution that works best for them in =
their
> environment.
> >
> > Today, we can get NTP server information only with DHCP. DHCP only =
works
> after RAs have been processed. In some environments (mobile IPv6) =
delays in
> acquiring NTP and other servers information is critical and waiting =
for DHCP
> to come up is NOT an ideal solution.
> >
> > Cheers, Manav
> >
> >
> >
> >
> > --------------------------------------------------------------------
> > 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
> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From brian@innovationslab.net  Thu Dec 22 05:48:02 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 D361521F8AEA for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 05:48:02 -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 gL3da2r8fYx0 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 05:48:02 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6B08821F8541 for <ipv6@ietf.org>; Thu, 22 Dec 2011 05:48: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 87A49881F3 for <ipv6@ietf.org>; Thu, 22 Dec 2011 05:47:55 -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 4862C130004 for <ipv6@ietf.org>; Thu, 22 Dec 2011 05:47:55 -0800 (PST)
Message-ID: <4EF33509.1060102@innovationslab.net>
Date: Thu, 22 Dec 2011 08:47:53 -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: IPv6 Router Advertisement Option for NTP Server Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.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, 22 Dec 2011 13:48:02 -0000

Hi Manav,

On 12/19/11 8:24 PM, Bhatia, Manav (Manav) wrote:
> Hi,
>
> We have posted a new draft that extends Router Advertisements to
> include information about the one or more NTP servers present in the
> network. This is useful where the delays in acquiring server
> addresses and communicating with the servers are critical (mobile
> environment for example).
>
> http://www.ietf.org/internet-drafts/draft-bcd-6man-ntp-server-ra-opt-00.txt
>
>  Would be great to get some feedback from the WG.
>
> We will also be soliciting comments from the NTP and the TICTOC WGs.

So, as co-chair of both NTP and 6MAN, I would ask how this draft differs 
from RFC 5908.

Regards,
Brian


From manav.bhatia@alcatel-lucent.com  Thu Dec 22 05:57:04 2011
Return-Path: <manav.bhatia@alcatel-lucent.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 C233B21F84C9 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 05:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086,  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 XjTcMPt6il2F for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 05:57:03 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id CC60521F8509 for <ipv6@ietf.org>; Thu, 22 Dec 2011 05:57:03 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id pBMDuvVm004294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Dec 2011 07:56:59 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBMDuutb005350 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Dec 2011 19:26:56 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Thu, 22 Dec 2011 19:26:56 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Wuyts Carl <Carl.Wuyts@technicolor.com>, "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>, Samita Chakrabarti <samita.chakrabarti@ericsson.com>
Date: Thu, 22 Dec 2011 19:26:55 +0530
Subject: RE: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Topic: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Index: AczARxgzXoT7LoWhQL+MZgtH5VdKywAMjeJgAAx/VgA=
Message-ID: <7C362EEF9C7896468B36C9B79200D8350D027BA990@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <16D60F43CA0B724F8052D7E9323565D7278983ACE8@EUSAACMS0715.eamcs.ericsson.se> <CAEFnT+yXqQB+NvA8Rs1NhKOu5nhKk72QF+hPJSE+itijbHYO3Q@mail.gmail.com> <867F4B6A1672E541A94676D556793ACD0CB45026D4@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB45026D4@MOPESMBX01.eu.thmulti.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-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
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, 22 Dec 2011 13:57:04 -0000

This problem definitely needs to be addressed. However, its not unique to t=
his draft.

The similar problem exists with DNS, similar prefixes, and a lot of other p=
arameters that you can get with both DHCP and RA.

This is debatable but can be argued as a configuration issue as SLAAC and D=
HCPv6 shouldn't really be providing conflicting information. One could alwa=
ys provide a CLI knob to assign priorities against these.

Cheers, Manav

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On=20
> Behalf Of Wuyts Carl
> Sent: Thursday, December 22, 2011 12:49 PM
> To: Hing-Kam (Kam) Lam; Samita Chakrabarti
> Cc: 6man Mailing List
> Subject: RE: IPv6 Router Advertisement Option for NTP Server=20
> Configuration
>=20
> I agree that one could benefit in some cases from NTP through=20
> RA's, however I don't see any info on "cooperation" between=20
> DHCPv6 and RA in your draft, i.e. what is you get your NTP=20
> through both channels (both RA and DHCPv6) ?  What if content=20
> is different on these 2 channels ?  What if (if received on=20
> both channels) the content of one of them is not available=20
> anymore at some point in time ? ..., Apart from that, we now=20
> have DNS support in RA, you're adding NTP, what's next ... ? =20
> If more info gets sent through RA, more clashes are possible=20
> in case the info is also present though DHCPv6, hence the=20
> more complex it'll get letting them work together.
>=20
> regs
>=20
> Carl Wuyts
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On=20
> Behalf Of Hing-Kam (Kam) Lam
> Sent: donderdag 22 december 2011 2:15
> To: Samita Chakrabarti
> Cc: 6man Mailing List
> Subject: Re: IPv6 Router Advertisement Option for NTP Server=20
> Configuration
>=20
> Yes, i agree with Manav and Samita. There are networks where=20
> SLAAC is essential and NTP being a core component, must get extended.
>=20
> Kam
>=20
> On Thu, Dec 22, 2011 at 6:14 AM, Samita Chakrabarti=20
> <samita.chakrabarti@ericsson.com> wrote:
> >
> > Agree with Manav on the usecases.
> >
> > Adhoc type of networks, m2m IoT networks and some home=20
> networks benefit from SLAAC where DHCP Service may not make=20
> sense or may be an overhead to maintain.
> >
> > -Samita
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org]=20
> On Behalf=20
> > Of Bhatia, Manav (Manav)
> > Sent: Wednesday, December 21, 2011 3:52 PM
> > To: Doug Barton
> > Cc: 6man Mailing List
> > Subject: RE: IPv6 Router Advertisement Option for NTP Server=20
> > Configuration
> >
> > Hi Doug,
> >
> >>
> >> Sort of surprised that no one else has responded so far, but I'll=20
> >> bite.
> >> Quite simply, "no." Slightly less simply, "use DHCP since=20
> that's what=20
> >> it's for."
> >>
> >
> > I wish it were this simple.
> >
> > Different operators have different requirements and=20
> preferences based on their environments. I have seen=20
> deployments where SLAAC is much more useful than DHCPv6. I've=20
> seen deployments where DHCPv6 is needed. So both have a place=20
> and we should let the operators decide what they want to use.=20
> Environments with 4 to 20 devices in them (small businesses)=20
> may not want the complexity of setting up a central server.=20
> Those environments are probably more suited for SLAAC.
> >
> > We have heard customers asking SLAAC to be extended to=20
> support NTP, "boot-file", "next-server" and a few other=20
> things that are currently only available with DHCP.
> >
> > Currently, operators need to use both SLAAC and DHCP to run=20
> their networks. This is far from ideal. Far better for=20
> organizations to look at 2 complete solutions and pick the=20
> solution that works best for them in their environment.
> >
> > Today, we can get NTP server information only with DHCP.=20
> DHCP only works after RAs have been processed. In some=20
> environments (mobile IPv6) delays in acquiring NTP and other=20
> servers information is critical and waiting for DHCP to come=20
> up is NOT an ideal solution.
> >
> > Cheers, Manav
> >
> >
> >
> >
> > --------------------------------------------------------------------
> > 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
> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> =

From simon.perreault@viagenie.ca  Thu Dec 22 05:57:06 2011
Return-Path: <simon.perreault@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 A556621F85B8 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 05:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149,  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 zOlUuhSILwtQ for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 05:57:06 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id 1A5C521F851F for <ipv6@ietf.org>; Thu, 22 Dec 2011 05:57:06 -0800 (PST)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 5338621CC2; Thu, 22 Dec 2011 08:56:35 -0500 (EST)
Message-ID: <4EF33712.6010503@viagenie.ca>
Date: Thu, 22 Dec 2011 08:56:34 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0
MIME-Version: 1.0
To: Sander Steffann <sander@steffann.nl>
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <0D532F72-52D3-47D2-B206-6A724ADC8AC3@steffann.nl> <C72CBD9FE3CA604887B1B3F1D145D05E0122EE6C@szxeml528-mbx.china.huawei.com> <941C720A-5AB8-46DF-B41C-E13ADAC6EA5E@steffann.nl>
In-Reply-To: <941C720A-5AB8-46DF-B41C-E13ADAC6EA5E@steffann.nl>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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, 22 Dec 2011 13:57:06 -0000

On 2011-12-22 04:34, Sander Steffann wrote:
>>>> SLAAC + Stateless DHCPv6. I agree that a central Stateful DHCPv6 server is
>>>> too complex for such a situation, but come on: a stateless DHCPv6 server is
>>>> simple….
>> [Dacheng Zhang]
>> But in this case, we still need to deploy a server... If we can use RAs in such environments, even a stateless DHCP server is not necessary. Please correct me if I am wrong or miss anything.
>
> Depends on how you see 'deploying a server'. Your router can easily perform the stateless DHCPv6 server function. Even tiny CPEs can do that these days, and Cisco has been doing that for ages.

Right. To me, this (a stateless DHCPv6 server function in the router device) is 
what this draft has to compete against. The authors would have to demonstrate a 
use case where this is not acceptable/feasible/sufficient.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From manav.bhatia@alcatel-lucent.com  Thu Dec 22 05:59:16 2011
Return-Path: <manav.bhatia@alcatel-lucent.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 2E20D21F8AC9 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 05:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  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 WHpHAlJ0c26k for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 05:59:15 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9F37F21F8500 for <ipv6@ietf.org>; Thu, 22 Dec 2011 05:59:15 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id pBMDxCPa002502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Dec 2011 07:59:14 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBMDxBLO005492 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Dec 2011 19:29:11 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Thu, 22 Dec 2011 19:29:11 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Date: Thu, 22 Dec 2011 19:29:09 +0530
Subject: RE: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Topic: IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Index: AczAsFnqjLKVf0JHQWOVg8hzIke22wAAUdtw
Message-ID: <7C362EEF9C7896468B36C9B79200D8350D027BA991@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF33509.1060102@innovationslab.net>
In-Reply-To: <4EF33509.1060102@innovationslab.net>
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-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
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, 22 Dec 2011 13:59:16 -0000

Hi Brian,

5908 uses DHCPv6. We're extending RAs to advertise the NTP info.

Cheers, Manav=20

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On=20
> Behalf Of Brian Haberman
> Sent: Thursday, December 22, 2011 7:18 PM
> To: ipv6@ietf.org
> Subject: Re: IPv6 Router Advertisement Option for NTP Server=20
> Configuration
>=20
> Hi Manav,
>=20
> On 12/19/11 8:24 PM, Bhatia, Manav (Manav) wrote:
> > Hi,
> >
> > We have posted a new draft that extends Router Advertisements to=20
> > include information about the one or more NTP servers=20
> present in the=20
> > network. This is useful where the delays in acquiring=20
> server addresses=20
> > and communicating with the servers are critical (mobile environment=20
> > for example).
> >
> >=20
> http://www.ietf.org/internet-drafts/draft-bcd-6man-ntp-server-ra-opt-0
> > 0.txt
> >
> >  Would be great to get some feedback from the WG.
> >
> > We will also be soliciting comments from the NTP and the TICTOC WGs.
>=20
> So, as co-chair of both NTP and 6MAN, I would ask how this=20
> draft differs from RFC 5908.
>=20
> Regards,
> Brian
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> =

From brian@innovationslab.net  Thu Dec 22 06:24:33 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 20C8F21F8AD6 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 06:24:33 -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 AZFeabuYtwGh for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 06:24:32 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7887E21F8AC3 for <ipv6@ietf.org>; Thu, 22 Dec 2011 06:24:32 -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 6394C881F3; Thu, 22 Dec 2011 06:24:32 -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 DFE2C130004; Thu, 22 Dec 2011 06:24:31 -0800 (PST)
Message-ID: <4EF33D9E.2040808@innovationslab.net>
Date: Thu, 22 Dec 2011 09:24:30 -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: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF33509.1060102@innovationslab.net> <7C362EEF9C7896468B36C9B79200D8350D027BA991@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D027BA991@INBANSXCHMBSA1.in.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 22 Dec 2011 14:24:33 -0000

On 12/22/11 8:59 AM, Bhatia, Manav (Manav) wrote:
> Hi Brian,
>
> 5908 uses DHCPv6. We're extending RAs to advertise the NTP info.
>

I guess it is a little too early and I did not ask my question clearly 
enough.

Does this RA-based approach provide the exact same information as the 
RFC 5908 DHCP option?  Less info?  More info?

Have you considered simply using the multicast-based NTP server 
discovery in environments where DHCP is not available or providing NTP 
information?

Regards,
Brian

> Cheers, Manav
>
>> -----Original Message-----
>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On
>> Behalf Of Brian Haberman
>> Sent: Thursday, December 22, 2011 7:18 PM
>> To: ipv6@ietf.org
>> Subject: Re: IPv6 Router Advertisement Option for NTP Server
>> Configuration
>>
>> Hi Manav,
>>
>> On 12/19/11 8:24 PM, Bhatia, Manav (Manav) wrote:
>>> Hi,
>>>
>>> We have posted a new draft that extends Router Advertisements to
>>> include information about the one or more NTP servers
>> present in the
>>> network. This is useful where the delays in acquiring
>> server addresses
>>> and communicating with the servers are critical (mobile environment
>>> for example).
>>>
>>>
>> http://www.ietf.org/internet-drafts/draft-bcd-6man-ntp-server-ra-opt-0
>>> 0.txt
>>>
>>>   Would be great to get some feedback from the WG.
>>>
>>> We will also be soliciting comments from the NTP and the TICTOC WGs.
>>
>> So, as co-chair of both NTP and 6MAN, I would ask how this
>> draft differs from RFC 5908.
>>
>> Regards,
>> Brian
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------


From bzeeb-lists@lists.zabbadoz.net  Thu Dec 22 06:58:34 2011
Return-Path: <bzeeb-lists@lists.zabbadoz.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 051B221F888A for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 06:58:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 tDaQw4lFp3bh for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 06:58:33 -0800 (PST)
Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD6921F85CE for <ipv6@ietf.org>; Thu, 22 Dec 2011 06:58:31 -0800 (PST)
Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 222D725D3888; Thu, 22 Dec 2011 14:58:29 +0000 (UTC)
Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 3999DBD78C8; Thu, 22 Dec 2011 14:58:29 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sbone.de
Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id zdjDR+U7q5uN; Thu, 22 Dec 2011 14:58:27 +0000 (UTC)
Received: from orange-en1.sbone.de (orange-en1.sbone.de [IPv6:fde9:577b:c1a9:31:cabc:c8ff:fecf:e8e3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 82BD2BD78C7; Thu, 22 Dec 2011 14:58:25 +0000 (UTC)
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
In-Reply-To: <4EF33D9E.2040808@innovationslab.net>
Date: Thu, 22 Dec 2011 14:58:24 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC1251AE-2FBB-4297-9152-4338C008414D@lists.zabbadoz.net>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF33509.1060102@innovationslab.net> <7C362EEF9C7896468B36C9B79200D8350D027BA991@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF33D9E.2040808@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
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, 22 Dec 2011 14:58:34 -0000

On 22. Dec 2011, at 14:24 , Brian Haberman wrote:

> On 12/22/11 8:59 AM, Bhatia, Manav (Manav) wrote:
>> Hi Brian,
>>=20
>> 5908 uses DHCPv6. We're extending RAs to advertise the NTP info.
>>=20
>=20
> I guess it is a little too early and I did not ask my question clearly =
enough.
>=20
> Does this RA-based approach provide the exact same information as the =
RFC 5908 DHCP option?  Less info?  More info?
>=20
> Have you considered simply using the multicast-based NTP server =
discovery in environments where DHCP is not available or providing NTP =
information?

Just seeing the discussion...

+1 for just using MC NTP.  Even just ff02::101 is great for a lot of use
cases already.  Almost wonder if it should be a lose requirement for =
v6ops
and the CPEs...  Of course more problematic in large campus networks but
configuring all the services on all the routers for RA there is not what
you really want either.

/bz

--=20
Bjoern A. Zeeb                                 You have to have visions!
         Stop bit received. Insert coin for new address family.=

From prvs=3304ccdf4=mukul@uwm.edu  Thu Dec 22 07:04:52 2011
Return-Path: <prvs=3304ccdf4=mukul@uwm.edu>
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 9B8AA21F8A7D; Thu, 22 Dec 2011 07:04:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.466
X-Spam-Level: 
X-Spam-Status: No, score=-6.466 tagged_above=-999 required=5 tests=[AWL=0.133,  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 n3npceKxeo7r; Thu, 22 Dec 2011 07:04:48 -0800 (PST)
Received: from ip1mta.uwm.edu (ip1mta.uwm.edu [129.89.7.18]) by ietfa.amsl.com (Postfix) with ESMTP id 99DDD21F8A66; Thu, 22 Dec 2011 07:04:48 -0800 (PST)
Received: from localhost (HELO mta03.pantherlink.uwm.edu) ([127.0.0.1]) by ip1mta.uwm.edu with ESMTP; 22 Dec 2011 09:04:35 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta03.pantherlink.uwm.edu (Postfix) with ESMTP id 5B3281FD0AB; Thu, 22 Dec 2011 09:04:35 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta03.pantherlink.uwm.edu
Received: from mta03.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta03.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YIqWAzTiRgx1; Thu, 22 Dec 2011 09:04:34 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta03.pantherlink.uwm.edu (Postfix) with ESMTP id 1989D1FD014; Thu, 22 Dec 2011 09:04:34 -0600 (CST)
Date: Thu, 22 Dec 2011 09:04:33 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Jonathan Hui <jonhui@cisco.com>
Message-ID: <1026538192.732410.1324566273913.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <04F68F74-2053-4902-AB99-BDE5FD65FCCF@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll <roll@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, 22 Dec 2011 15:04:52 -0000

Hi Jonathan

>And by the same logic, when forwarding a message, there is no guarantee that all neighboring nodes reachable via an interface belong to the same RPL routing domain.

The receiving router could check if it belongs to the RPL domain listed in the SRH. If not, it can drop the packet.

>The *entire* point of the RPL Instance concept is to support MTR.  The RPL Instance is used to distinguish between different DODAGs from the same root.  It gives you the ability to have multiple different routes to the same destination (e.g. one that minimizes latency vs. one that minimizes energy consumption).  If you don't have the RPL Instance information when forwarding a packet, how do you know whether to forward along the path that minimizes latency vs. the path that minimizes energy?

Suppose a tunnel exit point knows that the SRH that carried the packet so far had RPL Instance ID 'x' which happens to be associated with OF0. What information does that give to the tunnel exit point? Is OF0 associated with minimizing of latency or of energy? What is preventing this particular RPL Instance ID 'x' with OF0 to be associated with two different DAGs - one minimizing latency and the other minimizing energy?

>See slide 18 of http://www.iab.org/wp-content/IAB-uploads/2011/04/Vasseur.pdf if you want one such reference of MTR and RPL Instances.

>As I mentioned above, the RPL Instance allows you to have multiple distinct paths towards the same destination.  The RPL hop-by-hop option includes a RPL Instance ID so that a forwarding node knows which routing topology to use.  If RPL did not allow multiple routes to the same destination, then why bother having a RPL Instance?  You would only need the DODAGID to uniquely identify a DODAG (whereas the existing definition is the "tuple (RPLInstanceID, DODAGID) uniquely identifies a DODAG".

All this discussion is really besides the point. If we could just have the RPL domain and not the RPL Instance as the scope for an SRH, that will solve my problem.

Thanks
Mukul


--
Jonathan Hui


From warren@kumari.net  Thu Dec 22 07:34:22 2011
Return-Path: <warren@kumari.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 A118221F8A6C for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 07:34:22 -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 VY6t4oigIkfO for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 07:34:22 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 13B3821F85A8 for <ipv6@ietf.org>; Thu, 22 Dec 2011 07:34:21 -0800 (PST)
Received: from dhcp-172-19-119-228.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id BAB311B407CA; Thu, 22 Dec 2011 10:34:19 -0500 (EST)
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com>
Date: Thu, 22 Dec 2011 10:34:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <43D91249-102E-4C02-92BF-E73CB8326E0B@kumari.net>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1084)
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, 22 Dec 2011 15:34:22 -0000

On Dec 21, 2011, at 6:52 PM, Bhatia, Manav (Manav) wrote:

> Hi Doug,
>=20
>>=20
>> Sort of surprised that no one else has responded so far, but=20
>> I'll bite.
>> Quite simply, "no." Slightly less simply, "use DHCP since=20
>> that's what it's for."
>>=20
>=20
> I wish it were this simple.
>=20
> Different operators have different requirements and preferences based =
on their environments.

Yes.

> I have seen deployments where SLAAC is much more useful than DHCPv6. =
I've seen deployments where DHCPv6 is needed. So both have a place and =
we should let the operators decide what they want to use. Environments =
with 4 to 20 devices in them (small businesses) may not want the =
complexity of setting up a central server.

I have a (home) network with 4 to 20 (actually, looking it is more like =
60) devices. I don't want the complexity of setting up a central server. =
Oh! Wait a sec. I didn't set up a central server, the same device that =
does SLAAC also does DHCPv6. Convenient, huh? Almost like someone was =
planning ahead.

> Those environments are probably more suited for SLAAC.
>=20
> We have heard customers asking SLAAC to be extended to support NTP, =
"boot-file", "next-server" and a few other things that are currently =
only available with DHCP.=20

Yup.=20
I'd also like to hand out WINS servers and workgroup name and a proxy =
server and a log server and a hostname and a preference identifier (so I =
know which network is "trusted") and a MTU hint and a timezone offset =
and a walled garden authentication server and a geographical hint so I =
know how find the nearest Starbucks and local language identifier and =
base-64 encoded note as to where I left my car keys this time and ...

>=20
> Currently, operators need to use both SLAAC and DHCP to run their =
networks. This is far from ideal. Far better for organizations to look =
at 2 complete solutions and pick the solution that works best for them =
in their environment.
>=20
> Today, we can get NTP server information only with DHCP. DHCP only =
works after RAs have been processed. In some environments (mobile IPv6) =
delays in acquiring NTP and other servers information is critical and =
waiting for DHCP to come up is NOT an ideal solution.

'tis not ideal that I cannot find my car keys, especially when I'm =
already late for work. Where's my RA provided key hint option, please?

>=20
> Cheers, Manav

Cheerio,
  W

P.S: I have not had my morning coffee - this email might sound more =
pissy than I intended...=20

>=20
>=20
>=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 Dec 22 07:40:15 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 EFD8321F8B10; Thu, 22 Dec 2011 07:40:15 -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 hLeCab3hjN2p; Thu, 22 Dec 2011 07:40:11 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id B266421F8B09; Thu, 22 Dec 2011 07:40:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=2955; q=dns/txt; s=iport; t=1324568411; x=1325778011; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=M4PCcrHsk9nNkvZvNhDyIgSVUkJD8U/py4HbzxtIJus=; b=LXwUBSKsNWXzt5NNCzK+ADbRrRP6inRQnxZrZSD72XF/lTLgxXV8OR35 fcqn8eR/ElPlr7SFZLrlSSnOZZ74n0amb3H1xL/b7fFtUCx9ZDVbU7rc3 Sk8MDrQWIk/Z45eKg0qMS+Cwu4oZgxnZ+XmuvOEHukWcAMZClPywJjc58 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAD1O806rRDoG/2dsb2JhbAA6Cg6sHYEFgXIBAQMCEgEnLRIQC0ZXBjWHYJkRAZ46iFaCVmMEiDeMSpF7WA
X-IronPort-AV: E=Sophos;i="4.71,393,1320624000"; d="scan'208";a="22099927"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 22 Dec 2011 15:34:38 +0000
Received: from dhcp-128-107-155-213.cisco.com (dhcp-128-107-155-213.cisco.com [128.107.155.213]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pBMFYcrk017175; Thu, 22 Dec 2011 15:34:38 GMT
Subject: Re: draft-ietf-6man-rpl-routing-header-07
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <1026538192.732410.1324566273913.JavaMail.root@mail17.pantherlink.uwm.edu>
Date: Thu, 22 Dec 2011 07:34:40 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A027178-7819-4608-836E-940C9B25EB60@cisco.com>
References: <1026538192.732410.1324566273913.JavaMail.root@mail17.pantherlink.uwm.edu>
To: Mukul Goyal <mukul@uwm.edu>
X-Mailer: Apple Mail (2.1084)
Cc: roll <roll@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, 22 Dec 2011 15:40:16 -0000

On Dec 22, 2011, at 7:04 AM, Mukul Goyal wrote:

>> And by the same logic, when forwarding a message, there is no =
guarantee that all neighboring nodes reachable via an interface belong =
to the same RPL routing domain.
>=20
> The receiving router could check if it belongs to the RPL domain =
listed in the SRH. If not, it can drop the packet.

And what information does the SRH provide that indicates what RPL =
routing domain it is coming from?  A node now has to know what neighbors =
are in its RPL routing domain?

>> The *entire* point of the RPL Instance concept is to support MTR.  =
The RPL Instance is used to distinguish between different DODAGs from =
the same root.  It gives you the ability to have multiple different =
routes to the same destination (e.g. one that minimizes latency vs. one =
that minimizes energy consumption).  If you don't have the RPL Instance =
information when forwarding a packet, how do you know whether to forward =
along the path that minimizes latency vs. the path that minimizes =
energy?
>=20
> Suppose a tunnel exit point knows that the SRH that carried the packet =
so far had RPL Instance ID 'x' which happens to be associated with OF0. =
What information does that give to the tunnel exit point? Is OF0 =
associated with minimizing of latency or of energy? What is preventing =
this particular RPL Instance ID 'x' with OF0 to be associated with two =
different DAGs - one minimizing latency and the other minimizing energy?

The tunnel exit-point knows what kind of paths the tunnel entry-point is =
forwarding the packet along.  Again, the whole purpose of RPL Instances =
is to allow multiple paths optimized with different OFs towards the same =
destination.  If a forwarding device has no idea of what path to choose, =
then why bother with a RPL Instance?

>> See slide 18 of =
http://www.iab.org/wp-content/IAB-uploads/2011/04/Vasseur.pdf if you =
want one such reference of MTR and RPL Instances.
>=20
>> As I mentioned above, the RPL Instance allows you to have multiple =
distinct paths towards the same destination.  The RPL hop-by-hop option =
includes a RPL Instance ID so that a forwarding node knows which routing =
topology to use.  If RPL did not allow multiple routes to the same =
destination, then why bother having a RPL Instance?  You would only need =
the DODAGID to uniquely identify a DODAG (whereas the existing =
definition is the "tuple (RPLInstanceID, DODAGID) uniquely identifies a =
DODAG".
>=20
> All this discussion is really besides the point. If we could just have =
the RPL domain and not the RPL Instance as the scope for an SRH, that =
will solve my problem.


Limiting to a RPL Instance is well-defined.  Limiting to a RPL routing =
domain requires a little more thought.  Can you propose the exact =
processing rules that would clearly limit a routing header to a RPL =
routing domain?

--
Jonathan Hui


From prvs=3304ccdf4=mukul@uwm.edu  Thu Dec 22 08:05:13 2011
Return-Path: <prvs=3304ccdf4=mukul@uwm.edu>
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 825CF21F86AA; Thu, 22 Dec 2011 08:05:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.483
X-Spam-Level: 
X-Spam-Status: No, score=-6.483 tagged_above=-999 required=5 tests=[AWL=0.116,  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 RF02BrAHqy6g; Thu, 22 Dec 2011 08:05:13 -0800 (PST)
Received: from ip1mta.uwm.edu (ip1mta.uwm.edu [129.89.7.18]) by ietfa.amsl.com (Postfix) with ESMTP id C7A0421F85C7; Thu, 22 Dec 2011 08:05:12 -0800 (PST)
Received: from localhost (HELO mta04.pantherlink.uwm.edu) ([127.0.0.1]) by ip1mta.uwm.edu with ESMTP; 22 Dec 2011 10:05:11 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta04.pantherlink.uwm.edu (Postfix) with ESMTP id 06BD12B3EDB; Thu, 22 Dec 2011 10:03:24 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta04.pantherlink.uwm.edu
Received: from mta04.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta04.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 515sfAWOB5xl; Thu, 22 Dec 2011 10:03:23 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta04.pantherlink.uwm.edu (Postfix) with ESMTP id BE9502B3ED8; Thu, 22 Dec 2011 10:03:23 -0600 (CST)
Date: Thu, 22 Dec 2011 10:05:11 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Jonathan Hui <jonhui@cisco.com>
Message-ID: <279988575.733200.1324569911307.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <2A027178-7819-4608-836E-940C9B25EB60@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll <roll@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, 22 Dec 2011 16:05:13 -0000

>And what information does the SRH provide that indicates what RPL routing domain it is coming from?  A node now has to know what neighbors are in its RPL routing domain?

The simplest option would be for the router to decide before hand which of its interfaces belong to "the" RPL domain and which not. The SRH need not have any RPL domain field. The router would drop the packet if received over an interface not in "the" RPL domain. If the packet was received over an interface in the RPL domain, it wont be forwarded down the interfaces not in the RPL domain.

A more complicated scheme would be to allow for multiple RPL domains and list the RPL Domain ID in the SRH. The router would know which RPL domains its interfaces belong to and would treat the packet accordingly.

> 
>> Suppose a tunnel exit point knows that the SRH that carried the packet so far had RPL Instance ID 'x' which happens to be associated with OF0. What information does that give to the tunnel exit point? Is OF0 associated with minimizing of latency or of energy? What is preventing this particular RPL Instance ID 'x' with OF0 to be associated with two different DAGs - one minimizing latency and the other minimizing energy?

>The tunnel exit-point knows what kind of paths the tunnel entry-point is forwarding the packet along. 

I am trying to say that RPL Instance ID does not give that information to the tunnel exit point. As per RPL spec, RPL Instance ID would have a mapping to the OF. It nowhere says that RPL Instance ID also has a mapping to metrics in use.
 
> Again, the whole purpose of RPL Instances is to allow multiple paths optimized with different OFs towards the same destination.

OF is just a way to calculate the rank. OF does not imply the use of particular routing metrics. Since RPL Instance ID does not identify the routing metrics in use, it can not tell what kind of route is being used to forward a packet.

> If a forwarding device has no idea of what path to choose, then why bother with a RPL Instance?

RPL Instance is the top level identifier of the DAGs that can be used to forward the packet. It also maps to a particular OF. In my opinion and as per RPL spec, RPL instance has no other significance.

>> 
>> All this discussion is really besides the point. If we could just have the RPL domain and not the RPL Instance as the scope for an SRH, that will solve my problem.

>Limiting to a RPL Instance is well-defined.  Limiting to a RPL routing domain requires a little more thought.  Can you propose the exact processing rules that would clearly limit a routing header to a RPL routing domain?

Lets assume that RPL domain is defined as you suggested some time back to be analogous to the routing domain definition in RFC 1195 (section 1.2). I interpret it to mean that the RPL router would characterize its interfaces as either belonging to the RPL domain or outside the RPL domain.

With this interpretation of RPL domain in mind, the following processing rules would replace the rules 2 and 3 on page 13 of your draft:

2.  Datagrams, carrying an SRH and received on an interface not belonging to the RPL domain, will be dropped with no further processing.

3.  Datagrams, carrying an SRH and destined to be forwarded along interfaces outside the RPL domain, are dropped with no further processing.

Thanks
Mukul




--
Jonathan Hui


From jonhui@cisco.com  Thu Dec 22 08:33:25 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 0B56221F8AFB; Thu, 22 Dec 2011 08:33:25 -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=[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 QjJb9kjA2+WL; Thu, 22 Dec 2011 08:33:24 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 48C7A21F8AF2; Thu, 22 Dec 2011 08:33:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=4253; q=dns/txt; s=iport; t=1324571604; x=1325781204; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=wk6l4N8Pr8Lgn+hvNjXll+RAsMKQ9SFbH2+75QSIXbE=; b=UCbJq6chYzTP73kbqWhJGHVpWT8XmJA3qIsTGaDM7TJvJO1yRpjvwdN5 ktBkf9YGkvaEZKkY4NuGM164ChKJFeHDbfxKd29OPYT6ywROkE30GFB98 DnmO92mZH69HEvzwcMJVV/DmcY6Jw0Rc5OQQZh3WBuzsVKgTPKAvEyF++ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAO9a806rRDoH/2dsb2JhbAA5Cg6sH4EFgXIBAQUSASc/BQsLRlcGNaBzAZ40iFaCVmMEiDeMSpF7WA
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 22 Dec 2011 16:17:15 +0000
Received: from dhcp-128-107-155-213.cisco.com (dhcp-128-107-155-213.cisco.com [128.107.155.213]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pBMGHEOG009320; Thu, 22 Dec 2011 16:17:14 GMT
Subject: Re: draft-ietf-6man-rpl-routing-header-07
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <279988575.733200.1324569911307.JavaMail.root@mail17.pantherlink.uwm.edu>
Date: Thu, 22 Dec 2011 08:17:15 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C1711F1-AB47-4870-8228-A6A36A0C3164@cisco.com>
References: <279988575.733200.1324569911307.JavaMail.root@mail17.pantherlink.uwm.edu>
To: Mukul Goyal <mukul@uwm.edu>
X-Mailer: Apple Mail (2.1084)
Cc: roll <roll@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, 22 Dec 2011 16:33:25 -0000

On Dec 22, 2011, at 8:05 AM, Mukul Goyal wrote:

>> And what information does the SRH provide that indicates what RPL =
routing domain it is coming from?  A node now has to know what neighbors =
are in its RPL routing domain?
>=20
> The simplest option would be for the router to decide before hand =
which of its interfaces belong to "the" RPL domain and which not. The =
SRH need not have any RPL domain field. The router would drop the packet =
if received over an interface not in "the" RPL domain. If the packet was =
received over an interface in the RPL domain, it wont be forwarded down =
the interfaces not in the RPL domain.

Again, just because you received a message on an interface for which =
you've enabled RPL doesn't mean you know the message came from a router =
that is within the same RPL routing domain.  A router not running RPL =
could have sent you that message.

> A more complicated scheme would be to allow for multiple RPL domains =
and list the RPL Domain ID in the SRH. The router would know which RPL =
domains its interfaces belong to and would treat the packet accordingly.

Except that there is no such concept.  RPL Instance ID is the closest we =
have.

>> The tunnel exit-point knows what kind of paths the tunnel entry-point =
is forwarding the packet along.=20
>=20
> I am trying to say that RPL Instance ID does not give that information =
to the tunnel exit point. As per RPL spec, RPL Instance ID would have a =
mapping to the OF. It nowhere says that RPL Instance ID also has a =
mapping to metrics in use.

=46rom Section 3.2.1 of draft-ietf-roll-rpl:

   The Objective Function (OF) defines how RPL nodes select and optimize
   routes within a RPL Instance.  The OF is identified by an Objective
   Code Point (OCP) within the DIO Configuration option.  An OF defines
   how nodes translate one or more metrics and constraints, which are
   themselves defined in [I-D.ietf-roll-routing-metrics], into a value
   called Rank, which approximates the node's distance from a DODAG
   root.  An OF also defines how nodes select parents.  Further details
   may be found in Section 14, [I-D.ietf-roll-routing-metrics],
   [I-D.ietf-roll-of0], and related companion specifications.

As you state, RPL Instance maps to OF which, from the cited text, maps =
to metrics and route selection.  By transitivity, RPL Instance ID does =
map to metrics and how routes are formed.

>> Again, the whole purpose of RPL Instances is to allow multiple paths =
optimized with different OFs towards the same destination.
>=20
> OF is just a way to calculate the rank. OF does not imply the use of =
particular routing metrics. Since RPL Instance ID does not identify the =
routing metrics in use, it can not tell what kind of route is being used =
to forward a packet.

In reality, it doesn't need to care.  It just needs to care about =
sending along routes that were created using the same OF.  Having each =
RPL router choose an arbitrary route created using an arbitrary OF does =
not make any sense.

>> If a forwarding device has no idea of what path to choose, then why =
bother with a RPL Instance?
>=20
> RPL Instance is the top level identifier of the DAGs that can be used =
to forward the packet. It also maps to a particular OF. In my opinion =
and as per RPL spec, RPL instance has no other significance.

See above.  RPL Instance does map to metrics.

>> Limiting to a RPL Instance is well-defined.  Limiting to a RPL =
routing domain requires a little more thought.  Can you propose the =
exact processing rules that would clearly limit a routing header to a =
RPL routing domain?
>=20
> Lets assume that RPL domain is defined as you suggested some time back =
to be analogous to the routing domain definition in RFC 1195 (section =
1.2). I interpret it to mean that the RPL router would characterize its =
interfaces as either belonging to the RPL domain or outside the RPL =
domain.

The definition I proposed was simply a collection of routers running RPL =
under the same administrative domain.  As mentioned above, that does not =
mean that every router on an interface belongs to a RPL routing domain.

--
Jonathan Hui


From prvs=3304ccdf4=mukul@uwm.edu  Thu Dec 22 09:24:44 2011
Return-Path: <prvs=3304ccdf4=mukul@uwm.edu>
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 38E9C21F899F; Thu, 22 Dec 2011 09:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.496
X-Spam-Level: 
X-Spam-Status: No, score=-6.496 tagged_above=-999 required=5 tests=[AWL=0.103,  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 tUZjQBsZTOZj; Thu, 22 Dec 2011 09:24:43 -0800 (PST)
Received: from ip2mta.uwm.edu (ip2mta.uwm.edu [129.89.7.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7B9EC21F893C; Thu, 22 Dec 2011 09:24:43 -0800 (PST)
Received: from localhost (HELO mta03.pantherlink.uwm.edu) ([127.0.0.1]) by ip2mta.uwm.edu with ESMTP; 22 Dec 2011 11:24:42 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta03.pantherlink.uwm.edu (Postfix) with ESMTP id E7F6B1FD013; Thu, 22 Dec 2011 11:24:42 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta03.pantherlink.uwm.edu
Received: from mta03.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta03.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cXO5W0Vhr9RZ; Thu, 22 Dec 2011 11:24:42 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta03.pantherlink.uwm.edu (Postfix) with ESMTP id A8F311FD011; Thu, 22 Dec 2011 11:24:42 -0600 (CST)
Date: Thu, 22 Dec 2011 11:24:42 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: Jonathan Hui <jonhui@cisco.com>
Message-ID: <1033338721.734443.1324574682571.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <6C1711F1-AB47-4870-8228-A6A36A0C3164@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll <roll@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, 22 Dec 2011 17:24:44 -0000

>Again, just because you received a message on an interface for which you've enabled RPL doesn't mean you know the message came from a router that is within the same RPL routing domain.  A router not running RPL could have sent you that message.

A router not running RPL could have sent me a message carrying SRH?

>> A more complicated scheme would be to allow for multiple RPL domains and list the RPL Domain ID in the SRH. The router would know which RPL domains its interfaces belong to and would treat the packet accordingly.

>Except that there is no such concept.  RPL Instance ID is the closest we have.

Yes, the concept of RPL domain needs to be defined - either in rpl-terminology draft or in your draft.

>> I am trying to say that RPL Instance ID does not give that information to the tunnel exit point. As per RPL spec, RPL Instance ID would have a mapping to the OF. It nowhere says that RPL Instance ID also has a mapping to metrics in use.

>From Section 3.2.1 of draft-ietf-roll-rpl:

   The Objective Function (OF) defines how RPL nodes select and optimize
   routes within a RPL Instance.  The OF is identified by an Objective
   Code Point (OCP) within the DIO Configuration option.  An OF defines
   how nodes translate one or more metrics and constraints, which are
   themselves defined in [I-D.ietf-roll-routing-metrics], into a value
   called Rank, which approximates the node's distance from a DODAG
   root.  An OF also defines how nodes select parents.  Further details
   may be found in Section 14, [I-D.ietf-roll-routing-metrics],
   [I-D.ietf-roll-of0], and related companion specifications.

>As you state, RPL Instance maps to OF which, from the cited text, maps to metrics and route selection.  By transitivity, RPL Instance ID does map to metrics and how routes are formed.

The text you quoted no where says that an OF maps to particular metric. OF0 is metrics-independent. OF1 (draft-ietf-roll-minrank-hysteresis-of-04) applies to any additive metric. No RPL doc says that, for a particular LLN, a particular OF maps to a particular metric only. 

I think the following text clearly specifies what an RPL Instance is. Also, this text clearly says that an RPL Instance ID maps to a particular OF:

rpl-19 section 3.1.2:
      A RPLInstanceID identifies a set of
      one or more Destination Oriented DAGs (DODAGs).  A network may
      have multiple RPLInstanceIDs, each of which defines an independent
      set of DODAGs, which may be optimized for different Objective
      Functions (OFs) and/or applications.  The set of DODAGs identified
      by a RPLInstanceID is called a RPL Instance.  All DODAGs in the
      same RPL Instance use the same OF.

This definition says an RPLInstanceID identifies a set of DAGs with a common OF. No more and no less. A particular LLN may choose to map an OF to a particular metric but there is no such requirement as per RPL specs.
 
>> RPL Instance is the top level identifier of the DAGs that can be used to forward the packet. It also maps to a particular OF. In my opinion and as per RPL spec, RPL instance has no other significance.

>See above.  RPL Instance does map to metrics.

It need not.

>The definition I proposed was simply a collection of routers running RPL under the same administrative domain.  As mentioned above, that does not mean that every router on an interface belongs to a RPL routing domain.

I think the definition you provided is sufficient. An RPL domain is a collection of routers running RPL under the same administrative domain. Each router in the RPL domain needs to classify all its interfaces regarding whether they belong to the RPL domain or not.

A packet can be assumed to be coming from a router in the RPL domain if it carries an SRH.

Thanks
Mukul
 

From jonhui@cisco.com  Thu Dec 22 10:02:29 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 1959B21F84CE; Thu, 22 Dec 2011 10:02:29 -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 IpcuwoHl+aAA; Thu, 22 Dec 2011 10:02:28 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 829DA21F84CD; Thu, 22 Dec 2011 10:02:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=4452; q=dns/txt; s=iport; t=1324576948; x=1325786548; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Rk6oJcPLieem4HkndKo6KGDOLHjm5a1wk2lVuo9vPhM=; b=k4ocyQ7V+5Azk3lx28eSteR3V3bZ9t8W1RqJ666znkcEY61YKZHVj9uA rMMJeCGG0o1W4EcXpNZLwdZxlEqA0niAZtaa61TQX8lfOt36Iz3uArb18 uvuG3As8mGTdQpJ8cWHtHtV7IaHMfu0eWtKGbKpSf4QfX1jUXfIZZwrHv Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EABZw806rRDoG/2dsb2JhbABDDqwfgQWBcgEBAQMBEgEnLRIFCwtGVwY1h1iZCAGeKYssYwSIN4xKkXtY
X-IronPort-AV: E=Sophos;i="4.71,394,1320624000"; d="scan'208";a="22147265"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 22 Dec 2011 18:02:28 +0000
Received: from dhcp-128-107-155-213.cisco.com (dhcp-128-107-155-213.cisco.com [128.107.155.213]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pBMI2SVe000675; Thu, 22 Dec 2011 18:02:28 GMT
Subject: Re: draft-ietf-6man-rpl-routing-header-07
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <1033338721.734443.1324574682571.JavaMail.root@mail17.pantherlink.uwm.edu>
Date: Thu, 22 Dec 2011 10:02:29 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6EF9DCC-5743-41FF-BEF5-5AA7C6C27BA9@cisco.com>
References: <1033338721.734443.1324574682571.JavaMail.root@mail17.pantherlink.uwm.edu>
To: Mukul Goyal <mukul@uwm.edu>
X-Mailer: Apple Mail (2.1084)
Cc: roll <roll@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, 22 Dec 2011 18:02:29 -0000

On Dec 22, 2011, at 9:24 AM, Mukul Goyal wrote:

>> Again, just because you received a message on an interface for which =
you've enabled RPL doesn't mean you know the message came from a router =
that is within the same RPL routing domain.  A router not running RPL =
could have sent you that message.
>=20
> A router not running RPL could have sent me a message carrying SRH?

Sure.  It could be a host as well.  Part of limiting the scope is to =
limit the scope of an attack.  See the Security Considerations.

>> =46rom Section 3.2.1 of draft-ietf-roll-rpl:
>=20
>   The Objective Function (OF) defines how RPL nodes select and =
optimize
>   routes within a RPL Instance.  The OF is identified by an Objective
>   Code Point (OCP) within the DIO Configuration option.  An OF defines
>   how nodes translate one or more metrics and constraints, which are
>   themselves defined in [I-D.ietf-roll-routing-metrics], into a value
>   called Rank, which approximates the node's distance from a DODAG
>   root.  An OF also defines how nodes select parents.  Further details
>   may be found in Section 14, [I-D.ietf-roll-routing-metrics],
>   [I-D.ietf-roll-of0], and related companion specifications.
>=20
>> As you state, RPL Instance maps to OF which, from the cited text, =
maps to metrics and route selection.  By transitivity, RPL Instance ID =
does map to metrics and how routes are formed.
>=20
> The text you quoted no where says that an OF maps to particular =
metric. OF0 is metrics-independent. OF1 =
(draft-ietf-roll-minrank-hysteresis-of-04) applies to any additive =
metric. No RPL doc says that, for a particular LLN, a particular OF maps =
to a particular metric only.=20

Incorrect.  =46rom draft-ietf-roll-routing-metrics-19:

   The set of routing metrics and constraints used by an RPL deployment
   is signaled along the DAG that is built according to the Objective
   Function (rules governing how to build a DAG) and the routing metrics
   and constraints are advertised in the DAG Information Option (DIO)
   message specified in [I-D.ietf-roll-rpl].

In other words, the combination of the OCP and the metrics identified by =
the DODAG Root describes how to optimize the routes.  In the case of =
OF0, the metric is the Rank itself.

> I think the following text clearly specifies what an RPL Instance is. =
Also, this text clearly says that an RPL Instance ID maps to a =
particular OF:
>=20
> rpl-19 section 3.1.2:
>      A RPLInstanceID identifies a set of
>      one or more Destination Oriented DAGs (DODAGs).  A network may
>      have multiple RPLInstanceIDs, each of which defines an =
independent
>      set of DODAGs, which may be optimized for different Objective
>      Functions (OFs) and/or applications.  The set of DODAGs =
identified
>      by a RPLInstanceID is called a RPL Instance.  All DODAGs in the
>      same RPL Instance use the same OF.
>=20
> This definition says an RPLInstanceID identifies a set of DAGs with a =
common OF. No more and no less. A particular LLN may choose to map an OF =
to a particular metric but there is no such requirement as per RPL =
specs.

You never answered my question.  Why bother having a RPL Instance ID if =
you don't care how the routes are optimized?  Why bother maintaining =
multiple paths optimized using different OFs and/or metrics?

>>> RPL Instance is the top level identifier of the DAGs that can be =
used to forward the packet. It also maps to a particular OF. In my =
opinion and as per RPL spec, RPL instance has no other significance.
>=20
>> See above.  RPL Instance does map to metrics.
>=20
> It need not.

You are incorrect again!

>> The definition I proposed was simply a collection of routers running =
RPL under the same administrative domain.  As mentioned above, that does =
not mean that every router on an interface belongs to a RPL routing =
domain.
>=20
> I think the definition you provided is sufficient. An RPL domain is a =
collection of routers running RPL under the same administrative domain. =
Each router in the RPL domain needs to classify all its interfaces =
regarding whether they belong to the RPL domain or not.
>=20
> A packet can be assumed to be coming from a router in the RPL domain =
if it carries an SRH.


Nope.  As I stated before, that would invalidate the Security =
Considerations section.

--
Jonathan Hui


From hart@ntp.org  Thu Dec 22 21:58:43 2011
Return-Path: <hart@ntp.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 886B921F85F1 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 21:58:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 f63aQq+edMhF for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 21:58:43 -0800 (PST)
Received: from mail2.ntp.org (mail2.ntp.org [IPv6:2001:4f8:fff7:1::6]) by ietfa.amsl.com (Postfix) with ESMTP id 1472421F85EF for <ipv6@ietf.org>; Thu, 22 Dec 2011 21:58:42 -0800 (PST)
Received: from mail-ey0-f172.google.com ([209.85.215.172]) by mail2.ntp.org with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76 (FreeBSD)) (envelope-from <hart@ntp.org>) id 1Rdy9F-0000d7-RR for ipv6@ietf.org; Fri, 23 Dec 2011 05:58:40 +0000
Received: by eaak10 with SMTP id k10so2223066eaa.31 for <ipv6@ietf.org>; Thu, 22 Dec 2011 21:58:22 -0800 (PST)
Received: by 10.204.38.16 with SMTP id z16mr3977151bkd.66.1324619902502; Thu, 22 Dec 2011 21:58:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.204.229.3 with HTTP; Thu, 22 Dec 2011 21:57:59 -0800 (PST)
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D026F16A9@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <Acy+tsYFqXqC79VBScCLCMBty+1W/A==> <7C362EEF9C7896468B36C9B79200D8350D026F16A9@INBANSXCHMBSA1.in.alcatel-lucent.com>
From: Dave Hart <hart@ntp.org>
Date: Fri, 23 Dec 2011 05:57:59 +0000
Message-ID: <CAMbSiYA6v7ejJ-=ePLtSi_N2Tgc_qWkAuc_tZr0g-3q8-wPoqQ@mail.gmail.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
X-SA-Exim-Connect-IP: 209.85.215.172
X-SA-Exim-Rcpt-To: ipv6@ietf.org
X-SA-Exim-Mail-From: hart@ntp.org
Subject: Re: [TICTOC] IPv6 Router Advertisement Option for NTP Server Configuration
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail2.ntp.org)
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: Fri, 23 Dec 2011 05:58:43 -0000

I have feedback that is generic to both autoconfiguration approaches
to distributing NTP configuration information -- RA as well as DHCPv6.
 Regardless of means, I'm suspicious of standardizing a way to
distribute multicast NTP server addresses without also standardizing
distribution of NTP symmetric authentication parameters needed to
secure broadcast/multicast NTP.  If providing such authentication
parameters (key number/id, digest algorithm, and shared secret) is
deemed too cumbersome, I suggest removing support for distributing
multicast NTP server information is preferable to providing means
which enable only ill-advised configurations that blindly accept
unauthenticated multicast NTP service.

Similarly, I would prefer to see broader support for other NTP
configurations.  If NTP symmetric authentication parameters are
provided for, NTP's manycast mode should be configurable as well.
Clients solicit manycast servers via authenticated multicast NTP mode
3 (client) requests destined to a multicast group address.  Manycast
servers respond via unicast mode 4 (server) responses, which triggers
manycast clients to spin authenticated unicast associations.  The
prime advantage over multicast service is the unicast operation with
discovered servers, which allows ongoing round-trip delay measurement
as compared to one-time multicast delay calibration at ntpd startup.
In short, manycast operation provides the automatic server discovery
benefit of multicast NTP without the degraded quality of time service
inherent in a one-to-many multicast/broadcast NTP configuration.

Cheers,
Dave Hart

From dougb@dougbarton.us  Thu Dec 22 23:57:03 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 031AC21F8492 for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 23:57:03 -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 qGuVE4MuKBvp for <ipv6@ietfa.amsl.com>; Thu, 22 Dec 2011 23:57:02 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id D98D321F841C for <ipv6@ietf.org>; Thu, 22 Dec 2011 23:57:01 -0800 (PST)
Received: (qmail 16553 invoked by uid 399); 23 Dec 2011 07:57:00 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Dec 2011 07:57:00 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4EF4344B.6040504@dougbarton.us>
Date: Thu, 22 Dec 2011 23:56:59 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: IPv6 Router Advertisement Option for Foobar Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <4EF2373B.6060905@gmail.com> <4EF24007.3030300@dougbarton.us> <4EF258A5.1040106@gmail.com>
In-Reply-To: <4EF258A5.1040106@gmail.com>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Fri, 23 Dec 2011 07:57:03 -0000

Yeah, and/or the recently approved multicast DNS draft. Personally I
like DHCP, but I'm not saying it's the only answer.

What I *am* saying is that extending RA is always the *wrong* answer.


Doug


On 12/21/2011 14:07, Brian E Carpenter wrote:
> Doug,
> 
> Excuse front posting, but I think there's another aspect to this,
> which is that the Service Location Protocol (RFC 2165) was
> standardised in 1997, when DHCP was still a newcomer, and it
> offers a multicast service discovery mechanism that doesn't
> need *any* central server (the SLP Directory Agent is optional).
> 
> A combination of basic RA plus directory-less SLP would be
> necessary and sufficient for small unmanaged networks, I think.
> 
> Regards
>    Brian
> 
> On 2011-12-22 09:22, Doug Barton wrote:
>> On 12/21/2011 11:44 AM, Brian E Carpenter wrote:
>>> On 2011-12-22 07:37, Doug Barton wrote:
>>>> On 12/19/2011 5:24 PM, Bhatia, Manav (Manav) wrote:
>>>>> Hi,
>>>>>
>>>>> We have posted a new draft that extends Router Advertisements to
>>>>> include information about the one or more NTP servers present in the
>>>>> network. This is useful where the delays in acquiring server
>>>>> addresses and communicating with the servers are critical (mobile
>>>>> environment for example).
>>>> Sort of surprised that no one else has responded so far, but I'll bite.
>>>> Quite simply, "no." Slightly less simply, "use DHCP since that's what
>>>> it's for."
>>>>
>>>> I'm happy to expound on the evils of "camel's nose already too far under
>>>> the tent," etc.
>>> There is of course a broader issue here, illustrated by the endless loop
>>> over in MIF about draft-ietf-mif-dhcpv6-route-option.
>>
>> ... or the endless loop of "we need DNS info in RA" until it finally got
>> adopted.
>>
>>> What is the intended scope of the RA mechanism?
>>>
>>> I was a strong proponent of standardising the DNS server option
>>> in RA, because it is an absolute requirement for even the most
>>> minimal host to get onto the Internet. But I am also a strong
>>> proponent of -dhcpv6-route-option, because it seems clear that
>>> more complex environments will inevitably require the extensibility
>>> that comes with DHCPv6.
>>
>> So, expound it is. :)
>>
>> When I first got interested in IPv6 protocol work back in 2000 or so I
>> was curious about this "RA" thing. Given that DHCP was already widely
>> deployed and successful in the IPv4 world I wondered why such a thing
>> was necessary/useful.* I was told at the time that a key feature of IPv6
>> was going to be the ability to bring "dumb" devices onto the network
>> that only needed to be addressable (light switches were a commonly used
>> example). The RA mechanism was perfect for this as it involved no state,
>> and anything that needed to be even slightly "smart" would use DHCPv6.
>> As much as I was dubious about it at the time, I accepted that
>> explanation at face value.
>>
>> Then someone realized that RA was great for getting a thing on the
>> network, but at that point the thing wasn't really all that useful. So
>> the logical next step was to extend RA to allow for sending out
>> resolving DNS info. The point I (and others) tried to make at the time
>> went something like this (I will use the first person so as to take 100%
>> of the blame, but that's not meant to exclude the others who made
>> significant contributions to the line of argument that I support):
>>
>> Me:	Um, if it's not a dumb device, why can't it use DHCP?
>> Them:	DHCP is too heavy-weight. We just need one more piece of
>> information provided by RA and then we'll have a fully-functional client
>> without the need for DHCP at all, isn't that great!
>> Me:	Um, well, I see what you're saying, but doesn't that sort of open
>> the door for adding more things down the road? And as both a system
>> administrator and an operating system developer I have serious concerns
>> about having to support 2 different host configuration protocols. It
>> will inevitably lead to problems, and ...
>> Them:	No no no, don't be silly! We JUST want to add this ONE little
>> thing. After that we promise, no more!
>> Me:	I just think it's a bad precedent. Besides, adding only the
>> nameserver info isn't enough, you also need the domain and/or search
>> string to make it useful.
>> Them:	*snap* Oh, right! Thanks for pointing that out. Ok, we'll add that
>> too, but after that, NO MORE. I PROMISE!
>> Me:	Um ....
>>
>>> I think we need a standards track document that defines the maximum
>>> scope of the RA mechanism once and for all. Personally I would
>>> probably freeze it where it is today, but we need a reasoned
>>> architectural decision about this.
>>
>> Given that using RA for DNS info isn't widely deployed yet, I would vote
>> for rolling RA back to its originally designed purpose, THEN saying "no
>> more, really, I mean it." But I doubt that either of those options will
>> be successful. I would be ecstatic to be proven wrong however.
>>
>>
>> Doug
>>
>> * I realize that when RA was first conceived DHCP wasn't that well
>> established yet, and furthermore I understand that some people disagree
>> on how well established it was even as late as 2000. My experience at
>> the time was that DHCP was already widely used in both the SOHO and
>> large enterprise markets. In any case I don't think anyone can argue
>> that in the last 11 years it hasn't been firmly established. Failure to
>> recognize why DHCP is popular, and why RA isn't, is a bug in the
>> protocol development process.
>>



-- 

		[^L]

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


From dougb@dougbarton.us  Fri Dec 23 00:20:01 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 164D41F0C3F for <ipv6@ietfa.amsl.com>; Fri, 23 Dec 2011 00:20:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, GB_FREEBONUS=1, 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 KlC8NtACyT6C for <ipv6@ietfa.amsl.com>; Fri, 23 Dec 2011 00:20:00 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2BBD41F0C3B for <ipv6@ietf.org>; Fri, 23 Dec 2011 00:19:59 -0800 (PST)
Received: (qmail 29104 invoked by uid 399); 23 Dec 2011 08:19:54 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Dec 2011 08:19:54 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4EF439A9.4070502@dougbarton.us>
Date: Fri, 23 Dec 2011 00:19:53 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Fri, 23 Dec 2011 08:20:01 -0000

On 12/21/2011 15:52, Bhatia, Manav (Manav) wrote:
> Hi Doug,
> 
>> 
>> Sort of surprised that no one else has responded so far, but I'll
>> bite. Quite simply, "no." Slightly less simply, "use DHCP since 
>> that's what it's for."
>> 
> 
> I wish it were this simple.

Well good news for you then, it IS that simple. :)

> Different operators have different requirements and preferences based
> on their environments. I have seen deployments where SLAAC is much
> more useful than DHCPv6. I've seen deployments where DHCPv6 is
> needed. So both have a place and we should let the operators decide
> what they want to use.

Eloquent words, but they miss a central point. There is a huge cost
involved in implementing the same configuration information through
different mechanisms. Over strenuous objections DNS information was
added to RA and we're still dealing with the fallout. There are also
costs in the development and deployment areas. It's not like we can just
wave a magic wand and make all possibilities available to all the
players without any work involved.

> Environments with 4 to 20 devices in them
> (small businesses) may not want the complexity of setting up a
> central server. Those environments are probably more suited for
> SLAAC.

Show me the small business that doesn't already have a DHCP server baked
into their router/toaster, that doesn't "just work" with near-zero human
interaction.

> We have heard customers asking SLAAC to be extended to support NTP,
> "boot-file", "next-server" and a few other things that are currently
> only available with DHCP.

I'm asking for a pony. Hook me up. :)

> Currently, operators need to use both SLAAC and DHCP to run their
> networks. This is far from ideal.

This much I agree with.

> Far better for organizations to
> look at 2 complete solutions and pick the solution that works best
> for them in their environment.

Wrong answer. The right answer is for DHCPv6 to be a superset of RA so
that organizations that need more than RA provides only have to run
DHCP. As a free bonus, it's FAR easier to add one knob (default route)
to DHCPv6 than it is to add all features to RA. Extra bonus, the only
hurdles are political, not technical.

> Today, we can get NTP server information only with DHCP. DHCP only
> works after RAs have been processed. In some environments (mobile
> IPv6) delays in acquiring NTP and other servers information is
> critical and waiting for DHCP to come up is NOT an ideal solution.

See above.


Doug

-- 

		[^L]

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


From internet-drafts@ietf.org  Fri Dec 23 00:43:23 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 9201121F8B0B; Fri, 23 Dec 2011 00:43:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.453
X-Spam-Level: 
X-Spam-Status: No, score=-102.453 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, SARE_SUB_OBFU_Z=0.259, 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 TaT-Z6vmG-W7; Fri, 23 Dec 2011 00:43:23 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3702121F8B04; Fri, 23 Dec 2011 00:43:23 -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-udpzero-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111223084323.31710.23525.idtracker@ietfa.amsl.com>
Date: Fri, 23 Dec 2011 00:43:23 -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: Fri, 23 Dec 2011 08:43:23 -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           : IPv6 UDP Checksum Considerations
	Author(s)       : Godred Fairhurst
                          Magnus Westerlund
	Filename        : draft-ietf-6man-udpzero-05.txt
	Pages           : 34
	Date            : 2011-12-23

   This document examines the role of the UDP transport checksum when
   used with IPv6, as defined in RFC2460.  It presents a summary of the
   trade-offs for evaluating the safety of updating RFC 2460 to permit
   an IPv6 UDP endpoint to use a zero value in the checksum field as an
   indication that no checksum is present.  This method is compared with
   some other possibilities.  The document also describes the issues and
   design principles that need to be considered when UDP is used with
   IPv6 to support tunnel encapsulations.  It concludes that UDP with a
   zero checksum in IPv6 can safely be used for this purpose, provided
   that this usage is governed by a set of constraints.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-udpzero-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-udpzero-05.txt


From fweimer@bfk.de  Fri Dec 23 02:46:50 2011
Return-Path: <fweimer@bfk.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 4A94321F8B2F for <ipv6@ietfa.amsl.com>; Fri, 23 Dec 2011 02:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level: 
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[AWL=0.629,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 A38X5IiISzwh for <ipv6@ietfa.amsl.com>; Fri, 23 Dec 2011 02:46:49 -0800 (PST)
Received: from mx01.bfk.de (mx01.bfk.de [193.227.124.2]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC1721F8B2B for <ipv6@ietf.org>; Fri, 23 Dec 2011 02:46:49 -0800 (PST)
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1Re2eF-00065I-2c; Fri, 23 Dec 2011 10:46:47 +0000
Received: by bfk.de with local id 1Re2eE-00038Z-To; Fri, 23 Dec 2011 10:46:46 +0000
From: Florian Weimer <fweimer@bfk.de>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com> <82fwgfk1ev.fsf@mid.bfk.de> <4EF0FFDF.6010703@gont.com.ar>
Date: Fri, 23 Dec 2011 10:46:46 +0000
Message-ID: <82d3bfbm5l.fsf@mid.bfk.de>
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
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, 23 Dec 2011 10:46:50 -0000

* Fernando Gont:

> Hello, Florian,
>
> On 12/20/2011 07:00 AM, Florian Weimer wrote:
>>> ---- cut here ----
>>>    IPv6 allows packets to contain a Fragment Header, without the packet
>>>    being actually fragmented into multiple pieces.  Such packets
>>>    typically result from hosts that have received an ICMPv6 "Packet Too
>>>    Big" error message that advertises a "Next-Hop MTU" smaller than 1280
>>>    bytes, and are currently processed by hosts as "fragmented
>>>    traffic".
>>=20
>> Does such traffic actually occur in the wild, or would it only be used
>> in attacks?
>
> They have been seen in the wild.

Yuck.

> That aside, I don't know whether e.g. NAT64 or the like used this
> (.e.g, whether they are used for transition technologies as envisioned
> in RFC 2460). However, it might also be the case that such "atomic
> fragments" are generated when communicating through networks that do
> not really have a MTU >=3D 1280. In such scenarios there might be some
> for of gateway that sends the ICMPv6 PTB advertising a Next-Hop MTU
> smaller than 1280, thus resulting in atomic fragments (such that it's
> easier for the "gateway" to fragment the IPv6 packets).

Yes, this seems a plausible explanation.  I wouldn't consider this
actual use, rather network misconfiguration.  In my opinion, we need
more evidence that these fragments actually serve a useful purpose.

> That aside, there's the proposal by Mark Andrews which would add yet
> another use case for these atomic fragments.

Not really.  It's a workaround so that stateless IPv6 services are
possible, despite this protocol weiredness.

>> Per previous WG discussion, when reassembling such atomic fragments,

I think I meant to write "any fragments".

>> IPv6 implementations must ignore the upper 16 bits of the fragment ID
>> (otherwise the stateless v4/v6 gateways won't work).  Clearly, this is
>> not desirable.
>
> I may be missing something, but: when sending from the v6 side to the v4
> side, we can probably assume that only the low order 16 bits of the
> Fragment Identification field are used (whether you set the rest of the
> bits or not, it doesn't matter -- particularly if the Fragment
> Identification for each destination is a linear function (as e.g. in the
> algorithm proposed in the I-D)). That is, you don't really need to do
> anything special with the high order bits.

Actually, atomic fragments aren't the problem, but the technology that
serves as a justification for them.  If there are sub-1280 links which
require network fragmentation and which fail to preserve the entire
fragment ID, this happen to a packet which has already been fragmented
by the sending host: One fragment is delivered over a regular IPv6 link
and not fragmented further.  Another fragment is sent over a different
link involving some v4 transition technology, causing further
fragmentation and loss of the upper 16 bit of the fragment id.  The
receiving node can reassemble the original packet only if it disregards
the upper 16 bits in all those fragments.

--=20
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstra=DFe 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

From robert.cragie@gridmerge.com  Fri Dec 23 10:07:12 2011
Return-Path: <robert.cragie@gridmerge.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 3EF8E21F85F2; Fri, 23 Dec 2011 10:07:12 -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 qhxRWAhg+x6C; Fri, 23 Dec 2011 10:07:11 -0800 (PST)
Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by ietfa.amsl.com (Postfix) with ESMTP id EF7D121F85EF; Fri, 23 Dec 2011 10:07:10 -0800 (PST)
Received: from client-82-31-21-125.midd.adsl.virginmedia.com ([82.31.21.125] helo=[192.168.0.2]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) id 1Re9WG-0004Sf-7W; Fri, 23 Dec 2011 18:07:00 +0000
Message-ID: <4EF4C358.60103@gridmerge.com>
Date: Fri, 23 Dec 2011 18:07:20 +0000
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Jonathan Hui <jonhui@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
References: <1033338721.734443.1324574682571.JavaMail.root@mail17.pantherlink.uwm.edu> <B6EF9DCC-5743-41FF-BEF5-5AA7C6C27BA9@cisco.com>
In-Reply-To: <B6EF9DCC-5743-41FF-BEF5-5AA7C6C27BA9@cisco.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040305020204050403030002"
X-Authenticated-As: robert.cragie@gridmerge.com
Cc: ipv6@ietf.org, roll <roll@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.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, 23 Dec 2011 18:07:12 -0000

This is a cryptographically signed message in MIME format.

--------------ms040305020204050403030002
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi Jonathan,

Some comments and questions below.

Robert

On 22/12/2011 6:02 PM, Jonathan Hui wrote:
> On Dec 22, 2011, at 9:24 AM, Mukul Goyal wrote:
>
>>> Again, just because you received a message on an interface for which =
you've enabled RPL doesn't mean you know the message came from a router t=
hat is within the same RPL routing domain.  A router not running RPL coul=
d have sent you that message.
>> A router not running RPL could have sent me a message carrying SRH?
> Sure.  It could be a host as well.  Part of limiting the scope is to li=
mit the scope of an attack.  See the Security Considerations.
<RCC>I'm not getting this. The use of SRH is for non-storing mode,=20
correct? And only for non-storing mode? There is no current definition=20
of partial storing mode and stored mode doesn't need SRH. So the source=20
routes are created on the DAG root based on transit information obtained =

by DAOs. How can any router outside of the RPL domain initiate a=20
source-routed message to a node in the RPL domain? It would be tunneled=20
at the point it got to the DAG root. Therefore, by implication, normally =

the source and destination of the message with SRH must be in the RPL=20
domain. So we need to check for exceptions - surely the rules Mukul=20
stated are sufficient?</RCC>
>
>>>  From Section 3.2.1 of draft-ietf-roll-rpl:
>>    The Objective Function (OF) defines how RPL nodes select and optimi=
ze
>>    routes within a RPL Instance.  The OF is identified by an Objective=

>>    Code Point (OCP) within the DIO Configuration option.  An OF define=
s
>>    how nodes translate one or more metrics and constraints, which are
>>    themselves defined in [I-D.ietf-roll-routing-metrics], into a value=

>>    called Rank, which approximates the node's distance from a DODAG
>>    root.  An OF also defines how nodes select parents.  Further detail=
s
>>    may be found in Section 14, [I-D.ietf-roll-routing-metrics],
>>    [I-D.ietf-roll-of0], and related companion specifications.
>>
>>> As you state, RPL Instance maps to OF which, from the cited text, map=
s to metrics and route selection.  By transitivity, RPL Instance ID does =
map to metrics and how routes are formed.
>> The text you quoted no where says that an OF maps to particular metric=
=2E OF0 is metrics-independent. OF1 (draft-ietf-roll-minrank-hysteresis-o=
f-04) applies to any additive metric. No RPL doc says that, for a particu=
lar LLN, a particular OF maps to a particular metric only.
> Incorrect.  From draft-ietf-roll-routing-metrics-19:
>
>     The set of routing metrics and constraints used by an RPL deploymen=
t
>     is signaled along the DAG that is built according to the Objective
>     Function (rules governing how to build a DAG) and the routing metri=
cs
>     and constraints are advertised in the DAG Information Option (DIO)
>     message specified in [I-D.ietf-roll-rpl].
>
> In other words, the combination of the OCP and the metrics identified b=
y the DODAG Root describes how to optimize the routes.  In the case of OF=
0, the metric is the Rank itself.
>
>> I think the following text clearly specifies what an RPL Instance is. =
Also, this text clearly says that an RPL Instance ID maps to a particular=
 OF:
>>
>> rpl-19 section 3.1.2:
>>       A RPLInstanceID identifies a set of
>>       one or more Destination Oriented DAGs (DODAGs).  A network may
>>       have multiple RPLInstanceIDs, each of which defines an independe=
nt
>>       set of DODAGs, which may be optimized for different Objective
>>       Functions (OFs) and/or applications.  The set of DODAGs identifi=
ed
>>       by a RPLInstanceID is called a RPL Instance.  All DODAGs in the
>>       same RPL Instance use the same OF.
>>
>> This definition says an RPLInstanceID identifies a set of DAGs with a =
common OF. No more and no less. A particular LLN may choose to map an OF =
to a particular metric but there is no such requirement as per RPL specs.=

> You never answered my question.  Why bother having a RPL Instance ID if=
 you don't care how the routes are optimized?  Why bother maintaining mul=
tiple paths optimized using different OFs and/or metrics?
<RCC>
The source route is determined by the transit options, nothing else.=20
There is no processing done at each hop - it simply forwards it to the=20
next based on what's in the SRH. So no need for RPL instance (or domain) =

there. You could potentially build up multiple tables for each RPL=20
instance but you would just formulate a different SRH based on which=20
table you picked. When it gets to the destination, why would the=20
OF/metric of whatever DAG it happen to transit through have any bearing=20
on where it is subsequently going? I ask this because there is no=20
further information based on the domain it has just gone through. The=20
message originator would not even be aware of any subsequent RPL domains =

beyond itself; it is bounded by the root and the leaf routers. Unless=20
the destination is on path between the DAG root and a leaf router, an=20
SRH will always go between the DAG root and a leaf router. I find the=20
concept of a partial SRH quite baffling even if it is for the purposes=20
of traceroute - even then at the point it emerges someway down the path, =

it will return a time exceeded error.

So basically, I am still failing to understand the need to carry RPL=20
instance in the SRH for non-storing mode. I could see its use in partial =

storing mode whereby SRH carries it part of the way and the stored=20
information on subsequent routers the rest, but in this case surely you=20
would put a RPL option in the inner packet and tunnel? So when it=20
emerges from the source-routed tunnel, it is ready to be forwarded using =

RPL.
<RCC>
>
>>>> RPL Instance is the top level identifier of the DAGs that can be use=
d to forward the packet. It also maps to a particular OF. In my opinion a=
nd as per RPL spec, RPL instance has no other significance.
>>> See above.  RPL Instance does map to metrics.
>> It need not.
> You are incorrect again!
>
>>> The definition I proposed was simply a collection of routers running =
RPL under the same administrative domain.  As mentioned above, that does =
not mean that every router on an interface belongs to a RPL routing domai=
n.
>> I think the definition you provided is sufficient. An RPL domain is a =
collection of routers running RPL under the same administrative domain. E=
ach router in the RPL domain needs to classify all its interfaces regardi=
ng whether they belong to the RPL domain or not.
>>
>> A packet can be assumed to be coming from a router in the RPL domain i=
f it carries an SRH.
>
> Nope.  As I stated before, that would invalidate the Security Considera=
tions section.
<RCC>I agree with Mukul: in normal circumstances a packet with an SRH=20
will come from a router in the RPL domain and the rules Mukul stated can =

be used to make sure it doesn't go beyond.</RCC>
>
> --
> Jonathan Hui
>
>


--------------ms040305020204050403030002
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIP3jCC
BIowggNyoAMCAQICECf06hH0eobEbp27bqkXBwcwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UE
BhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5h
bCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0w
NTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMC
VVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5l
dHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVN
NRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQy
lbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXq
vgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6
hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu
9mIwFIws6wIDAQABo4HhMIHeMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0G
A1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/
BAUwAwEB/zB7BgNVHR8EdDByMDigNqA0hjJodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9BZGRU
cnVzdEV4dGVybmFsQ0FSb290LmNybDA2oDSgMoYwaHR0cDovL2NybC5jb21vZG8ubmV0L0Fk
ZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQAZ2IkRbyispgCi
54fBm5AD236hEv0e8+LwAamUVEJrmgnEoG3XkJIEA2Z5Q3H8+G+v23ZF4jcaPd3kWQR4rBz0
g0bzes9bhHIt5UbBuhgRKfPLSXmHPLptBZ2kbWhPrXIUNqi5sf2/z3/wpGqUNVCPz4FtVbHd
WTBK322gnGQfSXzvNrv042n0+DmPWq1LhTq3Du3Tzw1EovsEv+QvcI4l+1pUBrPQxLxtjftz
Mizpm4QkLdZ/kXpoAlAfDj9N6cz1u2fo3BwuO/xOzf4CjuOoEwqlJkRl6RDyTVKnrtw+ymsy
XEFs/vVdoOr/0fqbhlhtPZZH5f4ulQTCAMyOofK7MIIFGjCCBAKgAwIBAgIQbRnqpxlPajMi
5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcw
FQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3Jr
MSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VS
Rmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMTA0MjgwMDAwMDBa
Fw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tXmNReL4uk4UDIo1NY
X2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vxaa7lIBvky2NeYMqi
QfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrlVICv2HEKHTcKAlBT
bJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+OsvxQ7sCVxaD30D9YX
WEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hRmWONGoulzEKbm30i
Y9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0jBBgwFoAUiYJnfcSd
JnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8ecV7MA4GA1UdDwEB
/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYEVR0gADBYBgNVHR8E
UTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVTRVJGaXJzdC1DbGll
bnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRoMGYwPQYIKwYBBQUH
MAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENsaWVudF9DQS5jcnQw
JQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQEFBQAD
ggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtzbj7pJnzmTJjBMCjf
y/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqTecr+4pEeVnSy+I3T
4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPNM1+b0L1garM7/vrU
yTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZhtZdVwcbpzC+S0lE
uJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/bucwggYuMIIFFqAD
AgECAhBcMVDbxC2oy5hyHl/adO9mMA0GCSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEb
MBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQK
ExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDkwMjAwMDAwMFoXDTE0MDkwMTIzNTk1
OVowggE3MQswCQYDVQQGEwJHQjEQMA4GA1UEERMHV0Y0IDRXQTEXMBUGA1UECBMOV2VzdCBZ
b3Jrc2hpcmUxEjAQBgNVBAcTCVdha2VmaWVsZDEUMBIGA1UECRMLR3JhbmdlIE1vb3IxHzAd
BgNVBAkTFjg5IEdyZWVuZmllbGQgQ3Jlc2NlbnQxFzAVBgNVBAoTDkdyaWRtZXJnZSBMdGQu
MTQwMgYDVQQLEytJc3N1ZWQgdGhyb3VnaCBHcmlkbWVyZ2UgTHRkLiBFLVBLSSBNYW5hZ2Vy
MR8wHQYDVQQLExZDb3Jwb3JhdGUgU2VjdXJlIEVtYWlsMRYwFAYDVQQDEw1Sb2JlcnQgQ3Jh
Z2llMSowKAYJKoZIhvcNAQkBFhtyb2JlcnQuY3JhZ2llQGdyaWRtZXJnZS5jb20wggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxOGq8t5ZTVDVkmadv7ZRBLA5ApaiTcDUzCTn
zYB2/BoBDIEWWI/InSRcmq3A0Ghm+T7dYmvRADllGv4nTHexdWlzFp2iM/Yc3PLWCyAO0gYb
yW2hTi+ZfUDwFOU4hRP4+Dyn9tKu7FXS/PQJHyGjaGxHRmLm9T6tAo2ZuC59uRaGVCcwRiOS
d6axwtB/DVhnP3S1rrt2g0O6MXLr5fojToemO52AxjHxt2w1LnFUUXC4EDV6o1Ctr7EvOEI5
5f088H/Mrryp02GueLdY9gb0SFK3gPOT7EjP2GPvCtRkhVcNM+xjyptRIFWnCbMjmUIc+DO6
sfU4rtbCCkNKyXmnAgMBAAGjggHVMIIB0TAfBgNVHSMEGDAWgBR6E04AdFvGeGNkJ8Ev4qBb
vHnFezAdBgNVHQ4EFgQUEI5c0f6UObxT2DLdvdtG+vG8qCswDgYDVR0PAQH/BAQDAgWgMAwG
A1UdEwEB/wQCMAAwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMEYGA1UdIAQ/MD0w
OwYMKwYBBAGyMQECAQMFMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5u
ZXQvQ1BTMFcGA1UdHwRQME4wTKBKoEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9E
T0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEB
BHwwejBSBggrBgEFBQcwAoZGaHR0cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50
QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDov
L29jc3AuY29tb2RvY2EuY29tMCYGA1UdEQQfMB2BG3JvYmVydC5jcmFnaWVAZ3JpZG1lcmdl
LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAPpv87QuQ9q+RHhmeirGDQB3szd24Obi7N+uVfh5y
CrnoJx3B37dNrLPsTB6PfTChUyZMqQD80pFoJ3TBUz3yx4X+hmNco7ujVIfbuKBGcZJaMKhZ
ex3AkZ9ltie9wgiGGzEmgI81t5JHsLQ8AUMqw/fGsnIwcyWMgmyhFtm79+dg3IVaH05d/t9g
k4aYoMoCFJptQZ+Fju6a9T139hOqjTZDpjMLt3jM80bVrvkC4dIRyF/oZ0qrJwbfwjnL2OUN
ph9eymhLc+VM0Ih5k41s5IxmB+2c0RUqr5JbK0WrIb/z53Cmb9rXYox7HknyIfBpQqP77Y7a
sAU2MMOpel4RijGCBAwwggQIAgEBMIGoMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3Jl
YXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0Eg
TGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2Vj
dXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMAkGBSsOAwIaBQCgggI4MBgGCSqGSIb3
DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTIyMzE4MDcyMFowIwYJKoZI
hvcNAQkEMRYEFN6S88g8va+wNVxO0JuyotsKD2ZTMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDCBuQYJKwYBBAGCNxAEMYGrMIGoMIGTMQswCQYDVQQGEwJH
QjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYD
VQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMIG7BgsqhkiG
9w0BCRACCzGBq6CBqDCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hl
c3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3
BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBD
QQIQXDFQ28QtqMuYch5f2nTvZjANBgkqhkiG9w0BAQEFAASCAQAGVrPUxKbMa9c0W15/C6oa
h6V9GsLv1y5QqZGZSKZeilxNTDiDT6j11fY4tITmbpZ4uNTRlCaFVWl4egV5tASF8Cms/Zf4
43b2IU75XFOWz5QbJHh872cN6BTgnWrWaqfKuywO0PqfxM6cCtgGmGwA0d+vQFVtjEVRSrsu
8u6XBcxdhPK5TPOTLVtWeYInAJ5Z/zhLhys3p4tyZq3XMwiOvqCIdn6l0btK/Ccm9WzUGYQW
Hhq7RTHktB1h4c6MtMiM1mQV/cZImyXtd7Ch5KBVsBycRWonlcKOnNQnCsWd7nbYQf3j0nDv
6x3VwPB18aR/ja6qEdg5yMWktAPVKjlsAAAAAAAA
--------------ms040305020204050403030002--

From prvs=331fbc5f4=mukul@uwm.edu  Fri Dec 23 10:33:07 2011
Return-Path: <prvs=331fbc5f4=mukul@uwm.edu>
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 5C0EF21F8A6F; Fri, 23 Dec 2011 10:33:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level: 
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=0.093,  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 fvxGcjY95oQM; Fri, 23 Dec 2011 10:33:06 -0800 (PST)
Received: from ip1mta.uwm.edu (ip1mta.uwm.edu [129.89.7.18]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9ED21F84E5; Fri, 23 Dec 2011 10:33:06 -0800 (PST)
Received: from localhost (HELO mta01.pantherlink.uwm.edu) ([127.0.0.1]) by ip1mta.uwm.edu with ESMTP; 23 Dec 2011 12:33:05 -0600
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta01.pantherlink.uwm.edu (Postfix) with ESMTP id ABE2FE6A75; Fri, 23 Dec 2011 12:33:05 -0600 (CST)
X-Virus-Scanned: amavisd-new at mta01.pantherlink.uwm.edu
Received: from mta01.pantherlink.uwm.edu ([127.0.0.1]) by localhost (mta01.pantherlink.uwm.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IxY0yX0P4JkT; Fri, 23 Dec 2011 12:33:04 -0600 (CST)
Received: from mail17.pantherlink.uwm.edu (mail17.pantherlink.uwm.edu [129.89.7.177]) by mta01.pantherlink.uwm.edu (Postfix) with ESMTP id 907C2E6A74; Fri, 23 Dec 2011 12:33:04 -0600 (CST)
Date: Fri, 23 Dec 2011 12:33:04 -0600 (CST)
From: Mukul Goyal <mukul@uwm.edu>
To: "Jonathan Hui (johui)" <johui@cisco.com>
Message-ID: <1431347815.744466.1324665184537.JavaMail.root@mail17.pantherlink.uwm.edu>
In-Reply-To: <ABAF5F0D-5D0C-4EF0-9315-201376731A65@cisco.com>
Subject: Re: draft-ietf-6man-rpl-routing-header-07
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [129.89.7.92]
X-Mailer: Zimbra 6.0.13_GA_2918 (ZimbraWebClient - IE8 (Win)/6.0.13_GA_2918)
X-Authenticated-User: mukul@uwm.edu
Cc: roll <roll@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, 23 Dec 2011 18:33:07 -0000

If a packet, carrying an SRH, is received over an interface not in RPL doma=
in, it is discarded. Thus, an attack may only be mounted within an RPL doma=
in.

Also, a packet, carrying an SRH, cant be sent over an interface not in RPL =
domain. So, any attack can not propagate beyond the RPL domain.

Also, whats wrong with defining RPL domain based on interfaces?

As I mentioned before, using RPL Instance as the scope of SRH is a problem.=
 Rules on page 13 are difficult to meet. An RPL router has no idea whether =
the next hop belongs to the particular RPL Instance or not. If the rules ar=
e changed so that a router has to check if it itself belongs to the particu=
lar RPL Instance, that will be a problem as well. This is because routers o=
n a source route discovered using P2P-RPL dont remember RPL Instance under =
which the route was discovered. Requiring maintenance of state to be part o=
f a source route does not sound like a good idea.=20

Thanks
Mukul



----- Original Message -----
From: "Jonathan Hui (johui)" <johui@cisco.com>
To: "robert cragie" <robert.cragie@gridmerge.com>
Cc: "Mukul Goyal" <mukul@uwm.edu>, ipv6@ietf.org, "roll" <roll@ietf.org>
Sent: Friday, December 23, 2011 12:17:18 PM
Subject: Re: draft-ietf-6man-rpl-routing-header-07

To alleviate some of the usual security concerns with source routing, we wa=
nt to limit the scope if where attacks can be initiated.

Any outside attacker can fabricate a SRH and send it to a RPL router.  How =
do you prevent that without some way of limiting the scope?

Also,  Mukul's proposal is to define the scope based on interfaces.  That i=
s not the same as limiting the scope to a collection of RPL routers.

--
Jonathan Hui

On Dec 23, 2011, at 10:07 AM, "Robert Cragie" <robert.cragie@gridmerge.com>=
 wrote:

> Hi Jonathan,
>=20
> Some comments and questions below.
>=20
> Robert
>=20
> On 22/12/2011 6:02 PM, Jonathan Hui wrote:
>> On Dec 22, 2011, at 9:24 AM, Mukul Goyal wrote:
>>=20
>>>> Again, just because you received a message on an interface for which y=
ou've enabled RPL doesn't mean you know the message came from a router that=
 is within the same RPL routing domain.  A router not running RPL could hav=
e sent you that message.
>>> A router not running RPL could have sent me a message carrying SRH?
>> Sure.  It could be a host as well.  Part of limiting the scope is to lim=
it the scope of an attack.  See the Security Considerations.
> <RCC>I'm not getting this. The use of SRH is for non-storing mode, correc=
t? And only for non-storing mode? There is no current definition of partial=
 storing mode and stored mode doesn't need SRH. So the source routes are cr=
eated on the DAG root based on transit information obtained by DAOs. How ca=
n any router outside of the RPL domain initiate a source-routed message to =
a node in the RPL domain? It would be tunneled at the point it got to the D=
AG root. Therefore, by implication, normally the source and destination of =
the message with SRH must be in the RPL domain. So we need to check for exc=
eptions - surely the rules Mukul stated are sufficient?</RCC>
>>=20
>>>> From Section 3.2.1 of draft-ietf-roll-rpl:
>>>   The Objective Function (OF) defines how RPL nodes select and optimize
>>>   routes within a RPL Instance.  The OF is identified by an Objective
>>>   Code Point (OCP) within the DIO Configuration option.  An OF defines
>>>   how nodes translate one or more metrics and constraints, which are
>>>   themselves defined in [I-D.ietf-roll-routing-metrics], into a value
>>>   called Rank, which approximates the node's distance from a DODAG
>>>   root.  An OF also defines how nodes select parents.  Further details
>>>   may be found in Section 14, [I-D.ietf-roll-routing-metrics],
>>>   [I-D.ietf-roll-of0], and related companion specifications.
>>>=20
>>>> As you state, RPL Instance maps to OF which, from the cited text, maps=
 to metrics and route selection.  By transitivity, RPL Instance ID does map=
 to metrics and how routes are formed.
>>> The text you quoted no where says that an OF maps to particular metric.=
 OF0 is metrics-independent. OF1 (draft-ietf-roll-minrank-hysteresis-of-04)=
 applies to any additive metric. No RPL doc says that, for a particular LLN=
, a particular OF maps to a particular metric only.
>> Incorrect.  From draft-ietf-roll-routing-metrics-19:
>>=20
>>    The set of routing metrics and constraints used by an RPL deployment
>>    is signaled along the DAG that is built according to the Objective
>>    Function (rules governing how to build a DAG) and the routing metrics
>>    and constraints are advertised in the DAG Information Option (DIO)
>>    message specified in [I-D.ietf-roll-rpl].
>>=20
>> In other words, the combination of the OCP and the metrics identified by=
 the DODAG Root describes how to optimize the routes.  In the case of OF0, =
the metric is the Rank itself.
>>=20
>>> I think the following text clearly specifies what an RPL Instance is. A=
lso, this text clearly says that an RPL Instance ID maps to a particular OF=
:
>>>=20
>>> rpl-19 section 3.1.2:
>>>      A RPLInstanceID identifies a set of
>>>      one or more Destination Oriented DAGs (DODAGs).  A network may
>>>      have multiple RPLInstanceIDs, each of which defines an independent
>>>      set of DODAGs, which may be optimized for different Objective
>>>      Functions (OFs) and/or applications.  The set of DODAGs identified
>>>      by a RPLInstanceID is called a RPL Instance.  All DODAGs in the
>>>      same RPL Instance use the same OF.
>>>=20
>>> This definition says an RPLInstanceID identifies a set of DAGs with a c=
ommon OF. No more and no less. A particular LLN may choose to map an OF to =
a particular metric but there is no such requirement as per RPL specs.
>> You never answered my question.  Why bother having a RPL Instance ID if =
you don't care how the routes are optimized?  Why bother maintaining multip=
le paths optimized using different OFs and/or metrics?
> <RCC>
> The source route is determined by the transit options, nothing else. Ther=
e is no processing done at each hop - it simply forwards it to the next bas=
ed on what's in the SRH. So no need for RPL instance (or domain) there. You=
 could potentially build up multiple tables for each RPL instance but you w=
ould just formulate a different SRH based on which table you picked. When i=
t gets to the destination, why would the OF/metric of whatever DAG it happe=
n to transit through have any bearing on where it is subsequently going? I =
ask this because there is no further information based on the domain it has=
 just gone through. The message originator would not even be aware of any s=
ubsequent RPL domains beyond itself; it is bounded by the root and the leaf=
 routers. Unless the destination is on path between the DAG root and a leaf=
 router, an SRH will always go between the DAG root and a leaf router. I fi=
nd the concept of a partial SRH quite baffling even if it is for the purpos=
es of traceroute - even then at the point it emerges someway down the path,=
 it will return a time exceeded error.
>=20
> So basically, I am still failing to understand the need to carry RPL inst=
ance in the SRH for non-storing mode. I could see its use in partial storin=
g mode whereby SRH carries it part of the way and the stored information on=
 subsequent routers the rest, but in this case surely you would put a RPL o=
ption in the inner packet and tunnel? So when it emerges from the source-ro=
uted tunnel, it is ready to be forwarded using RPL.
> <RCC>
>>=20
>>>>> RPL Instance is the top level identifier of the DAGs that can be used=
 to forward the packet. It also maps to a particular OF. In my opinion and =
as per RPL spec, RPL instance has no other significance.
>>>> See above.  RPL Instance does map to metrics.
>>> It need not.
>> You are incorrect again!
>>=20
>>>> The definition I proposed was simply a collection of routers running R=
PL under the same administrative domain.  As mentioned above, that does not=
 mean that every router on an interface belongs to a RPL routing domain.
>>> I think the definition you provided is sufficient. An RPL domain is a c=
ollection of routers running RPL under the same administrative domain. Each=
 router in the RPL domain needs to classify all its interfaces regarding wh=
ether they belong to the RPL domain or not.
>>>=20
>>> A packet can be assumed to be coming from a router in the RPL domain if=
 it carries an SRH.
>>=20
>> Nope.  As I stated before, that would invalidate the Security Considerat=
ions section.
> <RCC>I agree with Mukul: in normal circumstances a packet with an SRH wil=
l come from a router in the RPL domain and the rules Mukul stated can be us=
ed to make sure it doesn't go beyond.</RCC>
>>=20
>> --
>> Jonathan Hui
>>=20
>>=20
>=20

From johui@cisco.com  Fri Dec 23 10:17:23 2011
Return-Path: <johui@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 5CB1221F84D2; Fri, 23 Dec 2011 10:17:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.779
X-Spam-Level: 
X-Spam-Status: No, score=-2.779 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
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 7p6AlSMTgZ7E; Fri, 23 Dec 2011 10:17:22 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 55B7221F84C3; Fri, 23 Dec 2011 10:17:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10252; q=dns/txt; s=iport; t=1324664242; x=1325873842; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=o1AyCqLOS4PBampW68XEF4cr+n561hwyEj7jCMwlA/4=; b=mdGUizYRmRWpmdM85wozcaABzzRd24b+oIQH2t2i0h9tYybcGyMWRDjS 4dPIuuSfWajiNC+oTZ1bkHTEkLMkRuRIKsH/zZC07JiWaT9t9wRCvaCGp KOSkimRMJdsuwniNlJBtDMWJ0S21XYXeHqgMKC2bmIgxwxWwS7uDedNSR 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAErF9E6tJV2c/2dsb2JhbABDiVehOAGBJQKBBYFyAQEBAwESASEGLRIFCwIBCBguAlUBAQQTIodYmTEBnhSLLGMEiDeMS5JV
X-IronPort-AV: E=Sophos;i="4.71,399,1320624000"; d="scan'208";a="44029831"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 23 Dec 2011 18:17:21 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id pBNIHL0l009355;  Fri, 23 Dec 2011 18:17:21 GMT
Received: from xmb-rcd-207.cisco.com ([72.163.62.214]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 23 Dec 2011 12:17:21 -0600
Received: from 72.163.63.12 ([72.163.63.12]) by XMB-RCD-207.cisco.com ([72.163.62.214]) with Microsoft Exchange Server HTTP-DAV ;  Fri, 23 Dec 2011 18:17:21 +0000
Subject: Re: draft-ietf-6man-rpl-routing-header-07
References: <1033338721.734443.1324574682571.JavaMail.root@mail17.pantherlink.uwm.edu> <B6EF9DCC-5743-41FF-BEF5-5AA7C6C27BA9@cisco.com> <4EF4C358.60103@gridmerge.com>
Content-Transfer-Encoding: base64
From: "Jonathan Hui (johui)" <johui@cisco.com>
Thread-Topic: draft-ietf-6man-rpl-routing-header-07
Thread-Index: AczBnxz1KPcGiWBlR+yv9mrDxtSHRQ==
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <4EF4C358.60103@gridmerge.com>
Message-ID: <ABAF5F0D-5D0C-4EF0-9315-201376731A65@cisco.com>
Date: Fri, 23 Dec 2011 10:17:18 -0800
To: <robert.cragie@gridmerge.com>
MIME-Version: 1.0 (1.0)
X-OriginalArrivalTime: 23 Dec 2011 18:17:21.0623 (UTC) FILETIME=[1CEE1E70:01CCC19F]
X-Mailman-Approved-At: Fri, 23 Dec 2011 10:59:53 -0800
Cc: ipv6@ietf.org, roll <roll@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, 23 Dec 2011 18:18:10 -0000

VG8gYWxsZXZpYXRlIHNvbWUgb2YgdGhlIHVzdWFsIHNlY3VyaXR5IGNvbmNlcm5zIHdpdGggc291
cmNlIHJvdXRpbmcsIHdlIHdhbnQgdG8gbGltaXQgdGhlIHNjb3BlIGlmIHdoZXJlIGF0dGFja3Mg
Y2FuIGJlIGluaXRpYXRlZC4NCg0KQW55IG91dHNpZGUgYXR0YWNrZXIgY2FuIGZhYnJpY2F0ZSBh
IFNSSCBhbmQgc2VuZCBpdCB0byBhIFJQTCByb3V0ZXIuICBIb3cgZG8geW91IHByZXZlbnQgdGhh
dCB3aXRob3V0IHNvbWUgd2F5IG9mIGxpbWl0aW5nIHRoZSBzY29wZT8NCg0KQWxzbywgIE11a3Vs
J3MgcHJvcG9zYWwgaXMgdG8gZGVmaW5lIHRoZSBzY29wZSBiYXNlZCBvbiBpbnRlcmZhY2VzLiAg
VGhhdCBpcyBub3QgdGhlIHNhbWUgYXMgbGltaXRpbmcgdGhlIHNjb3BlIHRvIGEgY29sbGVjdGlv
biBvZiBSUEwgcm91dGVycy4NCg0KLS0NCkpvbmF0aGFuIEh1aQ0KDQpPbiBEZWMgMjMsIDIwMTEs
IGF0IDEwOjA3IEFNLCAiUm9iZXJ0IENyYWdpZSIgPHJvYmVydC5jcmFnaWVAZ3JpZG1lcmdlLmNv
bT4gd3JvdGU6DQoNCj4gSGkgSm9uYXRoYW4sDQo+IA0KPiBTb21lIGNvbW1lbnRzIGFuZCBxdWVz
dGlvbnMgYmVsb3cuDQo+IA0KPiBSb2JlcnQNCj4gDQo+IE9uIDIyLzEyLzIwMTEgNjowMiBQTSwg
Sm9uYXRoYW4gSHVpIHdyb3RlOg0KPj4gT24gRGVjIDIyLCAyMDExLCBhdCA5OjI0IEFNLCBNdWt1
bCBHb3lhbCB3cm90ZToNCj4+IA0KPj4+PiBBZ2FpbiwganVzdCBiZWNhdXNlIHlvdSByZWNlaXZl
ZCBhIG1lc3NhZ2Ugb24gYW4gaW50ZXJmYWNlIGZvciB3aGljaCB5b3UndmUgZW5hYmxlZCBSUEwg
ZG9lc24ndCBtZWFuIHlvdSBrbm93IHRoZSBtZXNzYWdlIGNhbWUgZnJvbSBhIHJvdXRlciB0aGF0
IGlzIHdpdGhpbiB0aGUgc2FtZSBSUEwgcm91dGluZyBkb21haW4uICBBIHJvdXRlciBub3QgcnVu
bmluZyBSUEwgY291bGQgaGF2ZSBzZW50IHlvdSB0aGF0IG1lc3NhZ2UuDQo+Pj4gQSByb3V0ZXIg
bm90IHJ1bm5pbmcgUlBMIGNvdWxkIGhhdmUgc2VudCBtZSBhIG1lc3NhZ2UgY2FycnlpbmcgU1JI
Pw0KPj4gU3VyZS4gIEl0IGNvdWxkIGJlIGEgaG9zdCBhcyB3ZWxsLiAgUGFydCBvZiBsaW1pdGlu
ZyB0aGUgc2NvcGUgaXMgdG8gbGltaXQgdGhlIHNjb3BlIG9mIGFuIGF0dGFjay4gIFNlZSB0aGUg
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMuDQo+IDxSQ0M+SSdtIG5vdCBnZXR0aW5nIHRoaXMuIFRo
ZSB1c2Ugb2YgU1JIIGlzIGZvciBub24tc3RvcmluZyBtb2RlLCBjb3JyZWN0PyBBbmQgb25seSBm
b3Igbm9uLXN0b3JpbmcgbW9kZT8gVGhlcmUgaXMgbm8gY3VycmVudCBkZWZpbml0aW9uIG9mIHBh
cnRpYWwgc3RvcmluZyBtb2RlIGFuZCBzdG9yZWQgbW9kZSBkb2Vzbid0IG5lZWQgU1JILiBTbyB0
aGUgc291cmNlIHJvdXRlcyBhcmUgY3JlYXRlZCBvbiB0aGUgREFHIHJvb3QgYmFzZWQgb24gdHJh
bnNpdCBpbmZvcm1hdGlvbiBvYnRhaW5lZCBieSBEQU9zLiBIb3cgY2FuIGFueSByb3V0ZXIgb3V0
c2lkZSBvZiB0aGUgUlBMIGRvbWFpbiBpbml0aWF0ZSBhIHNvdXJjZS1yb3V0ZWQgbWVzc2FnZSB0
byBhIG5vZGUgaW4gdGhlIFJQTCBkb21haW4/IEl0IHdvdWxkIGJlIHR1bm5lbGVkIGF0IHRoZSBw
b2ludCBpdCBnb3QgdG8gdGhlIERBRyByb290LiBUaGVyZWZvcmUsIGJ5IGltcGxpY2F0aW9uLCBu
b3JtYWxseSB0aGUgc291cmNlIGFuZCBkZXN0aW5hdGlvbiBvZiB0aGUgbWVzc2FnZSB3aXRoIFNS
SCBtdXN0IGJlIGluIHRoZSBSUEwgZG9tYWluLiBTbyB3ZSBuZWVkIHRvIGNoZWNrIGZvciBleGNl
cHRpb25zIC0gc3VyZWx5IHRoZSBydWxlcyBNdWt1bCBzdGF0ZWQgYXJlIHN1ZmZpY2llbnQ/PC9S
Q0M+DQo+PiANCj4+Pj4gRnJvbSBTZWN0aW9uIDMuMi4xIG9mIGRyYWZ0LWlldGYtcm9sbC1ycGw6
DQo+Pj4gICBUaGUgT2JqZWN0aXZlIEZ1bmN0aW9uIChPRikgZGVmaW5lcyBob3cgUlBMIG5vZGVz
IHNlbGVjdCBhbmQgb3B0aW1pemUNCj4+PiAgIHJvdXRlcyB3aXRoaW4gYSBSUEwgSW5zdGFuY2Uu
ICBUaGUgT0YgaXMgaWRlbnRpZmllZCBieSBhbiBPYmplY3RpdmUNCj4+PiAgIENvZGUgUG9pbnQg
KE9DUCkgd2l0aGluIHRoZSBESU8gQ29uZmlndXJhdGlvbiBvcHRpb24uICBBbiBPRiBkZWZpbmVz
DQo+Pj4gICBob3cgbm9kZXMgdHJhbnNsYXRlIG9uZSBvciBtb3JlIG1ldHJpY3MgYW5kIGNvbnN0
cmFpbnRzLCB3aGljaCBhcmUNCj4+PiAgIHRoZW1zZWx2ZXMgZGVmaW5lZCBpbiBbSS1ELmlldGYt
cm9sbC1yb3V0aW5nLW1ldHJpY3NdLCBpbnRvIGEgdmFsdWUNCj4+PiAgIGNhbGxlZCBSYW5rLCB3
aGljaCBhcHByb3hpbWF0ZXMgdGhlIG5vZGUncyBkaXN0YW5jZSBmcm9tIGEgRE9EQUcNCj4+PiAg
IHJvb3QuICBBbiBPRiBhbHNvIGRlZmluZXMgaG93IG5vZGVzIHNlbGVjdCBwYXJlbnRzLiAgRnVy
dGhlciBkZXRhaWxzDQo+Pj4gICBtYXkgYmUgZm91bmQgaW4gU2VjdGlvbiAxNCwgW0ktRC5pZXRm
LXJvbGwtcm91dGluZy1tZXRyaWNzXSwNCj4+PiAgIFtJLUQuaWV0Zi1yb2xsLW9mMF0sIGFuZCBy
ZWxhdGVkIGNvbXBhbmlvbiBzcGVjaWZpY2F0aW9ucy4NCj4+PiANCj4+Pj4gQXMgeW91IHN0YXRl
LCBSUEwgSW5zdGFuY2UgbWFwcyB0byBPRiB3aGljaCwgZnJvbSB0aGUgY2l0ZWQgdGV4dCwgbWFw
cyB0byBtZXRyaWNzIGFuZCByb3V0ZSBzZWxlY3Rpb24uICBCeSB0cmFuc2l0aXZpdHksIFJQTCBJ
bnN0YW5jZSBJRCBkb2VzIG1hcCB0byBtZXRyaWNzIGFuZCBob3cgcm91dGVzIGFyZSBmb3JtZWQu
DQo+Pj4gVGhlIHRleHQgeW91IHF1b3RlZCBubyB3aGVyZSBzYXlzIHRoYXQgYW4gT0YgbWFwcyB0
byBwYXJ0aWN1bGFyIG1ldHJpYy4gT0YwIGlzIG1ldHJpY3MtaW5kZXBlbmRlbnQuIE9GMSAoZHJh
ZnQtaWV0Zi1yb2xsLW1pbnJhbmstaHlzdGVyZXNpcy1vZi0wNCkgYXBwbGllcyB0byBhbnkgYWRk
aXRpdmUgbWV0cmljLiBObyBSUEwgZG9jIHNheXMgdGhhdCwgZm9yIGEgcGFydGljdWxhciBMTE4s
IGEgcGFydGljdWxhciBPRiBtYXBzIHRvIGEgcGFydGljdWxhciBtZXRyaWMgb25seS4NCj4+IElu
Y29ycmVjdC4gIEZyb20gZHJhZnQtaWV0Zi1yb2xsLXJvdXRpbmctbWV0cmljcy0xOToNCj4+IA0K
Pj4gICAgVGhlIHNldCBvZiByb3V0aW5nIG1ldHJpY3MgYW5kIGNvbnN0cmFpbnRzIHVzZWQgYnkg
YW4gUlBMIGRlcGxveW1lbnQNCj4+ICAgIGlzIHNpZ25hbGVkIGFsb25nIHRoZSBEQUcgdGhhdCBp
cyBidWlsdCBhY2NvcmRpbmcgdG8gdGhlIE9iamVjdGl2ZQ0KPj4gICAgRnVuY3Rpb24gKHJ1bGVz
IGdvdmVybmluZyBob3cgdG8gYnVpbGQgYSBEQUcpIGFuZCB0aGUgcm91dGluZyBtZXRyaWNzDQo+
PiAgICBhbmQgY29uc3RyYWludHMgYXJlIGFkdmVydGlzZWQgaW4gdGhlIERBRyBJbmZvcm1hdGlv
biBPcHRpb24gKERJTykNCj4+ICAgIG1lc3NhZ2Ugc3BlY2lmaWVkIGluIFtJLUQuaWV0Zi1yb2xs
LXJwbF0uDQo+PiANCj4+IEluIG90aGVyIHdvcmRzLCB0aGUgY29tYmluYXRpb24gb2YgdGhlIE9D
UCBhbmQgdGhlIG1ldHJpY3MgaWRlbnRpZmllZCBieSB0aGUgRE9EQUcgUm9vdCBkZXNjcmliZXMg
aG93IHRvIG9wdGltaXplIHRoZSByb3V0ZXMuICBJbiB0aGUgY2FzZSBvZiBPRjAsIHRoZSBtZXRy
aWMgaXMgdGhlIFJhbmsgaXRzZWxmLg0KPj4gDQo+Pj4gSSB0aGluayB0aGUgZm9sbG93aW5nIHRl
eHQgY2xlYXJseSBzcGVjaWZpZXMgd2hhdCBhbiBSUEwgSW5zdGFuY2UgaXMuIEFsc28sIHRoaXMg
dGV4dCBjbGVhcmx5IHNheXMgdGhhdCBhbiBSUEwgSW5zdGFuY2UgSUQgbWFwcyB0byBhIHBhcnRp
Y3VsYXIgT0Y6DQo+Pj4gDQo+Pj4gcnBsLTE5IHNlY3Rpb24gMy4xLjI6DQo+Pj4gICAgICBBIFJQ
TEluc3RhbmNlSUQgaWRlbnRpZmllcyBhIHNldCBvZg0KPj4+ICAgICAgb25lIG9yIG1vcmUgRGVz
dGluYXRpb24gT3JpZW50ZWQgREFHcyAoRE9EQUdzKS4gIEEgbmV0d29yayBtYXkNCj4+PiAgICAg
IGhhdmUgbXVsdGlwbGUgUlBMSW5zdGFuY2VJRHMsIGVhY2ggb2Ygd2hpY2ggZGVmaW5lcyBhbiBp
bmRlcGVuZGVudA0KPj4+ICAgICAgc2V0IG9mIERPREFHcywgd2hpY2ggbWF5IGJlIG9wdGltaXpl
ZCBmb3IgZGlmZmVyZW50IE9iamVjdGl2ZQ0KPj4+ICAgICAgRnVuY3Rpb25zIChPRnMpIGFuZC9v
ciBhcHBsaWNhdGlvbnMuICBUaGUgc2V0IG9mIERPREFHcyBpZGVudGlmaWVkDQo+Pj4gICAgICBi
eSBhIFJQTEluc3RhbmNlSUQgaXMgY2FsbGVkIGEgUlBMIEluc3RhbmNlLiAgQWxsIERPREFHcyBp
biB0aGUNCj4+PiAgICAgIHNhbWUgUlBMIEluc3RhbmNlIHVzZSB0aGUgc2FtZSBPRi4NCj4+PiAN
Cj4+PiBUaGlzIGRlZmluaXRpb24gc2F5cyBhbiBSUExJbnN0YW5jZUlEIGlkZW50aWZpZXMgYSBz
ZXQgb2YgREFHcyB3aXRoIGEgY29tbW9uIE9GLiBObyBtb3JlIGFuZCBubyBsZXNzLiBBIHBhcnRp
Y3VsYXIgTExOIG1heSBjaG9vc2UgdG8gbWFwIGFuIE9GIHRvIGEgcGFydGljdWxhciBtZXRyaWMg
YnV0IHRoZXJlIGlzIG5vIHN1Y2ggcmVxdWlyZW1lbnQgYXMgcGVyIFJQTCBzcGVjcy4NCj4+IFlv
dSBuZXZlciBhbnN3ZXJlZCBteSBxdWVzdGlvbi4gIFdoeSBib3RoZXIgaGF2aW5nIGEgUlBMIElu
c3RhbmNlIElEIGlmIHlvdSBkb24ndCBjYXJlIGhvdyB0aGUgcm91dGVzIGFyZSBvcHRpbWl6ZWQ/
ICBXaHkgYm90aGVyIG1haW50YWluaW5nIG11bHRpcGxlIHBhdGhzIG9wdGltaXplZCB1c2luZyBk
aWZmZXJlbnQgT0ZzIGFuZC9vciBtZXRyaWNzPw0KPiA8UkNDPg0KPiBUaGUgc291cmNlIHJvdXRl
IGlzIGRldGVybWluZWQgYnkgdGhlIHRyYW5zaXQgb3B0aW9ucywgbm90aGluZyBlbHNlLiBUaGVy
ZSBpcyBubyBwcm9jZXNzaW5nIGRvbmUgYXQgZWFjaCBob3AgLSBpdCBzaW1wbHkgZm9yd2FyZHMg
aXQgdG8gdGhlIG5leHQgYmFzZWQgb24gd2hhdCdzIGluIHRoZSBTUkguIFNvIG5vIG5lZWQgZm9y
IFJQTCBpbnN0YW5jZSAob3IgZG9tYWluKSB0aGVyZS4gWW91IGNvdWxkIHBvdGVudGlhbGx5IGJ1
aWxkIHVwIG11bHRpcGxlIHRhYmxlcyBmb3IgZWFjaCBSUEwgaW5zdGFuY2UgYnV0IHlvdSB3b3Vs
ZCBqdXN0IGZvcm11bGF0ZSBhIGRpZmZlcmVudCBTUkggYmFzZWQgb24gd2hpY2ggdGFibGUgeW91
IHBpY2tlZC4gV2hlbiBpdCBnZXRzIHRvIHRoZSBkZXN0aW5hdGlvbiwgd2h5IHdvdWxkIHRoZSBP
Ri9tZXRyaWMgb2Ygd2hhdGV2ZXIgREFHIGl0IGhhcHBlbiB0byB0cmFuc2l0IHRocm91Z2ggaGF2
ZSBhbnkgYmVhcmluZyBvbiB3aGVyZSBpdCBpcyBzdWJzZXF1ZW50bHkgZ29pbmc/IEkgYXNrIHRo
aXMgYmVjYXVzZSB0aGVyZSBpcyBubyBmdXJ0aGVyIGluZm9ybWF0aW9uIGJhc2VkIG9uIHRoZSBk
b21haW4gaXQgaGFzIGp1c3QgZ29uZSB0aHJvdWdoLiBUaGUgbWVzc2FnZSBvcmlnaW5hdG9yIHdv
dWxkIG5vdCBldmVuIGJlIGF3YXJlIG9mIGFueSBzdWJzZXF1ZW50IFJQTCBkb21haW5zIGJleW9u
ZCBpdHNlbGY7IGl0IGlzIGJvdW5kZWQgYnkgdGhlIHJvb3QgYW5kIHRoZSBsZWFmIHJvdXRlcnMu
IFVubGVzcyB0aGUgZGVzdGluYXRpb24gaXMgb24gcGF0aCBiZXR3ZWVuIHRoZSBEQUcgcm9vdCBh
bmQgYSBsZWFmIHJvdXRlciwgYW4gU1JIIHdpbGwgYWx3YXlzIGdvIGJldHdlZW4gdGhlIERBRyBy
b290IGFuZCBhIGxlYWYgcm91dGVyLiBJIGZpbmQgdGhlIGNvbmNlcHQgb2YgYSBwYXJ0aWFsIFNS
SCBxdWl0ZSBiYWZmbGluZyBldmVuIGlmIGl0IGlzIGZvciB0aGUgcHVycG9zZXMgb2YgdHJhY2Vy
b3V0ZSAtIGV2ZW4gdGhlbiBhdCB0aGUgcG9pbnQgaXQgZW1lcmdlcyBzb21ld2F5IGRvd24gdGhl
IHBhdGgsIGl0IHdpbGwgcmV0dXJuIGEgdGltZSBleGNlZWRlZCBlcnJvci4NCj4gDQo+IFNvIGJh
c2ljYWxseSwgSSBhbSBzdGlsbCBmYWlsaW5nIHRvIHVuZGVyc3RhbmQgdGhlIG5lZWQgdG8gY2Fy
cnkgUlBMIGluc3RhbmNlIGluIHRoZSBTUkggZm9yIG5vbi1zdG9yaW5nIG1vZGUuIEkgY291bGQg
c2VlIGl0cyB1c2UgaW4gcGFydGlhbCBzdG9yaW5nIG1vZGUgd2hlcmVieSBTUkggY2FycmllcyBp
dCBwYXJ0IG9mIHRoZSB3YXkgYW5kIHRoZSBzdG9yZWQgaW5mb3JtYXRpb24gb24gc3Vic2VxdWVu
dCByb3V0ZXJzIHRoZSByZXN0LCBidXQgaW4gdGhpcyBjYXNlIHN1cmVseSB5b3Ugd291bGQgcHV0
IGEgUlBMIG9wdGlvbiBpbiB0aGUgaW5uZXIgcGFja2V0IGFuZCB0dW5uZWw/IFNvIHdoZW4gaXQg
ZW1lcmdlcyBmcm9tIHRoZSBzb3VyY2Utcm91dGVkIHR1bm5lbCwgaXQgaXMgcmVhZHkgdG8gYmUg
Zm9yd2FyZGVkIHVzaW5nIFJQTC4NCj4gPFJDQz4NCj4+IA0KPj4+Pj4gUlBMIEluc3RhbmNlIGlz
IHRoZSB0b3AgbGV2ZWwgaWRlbnRpZmllciBvZiB0aGUgREFHcyB0aGF0IGNhbiBiZSB1c2VkIHRv
IGZvcndhcmQgdGhlIHBhY2tldC4gSXQgYWxzbyBtYXBzIHRvIGEgcGFydGljdWxhciBPRi4gSW4g
bXkgb3BpbmlvbiBhbmQgYXMgcGVyIFJQTCBzcGVjLCBSUEwgaW5zdGFuY2UgaGFzIG5vIG90aGVy
IHNpZ25pZmljYW5jZS4NCj4+Pj4gU2VlIGFib3ZlLiAgUlBMIEluc3RhbmNlIGRvZXMgbWFwIHRv
IG1ldHJpY3MuDQo+Pj4gSXQgbmVlZCBub3QuDQo+PiBZb3UgYXJlIGluY29ycmVjdCBhZ2FpbiEN
Cj4+IA0KPj4+PiBUaGUgZGVmaW5pdGlvbiBJIHByb3Bvc2VkIHdhcyBzaW1wbHkgYSBjb2xsZWN0
aW9uIG9mIHJvdXRlcnMgcnVubmluZyBSUEwgdW5kZXIgdGhlIHNhbWUgYWRtaW5pc3RyYXRpdmUg
ZG9tYWluLiAgQXMgbWVudGlvbmVkIGFib3ZlLCB0aGF0IGRvZXMgbm90IG1lYW4gdGhhdCBldmVy
eSByb3V0ZXIgb24gYW4gaW50ZXJmYWNlIGJlbG9uZ3MgdG8gYSBSUEwgcm91dGluZyBkb21haW4u
DQo+Pj4gSSB0aGluayB0aGUgZGVmaW5pdGlvbiB5b3UgcHJvdmlkZWQgaXMgc3VmZmljaWVudC4g
QW4gUlBMIGRvbWFpbiBpcyBhIGNvbGxlY3Rpb24gb2Ygcm91dGVycyBydW5uaW5nIFJQTCB1bmRl
ciB0aGUgc2FtZSBhZG1pbmlzdHJhdGl2ZSBkb21haW4uIEVhY2ggcm91dGVyIGluIHRoZSBSUEwg
ZG9tYWluIG5lZWRzIHRvIGNsYXNzaWZ5IGFsbCBpdHMgaW50ZXJmYWNlcyByZWdhcmRpbmcgd2hl
dGhlciB0aGV5IGJlbG9uZyB0byB0aGUgUlBMIGRvbWFpbiBvciBub3QuDQo+Pj4gDQo+Pj4gQSBw
YWNrZXQgY2FuIGJlIGFzc3VtZWQgdG8gYmUgY29taW5nIGZyb20gYSByb3V0ZXIgaW4gdGhlIFJQ
TCBkb21haW4gaWYgaXQgY2FycmllcyBhbiBTUkguDQo+PiANCj4+IE5vcGUuICBBcyBJIHN0YXRl
ZCBiZWZvcmUsIHRoYXQgd291bGQgaW52YWxpZGF0ZSB0aGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlv
bnMgc2VjdGlvbi4NCj4gPFJDQz5JIGFncmVlIHdpdGggTXVrdWw6IGluIG5vcm1hbCBjaXJjdW1z
dGFuY2VzIGEgcGFja2V0IHdpdGggYW4gU1JIIHdpbGwgY29tZSBmcm9tIGEgcm91dGVyIGluIHRo
ZSBSUEwgZG9tYWluIGFuZCB0aGUgcnVsZXMgTXVrdWwgc3RhdGVkIGNhbiBiZSB1c2VkIHRvIG1h
a2Ugc3VyZSBpdCBkb2Vzbid0IGdvIGJleW9uZC48L1JDQz4NCj4+IA0KPj4gLS0NCj4+IEpvbmF0
aGFuIEh1aQ0KPj4gDQo+PiANCj4gDQo=

From brian.e.carpenter@gmail.com  Fri Dec 23 16:11:13 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 008E021F8AAA for <ipv6@ietfa.amsl.com>; Fri, 23 Dec 2011 16:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.524
X-Spam-Level: 
X-Spam-Status: No, score=-103.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 P2wcrfpQC3pL for <ipv6@ietfa.amsl.com>; Fri, 23 Dec 2011 16:11:12 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4980821F8A71 for <ipv6@ietf.org>; Fri, 23 Dec 2011 16:11:12 -0800 (PST)
Received: by eekc14 with SMTP id c14so8412457eek.31 for <ipv6@ietf.org>; Fri, 23 Dec 2011 16:11:11 -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=gzVC81KOmJORNJQa7KrnZOc7+q/bPP9r4oWGLsRdX34=; b=a8rtY0Yl2ecQkFh/keorGYwgyY0bpAZW5ZcNvxv8mspD1YggIZkYrH1pfC5wyaNkOf i3tBWTp+Ie2tiwuJtkmKuQgVLAB1wYnefOrRLUGE9hpUa6H/uuyWVtbei5+AP5hjZrDI wjD+rYK95Rws9FHJVslpevq9vZHEt/lWW8DU0=
Received: by 10.213.6.208 with SMTP id a16mr1254742eba.74.1324685471468; Fri, 23 Dec 2011 16:11:11 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id 76sm55216827eeh.0.2011.12.23.16.11.08 (version=SSLv3 cipher=OTHER); Fri, 23 Dec 2011 16:11:10 -0800 (PST)
Message-ID: <4EF51896.1020901@gmail.com>
Date: Sat, 24 Dec 2011 13:11:02 +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: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com>	<4EF22786.2070908@dougbarton.us>	<7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF439A9.4070502@dougbarton.us>
In-Reply-To: <4EF439A9.4070502@dougbarton.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Sat, 24 Dec 2011 00:11:13 -0000

> On 12/21/2011 15:52, Bhatia, Manav (Manav) wrote:

...
>> Today, we can get NTP server information only with DHCP. DHCP only
>> works after RAs have been processed. In some environments (mobile
>> IPv6) delays in acquiring NTP and other servers information is
>> critical and waiting for DHCP to come up is NOT an ideal solution.

Can you explain why it is so time critical? If the mobile device is
already up and running, it will already have an accurate current clock
time, and can resynch with NTP at its leisure.

If it's booting from cold, it will not be in any MIP session so there
can't be any urgency.

I assume that in any case the mobile will have a preconfigured default
NTP server, by DNS name or even IP address.

   Brian

From i.grok@comcast.net  Sat Dec 24 06:25:14 2011
Return-Path: <i.grok@comcast.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 D6BA421F84BB for <ipv6@ietfa.amsl.com>; Sat, 24 Dec 2011 06:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.599
X-Spam-Level: 
X-Spam-Status: No, score=-101.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_FREEBONUS=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 lQmTy5Y2ywdJ for <ipv6@ietfa.amsl.com>; Sat, 24 Dec 2011 06:25:14 -0800 (PST)
Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by ietfa.amsl.com (Postfix) with ESMTP id 7470B21F84BA for <ipv6@ietf.org>; Sat, 24 Dec 2011 06:25:14 -0800 (PST)
Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta15.emeryville.ca.mail.comcast.net with comcast id D2P21i0030b6N64AF2R5Em; Sat, 24 Dec 2011 14:25:05 +0000
Received: from odin.ulthar.us ([68.33.77.0]) by omta03.emeryville.ca.mail.comcast.net with comcast id D2Ta1i00D00PQ6U8P2TaV7; Sat, 24 Dec 2011 14:27:36 +0000
Received: from odin.ulthar.us (localhost [127.0.0.1]) by odin.ulthar.us (8.14.5/8.14.3) with ESMTP id pBOEP8LH014239 for <ipv6@ietf.org>; Sat, 24 Dec 2011 09:25:08 -0500
Received: (from draco@localhost) by odin.ulthar.us (8.14.5/8.14.5/Submit) id pBOEP6cE014238 for ipv6@ietf.org; Sat, 24 Dec 2011 09:25:06 -0500
Date: Sat, 24 Dec 2011 09:25:06 -0500
From: Scott Schmit <i.grok@comcast.net>
To: ipv6@ietf.org
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
Message-ID: <20111224142506.GA2954@odin.ulthar.us>
Mail-Followup-To: ipv6@ietf.org
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF439A9.4070502@dougbarton.us>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="OgqxwSJOaUobr8KG"
Content-Disposition: inline
In-Reply-To: <4EF439A9.4070502@dougbarton.us>
User-Agent: Mutt/1.5.21 (2010-09-15)
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, 24 Dec 2011 14:25:14 -0000

--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 23, 2011 at 12:19:53AM -0800, Doug Barton wrote:
> Wrong answer. The right answer is for DHCPv6 to be a superset of RA so
> that organizations that need more than RA provides only have to run
> DHCP. As a free bonus, it's FAR easier to add one knob (default route)
> to DHCPv6 than it is to add all features to RA. Extra bonus, the only
> hurdles are political, not technical.

I agree with your essential point, except to say that for me to be happy
with DHCPv6, I also want to be able to assign an address to a host by
taking some constant bit of information from the host (like, say, a MAC
address) and know that no matter how I reinstall that host, it'll retain
the address I gave it.

As it is today, to use DHCPv6 the way I want, I must first have my host
get an IP (the wrong one), figure out what DUID it used, and reconfigure
my server to give it the one I want it to have. With RA, I don't assign
the address, but to know what it is, I just look up its MAC address and
I'm done. With DHCPv4, I look up its MAC address, add it to my server
configuration and I'm done.

I don't really care if it's a MAC address per se, but I don't want to
have to deal with DUID change because of OS reinstallation, change of
client software, dual-boot, removal & re-adding of the connection
definition, etc. I can think of reasons why it might be nice to have
different DUIDs for different OS's, so I don't object to the option, but
in most cases the current spec hurts (me) more than it helps.

--=20
Scott Schmit

--OgqxwSJOaUobr8KG
Content-Type: application/x-pkcs7-signature
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIIQJgYJKoZIhvcNAQcCoIIQFzCCEBMCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
DVcwggY0MIIEHKADAgECAgEeMA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYD
VQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0
ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAe
Fw0wNzEwMjQyMTAxNTVaFw0xNzEwMjQyMTAxNTVaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UE
ChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUg
U2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0
ZSBDbGllbnQgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDHCYPMzi3YGrEp
pC4Tq5a+ijKDjKaIQZZVR63UbxIP6uq/I0fhCu+cQhoUfE6ERKKnu8zPf1Jwuk0tsvVCk6U9
b+0UjM0dLep3ZdE1gblK/1FwYT5Pipsu2yOMluLqwvsuz9/9f1+1PKHG/FaR/wpbfuIqu54q
zHDYeqiUfsYzoVflR80DAC7hmJ+SmZnNTWyUGHJbBpA8Q89lGxahNvuryGaC/o2/ceD2uYDX
9U8Eg5DpIpGQdcbQeGarV04WgAUjjXX5r/2dabmtxWMZwhZna//jdiSyrrSMTGKkDiXm6/3/
4ebfeZuCYKzN2P8O2F/Xe2AC/Y7zeEsnR7FOp+uXAgMBAAGjggGtMIIBqTAPBgNVHRMBAf8E
BTADAQH/MA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUU3Ltkpzg2ssBXHx+ljVO8tS4UYIw
HwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwZgYIKwYBBQUHAQEEWjBYMCcGCCsG
AQUFBzABhhtodHRwOi8vb2NzcC5zdGFydHNzbC5jb20vY2EwLQYIKwYBBQUHMAKGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNydDBbBgNVHR8EVDBSMCegJaAjhiFodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwJ6AloCOGIWh0dHA6Ly9jcmwuc3RhcnRzc2wu
Y29tL3Nmc2NhLmNybDCBgAYDVR0gBHkwdzB1BgsrBgEEAYG1NwECATBmMC4GCCsGAQUFBwIB
FiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQGCCsGAQUFBwIBFihodHRw
Oi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMA0GCSqGSIb3DQEBBQUAA4IC
AQAKgwh9eKssBly4Y4xerhy5I3dNoXHYfYa8PlVLL/qtXnkFgdtY1o95CfegFJTwqBBmf8py
TUnFsukDFUI22zF5bVHzuJ+GxhnSqN2sD1qetbYwBYK2iyYA5Pg7Er1A+hKMIzEzcduRkIMm
CeUTyMyikfbUFvIBivtvkR8ZFAk22BZy+pJfAoedO61HTz4qSfQoCRcLN5A0t4DkuVhTMXIz
uQ8CnykhExD6x4e6ebIbrjZLb7L+ocR0y4YjCl/Pd4MXU91y0vTipgr/O75CDUHDRHCCKBVm
z/Rzkc/b970MEeHt5LC3NiWTgBSvrLEuVzBKM586YoRD9Dy3OHQgWI270g+5MYA8GfgI/EPT
5G7xPbCDz+zjdH89PeR3U4So4lSXur6H6vp+m9TQXPF3a0LwZrp8MQ+Z77U1uL7TelWO5lAp
sbAonrqASfTpaprFVkL4nyGH+NHST2ZJPWIBk81i6Vw0ny0qZW2Niy/QvVNKbb43A43ny076
khXO7cNbBIRdJ/6qQNq9Bqb5C0Q5nEsFcj75oxQRqlKf6TcvGbjxkJh8BYtv9ePsXklAxtm8
J7GCUBthHSQgepbkOexhJ0wP8imUkyiPHQ0GvEnd83129fZjoEhdGwXV27ioRKbj/cIq7JRX
un0NbeY+UdMYu9jGfIpDLtUUGSgsg2zMGs5R4jCCBxswggYDoAMCAQICAwK+HTANBgkqhkiG
9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTExMDcxNzA1
MDQwNFoXDTEyMDcxNzExNDI1OVowYjEgMB4GA1UEDRMXNDY1MjU2LTBnRmI2Sk5ZWW44QnFW
bUwxGzAZBgNVBAMMEmkuZ3Jva0Bjb21jYXN0Lm5ldDEhMB8GCSqGSIb3DQEJARYSaS5ncm9r
QGNvbWNhc3QubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2AjLOMsBGaqN
hv2FcRbfom/QCeKMXu5tUd1JY5oIDZe5y29stnd+se/zUlEkiVeMam4Jgo1c8yGNnwLVYc5/
9xVi7Qg1Is5b9AB6aJWElJDw/jIdihymNZ2kwkSLT0wl/lzd0mXlwFJPRgQiRkmE6V0ZmjsQ
jaVtllVleGBbMvmWPm92e+4Bju9P81kKz7Xr02ijETmaPdVsl+jmOaKPS8Y+2Lat2xus4Ked
oJ/7aIWIpz1gRSKjAHSZ1Wmwi2TYUjYhZryChu9e1RWtqk1CycNoeusJ8xdEVN3WSnJ299w/
3ltK/x/9rpj2j9ShQZVB4NnX6cjQs7pz1lVxvIkjcQIDAQABo4IDrTCCA6kwCQYDVR0TBAIw
ADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQW
BBQ29j2I0O8sRYi0So9NwwmT1caakDAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6WNU7y1LhR
gjAdBgNVHREEFjAUgRJpLmdyb2tAY29tY2FzdC5uZXQwggIhBgNVHSAEggIYMIICFDCCAhAG
CysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20v
cG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJt
ZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBB
dXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcg
dG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4g
Y29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUF
BwICMIGPMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJp
bGl0eSBhbmQgd2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFu
ZCBMaW1pdGF0aW9ucyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAr
oCmgJ4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUH
AQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFz
czEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0
cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IBAQAZ5U0nL/2PQwsVfHgN7MVPbZEGzDzuj4Oy
pTgz4XQFwPcCuy6U9sp1Dwmo3DyKX5nKN4xA7pslN+2Pl/kElGamX7zMCAH0xED0RTOLyk+v
nDML4s+OUtWaYVnq1bZEp0F8Luq3zIslAYSebleyiz8M0EypZczsL5rOk86R2F9EYw1CBuFJ
5a4x0CmNu5o30fGNDFt+iXRlbJPp/KY25iUgVnBzJ4COT5kQjxn5lgr4t1I+BDCL5HQQ3h/8
2CzwrWVRBNb9Vqh9LL1ZtzYRt8JezoB6HkVvcKVNGlCZ+/MnvfMzPLwfbTDZC8o4d+4RH6aE
LeGF2XmAOaenc/YRqm9oMYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT
aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQQIDAr4dMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMTExMjI0MTQyNTA2WjAjBgkqhkiG9w0BCQQxFgQUK6snjukj
pl7JNEAY0J2DKoOkD54weQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUD
BAEWMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcN
AwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEABx0iFrNc
kWc3dEfTgwAQ3cEfPAtpKhBa0LIO3cnKA0mj94cuXJga2zl9MjkeraGrjaTPoT2XYnmIQXcF
OVxcy9j3fzeC19bAK6Lbw5ZX/Fiy2DaURhUpxjD16vy7Hqt3Bt2NAsL7lOoJawllpn01iRde
hkFkYkI3RW9+UznoF1JNLie5Lz4BulvkIkhdBEdGDYZNSjUAgbwICDFrp3L9HBZJeXAuVM3A
NY0rCixIe5eqSKnZPd30AC4O71uhO3NfGeWU+PWeLO+8LmY0u7dUGwXHOAtVc73rWfWowWmw
oyKpGLaa86zRsHRsAHYV6Qptprml8E+vAQrtwnSYKhsBXA==

--OgqxwSJOaUobr8KG--

From sthaug@nethelp.no  Sat Dec 24 06:53:47 2011
Return-Path: <sthaug@nethelp.no>
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 BE21221F84CD for <ipv6@ietfa.amsl.com>; Sat, 24 Dec 2011 06:53:47 -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 pTolmkujrBQg for <ipv6@ietfa.amsl.com>; Sat, 24 Dec 2011 06:53:47 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id C7D9A21F84CC for <ipv6@ietf.org>; Sat, 24 Dec 2011 06:53:46 -0800 (PST)
Received: (qmail 47354 invoked from network); 24 Dec 2011 14:53:44 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 24 Dec 2011 14:53:44 -0000
Date: Sat, 24 Dec 2011 15:53:44 +0100 (CET)
Message-Id: <20111224.155344.41656386.sthaug@nethelp.no>
To: i.grok@comcast.net
Subject: Re: IPv6 Router Advertisement Option for NTP Server Configuration
From: sthaug@nethelp.no
In-Reply-To: <20111224142506.GA2954@odin.ulthar.us>
References: <7C362EEF9C7896468B36C9B79200D8350D027BA76A@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF439A9.4070502@dougbarton.us> <20111224142506.GA2954@odin.ulthar.us>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
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: Sat, 24 Dec 2011 14:53:47 -0000

> As it is today, to use DHCPv6 the way I want, I must first have my host
> get an IP (the wrong one), figure out what DUID it used, and reconfigure
> my server to give it the one I want it to have. With RA, I don't assign
> the address, but to know what it is, I just look up its MAC address and
> I'm done. With DHCPv4, I look up its MAC address, add it to my server
> configuration and I'm done.
> 
> I don't really care if it's a MAC address per se, but I don't want to
> have to deal with DUID change because of OS reinstallation, change of
> client software, dual-boot, removal & re-adding of the connection
> definition, etc. I can think of reasons why it might be nice to have
> different DUIDs for different OS's, so I don't object to the option, but
> in most cases the current spec hurts (me) more than it helps.

I'm amazed at how the DUID was supposed to be "better than" (more
stable than) a MAC address - and therefore the MAC address wouldn't
be needed), but ends up being worse in too many cases. 

Steinar Haug, Nethelp consulting, sthaug@nethelp.no


From fgont@si6networks.com  Sat Dec 24 11:07:10 2011
Return-Path: <fgont@si6networks.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 5100421F844F for <ipv6@ietfa.amsl.com>; Sat, 24 Dec 2011 11:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.569
X-Spam-Level: 
X-Spam-Status: No, score=-1.569 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992]
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 nJ2OkUMTCaiZ for <ipv6@ietfa.amsl.com>; Sat, 24 Dec 2011 11:07:09 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 12EA721F844E for <ipv6@ietf.org>; Sat, 24 Dec 2011 11:07:08 -0800 (PST)
Received: from [190.48.214.189] (helo=[192.168.123.102]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1ReWvv-0002iS-3A; Sat, 24 Dec 2011 20:07:03 +0100
Message-ID: <4EF5647B.6070903@si6networks.com>
Date: Sat, 24 Dec 2011 02:34:51 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: Florian Weimer <fweimer@bfk.de>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com> <82fwgfk1ev.fsf@mid.bfk.de>	<4EF0FFDF.6010703@gont.com.ar> <82d3bfbm5l.fsf@mid.bfk.de>
In-Reply-To: <82d3bfbm5l.fsf@mid.bfk.de>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 24 Dec 2011 19:07:10 -0000

Hi, Florian,

On 12/23/2011 07:46 AM, Florian Weimer wrote:
>> That aside, I don't know whether e.g. NAT64 or the like used this
>> (.e.g, whether they are used for transition technologies as envisioned
>> in RFC 2460). However, it might also be the case that such "atomic
>> fragments" are generated when communicating through networks that do
>> not really have a MTU >= 1280. In such scenarios there might be some
>> for of gateway that sends the ICMPv6 PTB advertising a Next-Hop MTU
>> smaller than 1280, thus resulting in atomic fragments (such that it's
>> easier for the "gateway" to fragment the IPv6 packets).
> 
> Yes, this seems a plausible explanation.  I wouldn't consider this
> actual use, rather network misconfiguration.  

Why?


> In my opinion, we need
> more evidence that these fragments actually serve a useful purpose.
> 
>> That aside, there's the proposal by Mark Andrews which would add yet
>> another use case for these atomic fragments.
> 
> Not really.  It's a workaround so that stateless IPv6 services are
> possible, despite this protocol weiredness.

Not sure what you mean.



>> I may be missing something, but: when sending from the v6 side to the v4
>> side, we can probably assume that only the low order 16 bits of the
>> Fragment Identification field are used (whether you set the rest of the
>> bits or not, it doesn't matter -- particularly if the Fragment
>> Identification for each destination is a linear function (as e.g. in the
>> algorithm proposed in the I-D)). That is, you don't really need to do
>> anything special with the high order bits.
> 
> Actually, atomic fragments aren't the problem, but the technology that
> serves as a justification for them.  If there are sub-1280 links which
> require network fragmentation and which fail to preserve the entire
> fragment ID, this happen to a packet which has already been fragmented
> by the sending host: One fragment is delivered over a regular IPv6 link
> and not fragmented further.  Another fragment is sent over a different
> link involving some v4 transition technology, causing further
> fragmentation and loss of the upper 16 bit of the fragment id.  The
> receiving node can reassemble the original packet only if it disregards
> the upper 16 bits in all those fragments.

Sorry, I cannot see why some packets would require going through a
translator, while others wouldn't. That is, if the intended destination
is really a v4 node, all packets meant to it will go through a
translator, If it's not, none will.

Am I missing something?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




From brian.e.carpenter@gmail.com  Sat Dec 24 12:06:47 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 4344B21F84D4 for <ipv6@ietfa.amsl.com>; Sat, 24 Dec 2011 12:06:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.531
X-Spam-Level: 
X-Spam-Status: No, score=-103.531 tagged_above=-999 required=5 tests=[AWL=0.068, 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 9k2qy1RpAqnV for <ipv6@ietfa.amsl.com>; Sat, 24 Dec 2011 12:06:46 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6B39C21F84CC for <ipv6@ietf.org>; Sat, 24 Dec 2011 12:06:46 -0800 (PST)
Received: by eekc14 with SMTP id c14so8973684eek.31 for <ipv6@ietf.org>; Sat, 24 Dec 2011 12:06:45 -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=sUKUPi3/4ovqoXqKSbM6AuGfNQ5qkJVFv92Y0RRLTv0=; b=q1U7C71ov3jppf3reJlAf+q5KXLpuRE73EYlqmwYMrQCViRpUiY30G1PKtRLBy4A+K jk5qKRThkSV6PrvU1zRvSk7SJANNAwLleZ/vFH4Q4QMyYWfFTv7+VYc5zSqmq5P2nmik RiqYfjycLy1mAcTXFktDs7MJFBWpmN33cB+/w=
Received: by 10.213.13.220 with SMTP id d28mr4068500eba.98.1324757205393; Sat, 24 Dec 2011 12:06:45 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id 13sm67426130eeu.1.2011.12.24.12.06.42 (version=SSLv3 cipher=OTHER); Sat, 24 Dec 2011 12:06:44 -0800 (PST)
Message-ID: <4EF630C6.6050405@gmail.com>
Date: Sun, 25 Dec 2011 09:06:30 +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: Fernando Gont <fgont@si6networks.com>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com>	<82fwgfk1ev.fsf@mid.bfk.de>	<4EF0FFDF.6010703@gont.com.ar>	<82d3bfbm5l.fsf@mid.bfk.de> <4EF5647B.6070903@si6networks.com>
In-Reply-To: <4EF5647B.6070903@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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, 24 Dec 2011 20:06:47 -0000

On 2011-12-24 18:34, Fernando Gont wrote:
> Hi, Florian,
> 
> On 12/23/2011 07:46 AM, Florian Weimer wrote:
>>> That aside, I don't know whether e.g. NAT64 or the like used this
>>> (.e.g, whether they are used for transition technologies as envisioned
>>> in RFC 2460). However, it might also be the case that such "atomic
>>> fragments" are generated when communicating through networks that do
>>> not really have a MTU >= 1280. In such scenarios there might be some
>>> for of gateway that sends the ICMPv6 PTB advertising a Next-Hop MTU
>>> smaller than 1280, thus resulting in atomic fragments (such that it's
>>> easier for the "gateway" to fragment the IPv6 packets).
>> Yes, this seems a plausible explanation.  I wouldn't consider this
>> actual use, rather network misconfiguration.  
> 
> Why?

MTU <1280 is a complete breach of the IPv6 standard, so it is by
definition a misconfiguration.

   IPv6 requires that every link in the internet have an MTU of 1280
   octets or greater.  On any link that cannot convey a 1280-octet
   packet in one piece, link-specific fragmentation and reassembly must
   be provided at a layer below IPv6. [RFC 2460, sectioin 5].

     Brian

From rogerj@gmail.com  Sun Dec 25 06:06:14 2011
Return-Path: <rogerj@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 2F38B21F84FC for <ipv6@ietfa.amsl.com>; Sun, 25 Dec 2011 06:06:14 -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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 jvww0hFgJxG3 for <ipv6@ietfa.amsl.com>; Sun, 25 Dec 2011 06:06:13 -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 6DC5521F84FB for <ipv6@ietf.org>; Sun, 25 Dec 2011 06:06:13 -0800 (PST)
Received: by eaak10 with SMTP id k10so3976682eaa.31 for <ipv6@ietf.org>; Sun, 25 Dec 2011 06:06:12 -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=GRCHYLVimghheYqJXoY6FlLYkyliyl3imJ259eglqy8=; b=xUd836/kHFMtFa9O+nnDScAJLkeiuuZ3UjvoEHzr3JhLQUzS828GfP9JOuR48JasDN fKIE6jSFZBrP9UnGTbIfr3z4RyvbCE5+Zqw//AS51SG3We3h9C8j1/R2pAfn+itk5bIo ICT1StTJ2hWLSGBDHHqCMw6MZQxNLRtDW0iyA=
MIME-Version: 1.0
Received: by 10.204.145.86 with SMTP id c22mr5424484bkv.61.1324821972404; Sun, 25 Dec 2011 06:06:12 -0800 (PST)
Received: by 10.204.9.209 with HTTP; Sun, 25 Dec 2011 06:06:11 -0800 (PST)
Received: by 10.204.9.209 with HTTP; Sun, 25 Dec 2011 06:06:11 -0800 (PST)
In-Reply-To: <4EF4344B.6040504@dougbarton.us>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A8@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF22786.2070908@dougbarton.us> <4EF2373B.6060905@gmail.com> <4EF24007.3030300@dougbarton.us> <4EF258A5.1040106@gmail.com> <4EF4344B.6040504@dougbarton.us>
Date: Sun, 25 Dec 2011 15:06:11 +0100
Message-ID: <CAKFn1SGXLB4CExh4i9bjN1oLNFv+AL3pKzy5SDgWdSeSACrvCw@mail.gmail.com>
Subject: Re: IPv6 Router Advertisement Option for Foobar Configuration
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: multipart/alternative; boundary=00151758f3ec0e48b504b4eb272e
Cc: 6man Mailing List <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: Sun, 25 Dec 2011 14:06:14 -0000

--00151758f3ec0e48b504b4eb272e
Content-Type: text/plain; charset=ISO-8859-1

On Dec 23, 2011 8:57 AM, "Doug Barton" <dougb@dougbarton.us> wrote:
<snip>
> What I *am* saying is that extending RA is always the *wrong* answer.

Yes it is. Keep RA simple and lets solve "problems" elsewhere, dhcp is the
current tool.


--- Roger J ---

--00151758f3ec0e48b504b4eb272e
Content-Type: text/html; charset=ISO-8859-1

<p><br>
On Dec 23, 2011 8:57 AM, &quot;Doug Barton&quot; &lt;<a href="mailto:dougb@dougbarton.us">dougb@dougbarton.us</a>&gt; wrote:<br>
&lt;snip&gt;<br>
&gt; What I *am* saying is that extending RA is always the *wrong* answer.</p>
<p>Yes it is. Keep RA simple and lets solve &quot;problems&quot; elsewhere, dhcp is the current tool.<br><br><br></p>
<p>--- Roger J ---<br>
</p>

--00151758f3ec0e48b504b4eb272e--

From fernando.gont.netbook.win@gmail.com  Mon Dec 26 00:43:34 2011
Return-Path: <fernando.gont.netbook.win@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 B35A021F8AB0 for <ipv6@ietfa.amsl.com>; Mon, 26 Dec 2011 00:43:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.53
X-Spam-Level: 
X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, 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 Ae2BHx6bZcJ8 for <ipv6@ietfa.amsl.com>; Mon, 26 Dec 2011 00:43:34 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 35B2A21F8A55 for <ipv6@ietf.org>; Mon, 26 Dec 2011 00:43:34 -0800 (PST)
Received: by ghbg18 with SMTP id g18so3836498ghb.31 for <ipv6@ietf.org>; Mon, 26 Dec 2011 00:43:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=dH9KLf1G+SAt5qimJJFzwGieAEB0sH+QLT/wfqs/mUo=; b=WvF/LCZrjZbYD1Fmq2fa7hTGwE89rU1o7kOYbdZTwZ9GyHrt0S/G7lphA0CXzMo6tJ aa0/toYJZ1z03jhe5icaGu/zcj9EkonEv3vK/vjKrW9mLei8C66Tprym2EKssA/pYcuJ T0t3e58ZP4Ab1PBztDuGeHPyKpHokcLtLrkZs=
Received: by 10.236.178.101 with SMTP id e65mr32014799yhm.40.1324889013798; Mon, 26 Dec 2011 00:43:33 -0800 (PST)
Received: from [10.42.43.100] ([209.13.155.122]) by mx.google.com with ESMTPS id k10sm3628889anb.22.2011.12.26.00.43.27 (version=SSLv3 cipher=OTHER); Mon, 26 Dec 2011 00:43:32 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4EF7D880.3090102@gont.com.ar>
Date: Sun, 25 Dec 2011 23:14:24 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Fragmentation-related security issues
References: <4EEA0342.2040608@si6networks.com>	<82fwgfk1ev.fsf@mid.bfk.de>	<4EF0FFDF.6010703@gont.com.ar>	<82d3bfbm5l.fsf@mid.bfk.de>	<4EF5647B.6070903@si6networks.com> <4EF630C6.6050405@gmail.com>
In-Reply-To: <4EF630C6.6050405@gmail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 26 Dec 2011 08:43:34 -0000

Hi, Brian,

On 12/24/2011 05:06 PM, Brian E Carpenter wrote:
>>>> That aside, I don't know whether e.g. NAT64 or the like used this
>>>> (.e.g, whether they are used for transition technologies as envisioned
>>>> in RFC 2460). However, it might also be the case that such "atomic
>>>> fragments" are generated when communicating through networks that do
>>>> not really have a MTU >= 1280. In such scenarios there might be some
>>>> for of gateway that sends the ICMPv6 PTB advertising a Next-Hop MTU
>>>> smaller than 1280, thus resulting in atomic fragments (such that it's
>>>> easier for the "gateway" to fragment the IPv6 packets).
>>> Yes, this seems a plausible explanation.  I wouldn't consider this
>>> actual use, rather network misconfiguration.  
>>
>> Why?
> 
> MTU <1280 is a complete breach of the IPv6 standard, so it is by
> definition a misconfiguration.

Well, as long as communication does work without requiring the sending
node to fragment packets to < 1280, the standard is not being "broken".

In the scenario I was describing, the underlying reason for receiving an
ICMPv6 PTB <1280 might be a network that doesn't support an MTU >= 1280
(and hence, that violates the standard). However, that's irrelevant as
long as the sending host is not required to fragment to <1280 for
communication to work.

That aside, from my perspecitive std violation != misconfiguration. A
misconfiguration is probably the result of an error (probably on the
side of the administrator), while an std violation such as the one that
we're possibly talking about is most likely the result of a deliverate
action (which is probably not going to be fixed even if it's reported).

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1



