
From nobody Thu May  1 00:14:08 2014
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ED361A0A6F for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 00:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8fdMv0kcNHNF for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 00:12:46 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 044E01A0A50 for <6man@ietf.org>; Thu,  1 May 2014 00:12:45 -0700 (PDT)
Received: (qmail 66636 invoked from network); 1 May 2014 07:12:42 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 1 May 2014 07:12:42 -0000
Date: Thu, 01 May 2014 09:12:42 +0200 (CEST)
Message-Id: <20140501.091242.74687867.sthaug@nethelp.no>
To: swmike@swm.pp.se
Subject: Re: Q about IPv4-mapped IPv6 address & MPLS 
From: sthaug@nethelp.no
In-Reply-To: <alpine.DEB.2.02.1405010836220.29282@uplift.swm.pp.se>
References: <CF875D2F.1951A9%rajiva@cisco.com> <alpine.DEB.2.02.1405010836220.29282@uplift.swm.pp.se>
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
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/iIq8E8cOUsPcrKlGpaVLiiTYZ6A
Cc: mpls@ietf.org, v6ops@ietf.org, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 07:12:50 -0000

> http://tools.ietf.org/html/draft-itojun-v6ops-v4mapped-harmful-02
> 
> I realise this draft seems to have died, but I would never expect to see 
> packets with these addresses on the wire or in the routing table and if 
> they're there, I would want hosts/routers to drop them. Not doing this 
> seems to me it would open to all kinds of unwanted consequences when it 
> comes to filtering etc.

On the wire, definitely no. In the routing tables - ::ffff:127.0.0.0
is not expected, but other IPv4-mapped IPv6 address are possible, for
instance if you use 6VPE.

Steinar Haug, AS 2116


From nobody Thu May  1 01:59:52 2014
Return-Path: <gert@Space.Net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67FFA1A88E6 for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 01:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUhZil0A5F_j for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 01:59:42 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC241A6F2A for <6man@ietf.org>; Thu,  1 May 2014 01:59:42 -0700 (PDT)
X-Original-To: 6man@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 937CE62A44 for <6man@ietf.org>; Thu,  1 May 2014 10:59:39 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 5961C62A2C for <6man@ietf.org>; Thu,  1 May 2014 10:59:39 +0200 (CEST)
Received: (qmail 66840 invoked by uid 1007); 1 May 2014 10:59:39 +0200
Date: Thu, 1 May 2014 10:59:39 +0200
From: Gert Doering <gert@space.net>
To: "Rajiv Asati \(rajiva\)" <rajiva@cisco.com>
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Message-ID: <20140501085939.GG43641@Space.Net>
References: <CF875D2F.1951A9%rajiva@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CF875D2F.1951A9%rajiva@cisco.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/MxACanFO6LLxVG4k6XjQVBKg1-o
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 08:59:45 -0000

Hi,

On Thu, May 01, 2014 at 06:08:51AM +0000, Rajiv Asati (rajiva) wrote:
> We need your guidance on handling v4-mapped v6 addresses (section 2.5.5.2
> of [RFC4291]). 
> 
> 1. Should/Would they appear in IPv6 routing table?

"Yes and no".  It depends on the context - if the packet comes in and has
an IPv6 header, address lookup happens via the IPv6 routing table.  If 
a packet comes in with an IPv4 header, address lookup happens via the
IPv4 routing table.  

So, IPv4 should never "bleed over" to the IPv6 routing table, but if 
you happen to receive an IPv6 packet with a destination IPv6 address
in it's header of ::ffff:1.2.3.4, you'd either drop it right away,
or use the IPv6 routing table to find the destination.

The router itself should never ever source packets with a v4-mapped
destination address in the packet (see below).

> 2. Should an IPv6 packet with ::FFFF:127.0.0.0  be forwarded or dropped or
> treated as a loopback packet, if ever received?

Dropped.  v4-mapped is an internal representation of an IPv4 address
recevied on an ipv6 socket, and should never ever appear in packets on
the wire.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Thu May  1 02:02:36 2014
Return-Path: <gert@Space.Net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087121A6F04 for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 02:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-I3079bLOLb for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 02:02:19 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) by ietfa.amsl.com (Postfix) with ESMTP id 897B31A88E8 for <6man@ietf.org>; Thu,  1 May 2014 02:02:19 -0700 (PDT)
X-Original-To: 6man@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 63C0A62A53 for <6man@ietf.org>; Thu,  1 May 2014 11:02:17 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 370F862A43 for <6man@ietf.org>; Thu,  1 May 2014 11:02:17 +0200 (CEST)
Received: (qmail 67576 invoked by uid 1007); 1 May 2014 11:02:17 +0200
Date: Thu, 1 May 2014 11:02:17 +0200
From: Gert Doering <gert@space.net>
To: Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Message-ID: <20140501090217.GH43641@Space.Net>
References: <CF875D2F.1951A9%rajiva@cisco.com> <alpine.DEB.2.02.1405010836220.29282@uplift.swm.pp.se> <CF882A16.4EA36%hesham@elevatemobile.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CF882A16.4EA36%hesham@elevatemobile.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/4omwAjRObrwFgp_607zEfRaX4Hg
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 09:02:23 -0000

Hi,

On Thu, May 01, 2014 at 04:46:33PM +1000, Hesham Soliman wrote:
> >I realise this draft seems to have died, but I would never expect to see
> >packets with these addresses on the wire
> 
> => I recall an information RFC but don¹t remember the number. I agree they
> will most likely not appear on the wire.
> 
> > or in the routing table
> 
> => That¹s a different story. I don¹t think there is anything banning this,

If the packets are not going to appear on the wire, argueing about the
content of the routing table is a bit... theoretical.

I'd argue for internal representations of stuff to not use that format
either, as it will just confuse things.  The dual-stack API is bad enough
for operating system implementors (ran into a bunch of issues with Linux
recently) to avoid further use of v4-mapped stuff, anywhere.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Thu May  1 05:38:03 2014
Return-Path: <hesham@elevatemobile.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0C361A082F for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 05:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id efAo24-D6oQy for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 05:37:30 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id 369301A0850 for <6man@ietf.org>; Thu,  1 May 2014 05:37:27 -0700 (PDT)
Received: from [203.219.211.243] (helo=[192.168.0.8]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1WfqEs-0000hA-7Z; Thu, 01 May 2014 22:37:22 +1000
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Thu, 01 May 2014 22:37:12 +1000
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
From: Hesham Soliman <hesham@elevatemobile.com>
To: Gert Doering <gert@space.net>
Message-ID: <CF887CB6.4EA52%hesham@elevatemobile.com>
Thread-Topic: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
References: <CF875D2F.1951A9%rajiva@cisco.com> <alpine.DEB.2.02.1405010836220.29282@uplift.swm.pp.se> <CF882A16.4EA36%hesham@elevatemobile.com> <20140501090217.GH43641@Space.Net>
In-Reply-To: <20140501090217.GH43641@Space.Net>
Mime-version: 1.0
Content-type: text/plain; charset="EUC-KR"
Content-transfer-encoding: quoted-printable
X-Authenticated-User: hesham@elevatemobile.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/_jtnBqfkr_DNhRKWCV9txDTF19I
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 12:37:31 -0000

>Hi,
>
>On Thu, May 01, 2014 at 04:46:33PM +1000, Hesham Soliman wrote:
>> >I realise this draft seems to have died, but I would never expect to
>>see
>> >packets with these addresses on the wire
>>=20
>> =3D> I recall an information RFC but don=A9=F6t remember the number. I agree
>>they
>> will most likely not appear on the wire.
>>=20
>> > or in the routing table
>>=20
>> =3D> That=A9=F6s a different story. I don=A9=F6t think there is anything banning
>>this,
>
>If the packets are not going to appear on the wire, argueing about the
>content of the routing table is a bit... theoretical.

=3D> Of course it is. In theory we have no business mandating what hosts
should do internally, we can discuss best practices ..etc. The question
was whether it can happen and it can.

Hesham

>
>I'd argue for internal representations of stuff to not use that format
>either, as it will just confuse things.  The dual-stack API is bad enough
>for operating system implementors (ran into a bunch of issues with Linux
>recently) to avoid further use of v4-mapped stuff, anywhere.
>
>Gert Doering
>        -- NetMaster
>--=20
>have you enabled IPv6 on something today...?
>
>SpaceNet AG                        Vorstand: Sebastian v. Bomhard
>Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A.
>Grundner-Culemann
>D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
>Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279



From nobody Thu May  1 09:46:29 2014
Return-Path: <pat.kinney@kinneyconsultingllc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C61321A08F2; Thu,  1 May 2014 09:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dcMg-IoB5SL1; Thu,  1 May 2014 09:39:51 -0700 (PDT)
Received: from p3plsmtpa07-07.prod.phx3.secureserver.net (p3plsmtpa07-07.prod.phx3.secureserver.net [173.201.192.236]) by ietfa.amsl.com (Postfix) with ESMTP id D40C61A073F; Thu,  1 May 2014 09:39:50 -0700 (PDT)
Received: from [10.0.1.55] ([99.110.37.26]) by p3plsmtpa07-07.prod.phx3.secureserver.net with  id wgfj1n0080ZqqBn01gfkgL; Thu, 01 May 2014 09:39:48 -0700
Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_47ACDA0F-043C-4C37-8092-0F351C31649F"
From: Pat Kinney <pat.kinney@kinneyconsultingllc.com>
In-Reply-To: <CAMsDxWRgNoWdaRaZz=tOuWQ+ucCfFE7EnHxbbjBvBR64xoF_dQ@mail.gmail.com>
Date: Thu, 1 May 2014 11:39:42 -0500
Message-Id: <E3685BDE-AD30-4E4D-A224-B5863CBEAC5C@kinneyconsultingllc.com>
References: <534D4F7A.3040605@cox.net> <CAH7SZV9WeQmuaHvUZ35_ySL4ak4+SDfbmpMbXgqQL+C833sTGw@mail.gmail.com> <1397607559.92815.YahooMailNeo@web120004.mail.ne1.yahoo.com> <CAP+sJUfx6=-22+A_=M_v3iSf6piGeyHkF2_BPm2ntbWnCEhTSw@mail.gmail.com> <CAMsDxWRgNoWdaRaZz=tOuWQ+ucCfFE7EnHxbbjBvBR64xoF_dQ@mail.gmail.com>
To: "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/tsMeSIc19dqAoeSF9IlTCIuREOA
X-Mailman-Approved-At: Thu, 01 May 2014 09:46:26 -0700
Cc: Thubert Pascal <pthubert@cisco.com>, roll <roll@ietf.org>, Ines Robles <mariainesrobles@googlemail.com>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 16:39:54 -0000

--Apple-Mail=_47ACDA0F-043C-4C37-8092-0F351C31649F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Dear All;

Over the past 8 years ISA100 has been involved with wireless industrial =
networks using battery operated wireless modules that must last at least =
10 years on a single battery.  Since these applications are typically =
low data rate (50 - 250 kb/s), and TDMA for low energy usage, these =
industrial networks use the IEEE 802.15.4 MAC/PHY standard.  Since =
industrial environments contain significant interference, using shorter =
packet durations significantly increase the likelihood of a successful =
message receipt, dramatically reducing retries which consume energy and =
reduce network throughput.
=20
ISA100 worked with the IETF to allow ISA's first wireless standard, =
ISA100.11a that is now shipping, to use IPv6 with the 6LoWPAN header =
compression (RFC6282) at the network layer with a string critical =
requirement to keep the frame size minimal so as to stay under the 127 =
bytes limit as per the 802.15.4.  ISA100 would now like to consider a =
wireless industrial standard using the full 6TiSCH suite and in =
particular RPL (RFC 6550) and the backbone router technology; however =
using the RPL option in a Hop-by-Hop header as proposed in RFC6553 would =
add an additional 8 bytes to the packet.  Regretfully, this additional =
overhead can't be tolerated since it would result in security =
configuration packets (and others) being larger than the 127 byte limit.=20=

=20
As a co-chair of ISA100 as well as the editor of ISA100.11a-2011, I =
would ask the IETF 6man to seriously consider adopting =
draft-thubert-6man-flow-label-for-rpl that combines optimally with =
RFC6282 for a minima overhead in the compressed packet.=20

Pat Kinney
Kinney Consulting LLC
IEEE 802.15 WG vice chair, TG chair
ISA100.11a WG chair
O: +1.847.960.3715
pat.kinney@kinneyconsultingllc.com


On Apr 17, 2014, at 9:26 AM, Pascal Thubert (pthubert) =
<pthubert@cisco.com> wrote:

Dear all;
=20
Considering the support we have at 6TiSCH and ROLL for the work, I =
published draft-thubert-6man-flow-label-for-rpl-00.txt to the 6MAN WG.
The main discussion is probably to confirm whether our proposed use of =
the flow label inside the RPL domain is compatible with the goals that =
are achieved by RFC6437. Let us continue the discussion there from now =
on.
=20
Cheers,
=20
Pascal
=20
From: xvilajosana@gmail.com [mailto:xvilajosana@gmail.com] On Behalf Of =
Xavier Vilajosana
Sent: jeudi 17 avril 2014 10:00
To: Ines Robles
Cc: Pascal Thubert (pthubert); 6tisch@ietf.org; roll
Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL =
information in data packets
=20
+1 I think this is more than needed. In addition RFC 6282 defines how =
header compression needs to be handled together with extension headers. =
I think this is not clear and leads to confusions (afecting already some =
wireshark dissectors). The use of flow label will solve several problems =
at once.
=20
X.
=20
=20
=20

2014-04-16 22:44 GMT+02:00 Ines Robles <mariainesrobles@googlemail.com>:
+1
=20
Ines
=20
2014-04-15 21:19 GMT-03:00 Qin Wang <qinwang6top@yahoo.com>:
+1
=20
Qin
On Wednesday, April 16, 2014 1:47 AM, Prof. Diego Dujovne =
<diego.dujovne@mail.udp.cl> wrote:
+1 !
=20

2014-04-15 12:25 GMT-03:00 Tom Phinney <tom.phinney@cox.net>:
+1 for sure. The flow label has always been the preferable method for =
me, and I suspect for others with knowledge of how it is used in =
ISA100.11a.
=3D=3D=3D
=20
On 2014.04.15 07:25, Pascal Thubert (pthubert) wrote:
Dear all:
=20
As some of you remember, the RPL specification has changed over time WRT =
to the location of the information that RPL places in the data packets. =
We started with the flow label but these were the days when what became =
RFC 6437 was being defined at 6MAN, so we shied away and defined the HbH =
technique that is now specified as RFC 6553.
=20
We=92ll note that the RPL option defined in RFC 6553 takes 6 octets, and =
with the HbH hdr we end up with 8 extra octets. An extra IP-in-IP =
encapsulation is required on top of that unless both endpoints are in =
the same RPL domain. All this overhead may be acceptable when power is =
available and the PHY allows for larger frames, but in traditional =
battery-operated 15.4 with ~ 80 bytes usable per frame, my experience =
from integrating 6LoWPAN HC with ISA100.11a says that all these extra =
bytes will be on the way of the 6TiSCH adoption.
=20
Still, both RFC 6550 and RFC 6552 are designed to allow for an alternate =
technique and in particular for the use of the flow label, as is =
elaborated in =
http://tools.ietf.org/html/draft-thubert-roll-flow-label-02 . Using the =
flow label reduces the cost of the RPL information dramatically, down to =
a level that is probably acceptable for the target SDOs.
=20
So my plan for now is to move the flow label draft to 6MAN and prepare =
for a hot season, and I=92m looking for support from both 6TiSCH and =
ROLL to back me up from the start.  Yes, you can help!
=20
Please +1 if you agree we need this work to happen, and/or provide any =
suggestion.
=20
Cheers,
=20
Pascal
=20

_______________________________________________
6tisch mailing list
6tisch@ietf.org
https://www.ietf.org/mailman/listinfo/6tisch
=20

_______________________________________________
6tisch mailing list
6tisch@ietf.org
https://www.ietf.org/mailman/listinfo/6tisch




--=20
DIEGO DUJOVNE
Acad=E9mico Escuela de Ingenier=EDa en Inform=E1tica y =
Telecomunicaciones
Facultad de Ingenier=EDa UDP
www.ingenieria.udp.cl
(56 2) 676 8125
=20
_______________________________________________
6tisch mailing list
6tisch@ietf.org
https://www.ietf.org/mailman/listinfo/6tisch
=20


_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll

=20

_______________________________________________
6tisch mailing list
6tisch@ietf.org
https://www.ietf.org/mailman/listinfo/6tisch

=20


--Apple-Mail=_47ACDA0F-043C-4C37-8092-0F351C31649F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><i style=3D"font-family: Calibri, sans-serif; =
font-size: 11pt;">Dear All;</i></div><div><i style=3D"font-family: =
Calibri, sans-serif; font-size: 11pt;"><br></i></div><i =
style=3D"font-family: Calibri, sans-serif; font-size: 11pt;">Over the =
past 8 years ISA100 has been involved with wireless industrial networks =
using battery operated wireless modules that must last at least 10 years =
on a single battery. &nbsp;Since these applications are typically low =
data rate (50 - 250 kb/s), and TDMA for low energy usage, these =
industrial networks use the IEEE 802.15.4 MAC/PHY standard. &nbsp;Since =
industrial environments contain significant interference, using shorter =
packet durations significantly increase the likelihood of a successful =
message receipt, dramatically reducing retries which consume energy and =
reduce network throughput.</i><br><span style=3D"font-family: Calibri, =
sans-serif; font-size: 11pt;">&nbsp;</span><br><i style=3D"font-family: =
Calibri, sans-serif; font-size: 11pt;">ISA100 worked with the IETF to =
allow ISA's first wireless standard, ISA100.11a that is now shipping, to =
use IPv6 with the 6LoWPAN header compression (RFC6282) at the network =
layer with a string critical requirement to keep the frame size minimal =
so as to stay under the 127 bytes limit as per the 802.15.4. =
&nbsp;ISA100 would now like to consider a wireless industrial standard =
using the full 6TiSCH suite and in particular RPL (RFC 6550) and the =
backbone router technology; however using the RPL option in a Hop-by-Hop =
header as proposed in RFC6553 would add an additional 8 bytes to the =
packet. &nbsp;Regretfully, this additional overhead can't be tolerated =
since it would result in security configuration packets (and others) =
being larger than the 127 byte limit.&nbsp;</i><br><span =
style=3D"font-family: Calibri, sans-serif; font-size: =
11pt;">&nbsp;</span><br><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p></o:p></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p></o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><i>As a co-chair of =
ISA100 as well as the editor of ISA100.11a-2011, I would ask the IETF =
6man to seriously consider =
adopting&nbsp;</i>draft-thubert-6man-flow-label-for-rpl<i>&nbsp;that =
combines optimally with RFC6282 for a minima overhead in the compressed =
packet.&nbsp;</i></div></div></div><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica;  font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica;  font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica;  font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div><span class=3D"Apple-style-span" =
style=3D"font-size: 12px; "><div><br></div><div>Pat =
Kinney</div><div><b><i>Kinney Consulting LLC</i></b></div><div>IEEE =
802.15 WG vice chair, TG chair</div><div>ISA100.11a WG =
chair</div><div>O: +1.847.960.3715</div><div><a =
href=3D"mailto:pat.kinney@kinneyconsultingllc.com" =
style=3D"text-decoration: none; =
">pat.kinney@kinneyconsultingllc.com</a></div></span></div></div><div><br>=
</div></div></span></div></span></div></span><br =
class=3D"Apple-interchange-newline"></span></div><div><div>On Apr 17, =
2014, at 9:26 AM, Pascal Thubert (pthubert) &lt;<a =
href=3D"mailto:pthubert@cisco.com">pthubert@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered =
medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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]-->

<div 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;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">Dear all;<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">&nbsp;</span></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">Considering the support we have at 6TiSCH and ROLL =
for the work, I published draft-thubert-6man-flow-label-for-rpl-00.txt =
to the 6MAN WG.<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">The main discussion is probably to confirm whether =
our proposed use of the flow label inside the RPL domain is compatible =
with the goals that are achieved by
 RFC6437. Let us continue the discussion there from now =
on.<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">&nbsp;</span></p><p class=3D"MsoNormal"><span =
lang=3D"FR" =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">Cheers,<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span lang=3D"FR" =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">&nbsp;</span></p><p class=3D"MsoNormal"><span =
lang=3D"FR" =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">Pascal<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1F497D">&nbsp;</span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm"><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-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;"> <a href=3D"mailto:xvilajosana@gmail.com">xvilajosana@gmail.com</a>=
 [<a =
href=3D"mailto:xvilajosana@gmail.com">mailto:xvilajosana@gmail.com</a>]
<b>On Behalf Of </b>Xavier Vilajosana<br>
<b>Sent:</b> jeudi 17 avril 2014 10:00<br>
<b>To:</b> Ines Robles<br>
<b>Cc:</b> Pascal Thubert (pthubert); <a =
href=3D"mailto:6tisch@ietf.org">6tisch@ietf.org</a>; roll<br>
<b>Subject:</b> Re: [6tisch] [Roll] Support of flow label to carry the =
RPL information in data packets<o:p></o:p></span></p>
</div>
</div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div><p class=3D"MsoNormal">+1 I think this is more than needed. In =
addition RFC 6282 defines how header compression needs to be handled =
together with extension headers. I think this is not clear and leads to =
confusions (afecting already some wireshark dissectors).
 The use of flow label will solve several problems at =
once.<o:p></o:p></p>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal">X.<o:p></o:p></p>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<div><p class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div><p class=3D"MsoNormal">2014-04-16 22:44 GMT+02:00 Ines Robles =
&lt;<a href=3D"mailto:mariainesrobles@googlemail.com" =
target=3D"_blank">mariainesrobles@googlemail.com</a>&gt;:<o:p></o:p></p>
<div><p class=3D"MsoNormal">+1<o:p></o:p></p>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal">Ines<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div><p class=3D"MsoNormal">2014-04-15 21:19 GMT-03:00 Qin Wang &lt;<a =
href=3D"mailto:qinwang6top@yahoo.com" =
target=3D"_blank">qinwang6top@yahoo.com</a>&gt;:<o:p></o:p></p>
<div>
<div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;">+1<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;;color:#888888">&nbsp;</span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;;color:#888888">Qin<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">On =
Wednesday, April 16, 2014 1:47 AM, Prof. Diego Dujovne &lt;<a =
href=3D"mailto:diego.dujovne@mail.udp.cl" =
target=3D"_blank">diego.dujovne@mail.udp.cl</a>&gt; wrote:</span><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;"><o:p></=
o:p></span></p>
</div>
<div>
<div>
<div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">+1 =
!<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
/span></p>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">2014-04=
-15 12:25 GMT-03:00 Tom Phinney &lt;<a href=3D"mailto:tom.phinney@cox.net"=
 target=3D"_blank">tom.phinney@cox.net</a>&gt;:<o:p></o:p></span></p>
<div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">+1 =
for sure. The flow label has always been the preferable method for me, =
and I suspect for others with knowledge of how it is used in =
ISA100.11a.<br>
=3D=3D=3D<o:p></o:p></span></p>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
/span></p>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">On <a =
href=3D"tel:2014.04.15%2007" target=3D"_blank">
2014.04.15 07</a>:25, Pascal Thubert (pthubert) =
wrote:<o:p></o:p></span></p>
</div>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">Dear =
all:<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">As =
some of you remember, the RPL specification has changed over time WRT to =
the location of the information that RPL places in the data packets. We =
started with the flow label but these
 were the days when what became RFC 6437 was being defined at 6MAN, so =
we shied away and defined the HbH technique that is now specified as RFC =
6553.
<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">We=92ll=
 note that the RPL option defined in RFC 6553 takes 6 octets, and with =
the HbH hdr we end up with 8 extra octets. An extra IP-in-IP =
encapsulation is required on top of that unless
 both endpoints are in the same RPL domain. All this overhead may be =
acceptable when power is available and the PHY allows for larger frames, =
but in traditional battery-operated 15.4 with ~ 80 bytes usable per =
frame, my experience from integrating 6LoWPAN HC
 with ISA100.11a says that all these extra bytes will be on the way of =
the 6TiSCH adoption.
<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
o:p></o:p></span></p>
</div>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">Still, =
both RFC 6550 and RFC 6552 are designed to allow for an alternate =
technique and in particular for the use of the flow label, as is =
elaborated in
<a href=3D"http://tools.ietf.org/html/draft-thubert-roll-flow-label-02" =
target=3D"_blank">
http://tools.ietf.org/html/draft-thubert-roll-flow-label-02</a> . Using =
the flow label reduces the cost of the RPL information dramatically, =
down to a level that is probably acceptable for the target =
SDOs.<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">So my =
plan for now is to move the flow label draft to 6MAN and prepare for a =
hot season, and I=92m looking for support from both 6TiSCH and ROLL to =
back me up from the start. &nbsp;Yes, you can
 help! <o:p></o:p></span></p>
</div>
<div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">Please =
+1 if you agree we need this work to happen, and/or provide any =
suggestion.<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
o:p></o:p></span></p>
</div>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">Cheers,=
<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">Pascal<=
o:p></o:p></span></p>
</div>
</div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
/span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>6tisch mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:6tisch@ietf.org" =
target=3D"_blank">6tisch@ietf.org</a><o:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/6tisch</a><o:p></o=
:p></pre>
</blockquote><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
/span></p>
</div>
</div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;"><br>
_______________________________________________<br>
6tisch mailing list<br>
<a href=3D"mailto:6tisch@ietf.org" =
target=3D"_blank">6tisch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/6tisch</a><o:p></o=
:p></span></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;"><br>
<br clear=3D"all">
<br>
-- <br>
DIEGO DUJOVNE<br>
Acad=E9mico Escuela de Ingenier=EDa en Inform=E1tica y =
Telecomunicaciones<br>
Facultad de Ingenier=EDa UDP<br>
<a href=3D"http://www.ingenieria.udp.cl/" =
target=3D"_blank">www.ingenieria.udp.cl</a><br>
<a href=3D"tel:%2856%202%29%20676%208125" target=3D"_blank">(56 2) 676 =
8125</a><o:p></o:p></span></p>
</div>
</div>
</div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
/span></p>
<div><p class=3D"MsoNormal"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">_______=
________________________________________<br>
6tisch mailing list<br>
<a href=3D"mailto:6tisch@ietf.org" =
target=3D"_blank">6tisch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/6tisch</a><o:p></o=
:p></span></p>
</div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;<=
/span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org" target=3D"_blank">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/roll</a><o:p></o:p=
></p>
</div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
6tisch mailing list<br>
<a href=3D"mailto:6tisch@ietf.org">6tisch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/6tisch</a><o:p></o=
:p></p>
</div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>

</div></div><br></body></html>=

--Apple-Mail=_47ACDA0F-043C-4C37-8092-0F351C31649F--


From nobody Thu May  1 13:46:54 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A5621A0990; Thu,  1 May 2014 13:46:51 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sx7D12ddkuHm; Thu,  1 May 2014 13:46:49 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id C7FAE1A093E; Thu,  1 May 2014 13:46:49 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id fp1so3644114pdb.9 for <multiple recipients>; Thu, 01 May 2014 13:46:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=q4FEWSZC9vwYJLDdeQ1/jPvgcYHqofYoJYJ6ed0Jz/w=; b=AsCKhMR9N/AcugBVP+j2w8Ib0E+yd2WpE906gcYhS+WsA6mBsV+WoeU/WW10OTEpbY LJmX0Y+69eWseQrgcEil4wdHzS6gqdgN4ZEDJwsj5u8TGwVgaeTQVVpGBXOsNtLl9nSR 7SGTKWPUG9AT8R3bWsUsw5XpBMIIicOhe1b9O8tWUeyJasKUsZrp02hAeJHkufMdpKxp ZRIMTXutmMLn5V/Q4tnMlELQfUCK3gh9mPgPCVG45KnvNamA+FiwIxD3PmA5R5xrWcOy GQcMf9fBbxaa6/7BeBOFhIKOTaZqupFC86r7WFeOsdzgF4OzsLyXrH+RzPFrMXGeoiLH RGlw==
X-Received: by 10.66.146.170 with SMTP id td10mr25414186pab.105.1398977207665;  Thu, 01 May 2014 13:46:47 -0700 (PDT)
Received: from [192.168.178.20] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id ss2sm164748278pab.8.2014.05.01.13.46.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 13:46:46 -0700 (PDT)
Message-ID: <5362B2BD.7060602@gmail.com>
Date: Fri, 02 May 2014 08:46:53 +1200
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: Gert Doering <gert@space.net>
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
References: <CF875D2F.1951A9%rajiva@cisco.com> <20140501085939.GG43641@Space.Net>
In-Reply-To: <20140501085939.GG43641@Space.Net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/7TZweDpo7pnvk_SA0kvm7ynwAAQ
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 20:46:51 -0000

On 01/05/2014 20:59, Gert Doering wrote:
> Hi,
> 
> On Thu, May 01, 2014 at 06:08:51AM +0000, Rajiv Asati (rajiva) wrote:
>> We need your guidance on handling v4-mapped v6 addresses (section 2.5.5.2
>> of [RFC4291]). 
>>
>> 1. Should/Would they appear in IPv6 routing table?
> 
> "Yes and no".  It depends on the context - if the packet comes in and has
> an IPv6 header, address lookup happens via the IPv6 routing table.  If 
> a packet comes in with an IPv4 header, address lookup happens via the
> IPv4 routing table.  
> 
> So, IPv4 should never "bleed over" to the IPv6 routing table, but if 
> you happen to receive an IPv6 packet with a destination IPv6 address
> in it's header of ::ffff:1.2.3.4, you'd either drop it right away,
> or use the IPv6 routing table to find the destination.
> 
> The router itself should never ever source packets with a v4-mapped
> destination address in the packet (see below).
> 
>> 2. Should an IPv6 packet with ::FFFF:127.0.0.0  be forwarded or dropped or
>> treated as a loopback packet, if ever received?
> 
> Dropped.  v4-mapped is an internal representation of an IPv4 address
> recevied on an ipv6 socket, and should never ever appear in packets on
> the wire.

Nobody seems to have mentioned RFC 4038, which makes this very clear.
These addresses are an artefact and have no place in the routing
system as such, and still less on the wire.

    Brian


From nobody Thu May  1 13:54:01 2014
Return-Path: <rajiva@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD651A6FA7; Thu,  1 May 2014 13:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2TvX5G1glsY5; Thu,  1 May 2014 13:53:55 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 269AB1A093E; Thu,  1 May 2014 13:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1739; q=dns/txt; s=iport; t=1398977633; x=1400187233; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=alqSDzlX9MhUwXav2nw6kw4kGN8px33LmluVDrbdgdw=; b=S0BdYAEpDuMZV455Q3iMnhPJK5vNljlgKXuhRFrxIKFJOIIRvulNpJow 3gQ0M/1Edaq1e2E4syXgE22vL4OTuLBa8mfU9ocUgD4qpmpuB7i+bYyjl DVwEAwsNlB6QoFbLl4Pbru8mczVGLXITeBBIy4K5JXelRVVnecp33H9Va o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAEizYlOrRDoG/2dsb2JhbABagwZPV8RagRQWdIIlAQEBAwE6PwwEAgEIEQMBAh8QMh0IAgQBDQWIOQcBDcluF45SBwaEMwEDhFmUVoE8kTKDM4Ir
X-IronPort-AV: E=Sophos;i="4.97,966,1389744000"; d="scan'208";a="109108251"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 01 May 2014 20:53:52 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s41Krptj019847 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 1 May 2014 20:53:52 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.41]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Thu, 1 May 2014 15:53:50 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Christian Huitema <huitema@microsoft.com>, "6man@ietf.org" <6man@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: Q about IPv4-mapped IPv6 address & MPLS 
Thread-Topic: Q about IPv4-mapped IPv6 address & MPLS 
Thread-Index: AQHPZQPSCzbpGVI9y0mONiS9cBGpH5srRWcQgAEANQA=
Date: Thu, 1 May 2014 20:53:49 +0000
Message-ID: <CF882BEC.195BC5%rajiva@cisco.com>
References: <CF875D2F.1951A9%rajiva@cisco.com> <fd46bfdc1db843d2b34ae7a7e06c0c20@BLUPR03MB424.namprd03.prod.outlook.com>
In-Reply-To: <fd46bfdc1db843d2b34ae7a7e06c0c20@BLUPR03MB424.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.82.218.19]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B3272716FAD4DF4194E8B1CB6EBF7498@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/DQ4t92-7v3tGcFMhDjiZf0L6XAY
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 20:53:56 -0000

Hi Christian,

Thanks for the pointer. WKPs surely qualify to be in in the RIB/FIB and
label allocations.=20

However, v4-mapped v6 addresses are not used by RFC 6052. :o
=20

--=20
Cheers,
Rajiv Asati
Distinguished Engineer, Cisco





-----Original Message-----
From: Christian Huitema <huitema@microsoft.com>
Date: Thursday, May 1, 2014 at 2:44 AM
To: Rajiv Asati <rajiva@cisco.com>, "6man@ietf.org" <6man@ietf.org>,
"v6ops@ietf.org" <v6ops@ietf.org>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: RE: Q about IPv4-mapped IPv6 address & MPLS

>> We need your guidance on handling v4-mapped v6 addresses (section
>>2.5.5.2
>> of [RFC4291]).=20
>>
>> 1. Should/Would they appear in IPv6 routing table?
>> 2. Should an IPv6 packet with ::FFFF:127.0.0.0  be forwarded or dropped
>>or
>>      treated as a loopback packet, if ever received?
>>
>> The answer to Q#1 will help MPLS WG to decide the proper handling of
>> v4-mapped v6 addresses in LDPv6 draft section 7 1st para.
>> http://tools.ietf.org/html/draft-ietf-mpls-ldp-ipv6-12#section-7 *
>
>You may want to check RFC 6052, IPv6 Addressing of IPv4/IPv6 Translators.
>RFC 6052 updates RFC4291, and lets translators construct domain specific
>addresses that can actually be used in the routing tables. It also
>includes an answer to your loopback packet question:
>
>   The Well-Known Prefix MUST NOT be used to represent non-global IPv4
>   addresses, such as those defined in [RFC1918] or listed in Section 3
>   of [RFC5735].  Address translators MUST NOT translate packets in
>   which an address is composed of the Well-Known Prefix and a non-
>   global IPv4 address; they MUST drop these packets.
>
>-- Christian Huitema
>
>
>


From nobody Thu May  1 14:10:38 2014
Return-Path: <simon@per.reau.lt>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 422861A7D81; Thu,  1 May 2014 14:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSDUeGsRvbXR; Thu,  1 May 2014 14:10:27 -0700 (PDT)
Received: from nomis80.org (nomis80.org [23.92.21.33]) by ietfa.amsl.com (Postfix) with ESMTP id 444661A0971; Thu,  1 May 2014 14:10:27 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:ada6:3fa9:d0fd:fbe0]) by nomis80.org (Postfix) with ESMTPSA id 97BCC10EAB; Thu,  1 May 2014 21:10:45 +0000 (UTC)
Message-ID: <5362B83F.4020808@per.reau.lt>
Date: Thu, 01 May 2014 17:10:23 -0400
From: Simon Perreault <simon@per.reau.lt>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: v6ops@ietf.org
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
References: <CF875D2F.1951A9%rajiva@cisco.com>
In-Reply-To: <CF875D2F.1951A9%rajiva@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/S_X5bpmYAnoK-Tp6ETdXauPD7TU
Cc: mpls@ietf.org, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 21:10:36 -0000

Le 2014-05-01 02:08, Rajiv Asati (rajiva) a écrit :
> The answer to Q#1 will help MPLS WG to decide the proper handling of
> v4-mapped v6 addresses in LDPv6 draft section 7 1st para.
> http://tools.ietf.org/html/draft-ietf-mpls-ldp-ipv6-12#section-7 *

Rajiv,

In addition to what the others have said, to provide very precise
guidance, I think this text in your draft...

   An LSR MUST NOT allocate and MUST NOT advertise FEC-Label bindings
   for link-local IPv6 address, and ignore such bindings, if ever
   received. An LSR MUST treat the IPv4-mapped IPv6 address, defined in
   section 2.5.5.2 of [RFC4291], the same as that of a global IPv6
   address and not mix it with the 'corresponding' IPv4 address.

...should be changed to:

   An LSR MUST NOT allocate and MUST NOT advertise FEC-Label bindings
   for link-local or IPv4-mapped IPv6 address, and ignore such
   bindings, if ever received.

Simon


From nobody Thu May  1 15:20:31 2014
Return-Path: <rajiva@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA6301A0948; Thu,  1 May 2014 15:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v6a3X7n5ZGhr; Thu,  1 May 2014 15:20:22 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5837D1A06DB; Thu,  1 May 2014 15:20:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1520; q=dns/txt; s=iport; t=1398982820; x=1400192420; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=k4S/nS0HaDlaEU0x2uJcZ98uVGbisT63Zg6f8W/d8qc=; b=LUJJBZHVxCSUVfdN0YGrobWgpYPJzdaPKsFuSCFYWOZSvOzAJbI8mO/+ FsGk4OfA7KwRtL1vwzBIZ4PMTQ6+4yQIIyFp/4UNuTZrdxbSBGSCs6o25 Sexfi0uYS1jihnH8nGaRfQ9Hrtw2qFLPp9OmJjvNKMYmxzWVcRbFkECmR I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFACTIYlOtJA2D/2dsb2JhbABagwZPvXOHPoEUFnSCJQEBAQMBAQEBawsFCwIBCBguJwslAgQOBYg5CA3JaBeOUgeDJIEVBIlMj2OBPJEygzM
X-IronPort-AV: E=Sophos;i="4.97,967,1389744000"; d="scan'208";a="321837749"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP; 01 May 2014 22:20:20 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s41MKJO7032112 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 1 May 2014 22:20:19 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.41]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Thu, 1 May 2014 17:20:19 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Simon Perreault <simon@per.reau.lt>
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Thread-Topic: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Thread-Index: AQHPZYHVKyuQb1xSnUicpDemuoOtD5ssTA69
Date: Thu, 1 May 2014 22:20:19 +0000
Message-ID: <A88E5272-6E81-420B-977A-DE8CF21E8829@cisco.com>
References: <CF875D2F.1951A9%rajiva@cisco.com>,<5362B83F.4020808@per.reau.lt>
In-Reply-To: <5362B83F.4020808@per.reau.lt>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/N9q72I9hWVPpmnWBJJe9CnpJfUs
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:20:23 -0000

Hi Simon,

Ditto. This is what I was about to suggest for Q#1. Thanks.=20

I wish there was something like that for ospfv3, isis, rip, BGP etc. too.=20

Cheers,
Rajiv

> On May 1, 2014, at 5:10 PM, "Simon Perreault" <simon@per.reau.lt> wrote:
>=20
> Le 2014-05-01 02:08, Rajiv Asati (rajiva) a =E9crit :
>> The answer to Q#1 will help MPLS WG to decide the proper handling of
>> v4-mapped v6 addresses in LDPv6 draft section 7 1st para.
>> http://tools.ietf.org/html/draft-ietf-mpls-ldp-ipv6-12#section-7 *
>=20
> Rajiv,
>=20
> In addition to what the others have said, to provide very precise
> guidance, I think this text in your draft...
>=20
>   An LSR MUST NOT allocate and MUST NOT advertise FEC-Label bindings
>   for link-local IPv6 address, and ignore such bindings, if ever
>   received. An LSR MUST treat the IPv4-mapped IPv6 address, defined in
>   section 2.5.5.2 of [RFC4291], the same as that of a global IPv6
>   address and not mix it with the 'corresponding' IPv4 address.
>=20
> ...should be changed to:
>=20
>   An LSR MUST NOT allocate and MUST NOT advertise FEC-Label bindings
>   for link-local or IPv4-mapped IPv6 address, and ignore such
>   bindings, if ever received.
>=20
> Simon
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Thu May  1 15:21:35 2014
Return-Path: <rajiva@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD3911A0948; Thu,  1 May 2014 15:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fGou2mUIlS-b; Thu,  1 May 2014 15:21:29 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id EE7331A09C3; Thu,  1 May 2014 15:21:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1716; q=dns/txt; s=iport; t=1398982884; x=1400192484; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=myYq2XzCSmfR0qTQjRtA3D652avJA/7IdtRy07C9q9c=; b=NxfuQKN55d1iNsknSrfUoa05TsgBXINv8Di+Ia0grH1+4KKCBcMJ0UjR z5l7UGgQARY7QZNO0v6juLiA3Rz3VEtLAj8iaCYuYfXJvYHvTSJs+J/FR 7VGD/A/LMmEWh3J4YCdAAZJx72n7rl1+dVt9FAm5GysHxYp0Ym/dAzmt7 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAK/HYlOtJA2N/2dsb2JhbABagwbGAIEUFnSCJQEBAQMBOj8FCwIBCBgeECERJQIEDgWILQMJCMMiDYZFF4w7gWQzB4MkgRUBA5c9gXKNE4VbgzM
X-IronPort-AV: E=Sophos;i="4.97,967,1389744000"; d="scan'208";a="40393657"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-4.cisco.com with ESMTP; 01 May 2014 22:21:23 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s41MLNSx024751 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 1 May 2014 22:21:23 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.41]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0123.003; Thu, 1 May 2014 17:21:23 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Thread-Topic: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Thread-Index: AQHPZRuxmza+wZtqAkG9xRAfqumSLZsshpGA///GlVc=
Date: Thu, 1 May 2014 22:21:22 +0000
Message-ID: <C1C2AD52-81C1-4BDB-87B6-550530F01389@cisco.com>
References: <CF875D2F.1951A9%rajiva@cisco.com> <20140501085939.GG43641@Space.Net>,<5362B2BD.7060602@gmail.com>
In-Reply-To: <5362B2BD.7060602@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/yk0yru0qJTk5V9WpQydGgTBmMw4
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Gert Doering <gert@space.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:21:30 -0000

Thanks, Brian. Which RFC 4038 section in particular should be referenced to=
?

Cheers,
Rajiv

> On May 1, 2014, at 4:47 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.=
com> wrote:
>=20
>> On 01/05/2014 20:59, Gert Doering wrote:
>> Hi,
>>=20
>>> On Thu, May 01, 2014 at 06:08:51AM +0000, Rajiv Asati (rajiva) wrote:
>>> We need your guidance on handling v4-mapped v6 addresses (section 2.5.5=
.2
>>> of [RFC4291]).=20
>>>=20
>>> 1. Should/Would they appear in IPv6 routing table?
>>=20
>> "Yes and no".  It depends on the context - if the packet comes in and ha=
s
>> an IPv6 header, address lookup happens via the IPv6 routing table.  If=20
>> a packet comes in with an IPv4 header, address lookup happens via the
>> IPv4 routing table. =20
>>=20
>> So, IPv4 should never "bleed over" to the IPv6 routing table, but if=20
>> you happen to receive an IPv6 packet with a destination IPv6 address
>> in it's header of ::ffff:1.2.3.4, you'd either drop it right away,
>> or use the IPv6 routing table to find the destination.
>>=20
>> The router itself should never ever source packets with a v4-mapped
>> destination address in the packet (see below).
>>=20
>>> 2. Should an IPv6 packet with ::FFFF:127.0.0.0  be forwarded or dropped=
 or
>>> treated as a loopback packet, if ever received?
>>=20
>> Dropped.  v4-mapped is an internal representation of an IPv4 address
>> recevied on an ipv6 socket, and should never ever appear in packets on
>> the wire.
>=20
> Nobody seems to have mentioned RFC 4038, which makes this very clear.
> These addresses are an artefact and have no place in the routing
> system as such, and still less on the wire.
>=20
>    Brian
>=20


From nobody Thu May  1 15:23:30 2014
Return-Path: <rajiva@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 721041A6FD1; Thu,  1 May 2014 15:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RqWOY5IsAyC6; Thu,  1 May 2014 15:23:23 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id AEDAC1A09FD; Thu,  1 May 2014 15:23:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1486; q=dns/txt; s=iport; t=1398983002; x=1400192602; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=96vsd51YQJo+TPtRwY3YG0Z6Lb+rTV+ilM9D0NirNpM=; b=Ee4z89Vx/aT0/I3insgTNdEk+3UyKPW2S70UfYAij50jTQl5s0K9egCm I7sFlzuWRpMqP6EH8xzV83nJDASwtHJgcvpRjzo/UZLhrOhafSWOwlAhx DY9LGjBihDHS4UbYGgUoGHBW2f75Gm/LBBbel8NQ8ZQ+K+LRu7l8yvnah Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAAjJYlOtJA2G/2dsb2JhbABagwbGAIEUFnSCJQEBAQMBeQULAgEIGC4yJQIEDgWIOQjJdReOHzMHgySBFQSJTI9jkm6DMw
X-IronPort-AV: E=Sophos;i="4.97,967,1389744000"; d="scan'208";a="318773423"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-9.cisco.com with ESMTP; 01 May 2014 22:23:21 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s41MNLZ2028760 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 1 May 2014 22:23:21 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.41]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0123.003; Thu, 1 May 2014 17:23:20 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Gert Doering <gert@space.net>
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Thread-Topic: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
Thread-Index: AQHPZQkfIYq9UHb5jEKNapytnrV9qJsrwdmAgACL/+k=
Date: Thu, 1 May 2014 22:23:21 +0000
Message-ID: <BF663432-1AA5-4346-BED8-412C12190B03@cisco.com>
References: <CF875D2F.1951A9%rajiva@cisco.com> <alpine.DEB.2.02.1405010836220.29282@uplift.swm.pp.se> <CF882A16.4EA36%hesham@elevatemobile.com>,<20140501090217.GH43641@Space.Net>
In-Reply-To: <20140501090217.GH43641@Space.Net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ivU-SPJTePucxk8_cylhMfm8HuA
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:23:25 -0000

I wish there was a document stating this. It would help to refine the proto=
col behavior.=20

Cheers,
Rajiv

> On May 1, 2014, at 5:02 AM, "Gert Doering" <gert@space.net> wrote:
>=20
> Hi,
>=20
> On Thu, May 01, 2014 at 04:46:33PM +1000, Hesham Soliman wrote:
>>> I realise this draft seems to have died, but I would never expect to se=
e
>>> packets with these addresses on the wire
>>=20
>> =3D> I recall an information RFC but don=B9t remember the number. I agre=
e they
>> will most likely not appear on the wire.
>>=20
>>> or in the routing table
>>=20
>> =3D> That=B9s a different story. I don=B9t think there is anything banni=
ng this,
>=20
> If the packets are not going to appear on the wire, argueing about the
> content of the routing table is a bit... theoretical.
>=20
> I'd argue for internal representations of stuff to not use that format
> either, as it will just confuse things.  The dual-stack API is bad enough
> for operating system implementors (ran into a bunch of issues with Linux
> recently) to avoid further use of v4-mapped stuff, anywhere.
>=20
> Gert Doering
>        -- NetMaster
> --=20
> have you enabled IPv6 on something today...?
>=20
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culema=
nn
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Thu May  1 15:29:56 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B181A06DB; Thu,  1 May 2014 15:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.253
X-Spam-Level: 
X-Spam-Status: No, score=-104.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcGOiO1ntyLw; Thu,  1 May 2014 15:29:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 002F21A066A; Thu,  1 May 2014 15:29:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4DBC418000D; Thu,  1 May 2014 15:29:34 -0700 (PDT)
To: msweet@apple.com, brian.e.carpenter@gmail.com, cheshire@apple.com, bob.hinden@gmail.com
Subject: [Errata Rejected] RFC6874 (3633)
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140501222934.4DBC418000D@rfc-editor.org>
Date: Thu,  1 May 2014 15:29:34 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Qvq0bLHalktdWcUR3sU2zutFwA4
Cc: rfc-editor@rfc-editor.org, ipv6@ietf.org, ted.lemon@nominum.com, iesg@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:29:54 -0000

The following errata report has been rejected for RFC6874,
"Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3633

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Michael Sweet <msweet@apple.com>
Date Reported: 2013-05-23
Rejected by: Ted Lemon (IESG)

Section: 4

Original Text
-------------
  An HTTP client, proxy, or other intermediary MUST remove any ZoneID
  attached to an outgoing URI, as it has only local significance at the
  sending host.


Corrected Text
--------------
  An HTTP client, proxy, or other intermediary MUST retain any
  ZoneID attached to an outgoing URI, as it will be the only way
  for an HTTP server to return a URI containing a link-local address
  that can subsequently be used by the HTTP client.


Notes
-----
NOTE: PLEASE DO NOT REJECT THIS ERRATA BEFORE FURTHER REVIEW. I WILL BE SUBMITTING A NEW DRAFT PROPOSING THESE CHANGES; THIS ERRATA CAN SERVE AS PUBLIC NOTICE OF POTENTIAL CHANGES TO THE RFC.

The client uses the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care about the zoneid but the client depends on it (for link local anyways).

The client can supply the zoneid in the Host header. For example, the following illustrates a typical IPP request using the previously recommended IPvFuture format (which CUPS implements and uses):

   POST /ipp/print HTTP/1.1
   Host: [v1.fe80::1234+en0]:631
   Content-Type: application/ipp
   Transfer-Coding: chunked

   ... IPP request ...

The printer then validates the Host header and responds with URIs containing the same Host value in any reported IPv6 link-local URIs.

The key issue is one of context - the client *may* be able to query the interface used for a particular socket connection but it probably can't (easily) cache and map this information in the URIs that are embedded in the content returned by the printer, particularly when the client may have to process said content from a variety of sources - IPP is also supported over a USB transport, HTML can be read from disk, etc.  Clients are usually unable to connect to a given IPv6 link local address without the zoneid information to tell them which network interface to use.  And typically the only reason clients use an IPv6 link local address is because it was handed to them by a discovery protocol like WS-Discovery...

Requiring the client to rewrite all URIs is a tremendous burden and is error-prone.  Requiring the server to use the Host header is cheap in comparison.  Having the server validate and use the Host value also helps interoperability since existing clients may not support the new IPv6addrz format - for example, CUPS doesn't support it since it validates URIs and Host values using the ABNF in RFC 3986/STD 66.

The Host header mechanism has been standard practice outside the IETF for several years now. It is part of IPP Everywhere (Printer Working Group), Wi-Fi Direct Print Services (Wi-Fi Alliance), IPP USB (USB Implementers Forum), and AirPrint (Apple).  It solves the problem of client-side routing of IPv6 link local addresses that are used in URIs embedded in content returned by printers and other embedded devices.

Hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years. The new format is incompatible with parsers that use the ABNF in STD 66 (aka RFC 3986) and prevents the use of the Host header in HTTP requests to provide a backwards-compatible IPv6 implementation.
 --VERIFIER NOTES-- 
The attempt to use this erratum as a placeholder seems to be sapping the urgency from the work the author of the erratum promised to do.   This appears to be an end-run around the standards process.   Please do not re-submit this erratum, but instead please get to work in 6man fixing this problem, if indeed there is consensus that your proposed fix is correct.

--------------------------------------
RFC6874 (draft-ietf-6man-uri-zoneid-06)
--------------------------------------
Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
Publication Date    : February 2013
Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Thu May  1 15:53:32 2014
Return-Path: <owen@delong.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC2DA1A06DB; Thu,  1 May 2014 15:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.642
X-Spam-Level: 
X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GXM7UiMTaTHl; Thu,  1 May 2014 15:53:29 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 739241A09B8; Thu,  1 May 2014 15:53:29 -0700 (PDT)
Received: from [10.5.16.141] (adsl-69-228-81-237.dsl.pltn13.pacbell.net [69.228.81.237]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id s41MoxI2027613 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 1 May 2014 15:51:00 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com s41MoxI2027613
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1398984668; bh=s/p5JdKTZkmXXHVyAP7o24EKXZg=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=1HIL8aJbARsPdUde/tN3ZJQ+NYbjdZc+4C4Rrz3yiP2WP7QuhO8tq9eCiyLKwQOR/ jaBlI2ECfYVrLpIcbY2l1PRFolk2xgH9oGdCu9ZmbfMKCsIsTFsvS7kR8og9ipqTXz 48WTF+Dn7gmRl3dbI7tzGrl14oqlvbniUB89t+HA=
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
From: Owen DeLong <owen@delong.com>
In-Reply-To: <A88E5272-6E81-420B-977A-DE8CF21E8829@cisco.com>
Date: Thu, 1 May 2014 15:50:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <52768D51-C3DB-4EE8-BBDA-C54CF5027F27@delong.com>
References: <CF875D2F.1951A9%rajiva@cisco.com>, <5362B83F.4020808@per.reau.lt> <A88E5272-6E81-420B-977A-DE8CF21E8829@cisco.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
X-Mailer: Apple Mail (2.1874)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Thu, 01 May 2014 15:51:08 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/qzHtmd3J44oDKih6aOow8uetLqo
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:53:30 -0000

I like this proposed change as well.

Owne

On May 1, 2014, at 3:20 PM, Rajiv Asati (rajiva) <rajiva@cisco.com> =
wrote:

> Hi Simon,
>=20
> Ditto. This is what I was about to suggest for Q#1. Thanks.=20
>=20
> I wish there was something like that for ospfv3, isis, rip, BGP etc. =
too.=20
>=20
> Cheers,
> Rajiv
>=20
>> On May 1, 2014, at 5:10 PM, "Simon Perreault" <simon@per.reau.lt> =
wrote:
>>=20
>> Le 2014-05-01 02:08, Rajiv Asati (rajiva) a =E9crit :
>>> The answer to Q#1 will help MPLS WG to decide the proper handling of
>>> v4-mapped v6 addresses in LDPv6 draft section 7 1st para.
>>> http://tools.ietf.org/html/draft-ietf-mpls-ldp-ipv6-12#section-7 *
>>=20
>> Rajiv,
>>=20
>> In addition to what the others have said, to provide very precise
>> guidance, I think this text in your draft...
>>=20
>>  An LSR MUST NOT allocate and MUST NOT advertise FEC-Label bindings
>>  for link-local IPv6 address, and ignore such bindings, if ever
>>  received. An LSR MUST treat the IPv4-mapped IPv6 address, defined in
>>  section 2.5.5.2 of [RFC4291], the same as that of a global IPv6
>>  address and not mix it with the 'corresponding' IPv4 address.
>>=20
>> ...should be changed to:
>>=20
>>  An LSR MUST NOT allocate and MUST NOT advertise FEC-Label bindings
>>  for link-local or IPv4-mapped IPv6 address, and ignore such
>>  bindings, if ever received.
>>=20
>> Simon
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Thu May  1 16:00:27 2014
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3458C1A09FA; Thu,  1 May 2014 16:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0crbun9m1HHn; Thu,  1 May 2014 16:00:18 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0185.outbound.protection.outlook.com [207.46.163.185]) by ietfa.amsl.com (Postfix) with ESMTP id 851A81A0986; Thu,  1 May 2014 16:00:18 -0700 (PDT)
Received: from BLUPR03MB424.namprd03.prod.outlook.com (10.141.78.152) by BLUPR03MB424.namprd03.prod.outlook.com (10.141.78.152) with Microsoft SMTP Server (TLS) id 15.0.929.12; Thu, 1 May 2014 23:00:15 +0000
Received: from BLUPR03MB424.namprd03.prod.outlook.com ([10.141.78.152]) by BLUPR03MB424.namprd03.prod.outlook.com ([10.141.78.152]) with mapi id 15.00.0929.001; Thu, 1 May 2014 23:00:15 +0000
From: Christian Huitema <huitema@microsoft.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>, "6man@ietf.org" <6man@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Subject: RE: Q about IPv4-mapped IPv6 address & MPLS 
Thread-Topic: Q about IPv4-mapped IPv6 address & MPLS 
Thread-Index: AQHPZQPSCzbpGVI9y0mONiS9cBGpH5srRWcQgAEANQCAABITAA==
Date: Thu, 1 May 2014 23:00:15 +0000
Message-ID: <85910072e0794eae8149ba10ff933c58@BLUPR03MB424.namprd03.prod.outlook.com>
References: <CF875D2F.1951A9%rajiva@cisco.com> <fd46bfdc1db843d2b34ae7a7e06c0c20@BLUPR03MB424.namprd03.prod.outlook.com> <CF882BEC.195BC5%rajiva@cisco.com>
In-Reply-To: <CF882BEC.195BC5%rajiva@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ee31::2]
x-forefront-prvs: 01986AE76B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(189002)(199002)(86362001)(81542001)(76482001)(4396001)(86612001)(77982001)(81342001)(87936001)(101416001)(33646001)(92566001)(2656002)(558084003)(46102001)(83072002)(83322001)(31966008)(80022001)(20776003)(85852003)(80976001)(2201001)(74502001)(99396002)(79102001)(50986999)(76576001)(77096999)(76176999)(74316001)(99286001)(54356999)(74662001)(24736002)(3826001); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB424; H:BLUPR03MB424.namprd03.prod.outlook.com; FPR:BF12F1BD.36B147A3.39E38DCF.C4CE9E18.20082; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/euhx4Cu6VSFHN3-ma7sGXF5mFhg
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 23:00:21 -0000

> However, v4-mapped v6 addresses are not used by RFC 6052. :o
=20
That's intentional. The short answer is that you should not use them, and y=
ou should not place them in the routing tables.

-- Christian Huitema





From nobody Thu May  1 16:19:05 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5E021A882B; Thu,  1 May 2014 16:18:58 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tI4kly5hdEFs; Thu,  1 May 2014 16:18:56 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id DE5411A8829; Thu,  1 May 2014 16:18:55 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id ld10so4384151pab.40 for <multiple recipients>; Thu, 01 May 2014 16:18:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=E8J5t2zwBb7fIQheP/TNx4iWEF6ghG08CIDi8SUWrRA=; b=Kql3njOjXa1/zkBTtQIWvyEDFtUK+kOnzAFYRc5I1NgQeWmTEow3IvwP3r0oYT5KX5 bsGHIlAfW11yAhqY7VOy939+24A5l3wFWyazNPtzfrYhsehivNvw4S50tiaKBhFCbzkV dE7sP95EKquEU/cnpM4flvmwKZY+LOHO9QOSZS1lTIg5x1y1D1VEvyrYmYsTEZuMmMQK gGC8b+Ju0d87WpMGgs5Uu/t4vzpI2qGMfGBbwP7xPg1EO2K1uEF6xtGVyTKLQd8+ZJji GQLnhcvOQHTftmXvyoOZSoB+5Fh0h7SFUg0xuKnSk9f7NfxUavLYIgNsnkMJlqUpG88z no9Q==
X-Received: by 10.66.153.80 with SMTP id ve16mr26839745pab.143.1398986333809;  Thu, 01 May 2014 16:18:53 -0700 (PDT)
Received: from [192.168.178.20] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id vx10sm167396420pac.17.2014.05.01.16.18.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 16:18:53 -0700 (PDT)
Message-ID: <5362D663.7090501@gmail.com>
Date: Fri, 02 May 2014 11:18:59 +1200
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: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
Subject: Re: [v6ops] Q about IPv4-mapped IPv6 address & MPLS
References: <CF875D2F.1951A9%rajiva@cisco.com> <20140501085939.GG43641@Space.Net>, <5362B2BD.7060602@gmail.com> <C1C2AD52-81C1-4BDB-87B6-550530F01389@cisco.com>
In-Reply-To: <C1C2AD52-81C1-4BDB-87B6-550530F01389@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/6-lhZzMiAuv9Fr7lRQROQtLGBy4
Cc: "mpls@ietf.org" <mpls@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Gert Doering <gert@space.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 23:18:59 -0000

On 02/05/2014 10:21, Rajiv Asati (rajiva) wrote:
> Thanks, Brian. Which RFC 4038 section in particular should be referenced to?

I think section 4.2. "IPv6 Applications in a Dual-Stack Node".
It has a diagram that very clearly shows that packets that
are "decorated" inside the host with an IPv4-mapped address are
sent or received as native IPv4 packets.

It's an Informational RFC but even so it seem to be the
authoritative text in this case.

   Brian

> Cheers,
> Rajiv
> 
>> On May 1, 2014, at 4:47 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:
>>
>>> On 01/05/2014 20:59, Gert Doering wrote:
>>> Hi,
>>>
>>>> On Thu, May 01, 2014 at 06:08:51AM +0000, Rajiv Asati (rajiva) wrote:
>>>> We need your guidance on handling v4-mapped v6 addresses (section 2.5.5.2
>>>> of [RFC4291]). 
>>>>
>>>> 1. Should/Would they appear in IPv6 routing table?
>>> "Yes and no".  It depends on the context - if the packet comes in and has
>>> an IPv6 header, address lookup happens via the IPv6 routing table.  If 
>>> a packet comes in with an IPv4 header, address lookup happens via the
>>> IPv4 routing table.  
>>>
>>> So, IPv4 should never "bleed over" to the IPv6 routing table, but if 
>>> you happen to receive an IPv6 packet with a destination IPv6 address
>>> in it's header of ::ffff:1.2.3.4, you'd either drop it right away,
>>> or use the IPv6 routing table to find the destination.
>>>
>>> The router itself should never ever source packets with a v4-mapped
>>> destination address in the packet (see below).
>>>
>>>> 2. Should an IPv6 packet with ::FFFF:127.0.0.0  be forwarded or dropped or
>>>> treated as a loopback packet, if ever received?
>>> Dropped.  v4-mapped is an internal representation of an IPv4 address
>>> recevied on an ipv6 socket, and should never ever appear in packets on
>>> the wire.
>> Nobody seems to have mentioned RFC 4038, which makes this very clear.
>> These addresses are an artefact and have no place in the routing
>> system as such, and still less on the wire.
>>
>>    Brian
>>
> .
> 


From nobody Thu May  1 16:51:38 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA2D81A0958; Thu,  1 May 2014 16:51:35 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LC7Gw6o8V_nj; Thu,  1 May 2014 16:51:34 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 1541E1A066A; Thu,  1 May 2014 16:51:34 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id bj1so4455093pad.1 for <multiple recipients>; Thu, 01 May 2014 16:51:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ubFwALcyeNY8fwToOjx5jSRN8KU4gyn3JWoigs1TCVQ=; b=ggefMSF8PC+hgAZhXdchBP2/C+h5zJ5OwgrN8spYcgSp/PEn2y4kiVeDSnDFQh0iGr 7qwGrnIOW75y7GGjkilOAeHXhuYsqSJPpUgmrBn7/fyCB/cDTjprwxVdbtARPLMXGycD 5MCBjXRawl4UQukP5v18YUX3iZJFt7jxwDN4XlvcU6YDhyxkRPJsdRCCfmuMZKpyuP7c Vtyzp/L8mhUml/ql5mWqJnl9dhdjgLyCpDbRDRn48G5OhPXR2XOc+4GAs/AqZAE4OdXg deiCV/5TW7NLqEIAsoz8kyC88z5x4yMmEO2srYHfgTEKZ1urg1fxxYO9zyCRepD6zxhw Vfuw==
X-Received: by 10.66.142.42 with SMTP id rt10mr27281451pab.1.1398988292024; Thu, 01 May 2014 16:51:32 -0700 (PDT)
Received: from [192.168.178.20] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id xr9sm167528343pab.5.2014.05.01.16.51.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 16:51:31 -0700 (PDT)
Message-ID: <5362DE09.9010405@gmail.com>
Date: Fri, 02 May 2014 11:51:37 +1200
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: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
References: <534D4F7A.3040605@cox.net>	<CAH7SZV9WeQmuaHvUZ35_ySL4ak4+SDfbmpMbXgqQL+C833sTGw@mail.gmail.com>	<1397607559.92815.YahooMailNeo@web120004.mail.ne1.yahoo.com>	<CAP+sJUfx6=-22+A_=M_v3iSf6piGeyHkF2_BPm2ntbWnCEhTSw@mail.gmail.com> <CAMsDxWRgNoWdaRaZz=tOuWQ+ucCfFE7EnHxbbjBvBR64xoF_dQ@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD842605A64@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD842605A64@xmb-rcd-x01.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/AWw1JlpPappoRNVf-kf56KAuXnY
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "6man@ietf.org" <6man@ietf.org>, roll <roll@ietf.org>, Ines Robles <mariainesrobles@googlemail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 23:51:36 -0000

On 18/04/2014 02:27, Pascal Thubert (pthubert) wrote:
> Dear all;
>=20
> Considering the support we have at 6TiSCH and ROLL for the work, I publ=
ished draft-thubert-6man-flow-label-for-rpl-00.txt to the 6MAN WG.
> The main discussion is probably to confirm whether our proposed use of =
the flow label inside the RPL domain is compatible with the goals that ar=
e achieved by RFC6437. Let us continue the discussion there from now on.

The proposal really does three things:

1. Asserts (implicitly) that a ROLL domain is really, truly, absolutely
separated from the Internet at layer 3 except for traffic through its
root node (acting as a border router).

I think that needs to be stated very explicitly as a fundamental
requirement for this spec to be acceptable.

2. It recommends that the root rewrites the flow label on
outbound packets according to the provisions in RFC 6437.
The slight deviation from RFC 6437 purism there is that it
treats the existing flow label on the packets as if it was zero.

3. It requires that the root rewrites the flow label
on inbound packets even if they are already set to non-zero.
That is indeed a violation of RFC 6437. But it is a violation
we have already accepted in another case: "for compelling operational
security reasons". What's lost? The ability for nodes
inside the ROLL domain to perform flow-label based load balancing
for such inbound packets. I think it's for ROLL and 6TISCH
to say whether that loss matters.

In my opinion, we shouldn't be religious about this as long
as point 1 is guaranteed. I don't see any risks to the generic
use of the flow label.

I think the language around the relationship with RFC 6437
is a bit defensive at the moment and could probably be a bit
simpler and clearer. ("The following exceptions to the rules
in [RFC6437] are made:..."). I'd have a preference for doing that
without a formal update to 6437, because it's only RPL implementors
who need to change anything.

    Brian

> Cheers,
>=20
> Pascal
>=20
> From: xvilajosana@gmail.com [mailto:xvilajosana@gmail.com] On Behalf Of=
 Xavier Vilajosana
> Sent: jeudi 17 avril 2014 10:00
> To: Ines Robles
> Cc: Pascal Thubert (pthubert); 6tisch@ietf.org; roll
> Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL inf=
ormation in data packets
>=20
> +1 I think this is more than needed. In addition RFC 6282 defines how h=
eader compression needs to be handled together with extension headers. I =
think this is not clear and leads to confusions (afecting already some wi=
reshark dissectors). The use of flow label will solve several problems at=
 once.
>=20
> X.
>=20
>=20
>=20
> 2014-04-16 22:44 GMT+02:00 Ines Robles <mariainesrobles@googlemail.com<=
mailto:mariainesrobles@googlemail.com>>:
> +1
>=20
> Ines
>=20
> 2014-04-15 21:19 GMT-03:00 Qin Wang <qinwang6top@yahoo.com<mailto:qinwa=
ng6top@yahoo.com>>:
> +1
>=20
> Qin
> On Wednesday, April 16, 2014 1:47 AM, Prof. Diego Dujovne <diego.dujovn=
e@mail.udp.cl<mailto:diego.dujovne@mail.udp.cl>> wrote:
> +1 !
>=20
> 2014-04-15 12:25 GMT-03:00 Tom Phinney <tom.phinney@cox.net<mailto:tom.=
phinney@cox.net>>:
> +1 for sure. The flow label has always been the preferable method for m=
e, and I suspect for others with knowledge of how it is used in ISA100.11=
a.
> =3D=3D=3D
>=20
> On 2014.04.15 07<tel:2014.04.15%2007>:25, Pascal Thubert (pthubert) wro=
te:
> Dear all:
>=20
> As some of you remember, the RPL specification has changed over time WR=
T to the location of the information that RPL places in the data packets.=
 We started with the flow label but these were the days when what became =
RFC 6437 was being defined at 6MAN, so we shied away and defined the HbH =
technique that is now specified as RFC 6553.
>=20
> We=E2=80=99ll note that the RPL option defined in RFC 6553 takes 6 octe=
ts, and with the HbH hdr we end up with 8 extra octets. An extra IP-in-IP=
 encapsulation is required on top of that unless both endpoints are in th=
e same RPL domain. All this overhead may be acceptable when power is avai=
lable and the PHY allows for larger frames, but in traditional battery-op=
erated 15.4 with ~ 80 bytes usable per frame, my experience from integrat=
ing 6LoWPAN HC with ISA100.11a says that all these extra bytes will be on=
 the way of the 6TiSCH adoption.
>=20
> Still, both RFC 6550 and RFC 6552 are designed to allow for an alternat=
e technique and in particular for the use of the flow label, as is elabor=
ated in http://tools.ietf.org/html/draft-thubert-roll-flow-label-02 . Usi=
ng the flow label reduces the cost of the RPL information dramatically, d=
own to a level that is probably acceptable for the target SDOs.
>=20
> So my plan for now is to move the flow label draft to 6MAN and prepare =
for a hot season, and I=E2=80=99m looking for support from both 6TiSCH an=
d ROLL to back me up from the start.  Yes, you can help!
>=20
> Please +1 if you agree we need this work to happen, and/or provide any =
suggestion.
>=20
> Cheers,
>=20
> Pascal
>=20
>=20
> _______________________________________________
>=20
> 6tisch mailing list
>=20
> 6tisch@ietf.org<mailto:6tisch@ietf.org>
>=20
> https://www.ietf.org/mailman/listinfo/6tisch
>=20
>=20
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org<mailto:6tisch@ietf.org>
> https://www.ietf.org/mailman/listinfo/6tisch
>=20
>=20
>=20
> --
> DIEGO DUJOVNE
> Acad=C3=A9mico Escuela de Ingenier=C3=ADa en Inform=C3=A1tica y Telecom=
unicaciones
> Facultad de Ingenier=C3=ADa UDP
> www.ingenieria.udp.cl<http://www.ingenieria.udp.cl/>
> (56 2) 676 8125<tel:%2856%202%29%20676%208125>
>=20
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org<mailto:6tisch@ietf.org>
> https://www.ietf.org/mailman/listinfo/6tisch
>=20
>=20
> _______________________________________________
> Roll mailing list
> Roll@ietf.org<mailto:Roll@ietf.org>
> https://www.ietf.org/mailman/listinfo/roll
>=20
>=20
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org<mailto:6tisch@ietf.org>
> https://www.ietf.org/mailman/listinfo/6tisch
>=20


From nobody Thu May  1 20:57:34 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 080ED1A08F0 for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 20:57:32 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCtdT3iMnLcP for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 20:57:30 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E35CB1A86F5 for <ipv6@ietf.org>; Thu,  1 May 2014 20:57:29 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id kx10so1961635pab.5 for <ipv6@ietf.org>; Thu, 01 May 2014 20:57:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MgDMgn+2HbBioyc9QqsjJzBKs7udVmpUZypne4Nw5Ps=; b=zjaQCE8JgBQoa7B3Ssw7UKUhJ3PIvL7F+aO8rn+MPOYVgZRsfwiuY50O20QcURsqog QOrc8ASNeTc5bpsnBSKR/SEQfkV3bCLVeOsTRRRH/OhnIrUyP1lPZ9q0uTYHUFUfy/hr qrfuex0WF7ezrO+ebpEzZdu7K9M31c6v3C63pvLqbbT5PSVD+zlOKv/Q+fksLQM495Ow MfK4LLgNf/MPhIsRdHliSWclpJU5eT6YLjY+1cWpRlY8RZYJ0jjEJdX5x8tNKK398cuc hHLBiY3M4xLBLWxQFhECqaYkBvssmihl0UW6kYonM5dmzhyk0oZEgfVBsLhsxDsKiIh1 FqHA==
X-Received: by 10.66.218.193 with SMTP id pi1mr29479189pac.20.1399003047745; Thu, 01 May 2014 20:57:27 -0700 (PDT)
Received: from [192.168.178.20] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id vo1sm172464931pab.32.2014.05.01.20.57.25 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 20:57:26 -0700 (PDT)
Message-ID: <536317AE.1090500@gmail.com>
Date: Fri, 02 May 2014 15:57:34 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-gont-6man-ipv6-universal-extension-header-01.txt
References: <20140408103907.23507.46057.idtracker@ietfa.amsl.com>
In-Reply-To: <20140408103907.23507.46057.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/WshhWEYBdHWYMuJWLSo9m54DeP4
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 03:57:32 -0000

Hi,

I've finally understood what's been bothering me about this draft.
Actually, two things:

1. If a node (regardless of whether it's the destination host,
or an intermediate node such as a firewall) has a policy
of discarding packets with an unknown extension header
or an unknown transport protocol, it *doesn't matter* that
it can't distinguish them. The packet is discarded anyway.

Comment on that: In either case, this discard by a host is
consistent with RFC2460 (even as updated by RFC7045). In either
case, it's what we would expect a firewall to do if it has the
usual sort of paranoid policy, and that again is consistent
with RFC7045.

2. Given that argument, I think this draft should consider a
4th possible solution: Do Nothing. I think it's a valid option.

Nits: I don't see why this draft is tagged as Standards Track
and Updates 2460. It's an informational discussion.

Please change the title of the draft. At the moment it has
the same title as draft-gont-6man-rfc6564bis.

Regards
   Brian


From nobody Thu May  1 21:17:17 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1370E1A09CA for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 21:17:15 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AxhDnplRgydt for <ipv6@ietfa.amsl.com>; Thu,  1 May 2014 21:17:13 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id C63CB1A090D for <ipv6@ietf.org>; Thu,  1 May 2014 21:17:13 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kx10so4752390pab.25 for <ipv6@ietf.org>; Thu, 01 May 2014 21:17:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zF93T+eEryOpK3vFadgCBwD6wD2Np4f6GHQmM9zC6b4=; b=QZQqoyfQijYADtE7AC4TeYkQyZQNkFmODUYhaUdV8mTD0gyEce+gyQsGxqPv8OIOCk pi61EKtMGtk55zZphkhQyiNli8h1xK4O+OA1dcA31DpnAWqlZ/nfk4mB9rw87C3yyJ6O vmZLf781iaBexheuZ9FpgHKukOlL+Z7BWL1oEOqXrXgyEyQNWC0TugZUJ9XxCsRv8zZy GIulbcG/kQ+uyCCh9TIdDqvRZBG+juEwzeI9k/avlj1WhZ8bXVJT0VZ4hwr0uKBc7ni/ Z3amBBKOde71jpVxQM9k96IWMWhYFJiVDaRP2GPxjDrxzwMXYgWEgw91TiEdSqcE6ICX CzmQ==
X-Received: by 10.66.66.135 with SMTP id f7mr29833163pat.22.1399004231162; Thu, 01 May 2014 21:17:11 -0700 (PDT)
Received: from [192.168.178.20] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id pb7sm172102448pac.10.2014.05.01.21.17.09 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 21:17:10 -0700 (PDT)
Message-ID: <53631C4E.4000104@gmail.com>
Date: Fri, 02 May 2014 16:17:18 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-gont-6man-rfc6564bis-00.txt
References: <20140408103653.23478.12743.idtracker@ietfa.amsl.com>
In-Reply-To: <20140408103653.23478.12743.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/g-_6dSVFUaaGbYlJAaF-bGaYTmA
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 04:17:15 -0000

Hi,

I don't think we should really decide about this draft until we've
first decided about draft-gont-6man-ipv6-universal-extension-header.

However, I don't think it fixes the problem anyway. Firewalls that
drop unknown extension headers or transport protocols today will be
modified to drop unknown Universal Extension Header subtypes tomorrow,
so it will still be impossible to deploy new extensions unless firewalls
are regularly updated. All the rules we put in RFC7045 for handling
extension headers will have to be put in RFC7045bis for handling
Universal Extension Header subtypes. I think the problem is
simply recursive.

Nits: this draft should both obsolete 6564 and update 2460 if approved.

There should be an Informative Reference to
draft-gont-6man-ipv6-universal-extension-header. In fact sections 3
and 4 duplicate arguments from that draft.

> The entire Section 4 of [RFC6564] is hereby replaced as follows:

This document claims to obsolete 6564. Therefore you can't state
that you are replacing one section - you need to include everything
from 6564 that you want to keep.

> 8. IANA Considerations

This is incomplete. You have to request a new protocol number for
the new header type (and it must go in the IPv6 Extension Header Types
registry as specified in RFC7045).

   Brian


From nobody Fri May  2 06:23:52 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDC6C1A6FB4; Fri,  2 May 2014 06:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qu6nNSICirHN; Fri,  2 May 2014 06:23:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 484DC1A2130; Fri,  2 May 2014 06:23:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-enhanced-dad-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140502132347.11069.54678.idtracker@ietfa.amsl.com>
Date: Fri, 02 May 2014 06:23:47 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/zlhUf--YltdrmcPWRwn7Z8bbkuM
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 13:23:49 -0000

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

        Title           : Enhanced Duplicate Address Detection
        Authors         : Rajiv Asati
                          Hemant Singh
                          Wes Beebee
                          Eli Dart
                          Wes George
                          Carlos Pignataro
	Filename        : draft-ietf-6man-enhanced-dad-05.txt
	Pages           : 12
	Date            : 2014-05-02

Abstract:
   Appendix A of the IPv6 Duplicate Address Detection (DAD) document in
   RFC 4862 discusses Loopback Suppression and DAD.  However, RFC 4862
   does not settle on one specific automated means to detect loopback of
   Neighbor Discovery (ND of RFC 4861) messages used by DAD.  Several
   service provider communities have expressed a need for automated
   detection of looped backed ND messages used by DAD.  This document
   includes mitigation techniques and then outlines the Enhanced DAD
   algorithm to automate detection of looped back IPv6 ND messages used
   by DAD.  For network loopback tests, the Enhanced DAD algorithm
   allows IPv6 to self-heal after a loopback is placed and removed.
   Further, for certain access networks the document automates resolving
   a specific duplicate address conflict.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-enhanced-dad-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-enhanced-dad-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Fri May  2 06:26:30 2014
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63D061A2119; Fri,  2 May 2014 06:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4FRZ36o1ivC; Fri,  2 May 2014 06:26:26 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 8522B1A08F7; Fri,  2 May 2014 06:26:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2797; q=dns/txt; s=iport; t=1399037184; x=1400246784; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JXrDEgpKXuRXeKKU9uhr/+PkJ1ez2mWjnIANniMtcso=; b=XkfFB3V6EJxNGnRYVeNsmRFjaFcVGa7n0lrbEZy/umTusraj4OxeFEod Q72qvWztQTplZBUY6gTWdZQTpvCl+5gssH7Q0NrmyFoOQiXqQLHYNysfX YpHJ3b1JOuuPQ1hjoFgcz+lwZscr+o2NvqVmxD6Dj4CokyLNR86rilcEs M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkGAAGcY1OtJV2c/2dsb2JhbABagwZPUQa9D4c+gREWdIIlAQEBBAEBATc0CwwEAgEIEQQBAQsUCQcnCxQJCAIEAQ0FCAGIOAgFyT4XjiExBwaDHoEVBIVIlSSRM4M0gis
X-IronPort-AV: E=Sophos;i="4.97,972,1389744000"; d="scan'208";a="40547570"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-8.cisco.com with ESMTP; 02 May 2014 13:26:24 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s42DQOrH030661 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 May 2014 13:26:24 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.41]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0123.003; Fri, 2 May 2014 08:26:23 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>, Jouni Korhonen <jouni.nospam@gmail.com>
Subject: RE: I-D Action: draft-ietf-6man-enhanced-dad-05.txt
Thread-Topic: I-D Action: draft-ietf-6man-enhanced-dad-05.txt
Thread-Index: AQHPZgnFy1su8FLQG0yXnKc9UsVT9ZstR7JQ
Date: Fri, 2 May 2014 13:26:23 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B8911670D50@xmb-rcd-x06.cisco.com>
References: <20140502132347.11069.54678.idtracker@ietfa.amsl.com>
In-Reply-To: <20140502132347.11069.54678.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.243.136]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/3mZGbdNXl9Hz81_WsKkk3fJN3Xg
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 13:26:28 -0000

Jouni,

How have you been?  Sorry for the delay.  This version of the document has =
taken care of all your comments.  Thanks much for the great review.=20

Chairs, could you please initiate a LastCall for this document - thanks.

Cheers,

Hemant

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org
Sent: Friday, May 02, 2014 9:24 AM
To: i-d-announce@ietf.org
Cc: ipv6@ietf.org
Subject: I-D Action: draft-ietf-6man-enhanced-dad-05.txt


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 IET=
F.

        Title           : Enhanced Duplicate Address Detection
        Authors         : Rajiv Asati
                          Hemant Singh
                          Wes Beebee
                          Eli Dart
                          Wes George
                          Carlos Pignataro
	Filename        : draft-ietf-6man-enhanced-dad-05.txt
	Pages           : 12
	Date            : 2014-05-02

Abstract:
   Appendix A of the IPv6 Duplicate Address Detection (DAD) document in
   RFC 4862 discusses Loopback Suppression and DAD.  However, RFC 4862
   does not settle on one specific automated means to detect loopback of
   Neighbor Discovery (ND of RFC 4861) messages used by DAD.  Several
   service provider communities have expressed a need for automated
   detection of looped backed ND messages used by DAD.  This document
   includes mitigation techniques and then outlines the Enhanced DAD
   algorithm to automate detection of looped back IPv6 ND messages used
   by DAD.  For network loopback tests, the Enhanced DAD algorithm
   allows IPv6 to self-heal after a loopback is placed and removed.
   Further, for certain access networks the document automates resolving
   a specific duplicate address conflict.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-enhanced-dad-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-enhanced-dad-05


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

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

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


From nobody Fri May  2 09:13:38 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2F521A08FD for <ipv6@ietfa.amsl.com>; Fri,  2 May 2014 09:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dESkuhJd-6_r for <ipv6@ietfa.amsl.com>; Fri,  2 May 2014 09:13:33 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id F3A971A084B for <ipv6@ietf.org>; Fri,  2 May 2014 09:13:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=28908; q=dns/txt; s=iport; t=1399047211; x=1400256811; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=XHp61ohCzLSU3z941U4LTHI356IljFBX/TAZEBktKsk=; b=JIEB2IvD8OhQlgLLqU880JQWJca2Iz3RXfN2J5NRP/vavbruq0fU4OCE kU2OUeC7fxHr0WsK+nG4l2qH0ZEASXWd4p6sLMjhAHTvgjN0Y5EXYUXmH ZpBprKycv3+5U1bfJSkrcNC8sm/mBfQrrWpLGAFzxBCV5dHHSuc+5aK9q 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An4FAPPCY1OtJA2J/2dsb2JhbABXA4JCRE9YrHeOWYFCAYZnUYERFnSCJQEBAQQBAQEqHCUbAgEIEQQBAQsWBwchBgsTAQcBAQUDAgQTCIglAxENw1MNhkUXjDuBLxEGAQEBHSEMAQkBBguDE4EVBIRZA4RwjXIGgyiJToIKhVuBdYE/gW4IFyI
X-IronPort-AV: E=Sophos;i="4.97,973,1389744000";  d="scan'208,217";a="322068869"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-4.cisco.com with ESMTP; 02 May 2014 16:13:29 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s42GDTvk014140 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ipv6@ietf.org>; Fri, 2 May 2014 16:13:29 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.229]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Fri, 2 May 2014 11:13:29 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: FW: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
Thread-Topic: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
Thread-Index: AQHPZVwBFb7CAtMGZ0yEI5h3N59w25std8dA
Date: Fri, 2 May 2014 16:13:28 +0000
Deferred-Delivery: Fri, 2 May 2014 16:13:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD84263209E@xmb-rcd-x01.cisco.com>
References: <534D4F7A.3040605@cox.net> <CAH7SZV9WeQmuaHvUZ35_ySL4ak4+SDfbmpMbXgqQL+C833sTGw@mail.gmail.com> <1397607559.92815.YahooMailNeo@web120004.mail.ne1.yahoo.com> <CAP+sJUfx6=-22+A_=M_v3iSf6piGeyHkF2_BPm2ntbWnCEhTSw@mail.gmail.com> <CAMsDxWRgNoWdaRaZz=tOuWQ+ucCfFE7EnHxbbjBvBR64xoF_dQ@mail.gmail.com> <E3685BDE-AD30-4E4D-A224-B5863CBEAC5C@kinneyconsultingllc.com>
In-Reply-To: <E3685BDE-AD30-4E4D-A224-B5863CBEAC5C@kinneyconsultingllc.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.22.4]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD84263209Exmbrcdx01ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/bMBNZOjtUHc41AQ8OxoULwcPHAs
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 16:13:37 -0000

--_000_E045AECD98228444A58C61C200AE1BD84263209Exmbrcdx01ciscoc_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

From: Pat Kinney [mailto:pat.kinney@kinneyconsultingllc.com]
Sent: jeudi 1 mai 2014 18:40
To: 6man@ietf.org
Cc: 6tisch@ietf.org; roll; Xavier Vilajosana; Ines Robles; Brian E Carpente=
r; Pascal Thubert (pthubert)
Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL informa=
tion in data packets

Dear All;

Over the past 8 years ISA100 has been involved with wireless industrial net=
works using battery operated wireless modules that must last at least 10 ye=
ars on a single battery.  Since these applications are typically low data r=
ate (50 - 250 kb/s), and TDMA for low energy usage, these industrial networ=
ks use the IEEE 802.15.4 MAC/PHY standard.  Since industrial environments c=
ontain significant interference, using shorter packet durations significant=
ly increase the likelihood of a successful message receipt, dramatically re=
ducing retries which consume energy and reduce network throughput.

ISA100 worked with the IETF to allow ISA's first wireless standard, ISA100.=
11a that is now shipping, to use IPv6 with the 6LoWPAN header compression (=
RFC6282) at the network layer with a string critical requirement to keep th=
e frame size minimal so as to stay under the 127 bytes limit as per the 802=
.15.4.  ISA100 would now like to consider a wireless industrial standard us=
ing the full 6TiSCH suite and in particular RPL (RFC 6550) and the backbone=
 router technology; however using the RPL option in a Hop-by-Hop header as =
proposed in RFC6553 would add an additional 8 bytes to the packet.  Regretf=
ully, this additional overhead can't be tolerated since it would result in =
security configuration packets (and others) being larger than the 127 byte =
limit.

As a co-chair of ISA100 as well as the editor of ISA100.11a-2011, I would a=
sk the IETF 6man to seriously consider adopting draft-thubert-6man-flow-lab=
el-for-rpl that combines optimally with RFC6282 for a minima overhead in th=
e compressed packet.

Pat Kinney
Kinney Consulting LLC
IEEE 802.15 WG vice chair, TG chair
ISA100.11a WG chair
O: +1.847.960.3715
pat.kinney@kinneyconsultingllc.com<mailto:pat.kinney@kinneyconsultingllc.co=
m>



On Apr 17, 2014, at 9:26 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<=
mailto:pthubert@cisco.com>> wrote:

Dear all;

Considering the support we have at 6TiSCH and ROLL for the work, I publishe=
d draft-thubert-6man-flow-label-for-rpl-00.txt to the 6MAN WG.
The main discussion is probably to confirm whether our proposed use of the =
flow label inside the RPL domain is compatible with the goals that are achi=
eved by RFC6437. Let us continue the discussion there from now on.

Cheers,

Pascal

From: xvilajosana@gmail.com<mailto:xvilajosana@gmail.com> [mailto:xvilajosa=
na@gmail.com] On Behalf Of Xavier Vilajosana
Sent: jeudi 17 avril 2014 10:00
To: Ines Robles
Cc: Pascal Thubert (pthubert); 6tisch@ietf.org<mailto:6tisch@ietf.org>; rol=
l
Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL informa=
tion in data packets

+1 I think this is more than needed. In addition RFC 6282 defines how heade=
r compression needs to be handled together with extension headers. I think =
this is not clear and leads to confusions (afecting already some wireshark =
dissectors). The use of flow label will solve several problems at once.

X.



2014-04-16 22:44 GMT+02:00 Ines Robles <mariainesrobles@googlemail.com<mail=
to:mariainesrobles@googlemail.com>>:
+1

Ines

2014-04-15 21:19 GMT-03:00 Qin Wang <qinwang6top@yahoo.com<mailto:qinwang6t=
op@yahoo.com>>:
+1

Qin
On Wednesday, April 16, 2014 1:47 AM, Prof. Diego Dujovne <diego.dujovne@ma=
il.udp.cl<mailto:diego.dujovne@mail.udp.cl>> wrote:
+1 !

2014-04-15 12:25 GMT-03:00 Tom Phinney <tom.phinney@cox.net<mailto:tom.phin=
ney@cox.net>>:
+1 for sure. The flow label has always been the preferable method for me, a=
nd I suspect for others with knowledge of how it is used in ISA100.11a.
=3D=3D=3D

On 2014.04.15 07<tel:2014.04.15%2007>:25, Pascal Thubert (pthubert) wrote:
Dear all:

As some of you remember, the RPL specification has changed over time WRT to=
 the location of the information that RPL places in the data packets. We st=
arted with the flow label but these were the days when what became RFC 6437=
 was being defined at 6MAN, so we shied away and defined the HbH technique =
that is now specified as RFC 6553.

We'll note that the RPL option defined in RFC 6553 takes 6 octets, and with=
 the HbH hdr we end up with 8 extra octets. An extra IP-in-IP encapsulation=
 is required on top of that unless both endpoints are in the same RPL domai=
n. All this overhead may be acceptable when power is available and the PHY =
allows for larger frames, but in traditional battery-operated 15.4 with ~ 8=
0 bytes usable per frame, my experience from integrating 6LoWPAN HC with IS=
A100.11a says that all these extra bytes will be on the way of the 6TiSCH a=
doption.

Still, both RFC 6550 and RFC 6552 are designed to allow for an alternate te=
chnique and in particular for the use of the flow label, as is elaborated i=
n http://tools.ietf.org/html/draft-thubert-roll-flow-label-02 . Using the f=
low label reduces the cost of the RPL information dramatically, down to a l=
evel that is probably acceptable for the target SDOs.

So my plan for now is to move the flow label draft to 6MAN and prepare for =
a hot season, and I'm looking for support from both 6TiSCH and ROLL to back=
 me up from the start.  Yes, you can help!

Please +1 if you agree we need this work to happen, and/or provide any sugg=
estion.

Cheers,

Pascal


_______________________________________________

6tisch mailing list

6tisch@ietf.org<mailto:6tisch@ietf.org>

https://www.ietf.org/mailman/listinfo/6tisch


_______________________________________________
6tisch mailing list
6tisch@ietf.org<mailto:6tisch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tisch



--
DIEGO DUJOVNE
Acad=E9mico Escuela de Ingenier=EDa en Inform=E1tica y Telecomunicaciones
Facultad de Ingenier=EDa UDP
www.ingenieria.udp.cl<http://www.ingenieria.udp.cl/>
(56 2) 676 8125<tel:%2856%202%29%20676%208125>

_______________________________________________
6tisch mailing list
6tisch@ietf.org<mailto:6tisch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tisch


_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll


_______________________________________________
6tisch mailing list
6tisch@ietf.org<mailto:6tisch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tisch



--_000_E045AECD98228444A58C61C200AE1BD84263209Exmbrcdx01ciscoc_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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"><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;"> Pat Kinn=
ey [mailto:pat.kinney@kinneyconsultingllc.com]
<br>
<b>Sent:</b> jeudi 1 mai 2014 18:40<br>
<b>To:</b> 6man@ietf.org<br>
<b>Cc:</b> 6tisch@ietf.org; roll; Xavier Vilajosana; Ines Robles; Brian E C=
arpenter; Pascal Thubert (pthubert)<br>
<b>Subject:</b> Re: [6tisch] [Roll] Support of flow label to carry the RPL =
information in data packets<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><i><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Dear All;</span></i><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><i><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Over the past 8 years ISA100 has bee=
n involved with wireless industrial networks using battery operated wireles=
s modules that must last at least 10 years on a single battery.
 &nbsp;Since these applications are typically low data rate (50 - 250 kb/s)=
, and TDMA for low energy usage, these industrial networks use the IEEE 802=
.15.4 MAC/PHY standard. &nbsp;Since industrial environments contain signifi=
cant interference, using shorter packet durations
 significantly increase the likelihood of a successful message receipt, dra=
matically reducing retries which consume energy and reduce network throughp=
ut.</span></i><br>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;">&nbsp;</span><br>
<i><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;">ISA100 worked with the IETF to allow ISA's first wireless s=
tandard, ISA100.11a that is now shipping, to use IPv6 with the 6LoWPAN head=
er compression (RFC6282) at the network layer with a string
 critical requirement to keep the frame size minimal so as to stay under th=
e 127 bytes limit as per the 802.15.4. &nbsp;ISA100 would now like to consi=
der a wireless industrial standard using the full 6TiSCH suite and in parti=
cular RPL (RFC 6550) and the backbone
 router technology; however using the RPL option in a Hop-by-Hop header as =
proposed in RFC6553 would add an additional 8 bytes to the packet. &nbsp;Re=
gretfully, this additional overhead can't be tolerated since it would resul=
t in security configuration packets (and
 others) being larger than the 127 byte limit.&nbsp;</span></i><br>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;">&nbsp;</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><i><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">As a co-chair of ISA100 as well as t=
he editor of ISA100.11a-2011, I would ask the IETF 6man to seriously consid=
er adopting&nbsp;</span></i><span style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;">draft-thubert-6man-flow-label-for-=
rpl<i>&nbsp;that
 combines optimally with RFC6282 for a minima overhead in the compressed pa=
cket.&nbsp;</i><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;;color:black">Pat Kinney<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:9.0pt;font-family:&qu=
ot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">Kinney Consulting LL=
C</span></i></b><span style=3D"font-size:9.0pt;font-family:&quot;Helvetica&=
quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;;color:black">IEEE 802.15 WG vice chair,=
 TG chair<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;;color:black">ISA100.11a WG chair<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;;color:black">O: &#43;1.847.960.3715<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;;color:black"><a href=3D"mailto:pat.kinn=
ey@kinneyconsultingllc.com"><span style=3D"text-decoration:none">pat.kinney=
@kinneyconsultingllc.com</span></a><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">On Apr 17, 2014, at 9:26 AM, Pascal Thubert (pthuber=
t) &lt;<a href=3D"mailto:pthubert@cisco.com">pthubert@cisco.com</a>&gt; wro=
te:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dear all;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Considering the support w=
e have at 6TiSCH and ROLL for the work, I published draft-thubert-6man-flow=
-label-for-rpl-00.txt to the 6MAN WG.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The main discussion is pr=
obably to confirm whether our proposed use of the flow label inside the RPL=
 domain is compatible with the goals that are achieved by
 RFC6437. Let us continue the discussion there from now on.</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Cheers,</span=
><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span>=
<o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Pascal</span>=
<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<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;">
<a href=3D"mailto:xvilajosana@gmail.com">xvilajosana@gmail.com</a> [<a href=
=3D"mailto:xvilajosana@gmail.com">mailto:xvilajosana@gmail.com</a>]
<b>On Behalf Of </b>Xavier Vilajosana<br>
<b>Sent:</b> jeudi 17 avril 2014 10:00<br>
<b>To:</b> Ines Robles<br>
<b>Cc:</b> Pascal Thubert (pthubert); <a href=3D"mailto:6tisch@ietf.org">6t=
isch@ietf.org</a>; roll<br>
<b>Subject:</b> Re: [6tisch] [Roll] Support of flow label to carry the RPL =
information in data packets</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&#43;1 I think this is more than needed. In addition=
 RFC 6282 defines how header compression needs to be handled together with =
extension headers. I think this is not clear and leads to confusions (afect=
ing already some wireshark dissectors).
 The use of flow label will solve several problems at once.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">X.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">2014-04-16 22:44 GMT&#43;02:00 Ines Robles &lt;<a hr=
ef=3D"mailto:mariainesrobles@googlemail.com" target=3D"_blank">mariainesrob=
les@googlemail.com</a>&gt;:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&#43;1<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Ines<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">2014-04-15 21:19 GMT-03:00 Qin Wang &lt;<a href=3D"m=
ailto:qinwang6top@yahoo.com" target=3D"_blank">qinwang6top@yahoo.com</a>&gt=
;:<o:p></o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;">&#43;1</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#888888">&nbsp;</span><o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#888888">Qin</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">On Wednesday, April 16, 2014 1:47 AM, Prof. Diego Dujovne =
&lt;<a href=3D"mailto:diego.dujovne@mail.udp.cl" target=3D"_blank">diego.du=
jovne@mail.udp.cl</a>&gt; wrote:</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&#43;1 !</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p=
></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">2014-04-15 12:25 GMT-03:00 Tom Phinney &lt;<a href=3D"=
mailto:tom.phinney@cox.net" target=3D"_blank">tom.phinney@cox.net</a>&gt;:<=
/span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&#43;1 for sure. The flow label has always been the pr=
eferable method for me, and I suspect for others with knowledge of how it i=
s used in ISA100.11a.<br>
=3D=3D=3D</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">On <a href=3D"tel:2014.04.15%2007" target=3D"_blank">
2014.04.15 07</a>:25, Pascal Thubert (pthubert) wrote:</span><o:p></o:p></p=
>
</div>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">Dear all:</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">As some of you remember, the RPL specification has cha=
nged over time WRT to the location of the information that RPL places in th=
e data packets. We started with the flow label but these
 were the days when what became RFC 6437 was being defined at 6MAN, so we s=
hied away and defined the HbH technique that is now specified as RFC 6553.
</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">We&#8217;ll note that the RPL option defined in RFC 65=
53 takes 6 octets, and with the HbH hdr we end up with 8 extra octets. An e=
xtra IP-in-IP encapsulation is required on top of that unless
 both endpoints are in the same RPL domain. All this overhead may be accept=
able when power is available and the PHY allows for larger frames, but in t=
raditional battery-operated 15.4 with ~ 80 bytes usable per frame, my exper=
ience from integrating 6LoWPAN HC
 with ISA100.11a says that all these extra bytes will be on the way of the =
6TiSCH adoption.
</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">Still, both RFC 6550 and RFC 6552 are designed to allo=
w for an alternate technique and in particular for the use of the flow labe=
l, as is elaborated in
<a href=3D"http://tools.ietf.org/html/draft-thubert-roll-flow-label-02" tar=
get=3D"_blank">
http://tools.ietf.org/html/draft-thubert-roll-flow-label-02</a> . Using the=
 flow label reduces the cost of the RPL information dramatically, down to a=
 level that is probably acceptable for the target SDOs.</span><o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">So my plan for now is to move the flow label draft to =
6MAN and prepare for a hot season, and I&#8217;m looking for support from b=
oth 6TiSCH and ROLL to back me up from the start. &nbsp;Yes, you can
 help! </span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">Please &#43;1 if you agree we need this work to happen=
, and/or provide any suggestion.</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">Cheers,</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">Pascal</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p=
></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>6tisch mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:6tisch@ietf.org" target=3D"_blank">6tisch@ietf.org</=
a><o:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/6tisch</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;"><br>
_______________________________________________<br>
6tisch mailing list<br>
<a href=3D"mailto:6tisch@ietf.org" target=3D"_blank">6tisch@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/6tisch</a></span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;"><br>
<br clear=3D"all">
<br>
-- <br>
DIEGO DUJOVNE<br>
Acad=E9mico Escuela de Ingenier=EDa en Inform=E1tica y Telecomunicaciones<b=
r>
Facultad de Ingenier=EDa UDP<br>
<a href=3D"http://www.ingenieria.udp.cl/" target=3D"_blank">www.ingenieria.=
udp.cl</a><br>
<a href=3D"tel:%2856%202%29%20676%208125" target=3D"_blank">(56 2) 676 8125=
</a></span><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Helvetica&quot;,&qu=
ot;sans-serif&quot;">_______________________________________________<br>
6tisch mailing list<br>
<a href=3D"mailto:6tisch@ietf.org" target=3D"_blank">6tisch@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/6tisch</a></span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p=
></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org" target=3D"_blank">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/roll</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
6tisch mailing list<br>
<a href=3D"mailto:6tisch@ietf.org">6tisch@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/6tisch</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_E045AECD98228444A58C61C200AE1BD84263209Exmbrcdx01ciscoc_--


From nobody Fri May  2 09:54:33 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 305751A6FC1; Fri,  2 May 2014 09:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRpOq4ozpFJp; Fri,  2 May 2014 09:54:27 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id DCA4F1A6F88; Fri,  2 May 2014 09:54:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9878; q=dns/txt; s=iport; t=1399049665; x=1400259265; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=ekj1PpmxKhO2uYMjXFRs+nM3bzGN490KARETA+/vEv4=; b=MT15gGce8RyDgBHWFA3Cz2eGPC1dx0/+Bg6ngz0I4Jp6VP9819UVhUbB vHU9pFNgn0ATQ4UNRu+fLv0ploqgQfb3KlM8z8azS1PQeUKAGQciJxmVE XaEHbXDYCWpXawIKq+860WYcsq3wY53A+YTHAMf4z4zRjb3jhpcWoQ61L 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAMDMY1OtJV2c/2dsb2JhbABagwZPWIJnqhCQG4ZoURl4FnSCJQEBAQMBAQEBIBEVJQQHBQ0BCBEEAQEBAgIGHQMCBB8GCxMBAQgJAQQBDQUIiCUDCQgNpgedVw2GRBeBKosRgS8XAQEBHRYbgnY1gRUEhFkDkmIGgyiJToIKhVuBdYE/gXY5
X-IronPort-AV: E=Sophos;i="4.97,973,1389744000"; d="scan'208";a="40582311"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-2.cisco.com with ESMTP; 02 May 2014 16:54:21 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s42GsLCR004875 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 May 2014 16:54:21 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.229]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Fri, 2 May 2014 11:54:21 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Pat Kinney <pat.kinney@KINNEYCONSULTINGLLC.COM>
Subject: RE: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
Thread-Topic: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
Thread-Index: Ac9mJv51tx5eNW6ATb660Q0CI/KJdg==
Date: Fri, 2 May 2014 16:54:20 +0000
Deferred-Delivery: Fri, 2 May 2014 16:54:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD842632160@xmb-rcd-x01.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.22.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/-YJuEdey1jbZiO9v2scaUxhRODA
Cc: roll <roll@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 16:54:30 -0000

VGhhbmtzIGEgYnVuY2ggZm9yIHRoaXMgQnJpYW47DQoNCkknbGwgc3VibWl0IGEgcmV2aXNpb24g
YWRkcmVzc2luZyB5b3VyIHBvaW50cy4gUGxlYXNlIHNlZSBpbmxpbmU6DQoNCj4gPiBDb25zaWRl
cmluZyB0aGUgc3VwcG9ydCB3ZSBoYXZlIGF0IDZUaVNDSCBhbmQgUk9MTCBmb3IgdGhlIHdvcmss
IEkNCj4gcHVibGlzaGVkIGRyYWZ0LXRodWJlcnQtNm1hbi1mbG93LWxhYmVsLWZvci1ycGwtMDAu
dHh0IHRvIHRoZSA2TUFOIFdHLg0KPiA+IFRoZSBtYWluIGRpc2N1c3Npb24gaXMgcHJvYmFibHkg
dG8gY29uZmlybSB3aGV0aGVyIG91ciBwcm9wb3NlZCB1c2Ugb2YNCj4gdGhlIGZsb3cgbGFiZWwg
aW5zaWRlIHRoZSBSUEwgZG9tYWluIGlzIGNvbXBhdGlibGUgd2l0aCB0aGUgZ29hbHMgdGhhdCBh
cmUNCj4gYWNoaWV2ZWQgYnkgUkZDNjQzNy4gTGV0IHVzIGNvbnRpbnVlIHRoZSBkaXNjdXNzaW9u
IHRoZXJlIGZyb20gbm93IG9uLg0KPiANCj4gVGhlIHByb3Bvc2FsIHJlYWxseSBkb2VzIHRocmVl
IHRoaW5nczoNCj4gDQo+IDEuIEFzc2VydHMgKGltcGxpY2l0bHkpIHRoYXQgYSBST0xMIGRvbWFp
biBpcyByZWFsbHksIHRydWx5LCBhYnNvbHV0ZWx5IHNlcGFyYXRlZA0KPiBmcm9tIHRoZSBJbnRl
cm5ldCBhdCBsYXllciAzIGV4Y2VwdCBmb3IgdHJhZmZpYyB0aHJvdWdoIGl0cyByb290IG5vZGUg
KGFjdGluZyBhcw0KPiBhIGJvcmRlciByb3V0ZXIpLg0KPiANCj4gSSB0aGluayB0aGF0IG5lZWRz
IHRvIGJlIHN0YXRlZCB2ZXJ5IGV4cGxpY2l0bHkgYXMgYSBmdW5kYW1lbnRhbCByZXF1aXJlbWVu
dA0KPiBmb3IgdGhpcyBzcGVjIHRvIGJlIGFjY2VwdGFibGUuDQo+IA0KW1BUXSBUaGlzIGFzc3Vt
cHRpb24gaXMgdGhlcmUgdG9kYXksIHNpbmNlIFJQTCBleHBlY3RzIHRvIGJ1aWxkIHN0dWIgbmV0
d29ya3Mgd2l0aCBhIGRlZmF1bHQgcm91dGUgdG93YXJkcyB0aGUgcm9vdC4gSSBhZ3JlZSBpdCBt
YWtlcyBzZW5zZSB0byBwcm92aXNpb25hbGx5IGFkZCB3b3JkcyB0byBpbmRpY2F0ZSBhIHRyZWF0
bWVudCBmb3IgcGFja2V0cyBsZWF2aW5nIHRoZSBSUEwgZG9tYWluIHJlZ2FyZGxlc3Mgb2YgdGhl
IGV4aXQgcG9pbnQgaW4gY2FzZSBhIHdlaXJkIGRlcGxveW1lbnQgd291bGQgaW5qZWN0IHRyYWZm
aWMgaW50byB0aGUgaW50ZXJuZXQgZnJvbSBhIGxlYWYuIA0KPg0KPiAyLiBJdCByZWNvbW1lbmRz
IHRoYXQgdGhlIHJvb3QgcmV3cml0ZXMgdGhlIGZsb3cgbGFiZWwgb24gb3V0Ym91bmQgcGFja2V0
cw0KPiBhY2NvcmRpbmcgdG8gdGhlIHByb3Zpc2lvbnMgaW4gUkZDIDY0MzcuDQo+IFRoZSBzbGln
aHQgZGV2aWF0aW9uIGZyb20gUkZDIDY0MzcgcHVyaXNtIHRoZXJlIGlzIHRoYXQgaXQgdHJlYXRz
IHRoZSBleGlzdGluZw0KPiBmbG93IGxhYmVsIG9uIHRoZSBwYWNrZXRzIGFzIGlmIGl0IHdhcyB6
ZXJvLg0KPiANCltQVF0geWVzDQoNCj4gMy4gSXQgcmVxdWlyZXMgdGhhdCB0aGUgcm9vdCByZXdy
aXRlcyB0aGUgZmxvdyBsYWJlbCBvbiBpbmJvdW5kIHBhY2tldHMgZXZlbiBpZg0KPiB0aGV5IGFy
ZSBhbHJlYWR5IHNldCB0byBub24temVyby4NCj4gVGhhdCBpcyBpbmRlZWQgYSB2aW9sYXRpb24g
b2YgUkZDIDY0MzcuIEJ1dCBpdCBpcyBhIHZpb2xhdGlvbiB3ZSBoYXZlIGFscmVhZHkNCj4gYWNj
ZXB0ZWQgaW4gYW5vdGhlciBjYXNlOiAiZm9yIGNvbXBlbGxpbmcgb3BlcmF0aW9uYWwgc2VjdXJp
dHkgcmVhc29ucyIuDQo+IFdoYXQncyBsb3N0PyBUaGUgYWJpbGl0eSBmb3Igbm9kZXMgaW5zaWRl
IHRoZSBST0xMIGRvbWFpbiB0byBwZXJmb3JtIGZsb3ctDQo+IGxhYmVsIGJhc2VkIGxvYWQgYmFs
YW5jaW5nIGZvciBzdWNoIGluYm91bmQgcGFja2V0cy4gSSB0aGluayBpdCdzIGZvciBST0xMIGFu
ZA0KPiA2VElTQ0ggdG8gc2F5IHdoZXRoZXIgdGhhdCBsb3NzIG1hdHRlcnMuDQogDQpbUFRdIFJv
bGwgYW5kIDZUaVNDSCBhcmUgY29waWVkOyB0aGUgZHJhZnQgaGFzIGNpcmN1bGF0ZWQgYXMgYSBS
T0xMIGRyYWZ0IGZvciBxdWl0ZSBhIHdoaWxlIHdpdGhvdXQgYW4gb2JqZWN0aW9uIG9uIHRoYXQg
bWF0dGVyLg0KV2UgYXJlIG5vdCBkZXByZWNhdGluZyB0aGUgb3RoZXIgbWV0aG9kLCBidXQgd2Ug
YXJlIHByb3Bvc2luZyBhbiBhbHRlcm5hdGUgbWV0aG9kLiBJIHJlc3VsdHMgdGhhdCB3ZSdsbCBo
YXZlIHRvIGRlY2lkZSBob3cgYW4gaW1wbGVtZW50YXRpb24ga25vd3Mgd2hpY2ggbWV0aG9kIHRv
IHVzZS4NCg0KDQoNCg0KPiBJbiBteSBvcGluaW9uLCB3ZSBzaG91bGRuJ3QgYmUgcmVsaWdpb3Vz
IGFib3V0IHRoaXMgYXMgbG9uZyBhcyBwb2ludCAxIGlzDQo+IGd1YXJhbnRlZWQuIEkgZG9uJ3Qg
c2VlIGFueSByaXNrcyB0byB0aGUgZ2VuZXJpYyB1c2Ugb2YgdGhlIGZsb3cgbGFiZWwuDQo+IA0K
DQoNCg0KPiBJIHRoaW5rIHRoZSBsYW5ndWFnZSBhcm91bmQgdGhlIHJlbGF0aW9uc2hpcCB3aXRo
IFJGQyA2NDM3IGlzIGEgYml0IGRlZmVuc2l2ZQ0KPiBhdCB0aGUgbW9tZW50IGFuZCBjb3VsZCBw
cm9iYWJseSBiZSBhIGJpdCBzaW1wbGVyIGFuZCBjbGVhcmVyLiAoIlRoZQ0KPiBmb2xsb3dpbmcg
ZXhjZXB0aW9ucyB0byB0aGUgcnVsZXMgaW4gW1JGQzY0MzddIGFyZSBtYWRlOi4uLiIpLiBJJ2Qg
aGF2ZSBhDQo+IHByZWZlcmVuY2UgZm9yIGRvaW5nIHRoYXQgd2l0aG91dCBhIGZvcm1hbCB1cGRh
dGUgdG8gNjQzNywgYmVjYXVzZSBpdCdzIG9ubHkNCj4gUlBMIGltcGxlbWVudG9ycyB3aG8gbmVl
ZCB0byBjaGFuZ2UgYW55dGhpbmcuDQoNCltQVF0gQ2FuIEkgY2hhbmdlIHRoYXQgdGV4dCB0byBk
ZXNjcmliZSB0aGUgYmVoYXZpb3IgcHJvcG9zZWQgYnkgdGhlIGRyYWZ0IGluc2lkZSB0aGUgUlBM
IGRvbWFpbiBhcyB0aGUgd2F5IHRoZSBydWxlcyBpbiA2NDM3IGFyZSBpbnRlcnByZXRlZD8NCg0K
DQpDaGVlcnMsDQoNClBhc2NhbA0KPiA+DQo+ID4gRnJvbTogeHZpbGFqb3NhbmFAZ21haWwuY29t
IFttYWlsdG86eHZpbGFqb3NhbmFAZ21haWwuY29tXSBPbiBCZWhhbGYNCj4gPiBPZiBYYXZpZXIg
VmlsYWpvc2FuYQ0KPiA+IFNlbnQ6IGpldWRpIDE3IGF2cmlsIDIwMTQgMTA6MDANCj4gPiBUbzog
SW5lcyBSb2JsZXMNCj4gPiBDYzogUGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KTsgNnRpc2NoQGll
dGYub3JnOyByb2xsDQo+ID4gU3ViamVjdDogUmU6IFs2dGlzY2hdIFtSb2xsXSBTdXBwb3J0IG9m
IGZsb3cgbGFiZWwgdG8gY2FycnkgdGhlIFJQTA0KPiA+IGluZm9ybWF0aW9uIGluIGRhdGEgcGFj
a2V0cw0KPiA+DQo+ID4gKzEgSSB0aGluayB0aGlzIGlzIG1vcmUgdGhhbiBuZWVkZWQuIEluIGFk
ZGl0aW9uIFJGQyA2MjgyIGRlZmluZXMgaG93DQo+IGhlYWRlciBjb21wcmVzc2lvbiBuZWVkcyB0
byBiZSBoYW5kbGVkIHRvZ2V0aGVyIHdpdGggZXh0ZW5zaW9uIGhlYWRlcnMuIEkNCj4gdGhpbmsg
dGhpcyBpcyBub3QgY2xlYXIgYW5kIGxlYWRzIHRvIGNvbmZ1c2lvbnMgKGFmZWN0aW5nIGFscmVh
ZHkgc29tZQ0KPiB3aXJlc2hhcmsgZGlzc2VjdG9ycykuIFRoZSB1c2Ugb2YgZmxvdyBsYWJlbCB3
aWxsIHNvbHZlIHNldmVyYWwgcHJvYmxlbXMgYXQNCj4gb25jZS4NCj4gPg0KPiA+IFguDQo+ID4N
Cj4gPg0KPiA+DQo+ID4gMjAxNC0wNC0xNiAyMjo0NCBHTVQrMDI6MDAgSW5lcyBSb2JsZXMNCj4g
PG1hcmlhaW5lc3JvYmxlc0Bnb29nbGVtYWlsLmNvbTxtYWlsdG86bWFyaWFpbmVzcm9ibGVzQGdv
b2dsZW1haWwuY29tDQo+ID4+Og0KPiA+ICsxDQo+ID4NCj4gPiBJbmVzDQo+ID4NCj4gPiAyMDE0
LTA0LTE1IDIxOjE5IEdNVC0wMzowMCBRaW4gV2FuZw0KPiA8cWlud2FuZzZ0b3BAeWFob28uY29t
PG1haWx0bzpxaW53YW5nNnRvcEB5YWhvby5jb20+PjoNCj4gPiArMQ0KPiA+DQo+ID4gUWluDQo+
ID4gT24gV2VkbmVzZGF5LCBBcHJpbCAxNiwgMjAxNCAxOjQ3IEFNLCBQcm9mLiBEaWVnbyBEdWpv
dm5lDQo+IDxkaWVnby5kdWpvdm5lQG1haWwudWRwLmNsPG1haWx0bzpkaWVnby5kdWpvdm5lQG1h
aWwudWRwLmNsPj4gd3JvdGU6DQo+ID4gKzEgIQ0KPiA+DQo+ID4gMjAxNC0wNC0xNSAxMjoyNSBH
TVQtMDM6MDAgVG9tIFBoaW5uZXkNCj4gPHRvbS5waGlubmV5QGNveC5uZXQ8bWFpbHRvOnRvbS5w
aGlubmV5QGNveC5uZXQ+PjoNCj4gPiArMSBmb3Igc3VyZS4gVGhlIGZsb3cgbGFiZWwgaGFzIGFs
d2F5cyBiZWVuIHRoZSBwcmVmZXJhYmxlIG1ldGhvZCBmb3IgbWUsDQo+IGFuZCBJIHN1c3BlY3Qg
Zm9yIG90aGVycyB3aXRoIGtub3dsZWRnZSBvZiBob3cgaXQgaXMgdXNlZCBpbiBJU0ExMDAuMTFh
Lg0KPiA+ID09PQ0KPiA+DQo+ID4gT24gMjAxNC4wNC4xNSAwNzx0ZWw6MjAxNC4wNC4xNSUyMDA3
PjoyNSwgUGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KQ0KPiB3cm90ZToNCj4gPiBEZWFyIGFsbDoN
Cj4gPg0KPiA+IEFzIHNvbWUgb2YgeW91IHJlbWVtYmVyLCB0aGUgUlBMIHNwZWNpZmljYXRpb24g
aGFzIGNoYW5nZWQgb3ZlciB0aW1lDQo+IFdSVCB0byB0aGUgbG9jYXRpb24gb2YgdGhlIGluZm9y
bWF0aW9uIHRoYXQgUlBMIHBsYWNlcyBpbiB0aGUgZGF0YSBwYWNrZXRzLg0KPiBXZSBzdGFydGVk
IHdpdGggdGhlIGZsb3cgbGFiZWwgYnV0IHRoZXNlIHdlcmUgdGhlIGRheXMgd2hlbiB3aGF0IGJl
Y2FtZQ0KPiBSRkMgNjQzNyB3YXMgYmVpbmcgZGVmaW5lZCBhdCA2TUFOLCBzbyB3ZSBzaGllZCBh
d2F5IGFuZCBkZWZpbmVkIHRoZQ0KPiBIYkggdGVjaG5pcXVlIHRoYXQgaXMgbm93IHNwZWNpZmll
ZCBhcyBSRkMgNjU1My4NCj4gPg0KPiA+IFdl4oCZbGwgbm90ZSB0aGF0IHRoZSBSUEwgb3B0aW9u
IGRlZmluZWQgaW4gUkZDIDY1NTMgdGFrZXMgNiBvY3RldHMsIGFuZCB3aXRoDQo+IHRoZSBIYkgg
aGRyIHdlIGVuZCB1cCB3aXRoIDggZXh0cmEgb2N0ZXRzLiBBbiBleHRyYSBJUC1pbi1JUCBlbmNh
cHN1bGF0aW9uIGlzDQo+IHJlcXVpcmVkIG9uIHRvcCBvZiB0aGF0IHVubGVzcyBib3RoIGVuZHBv
aW50cyBhcmUgaW4gdGhlIHNhbWUgUlBMIGRvbWFpbi4NCj4gQWxsIHRoaXMgb3ZlcmhlYWQgbWF5
IGJlIGFjY2VwdGFibGUgd2hlbiBwb3dlciBpcyBhdmFpbGFibGUgYW5kIHRoZSBQSFkNCj4gYWxs
b3dzIGZvciBsYXJnZXIgZnJhbWVzLCBidXQgaW4gdHJhZGl0aW9uYWwgYmF0dGVyeS1vcGVyYXRl
ZCAxNS40IHdpdGggfiA4MA0KPiBieXRlcyB1c2FibGUgcGVyIGZyYW1lLCBteSBleHBlcmllbmNl
IGZyb20gaW50ZWdyYXRpbmcgNkxvV1BBTiBIQyB3aXRoDQo+IElTQTEwMC4xMWEgc2F5cyB0aGF0
IGFsbCB0aGVzZSBleHRyYSBieXRlcyB3aWxsIGJlIG9uIHRoZSB3YXkgb2YgdGhlIDZUaVNDSA0K
PiBhZG9wdGlvbi4NCj4gPg0KPiA+IFN0aWxsLCBib3RoIFJGQyA2NTUwIGFuZCBSRkMgNjU1MiBh
cmUgZGVzaWduZWQgdG8gYWxsb3cgZm9yIGFuIGFsdGVybmF0ZQ0KPiB0ZWNobmlxdWUgYW5kIGlu
IHBhcnRpY3VsYXIgZm9yIHRoZSB1c2Ugb2YgdGhlIGZsb3cgbGFiZWwsIGFzIGlzIGVsYWJvcmF0
ZWQgaW4NCj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtdGh1YmVydC1yb2xsLWZs
b3ctbGFiZWwtMDIgLiBVc2luZyB0aGUgZmxvdw0KPiBsYWJlbCByZWR1Y2VzIHRoZSBjb3N0IG9m
IHRoZSBSUEwgaW5mb3JtYXRpb24gZHJhbWF0aWNhbGx5LCBkb3duIHRvIGEgbGV2ZWwNCj4gdGhh
dCBpcyBwcm9iYWJseSBhY2NlcHRhYmxlIGZvciB0aGUgdGFyZ2V0IFNET3MuDQo+ID4NCj4gPiBT
byBteSBwbGFuIGZvciBub3cgaXMgdG8gbW92ZSB0aGUgZmxvdyBsYWJlbCBkcmFmdCB0byA2TUFO
IGFuZCBwcmVwYXJlDQo+IGZvciBhIGhvdCBzZWFzb24sIGFuZCBJ4oCZbSBsb29raW5nIGZvciBz
dXBwb3J0IGZyb20gYm90aCA2VGlTQ0ggYW5kIFJPTEwgdG8NCj4gYmFjayBtZSB1cCBmcm9tIHRo
ZSBzdGFydC4gIFllcywgeW91IGNhbiBoZWxwIQ0KPiA+DQo+ID4gUGxlYXNlICsxIGlmIHlvdSBh
Z3JlZSB3ZSBuZWVkIHRoaXMgd29yayB0byBoYXBwZW4sIGFuZC9vciBwcm92aWRlIGFueQ0KPiBz
dWdnZXN0aW9uLg0KPiA+DQo+ID4gQ2hlZXJzLA0KPiA+DQo+ID4gUGFzY2FsDQo+ID4NCj4gPg0K
PiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4N
Cj4gPiA2dGlzY2ggbWFpbGluZyBsaXN0DQo+ID4NCj4gPiA2dGlzY2hAaWV0Zi5vcmc8bWFpbHRv
OjZ0aXNjaEBpZXRmLm9yZz4NCj4gPg0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vNnRpc2NoDQo+ID4NCj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+ID4gNnRpc2NoIG1haWxpbmcgbGlzdA0KPiA+IDZ0aXNj
aEBpZXRmLm9yZzxtYWlsdG86NnRpc2NoQGlldGYub3JnPg0KPiA+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vNnRpc2NoDQo+ID4NCj4gPg0KPiA+DQo+ID4gLS0NCj4gPiBE
SUVHTyBEVUpPVk5FDQo+ID4gQWNhZMOpbWljbyBFc2N1ZWxhIGRlIEluZ2VuaWVyw61hIGVuIElu
Zm9ybcOhdGljYSB5IFRlbGVjb211bmljYWNpb25lcw0KPiA+IEZhY3VsdGFkIGRlIEluZ2VuaWVy
w61hIFVEUA0KPiA+IHd3dy5pbmdlbmllcmlhLnVkcC5jbDxodHRwOi8vd3d3LmluZ2VuaWVyaWEu
dWRwLmNsLz4NCj4gPiAoNTYgMikgNjc2IDgxMjU8dGVsOiUyODU2JTIwMiUyOSUyMDY3NiUyMDgx
MjU+DQo+ID4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KPiA+IDZ0aXNjaCBtYWlsaW5nIGxpc3QNCj4gPiA2dGlzY2hAaWV0Zi5vcmc8bWFpbHRv
OjZ0aXNjaEBpZXRmLm9yZz4NCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvLzZ0aXNjaA0KPiA+DQo+ID4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPiA+IFJvbGwgbWFpbGluZyBsaXN0DQo+ID4gUm9sbEBpZXRmLm9y
ZzxtYWlsdG86Um9sbEBpZXRmLm9yZz4NCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3JvbGwNCj4gPg0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4gPiA2dGlzY2ggbWFpbGluZyBsaXN0DQo+ID4gNnRpc2No
QGlldGYub3JnPG1haWx0bzo2dGlzY2hAaWV0Zi5vcmc+DQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby82dGlzY2gNCj4gPg0KDQo=


From nobody Fri May  2 13:22:53 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5D521A091A; Fri,  2 May 2014 13:22:51 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZtI7PfoqNXk; Fri,  2 May 2014 13:22:50 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 281C21A0913; Fri,  2 May 2014 13:22:50 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id y13so2924946pdi.35 for <multiple recipients>; Fri, 02 May 2014 13:22:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tCwYi14ig0Hy3fL6R9kS+T1itv9sheo6sd5ZStfPA5U=; b=bOwf94hDLKJ1/r3qudGwcgIykNx4Xo8Cy0f94jL30dFetYWUSYwR7yV7Vplbp5COLL YHYYth8Uxjrjnsm4Axhf6LeQAzRG+s2tDZJccTG4d2u3YaRj37UZXmx3K3At/Yai+qd1 2GAoupaPdIXrGHid46YPcisK+mGb2aFaTmE2zqSpZRuFLQb/wLCtwNL2kBX4sh/kbVLf E2Jsnu6bof5MQYTBLdOABaAKOtuocizh4xgXFE5ONMIkIs2dzLoy7uFOy62E5IaqgA0V evAwyWSVB9YrrVmH8DbYoD23Ml9IxjWxQVMKK01LW/tIALIxZDgxZ+4fwQ2Wkj+hS+4n HTZw==
X-Received: by 10.66.136.71 with SMTP id py7mr39005798pab.2.1399062167684; Fri, 02 May 2014 13:22:47 -0700 (PDT)
Received: from [192.168.178.20] (206.200.69.111.dynamic.snap.net.nz. [111.69.200.206]) by mx.google.com with ESMTPSA id xo9sm122918pab.18.2014.05.02.13.22.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 May 2014 13:22:46 -0700 (PDT)
Message-ID: <5363FE97.7090103@gmail.com>
Date: Sat, 03 May 2014 08:22:47 +1200
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: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
References: <E045AECD98228444A58C61C200AE1BD842632160@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD842632160@xmb-rcd-x01.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/AGWC-n4FPG0AstNZ_B72bbDXuZE
Cc: roll <roll@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>, Pat Kinney <pat.kinney@KINNEYCONSULTINGLLC.COM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 20:22:52 -0000

Hi Pascal,

Just responding to your question:

On 03/05/2014 04:54, Pascal Thubert (pthubert) wrote:
...
>> I think the language around the relationship with RFC 6437 is a bit defensive
>> at the moment and could probably be a bit simpler and clearer. ("The
>> following exceptions to the rules in [RFC6437] are made:..."). I'd have a
>> preference for doing that without a formal update to 6437, because it's only
>> RPL implementors who need to change anything.
> 
> [PT] Can I change that text to describe the behavior proposed by the draft inside the RPL domain as the way the rules in 6437 are interpreted?

Well, I don't think personally that you need to be shy about saying
that within an RPL domain, the rules are in fact slightly changed instead
of being interpreted. The main thing is to be completely clear.

    Brian


From nobody Sat May  3 12:12:20 2014
Return-Path: <heard@pobox.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27E351A0103 for <ipv6@ietfa.amsl.com>; Sat,  3 May 2014 12:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Se0ZWD4vAM0u for <ipv6@ietfa.amsl.com>; Sat,  3 May 2014 12:12:16 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB401A0100 for <ipv6@ietf.org>; Sat,  3 May 2014 12:12:16 -0700 (PDT)
Received: (qmail 8991 invoked from network); 3 May 2014 12:12:13 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 3 May 2014 12:12:12 -0700
Date: Sat, 3 May 2014 12:12:12 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-gont-6man-ipv6-universal-extension-header-01.txt
In-Reply-To: <536317AE.1090500@gmail.com>
Message-ID: <Pine.LNX.4.64.1405031048580.14081@shell4.bayarea.net>
References: <20140408103907.23507.46057.idtracker@ietfa.amsl.com> <536317AE.1090500@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/a7DYJwOXTJxoZdBQvNBrwkIbSFs
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 May 2014 19:12:18 -0000

On Fri, 2 May 2014, Brian E Carpenter wrote:
> I've finally understood what's been bothering me about this draft.
> Actually, two things:
> 
> 1. If a node (regardless of whether it's the destination host,
> or an intermediate node such as a firewall) has a policy
> of discarding packets with an unknown extension header
> or an unknown transport protocol, it *doesn't matter* that
> it can't distinguish them. The packet is discarded anyway.
> 
> Comment on that: In either case, this discard by a host is
> consistent with RFC2460 (even as updated by RFC7045). In either
> case, it's what we would expect a firewall to do if it has the
> usual sort of paranoid policy, and that again is consistent
> with RFC7045.

What motivated the draft was work on L2 middlebox functions that are 
not required to have the usual paranoid "default deny" policy in 
order to accomplish the intended purpose.  One was RA-Guard (see 
http://tools.ietf.org/html/rfc7113); the other was DHCPv6-Shield 
(http://tools.ietf.org/html/draft-ietf-opsec-dhcpv6-shield).  For 
those functions extension headers do not matter so long as the 
transport header can be found and inspected; the implementation 
advice for the RA-Guard and DHCPv6-Shield filters is to pass 
everything that can be positively identified as NOT being a 
forbidden RA message or DHCPv6 message.

That being said, if Brian is correct in his assertion that we should 
expect typical filtering middleboxes to agressively apply a "default 
deny" policy to unknown extension headers, then I'd have to agree 
with his conclusion that UEH (or a reserved range of next header 
values) would fail to achieve its intended purpose, which is to get 
them to skip over unknown extention headers.  On the other hand, I 
have gotten the impression from much of the discussion here and on 
v6ops that the usual aim of filtering middeboxes is to inspect 
transport headers, not specifically extension headers, and apply a 
"default deny" policy to transport protocols.  If the reason packets 
with extension headers get dropped is because the middleboxes lack 
the ability to find the transport header, then UEH (or a reserved 
range of next header values) could help.

> 2. Given that argument, I think this draft should consider a 4th 
> possible solution: Do Nothing. I think it's a valid option.

If "do nothing" means make no changes to the normative 
specifications in 7045 and 6564, then yes, that is a valid option.

That being said, there has in the past been an impression that RFC 
6564 guaranteed that it would be possible to skip over unknown 
extension headers -- see, e.g., the changes in the above-referenced 
DHCPv6-Shield draft in going from -01 to -02.

In order to clear up thus confusion, it would probably be useful to 
at least publish advice to implementors of middleboxes that any 
unrecognized Next Header value SHOULD be treated as if it indicates 
the presence of an unknown upper-layer header, because it is unsafe 
to treat it as if it were a new extension header with the TLV format 
defined by RFC 6564.  It would also be good to remind them that they 
MUST provide a configuration option to allow packets containing such 
values, as specified in RFC 7045, noting that a side-effect of 
allowing all unrecognized extension headers is that unrecognized 
transport protocols will be allowed also.

Mike Heard


From nobody Mon May  5 19:11:31 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E13D1A01F9 for <ipv6@ietfa.amsl.com>; Mon,  5 May 2014 19:11:30 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czoJKZchNvJ9 for <ipv6@ietfa.amsl.com>; Mon,  5 May 2014 19:11:28 -0700 (PDT)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8F81A0114 for <ipv6@ietf.org>; Mon,  5 May 2014 19:11:28 -0700 (PDT)
Received: by mail-ie0-f171.google.com with SMTP id to1so9111966ieb.2 for <ipv6@ietf.org>; Mon, 05 May 2014 19:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/jtzjxQQNJ8EPnRobHkshJUYQCYMwNXXoI5czHMszjA=; b=vM8WJhGF74ZQ7basudWcj1pLcORY7i+6yUETuiyvkpNyPS0N3qVuuYTDbEO6vKNt+2 v+EfQ7RIc5JsPkNcEI+5lo6d1Fxx5B8fUfZx37kI/Kso3cnChtLBR8AdEQ0oLgXnKdlP BXCwuGHNBzqScKjsPe3w+iPm6Qws3G22mT525jNPiueVkOkJdMP+J8Srpnur2WVeEdka z4NOFFTLSJo6MY9d2IssORWmdrttBhXz44PMbL49oSpNBC3JQhtjwN+tsN+C9pEWYBuU 0o+YRzjUY1pN6NWFYEtD3I/ucgDcWodd925A6Kd/Opjx3Q8SW34sZHg9qYfWqcA3kjs2 LUaA==
X-Received: by 10.50.72.50 with SMTP id a18mr28600735igv.35.1399342284552; Mon, 05 May 2014 19:11:24 -0700 (PDT)
Received: from [192.168.178.20] (117.193.69.111.dynamic.snap.net.nz. [111.69.193.117]) by mx.google.com with ESMTPSA id x7sm11485372igw.1.2014.05.05.19.11.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 May 2014 19:11:23 -0700 (PDT)
Message-ID: <536844CC.9060706@gmail.com>
Date: Tue, 06 May 2014 14:11:24 +1200
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: "C. M. Heard" <heard@pobox.com>
Subject: Re: I-D Action: draft-gont-6man-ipv6-universal-extension-header-01.txt
References: <20140408103907.23507.46057.idtracker@ietfa.amsl.com> <536317AE.1090500@gmail.com> <Pine.LNX.4.64.1405031048580.14081@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1405031048580.14081@shell4.bayarea.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/YnNUuVdCuAKwWZioVAGfpi9ShRY
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 02:11:30 -0000

On 04/05/2014 07:12, C. M. Heard wrote:
> On Fri, 2 May 2014, Brian E Carpenter wrote:
>> I've finally understood what's been bothering me about this draft.
>> Actually, two things:
>>
>> 1. If a node (regardless of whether it's the destination host,
>> or an intermediate node such as a firewall) has a policy
>> of discarding packets with an unknown extension header
>> or an unknown transport protocol, it *doesn't matter* that
>> it can't distinguish them. The packet is discarded anyway.
>>
>> Comment on that: In either case, this discard by a host is
>> consistent with RFC2460 (even as updated by RFC7045). In either
>> case, it's what we would expect a firewall to do if it has the
>> usual sort of paranoid policy, and that again is consistent
>> with RFC7045.
> 
> What motivated the draft was work on L2 middlebox functions that are 
> not required to have the usual paranoid "default deny" policy in 
> order to accomplish the intended purpose.  One was RA-Guard (see 
> http://tools.ietf.org/html/rfc7113); the other was DHCPv6-Shield 
> (http://tools.ietf.org/html/draft-ietf-opsec-dhcpv6-shield).  For 
> those functions extension headers do not matter so long as the 
> transport header can be found and inspected; the implementation 
> advice for the RA-Guard and DHCPv6-Shield filters is to pass 
> everything that can be positively identified as NOT being a 
> forbidden RA message or DHCPv6 message.
> 
> That being said, if Brian is correct in his assertion that we should 
> expect typical filtering middleboxes to agressively apply a "default 
> deny" policy to unknown extension headers, then I'd have to agree 
> with his conclusion that UEH (or a reserved range of next header 
> values) would fail to achieve its intended purpose, which is to get 
> them to skip over unknown extention headers.  On the other hand, I 
> have gotten the impression from much of the discussion here and on 
> v6ops that the usual aim of filtering middeboxes is to inspect 
> transport headers, not specifically extension headers, and apply a 
> "default deny" policy to transport protocols.  If the reason packets 
> with extension headers get dropped is because the middleboxes lack 
> the ability to find the transport header, then UEH (or a reserved 
> range of next header values) could help.

The scenario would be, for example, a load balancer or QoS classifier
that needs to find the transport header in order to extract port numbers.
And yes, I think you're right, if we have to cope with the risk of both
unknown extension headers (presumed to conform to RFC 6564) *and*
unknown transport protcols (about which we can presume nothing).

>> 2. Given that argument, I think this draft should consider a 4th 
>> possible solution: Do Nothing. I think it's a valid option.
> 
> If "do nothing" means make no changes to the normative 
> specifications in 7045 and 6564, then yes, that is a valid option.
> 
> That being said, there has in the past been an impression that RFC 
> 6564 guaranteed that it would be possible to skip over unknown 
> extension headers -- see, e.g., the changes in the above-referenced 
> DHCPv6-Shield draft in going from -01 to -02.
> 
> In order to clear up thus confusion, it would probably be useful to 
> at least publish advice to implementors of middleboxes that any 
> unrecognized Next Header value SHOULD be treated as if it indicates 
> the presence of an unknown upper-layer header, because it is unsafe 
> to treat it as if it were a new extension header with the TLV format 
> defined by RFC 6564.  

Right, because even if they use the complete IANA list of extension
headers, as specified in RFC 7045, it might be out of date.

> It would also be good to remind them that they 
> MUST provide a configuration option to allow packets containing such 
> values, as specified in RFC 7045, noting that a side-effect of 
> allowing all unrecognized extension headers is that unrecognized 
> transport protocols will be allowed also.

Yes. Whatever we decide about this draft and UEH, I think an
implementation guide is sorely needed.

    Brian


From nobody Tue May  6 01:52:18 2014
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 668BC1A0720 for <ipv6@ietfa.amsl.com>; Tue,  6 May 2014 01:52:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ahh_k7Fvnv6P for <ipv6@ietfa.amsl.com>; Tue,  6 May 2014 01:52:15 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 88D4E1A03AC for <ipv6@ietf.org>; Tue,  6 May 2014 01:52:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 1DD7D87006F; Tue,  6 May 2014 10:52:11 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0m8sHqvNtLL9; Tue,  6 May 2014 10:52:11 +0200 (CEST)
Received: from Rays-iMac.local (unknown [IPv6:2001:470:1f15:73a:6d15:59e3:90a3:24cd]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id D220B87005B; Tue,  6 May 2014 10:52:10 +0200 (CEST)
Message-ID: <5368A2B2.80405@globis.net>
Date: Tue, 06 May 2014 10:52:02 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-predictable-fragment-id-01.txt
References: <20140430065359.31690.30174.idtracker@ietfa.amsl.com>
In-Reply-To: <20140430065359.31690.30174.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/L9g4f5oOfKrBF0XNhpBc22IPEvc
Cc: fgont@si6networks.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 08:52:17 -0000

I have read this draft and think thatit is very well written and that it 
is important work. Detailed comments below.

internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
>
>          Title           : Security Implications of Predictable Fragment Identification Values
>          Author          : Fernando Gont
> 	Filename        : draft-ietf-6man-predictable-fragment-id-01.txt
> 	Pages           : 16
> 	Date            : 2014-04-29
>
> Abstract:
>     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 a 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 employed for any other fragmented
>     packet sent recently with the same Source Address and Destination
>     Address.  Some implementations use simple a global counter for
>     setting the 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 Identification field of the Fragment
>     Header, such that the aforementioned security implications are
>     mitigated.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-predictable-fragment-id/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-predictable-fragment-id-01
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-predictable-fragment-id-01
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>


A potential DoS attack is described in section 3.


> Finally,
>    the attacker send forged IPv6 fragments to the Host B, with their
>    IPv6 Source Address set to that of Host A, and Identification values
>    that would result in collisions with the Identification values
>    employed for the legitimate traffic sent by Host A to Host B. If Host
>    B discards fragments that result in collisions of Identification
>    values (e.g., such fragments overlap, and the host implements
>    [RFC5722]), the attacker could simply trash the Identification space
>    by sending multiple forged fragments with different Identification
>    values, such that any subsequent packets from Host A to Host B are
>    discarded at Host B as a result of the malicious fragments sent by
>    the attacker.
Comment 1.
Would this attack also be applicable to any middleware boxes that track 
session progress at the fragmentation level?

DoS attacker Host C could create a race condition by sending spoofed 
packets from A to B with forged fragment ident values, and the 
middelware box would potentially forward (or attempt to re-assemble) 
these packets in preference to the real next fragments arriving from A.

s/If Host B discards fragments /If Host B, or any intermediate 
middleware box tracking the session, discards fragments/ ?


Comment 2.
/The Identification value of the Fragment Header MUST NOT be predictable 
by an off-path attacker./

I think there should be more of a constraint on what is "good enough"

Is this not a s/MUST NOT/SHOULD NOT/?

Nothing actually breaks immediately if the advice is ignored.


Comment 3.
I have a concern with the ability of implementations to be able to 
comply with this requirement.

The effective field length is apparently only 16 bits when used in 
combination with IPv6/IPv4 translation (according to Section 5).

Sending 2^16 attack packets is not a big ask.

And it will be far fewer if the attacker relies on birthday type 
collisions to only disrupt 1 in n packets. e.g. if there are many 
packets in the stream and the aim of the attacker is to occasionally 
disrupt the stream they only need to send a fraction of the number of 
attack packets needed to disrupt every single packet.

So I think I also have to ask "is the fragment ident itself sufficiently 
long/ protected to be resistant to birthday type attacks, especially in 
combination with RFC6415 IPv6/IPv4 translation?"


Comment 4.
Do we also need to mandate /Nodes SHOULD also implement ICMP specific 
attack countermeasures as described in [RFC 5927] / in section 4, to 
prevent an off-path attacker being able force use of fragmentation in 
the first place?



-- 
Regards,
RayH


From nobody Wed May  7 03:20:46 2014
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE5471A03A7 for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 03:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maSycl_2fVoq for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 03:20:42 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D811A029B for <ipv6@ietf.org>; Wed,  7 May 2014 03:20:42 -0700 (PDT)
Received: from [2001:5c0:1000:a::1cb7] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <fernando@gont.com.ar>) id 1Whyxl-0005SC-On; Wed, 07 May 2014 12:20:34 +0200
Message-ID: <536A0828.5040103@gont.com.ar>
Date: Wed, 07 May 2014 05:17:12 -0500
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Ray Hunter <v6ops@globis.net>, ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-predictable-fragment-id-01.txt
References: <20140430065359.31690.30174.idtracker@ietfa.amsl.com> <5368A2B2.80405@globis.net>
In-Reply-To: <5368A2B2.80405@globis.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/XMOXxbBxp8DkbtU8adhSxCuLLxM
Cc: fgont@si6networks.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 10:20:45 -0000

Hi, Ray,

Thanks so much for your feedback! -- Please find my comments in-line...

On 05/06/2014 03:52 AM, Ray Hunter wrote:
> I have read this draft and think thatit is very well written and that it
> is important work. 

Thanks!



> 
>> Finally,
>>    the attacker send forged IPv6 fragments to the Host B, with their
>>    IPv6 Source Address set to that of Host A, and Identification values
>>    that would result in collisions with the Identification values
>>    employed for the legitimate traffic sent by Host A to Host B. If Host
>>    B discards fragments that result in collisions of Identification
>>    values (e.g., such fragments overlap, and the host implements
>>    [RFC5722]), the attacker could simply trash the Identification space
>>    by sending multiple forged fragments with different Identification
>>    values, such that any subsequent packets from Host A to Host B are
>>    discarded at Host B as a result of the malicious fragments sent by
>>    the attacker.
> Comment 1.
> Would this attack also be applicable to any middleware boxes that track
> session progress at the fragmentation level?

It certainly would. Question: do these voxes just "monitor" the traffic
(i.e., just snoop it), or do they actually receive-inspect-filter-if
appropriate)?   -- If the former, the attack could result in "evasion".
If the later, the attack would result in DoS.



> DoS attacker Host C could create a race condition by sending spoofed
> packets from A to B with forged fragment ident values, and the
> middelware box would potentially forward (or attempt to re-assemble)
> these packets in preference to the real next fragments arriving from A.

Agreed. That's, for instance, the DNS data-injection attack referenced
in the I-D.



> s/If Host B discards fragments /If Host B, or any intermediate
> middleware box tracking the session, discards fragments/ ?

I'd personally have the middleware stuff as a separate section or
paragraph.. what do you think?



> Comment 2.
> /The Identification value of the Fragment Header MUST NOT be predictable
> by an off-path attacker./
> 
> I think there should be more of a constraint on what is "good enough"
> 
> Is this not a s/MUST NOT/SHOULD NOT/?
> 
> Nothing actually breaks immediately if the advice is ignored.

I agree with the "nothing breaks" (and could certainly live with a
"SHOULD NOT")... although I'd note that it's pretty common to use
"MUST"s for security reasons... --- as in "the secret key MUST NOT be
known to possible attackers" or the like..

Another view is that if you include a "SHOULD NOT" (rather than MUST),
you should include cases where an implementer might decide to go against
the advice... but I don't see any reasons for that...



> Comment 3.
> I have a concern with the ability of implementations to be able to
> comply with this requirement.
> 
> The effective field length is apparently only 16 bits when used in
> combination with IPv6/IPv4 translation (according to Section 5).
> 
> Sending 2^16 attack packets is not a big ask.

I'd call that "brute forcing" rather than "predicting the ID".


> And it will be far fewer if the attacker relies on birthday type
> collisions to only disrupt 1 in n packets. e.g. if there are many
> packets in the stream and the aim of the attacker is to occasionally
> disrupt the stream they only need to send a fraction of the number of
> attack packets needed to disrupt every single packet.
> 
> So I think I also have to ask "is the fragment ident itself sufficiently
> long/ protected to be resistant to birthday type attacks, especially in
> combination with RFC6415 IPv6/IPv4 translation?"

It's certainly long enough. In this case, the problem is really in IPv4,
that has a far shorter Frag ID. I'd also say that I don't quite
understand why the translators expect to learn a sensible IPv4 Frag ID
from the IPv6 frag ID.  For instance, if the NAT64 box shares the same
IPv4 address among many IPv6 nodes, then, it may even lead to
collissions.  -- e.g.:


Host A   -----------
2001:db8::1         \+--------+
                     |        | 100.0.0.1
                     | NAT 64 +------------------ Host C
Host B   ------------|        |                   8.8.8.8
2001:db8::2          +--------+


Host A sends a packet "to 8.8.8.8" with frag ID 0xaaaa11111. Host B
sends a packet "to 8.8.8.8" with Frag ID 0xbbbb1111. Now both packets
employ the tuple (src 100.0.0.1, dst 8.8.8.8, frag id 0x1111) thus
resulting in a colision of Frag IDs.



> Comment 4.
> Do we also need to mandate /Nodes SHOULD also implement ICMP specific
> attack countermeasures as described in [RFC 5927] / in section 4, to
> prevent an off-path attacker being able force use of fragmentation in
> the first place?

I think they should -- also referencing RFC5927 in such a way would be a
down ref 8bcp/std track mandating an informational document). The only
caveat is: If the header chain is long enough (>1280 bytes), then the
transport protocol header will not be available in the ICMPv6 error.

(Unfortunately, mmany implementations don't even validate it when it's
available)

Thoughts?

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




From nobody Wed May  7 03:57:24 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F6701A06C9 for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 03:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oK0u3VHwBehc for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 03:57:20 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA8E41A064E for <ipv6@ietf.org>; Wed,  7 May 2014 03:57:19 -0700 (PDT)
Received: from [187.185.71.234] (helo=[172.17.68.218]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <fgont@si6networks.com>) id 1WhzXG-0005ZD-Rw; Wed, 07 May 2014 12:57:15 +0200
Message-ID: <536A0D7B.1070606@si6networks.com>
Date: Wed, 07 May 2014 05:39:55 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-gont-6man-ipv6-universal-extension-header-01.txt
References: <20140408103907.23507.46057.idtracker@ietfa.amsl.com> <536317AE.1090500@gmail.com>
In-Reply-To: <536317AE.1090500@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/RqLQZAyOzyzU88jeYzHgF63hJlE
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 10:57:22 -0000

Hi, Brian,

On 05/01/2014 10:57 PM, Brian E Carpenter wrote:
> 
> I've finally understood what's been bothering me about this draft.
> Actually, two things:
> 
> 1. If a node (regardless of whether it's the destination host,
> or an intermediate node such as a firewall) has a policy
> of discarding packets with an unknown extension header
> or an unknown transport protocol, it *doesn't matter* that
> it can't distinguish them. The packet is discarded anyway.
> 
> Comment on that: In either case, this discard by a host is
> consistent with RFC2460 (even as updated by RFC7045). 

While I agree that it is consistent with RFC2460, that also implicitly
means that new EHs are not incrementally deployable. Not only because of
firewalls, but also because of the hosts themselves. (i.e., if I send
you my packets with my sihny new EH then, if you don't understand it,
you'd drop the packet).

(another way to see it would be to assume that the reason for which
RFC2460 says so is because it didn't define a uniform format for EHs in
the first place?)


> In either
> case, it's what we would expect a firewall to do if it has the
> usual sort of paranoid policy, and that again is consistent
> with RFC7045.

I'm not sure I'd agree. in v4, some firewalls do not just filter packets
for the options they contain, but they do filter based on the {src ip,
dst ip, protocol, src port, dst port}



> 2. Given that argument, I think this draft should consider a
> 4th possible solution: Do Nothing. I think it's a valid option.

At the very least 6564 should probably be updated, or at least a
clarification issued. -- quite a few of us had assumed that as a result
of RFC6564, one could parse past unknown EH -- which is certainly not
possible.



> Nits: I don't see why this draft is tagged as Standards Track
> and Updates 2460. It's an informational discussion.

It's std track. And the "update" tag is because the UEH would be part of
the v6 specification (not to mention that otherwise it would be
virtually impossible for an IPv6 implementer to spot this document in
the first place).



> Please change the title of the draft. At the moment it has
> the same title as draft-gont-6man-rfc6564bis.

Will do.

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





From nobody Wed May  7 03:57:32 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB2E1A06D0 for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 03:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G-Uht2aL2545 for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 03:57:27 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) by ietfa.amsl.com (Postfix) with ESMTP id B83631A06CF for <ipv6@ietf.org>; Wed,  7 May 2014 03:57:27 -0700 (PDT)
Received: from [187.185.71.234] (helo=[172.17.68.218]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <fgont@si6networks.com>) id 1WhzXN-0005ZJ-PK; Wed, 07 May 2014 12:57:22 +0200
Message-ID: <536A114C.6060607@si6networks.com>
Date: Wed, 07 May 2014 05:56:12 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  "C. M. Heard" <heard@pobox.com>
Subject: Re: I-D Action: draft-gont-6man-ipv6-universal-extension-header-01.txt
References: <20140408103907.23507.46057.idtracker@ietfa.amsl.com> <536317AE.1090500@gmail.com> <Pine.LNX.4.64.1405031048580.14081@shell4.bayarea.net> <536844CC.9060706@gmail.com>
In-Reply-To: <536844CC.9060706@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/B_EZoAeWzC38eNaVk1j4CNEmDJQ
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 10:57:29 -0000

On 05/05/2014 09:11 PM, Brian E Carpenter wrote:
>>
>> That being said, if Brian is correct in his assertion that we should 
>> expect typical filtering middleboxes to agressively apply a "default 
>> deny" policy to unknown extension headers, 

Well, policy is policy. Why I'd expect such policy to be widespread,
we're essentially ruling out the other possibility.


>> then I'd have to agree 
>> with his conclusion that UEH (or a reserved range of next header 
>> values) would fail to achieve its intended purpose, which is to get 
>> them to skip over unknown extention headers.  On the other hand, I 
>> have gotten the impression from much of the discussion here and on 
>> v6ops that the usual aim of filtering middeboxes is to inspect 
>> transport headers, not specifically extension headers, and apply a 
>> "default deny" policy to transport protocols.

Exactly. That's the comment that I made in my previous response ot Brian.


>>> 2. Given that argument, I think this draft should consider a 4th 
>>> possible solution: Do Nothing. I think it's a valid option.
>>
>> If "do nothing" means make no changes to the normative 
>> specifications in 7045 and 6564, then yes, that is a valid option.
>>
>> That being said, there has in the past been an impression that RFC 
>> 6564 guaranteed that it would be possible to skip over unknown 
>> extension headers -- see, e.g., the changes in the above-referenced 
>> DHCPv6-Shield draft in going from -01 to -02.
>>
>> In order to clear up thus confusion, it would probably be useful to 
>> at least publish advice to implementors of middleboxes that any 
>> unrecognized Next Header value SHOULD be treated as if it indicates 
>> the presence of an unknown upper-layer header, because it is unsafe 
>> to treat it as if it were a new extension header with the TLV format 
>> defined by RFC 6564.  

Agreed.

> 
> Right, because even if they use the complete IANA list of extension
> headers, as specified in RFC 7045, it might be out of date.
> 
>> It would also be good to remind them that they 
>> MUST provide a configuration option to allow packets containing such 
>> values, as specified in RFC 7045, noting that a side-effect of 
>> allowing all unrecognized extension headers is that unrecognized 
>> transport protocols will be allowed also.
> 
> Yes. Whatever we decide about this draft and UEH, I think an
> implementation guide is sorely needed.

Yes. That's kind f the stuff we had in mind as part of elaborating on
Section 5.3 -- should that option be the "winner".

We will expand and resubmit.

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 nobody Wed May  7 09:27:23 2014
Return-Path: <heard@pobox.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78C411A0828 for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 09:27:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8QNca3xrsV0k for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 09:27:19 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id C417A1A0833 for <ipv6@ietf.org>; Wed,  7 May 2014 09:27:19 -0700 (PDT)
Received: (qmail 5826 invoked from network); 7 May 2014 09:27:14 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 7 May 2014 09:27:14 -0700
Date: Wed, 7 May 2014 09:27:14 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-gont-6man-ipv6-universal-extension-header-01.txt
In-Reply-To: <536A0D7B.1070606@si6networks.com>
Message-ID: <Pine.LNX.4.64.1405070835390.4162@shell4.bayarea.net>
References: <20140408103907.23507.46057.idtracker@ietfa.amsl.com> <536317AE.1090500@gmail.com> <536A0D7B.1070606@si6networks.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Ou2PWcBmpMXDb3-Gx_8JbqZyh2I
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 16:27:21 -0000

On Wed, 7 May 2014, Fernando Gont wrote:
> On 05/01/2014 10:57 PM, Brian E Carpenter wrote:
> > I've finally understood what's been bothering me about this draft.
> > Actually, two things:
> > 
> > 1. If a node (regardless of whether it's the destination host,
> > or an intermediate node such as a firewall) has a policy
> > of discarding packets with an unknown extension header
> > or an unknown transport protocol, it *doesn't matter* that
> > it can't distinguish them. The packet is discarded anyway.
> > 
> > Comment on that: In either case, this discard by a host is
> > consistent with RFC2460 (even as updated by RFC7045). 
> 
> While I agree that it is consistent with RFC2460, that also implicitly
> means that new EHs are not incrementally deployable. Not only because of
> firewalls, but also because of the hosts themselves. (i.e., if I send
> you my packets with my [shiny] new EH then, if you don't understand it,
> you'd drop the packet).

I don't agree with that at all.  If intermediate systems were 
transparent to EHs, as envisioned by RC 2460, then it would be 
possible for consenting hosts to use them without updates to the 
intervening network.  That counts as incremental deployment to me.

> (another way to see it would be to assume that the reason for which
> RFC2460 says so is because it didn't define a uniform format for EHs in
> the first place?)

I'd be inclined to say RFC 2460 did not bother to define a uniform 
format for EHs because it there was no need: the Destination Options 
header already provided a way to provide optional information that a 
host could skip over (i.e., ignore).  Here is what it said:

   Note that there are two possible ways to encode optional destination
   information in an IPv6 packet: either as an option in the Destination
   Options header, or as a separate extension header.  The Fragment
   header and the Authentication header are examples of the latter
   approach.  Which approach can be used depends on what action is
   desired of a destination node that does not understand the optional
   information:

      o  If the desired action is for the destination node to discard
         the packet and, only if the packet's Destination Address is not
         a multicast address, send an ICMP Unrecognized Type message to
         the packet's Source Address, then the information may be
         encoded either as a separate header or as an option in the
         Destination Options header whose Option Type has the value 11
         in its highest-order two bits.  The choice may depend on such
         factors as which takes fewer octets, or which yields better
         alignment or more efficient parsing.

      o  If any other action is desired, the information must be encoded
         as an option in the Destination Options header whose Option
         Type has the value 00, 01, or 10 in its highest-order two bits,
         specifying the desired action (see section 4.2).

To me, it is obvious that anything UEH can do, a destination option 
can also do, provided that a destination option header is allowed to 
appear as many times as needed.  To see this, consider the proposed 
UEH format:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Next Header  |  Hdr Ext Len  |    Subtype    |               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               +
    |                                                               |
    .                                                               .
    .                   Subtype Specific Data                       .
    .                                                               .
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


If this were encoded as a destination option, it would look like this:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Next Header  |  Hdr Ext Len  |    Subtype    | SubtypDataLen |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                                                               |
    .                                                               .
    .                   Subtype Specific Data                       .
    .                                                               .
    |                                                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

True, the subtype would need to have the two upper bits encoded to 
signal to the destination what to do if it does not understand the 
subtype.  But that is a feature, not a bug.  It also requires one 
extra byte for a possibly redundant subtype/option data length.  
One could imagine circumstances in which this would expand the 
header by up to eight bytes.  There is a possible cost in 
efficiency, but not in functionality.

> > In either case, it's what we would expect a firewall to do if it 
> > has the usual sort of paranoid policy, and that again is 
> > consistent with RFC7045.
> 
> I'm not sure I'd agree. in v4, some firewalls do not just filter packets
> for the options they contain, but they do filter based on the {src ip,
> dst ip, protocol, src port, dst port}

If firewalls treat IPv6 destination options as the do IPv4 options, 
then the desired effect is achieved by using the destination options 
header instead of the proposed UEH.

//cmh


From nobody Wed May  7 11:25:47 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4C501A035C for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 11:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQQ7dBNZkwf0 for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 11:25:44 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id B0BFC1A0207 for <ipv6@ietf.org>; Wed,  7 May 2014 11:25:44 -0700 (PDT)
Received: from [192.168.10.14] (77.18.132.223.tmi.telenormobil.no [77.18.132.223]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id EF5F4606E; Wed,  7 May 2014 11:25:38 -0700 (PDT)
From: Ole Troan <otroan@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_A10C35DC-ADB6-431B-89A4-F73A432A2569"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: No 6MAN session planned for IETF90
Date: Wed, 7 May 2014 20:25:33 +0200
Message-Id: <17A5AD98-783A-4F35-A310-9FA4D55DDF8F@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/zErOh1GrXAFKelaIVupOf_U5CmM
Cc: 6man-ads@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 18:25:45 -0000

--Apple-Mail=_A10C35DC-ADB6-431B-89A4-F73A432A2569
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

The chairs have decided to not hold a 6man session at IETF90.

Bob is not going to be in Toronto, because he is sailing to Hawaii (not =
to get their early though), while Ole is on holiday for most of July. =
After discussing the issue with our AD, and looking at the list of =
working group drafts, we have decided to not hold a 6MAN session at =
IETF90.  We feel there are not any pressing issues that need =
face-to-face discussion.

We=92ll continue progressing the documents as we get them as normal, and =
we also encourage the group continue work on the mailing list.

See you at IETF91 in Honolulu!

Best regards,
Bob and Ole

--Apple-Mail=_A10C35DC-ADB6-431B-89A4-F73A432A2569
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJTanqdAAoJEFuJXizso86gUFgIAMJM9IG2e15OHH795ogRMkKt
57k3HN+YHgwK3kBbeOrXwdK6f4GhC+07WkuP3VSDjrpX2mm5G4HXiPlbdKIkYMXP
McVBWrwAr/y/7Kgvxr9iHrm5yTOgX4k2CeA5CyueQfxl9IDlBO+esvfRJLngsevt
VZ80gT7idgI52KrKoyihoUyX9E8V61dwcNfy6L4iRh9W9xqr0sQr57m5xo/HzSZE
f+wSnnqYNeBeWSxesN4/hUPaeDC6FA7zO/FkI13Eb4Q7qxWmf4FIHJFZ2mldfhEX
t4TFdimXCO8St69cXcx1RYlEirs42wB26RREvdgtqxhEyEZNTwYqa15p1UuySi0=
=4XiH
-----END PGP SIGNATURE-----

--Apple-Mail=_A10C35DC-ADB6-431B-89A4-F73A432A2569--


From nobody Wed May  7 13:48:08 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 036F71A02F6 for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 13:48:06 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wqpck27yZ_nf for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 13:48:04 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id C516F1A01A0 for <ipv6@ietf.org>; Wed,  7 May 2014 13:48:04 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kp14so1626045pab.40 for <ipv6@ietf.org>; Wed, 07 May 2014 13:48:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gdpkzwOhGmzzS11KyDkhO2AdGQ2EEzk/mlv0Jyw7K/E=; b=s8fFBl4PqgzRrPiJiNZ/U78gFlqTWvF9nGJUBFochmvxRCRJfjytRHI7uzDGBq+UaU 5GsmeGAN573sXP7H07ydkPZVIPByEZrCRO/MNUN7XnT/evCRN5kXj0l83JlE2e5vJVvV oDpxauiNmzhFLzN8l8CCiz54ejDUi9ODVPwNp5qbKo7nG09wtpSCchvVENFJkbkOXYyE kciBneQtxMBegi8o/UNvferXN5vR8+xndVO1Og9/aY271hJIokc22bXKHGqu4JGEXhXV pLMWSsFnNuKEbKwbKlFfkly+Mo/Wa0Hx+1g91k85kcu53MWvMBnx/UZqjo0hxZyL/fYP NJ8g==
X-Received: by 10.66.139.38 with SMTP id qv6mr23248541pab.123.1399495680662; Wed, 07 May 2014 13:48:00 -0700 (PDT)
Received: from [192.168.178.20] (242.193.69.111.dynamic.snap.net.nz. [111.69.193.242]) by mx.google.com with ESMTPSA id tf10sm4779734pbc.70.2014.05.07.13.47.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 May 2014 13:47:59 -0700 (PDT)
Message-ID: <536A9C05.3010102@gmail.com>
Date: Thu, 08 May 2014 08:48:05 +1200
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: I-D Action: draft-gont-6man-ipv6-universal-extension-header-01.txt
References: <20140408103907.23507.46057.idtracker@ietfa.amsl.com> <536317AE.1090500@gmail.com> <536A0D7B.1070606@si6networks.com>
In-Reply-To: <536A0D7B.1070606@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/noXWbfOnaf3N1Z6jHCMTV7ytf3s
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 20:48:06 -0000

Fernando,

On 07/05/2014 22:39, Fernando Gont wrote:
...
>> Nits: I don't see why this draft is tagged as Standards Track
>> and Updates 2460. It's an informational discussion.

(My error: it claims to update 6564 in fact, but my comment stands.)

> 
> It's std track. And the "update" tag is because the UEH would be part of
> the v6 specification (not to mention that otherwise it would be
> virtually impossible for an IPv6 implementer to spot this document in
> the first place).

Sorry, that seems completely wrong to me. draft-gont-6man-rfc6564bis
is clearly standards track and this one clearly isn't. To quote
the Abstract, it "analyzes a problem... and discusses a number of
possible solutions." That's Informational.

   Brian



> 
> 
> 
>> Please change the title of the draft. At the moment it has
>> the same title as draft-gont-6man-rfc6564bis.
> 
> Will do.
> 
> Thanks!


From nobody Wed May  7 15:09:31 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13D3E1A03DD for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 15:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QwsYStisCEZ for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 15:09:23 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) by ietfa.amsl.com (Postfix) with ESMTP id 840141A03B8 for <ipv6@ietf.org>; Wed,  7 May 2014 15:09:23 -0700 (PDT)
Received: from [190.112.53.37] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <fgont@si6networks.com>) id 1WiA1d-0007dX-K2; Thu, 08 May 2014 00:09:17 +0200
Message-ID: <536AA04D.6010305@si6networks.com>
Date: Wed, 07 May 2014 16:06:21 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-gont-6man-ipv6-universal-extension-header-01.txt
References: <20140408103907.23507.46057.idtracker@ietfa.amsl.com> <536317AE.1090500@gmail.com> <536A0D7B.1070606@si6networks.com> <536A9C05.3010102@gmail.com>
In-Reply-To: <536A9C05.3010102@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/cFj3XtsoavqfgNy7uN8uEoxKgp4
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:09:26 -0000

On 05/07/2014 03:48 PM, Brian E Carpenter wrote:
> Fernando,
> 
> On 07/05/2014 22:39, Fernando Gont wrote:
> ...
>>> Nits: I don't see why this draft is tagged as Standards Track
>>> and Updates 2460. It's an informational discussion.
> 
> (My error: it claims to update 6564 in fact, but my comment stands.)
> 
>>
>> It's std track. And the "update" tag is because the UEH would be part of
>> the v6 specification (not to mention that otherwise it would be
>> virtually impossible for an IPv6 implementer to spot this document in
>> the first place).
> 
> Sorry, that seems completely wrong to me. draft-gont-6man-rfc6564bis
> is clearly standards track and this one clearly isn't. To quote
> the Abstract, it "analyzes a problem... and discusses a number of
> possible solutions." That's Informational.

You're right about that. Explanation:

The original I-D was clearly std track, proposing a specific solution.
Since some folks suggested that there might be different possible paths
forward, we took a step back, and made this version comment on the
possible options, in the hopes that the next rev or some next rev would
stick to one of them.

I guess that we could just kept version -00, and publish a separate I-D
for the analysis of the possible options...

Thanks!

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





From nobody Wed May  7 15:32:28 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 602F41A03F4; Wed,  7 May 2014 15:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DGM1awRSwuLt; Wed,  7 May 2014 15:32:26 -0700 (PDT)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id CE8791A03E0; Wed,  7 May 2014 15:32:25 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id lh4so2210028vcb.34 for <multiple recipients>; Wed, 07 May 2014 15:32:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=No2To863Yem7IZani+jfExr5aeaOZ+6dm4qjuGGiduY=; b=y5fmZHr75+Fm0bsMNNmx3RwnpwJPb6sHAxtxoseOXZa90iJ93t5yfCAsnvfsgd32/G pO1P+G2x9ebp/8hVKA8IngF+1C6Hx2y0hmCfWnI1qwABdr8ouzNdZDH7OgBSjXQj7c7m Lz25itjRubHL7auxgILNGwHL59omswc2nRbQzLEi77pKown7yzoYiOvE35hjlpVss+nz 4t8uzPElbyi4svvBgmPnjd8OQVy9Nnm/PyQEKoX2/07UgmKDvN2+vt5MYCe5aO2WuKCs qtjf/gaK/M75X/1lvVn803vCrVkh//cGNSoyRXvRgu8nRAYevypwTS5sjJxF2zK1m34L rtAQ==
MIME-Version: 1.0
X-Received: by 10.58.123.71 with SMTP id ly7mr41090042veb.11.1399501941301; Wed, 07 May 2014 15:32:21 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Wed, 7 May 2014 15:32:21 -0700 (PDT)
In-Reply-To: <24b1d0b72a33014b063100842790fa2c@xs4all.nl>
References: <20140408120215.2961.44204.idtracker@ietfa.amsl.com> <24b1d0b72a33014b063100842790fa2c@xs4all.nl>
Date: Wed, 7 May 2014 19:32:21 -0300
Message-ID: <CAP+sJUeL_P+fRzSGJbXhH1qGTeEyj1wLn_5ms1mnX=PvNYqypg@mail.gmail.com>
Subject: Fwd: [Roll] I-D Action: draft-ietf-roll-admin-local-policy-00.txt
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=089e0115f0a212ea1804f8d6f001
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/KvFpIxgIUiLajDi32-eARfSFvH8
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, roll <roll@ietf.org>, stokcons@xs4all.nl
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:32:27 -0000

--089e0115f0a212ea1804f8d6f001
Content-Type: text/plain; charset=UTF-8

Hello 6man WG,

We would like to have, please, your review of this draft [
https://datatracker.ietf.org/doc/draft-ietf-roll-admin-local-policy/]

Thank you very much in advance,

Michael & Ines.

---------- Forwarded message ----------
From: peter van der Stok <stokcons@xs4all.nl>
Date: 2014-04-09 4:26 GMT-03:00
Subject: Re: [Roll] I-D Action: draft-ietf-roll-admin-local-policy-00.txt
To: roll@ietf.org


In this new draft the following points have been changed:
- terminology and description text have been improved.
- The concept of a MPL4 router is introduced which automatically finds all
interfaces belonging to the zone in which MPL scope 4 messages are
distributed.

Looking forward to your reactions,

Peter


internet-drafts@ietf.org schreef op 2014-04-08 14:02:

 A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Routing Over Low power and Lossy
> networks Working Group of the IETF.
>
>         Title           : MPL forwarder policy for multicast with
> admin-local scope
>         Authors         : Peter van der Stok
>                           Robert Cragie
>         Filename        : draft-ietf-roll-admin-local-policy-00.txt
>         Pages           : 11
>         Date            : 2014-04-08
>
> Abstract:
>    The purpose of this document is to specify an automated policy for
>    the routing of MPL multicast messages with admin-local scope in a
>    border router.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-roll-admin-local-policy/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-roll-admin-local-policy-00
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>

_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll

--089e0115f0a212ea1804f8d6f001
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello 6man WG,<div><br></div><div>We would like to have, p=
lease, your review of this draft [<a href=3D"https://datatracker.ietf.org/d=
oc/draft-ietf-roll-admin-local-policy/" target=3D"_blank">https://datatrack=
er.ietf.org/<u></u>doc/draft-ietf-roll-admin-<u></u>local-policy/</a>]</div=
>
<div><br></div><div>Thank you very much in advance,</div><div><br></div><di=
v>Michael &amp; Ines.<br><br><div class=3D"gmail_quote">---------- Forwarde=
d message ----------<br>From: <b class=3D"gmail_sendername">peter van der S=
tok</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:stokcons@xs4all.nl">stokcon=
s@xs4all.nl</a>&gt;</span><br>
Date: 2014-04-09 4:26 GMT-03:00<br>Subject: Re: [Roll] I-D Action: draft-ie=
tf-roll-admin-local-policy-00.txt<br>To: <a href=3D"mailto:roll@ietf.org">r=
oll@ietf.org</a><br><br><br>In this new draft the following points have bee=
n changed:<br>

- terminology and description text have been improved.<br>
- The concept of a MPL4 router is introduced which automatically finds all =
interfaces belonging to the zone in which MPL scope 4 messages are distribu=
ted.<br>
<br>
Looking forward to your reactions,<br>
<br>
Peter<br>
<br>
<br>
<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-draf=
ts@ietf.org</a> schreef op 2014-04-08 14:02:<div class=3D""><div class=3D"h=
5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=C2=A0This draft is a work item of the Routing Over Low power and Lossy<br>
networks Working Group of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : MPL =
forwarder policy for multicast with<br>
admin-local scope<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Peter van=
 der Stok<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Robert Cragie<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename =C2=A0 =C2=A0 =C2=A0 =C2=A0: draft-iet=
f-roll-admin-local-<u></u>policy-00.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : 11<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 2014-04-08<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The purpose of this document is to specify an automated policy=
 for<br>
=C2=A0 =C2=A0the routing of MPL multicast messages with admin-local scope i=
n a<br>
=C2=A0 =C2=A0border router.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-roll-admin-local-pol=
icy/" target=3D"_blank">https://datatracker.ietf.org/<u></u>doc/draft-ietf-=
roll-admin-<u></u>local-policy/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-roll-admin-local-policy-00=
" target=3D"_blank">http://tools.ietf.org/html/<u></u>draft-ietf-roll-admin=
-local-<u></u>policy-00</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-<u></u>drafts/</a><br>
<br>
______________________________<u></u>_________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org" target=3D"_blank">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/roll</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org" target=3D"_blank">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/roll</a><br>
</div></div></div><br></div></div>

--089e0115f0a212ea1804f8d6f001--


From nobody Wed May  7 15:41:49 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A15C61A03C0; Wed,  7 May 2014 15:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xVA137lse-j; Wed,  7 May 2014 15:41:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CDC81A03F4; Wed,  7 May 2014 15:41:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-why64-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140507224134.16032.94188.idtracker@ietfa.amsl.com>
Date: Wed, 07 May 2014 15:41:34 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/YQpvK9qGKNdq9bs-l6MGCwFV9NQ
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:41:35 -0000

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

        Title           : Analysis of the 64-bit Boundary in IPv6 Addressing
        Authors         : Brian Carpenter
                          Tim Chown
                          Fernando Gont
                          Sheng Jiang
                          Alexandru Petrescu
                          Andrew Yourtchenko
	Filename        : draft-ietf-6man-why64-01.txt
	Pages           : 23
	Date            : 2014-05-07

Abstract:
   The IPv6 unicast addressing format includes a separation between the
   prefix used to route packets to a subnet and the interface identifier
   used to specify a given interface connected to that subnet.
   Currently the interface identifier is defined as 64 bits long for
   almost every case, leaving 64 bits for the subnet prefix.  This
   document describes the advantages of this fixed boundary and analyses
   the issues that would be involved in treating it as a variable
   boundary.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-why64/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-why64-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-why64-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Wed May  7 15:51:40 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 081271A0414 for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 15:51:21 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-L3X_ckggmu for <ipv6@ietfa.amsl.com>; Wed,  7 May 2014 15:51:19 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7235C1A0406 for <ipv6@ietf.org>; Wed,  7 May 2014 15:51:19 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id y10so1624858pdj.18 for <ipv6@ietf.org>; Wed, 07 May 2014 15:51:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=8NC8dg2UrFXpzJsquAGVjQm1pZULN4hvKtPbmqKwD54=; b=qwp7793bfaF6YFLFD7ElDKLc7+I3H5OhyUnVHWIb1VfJmod1HJrWAl9a9hrkHwKNwG 2O2Tc3YIfU5vDfeiBQnjH5+g0XBTyX3Q+VroNrIuMlAH6vP+QczC+QlG38njq1AAIOoO ghiZy5E++vdPwNXvtbYFoKh50A3gJ+xwnI5VdDf32CbsPuluFaXIdqpJuVmbzDjpvT58 WY34VVKkdhKFihDtdMLcFfB7OFCOTd6fNTDUWZY6hwGn88sTJ6NQDV0IY/rt8qmFx4mN N+g/5VaVebU9TdbFaJQ0Vig3OwtfwtVFvbqfimuy7CO1jUZAjQhX96tQTdB1UkPhqK04 tpdg==
X-Received: by 10.66.102.4 with SMTP id fk4mr24351998pab.59.1399503075221; Wed, 07 May 2014 15:51:15 -0700 (PDT)
Received: from [192.168.178.20] (242.193.69.111.dynamic.snap.net.nz. [111.69.193.242]) by mx.google.com with ESMTPSA id io8sm5066975pbc.96.2014.05.07.15.51.13 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 May 2014 15:51:14 -0700 (PDT)
Message-ID: <536AB8E8.6070507@gmail.com>
Date: Thu, 08 May 2014 10:51:20 +1200
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-ietf-6man-why64-01.txt]
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/qVurtUBDZIoa3-g6BJ5sD0cR0bE
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 22:51:21 -0000

Hi all,

Since discussion of this draft has died down, here's an update.

There are a few language improvements, one correction from Tatuya Jinmei,
and an added reference on TCAMs from Ran Atkinson.

Since we won't be meeting in Toronto, can the WG Chairs consider whether
this is ready for WG Last Call?

    Brian

-------- Original Message --------
Subject: I-D Action: draft-ietf-6man-why64-01.txt
Date: Wed, 07 May 2014 15:41:34 -0700
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
CC: ipv6@ietf.org


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

        Title           : Analysis of the 64-bit Boundary in IPv6 Addressing
        Authors         : Brian Carpenter
                          Tim Chown
                          Fernando Gont
                          Sheng Jiang
                          Alexandru Petrescu
                          Andrew Yourtchenko
	Filename        : draft-ietf-6man-why64-01.txt
	Pages           : 23
	Date            : 2014-05-07

Abstract:
   The IPv6 unicast addressing format includes a separation between the
   prefix used to route packets to a subnet and the interface identifier
   used to specify a given interface connected to that subnet.
   Currently the interface identifier is defined as 64 bits long for
   almost every case, leaving 64 bits for the subnet prefix.  This
   document describes the advantages of this fixed boundary and analyses
   the issues that would be involved in treating it as a variable
   boundary.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-why64/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-why64-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-why64-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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

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


From nobody Mon May 12 06:32:23 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A8D61A06FA; Mon, 12 May 2014 06:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMXfIVsocwfk; Mon, 12 May 2014 06:32:17 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 124961A0702; Mon, 12 May 2014 06:32:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11492; q=dns/txt; s=iport; t=1399901531; x=1401111131; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=oBgAYNn+yIQTS9uFn6BoGBG3vTLIzLJvnaJnmiqywW4=; b=UhQQmog10JAI79qD+xxsf9MLGazaJ72jGjGJhP8IRIpk6TLlMW8tlcqG z1O4AkrgXenK08fNfzl2dZvcOCIjaR3bKZjigMVf/yQWKT6jirhIaldV/ SEAeEryuOMfAV5e8rc0sID8KKpqcuo2GV2D3XTu3BcXEKy+xSF8nfQfyx U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnkFACzMcFOtJV2a/2dsb2JhbABZgwZPWIJnqx6QKoZrUQEZfRZ0giUBAQEEAQEBIBEVJQQHDAQCAQgRBAEBAQICBh0DAgICHwYLEwEBCAgCBA4FCIglAxENqwGdSw2GHxeBKosRgS8XAQEBHRYbBwaCbzaBFQSEWgSSeAaDKIlXggyFaIF3gT9tgQk5
X-IronPort-AV: E=Sophos;i="4.97,1035,1389744000"; d="scan'208";a="324208501"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-8.cisco.com with ESMTP; 12 May 2014 13:32:10 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s4CDWAVR021654 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 12 May 2014 13:32:10 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.238]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Mon, 12 May 2014 08:32:10 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
Thread-Topic: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
Thread-Index: AQHPZZhKFb7CAtMGZ0yEI5h3N59w25s8/TpQ
Date: Mon, 12 May 2014 13:32:09 +0000
Deferred-Delivery: Mon, 12 May 2014 13:32:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD84265698A@xmb-rcd-x01.cisco.com>
References: <534D4F7A.3040605@cox.net> <CAH7SZV9WeQmuaHvUZ35_ySL4ak4+SDfbmpMbXgqQL+C833sTGw@mail.gmail.com> <1397607559.92815.YahooMailNeo@web120004.mail.ne1.yahoo.com> <CAP+sJUfx6=-22+A_=M_v3iSf6piGeyHkF2_BPm2ntbWnCEhTSw@mail.gmail.com> <CAMsDxWRgNoWdaRaZz=tOuWQ+ucCfFE7EnHxbbjBvBR64xoF_dQ@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD842605A64@xmb-rcd-x01.cisco.com> <5362DE09.9010405@gmail.com>
In-Reply-To: <5362DE09.9010405@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.52]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/CJnDGT3IFh0xfKvoYihFBjBj5Z0
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, roll <roll@ietf.org>, Pat Kinney <pat.kinney@KINNEYCONSULTINGLLC.COM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 May 2014 13:32:21 -0000

SGkgQnJpYW46DQoNClRoYW5rcyBhIGJ1bmNoIGZvciB5b3VyIHJldmlldyBhbmQgc3VwcG9ydDoN
Cg0KVG8gYWRkcmVzcyB5b3VyIGlzc3Vlcywgd2hhdCB3b3VsZCB5b3UgdGhpbmsgYWJvdXQ6DQoN
CiIgDQoNCjEuMS4gIEFwcGxpY2FiaWxpdHkNCg0KICAgVGhpcyBzcGVjaWZpY2F0aW9uIGFwcGxp
ZXMgdG8gYSBSUEwgW1JGQzYyODJdIGRvbWFpbiB0aGF0IGZvcm1zIGENCiAgIHN0dWIgTExOIGFu
ZCBpcyBjb25uZWN0ZWQgdG8gdGhlIEludGVybmV0IGJ5IGFuZCBvbmx5IGJ5IGl0cyBSUEwNCiAg
IHJvb3QocyksIHdoaWNoIGFjdChzKSBhcyBCb3JkZXIgUm91dGVyKHMpIGZvciB0aGUgTExOLiBX
aXRoIFJQTCwgYQ0KICAgcm9vdCBpcyB0aGUgYm90dGxlbmVjayBmb3IgYWxsIHRoZSB0cmFmZmlj
IGJldHdlZW4gdGhlIEludGVybmV0IGFuZA0KICAgdGhlIERlc3RpbmF0aW9uLU9yaWVudGVkIERp
cmVjdGVkIEFjeWNsaWMgR3JhcGggKERPREFHKSB0aGF0IGl0DQogICBzZXJ2ZXMuDQoNCiAgIElu
IHRoYXQgY29udGV4dCwgdGhlIHNwZWNpZmljYXRpb24gZW50aXRsZXMgYSBSUEwgcm9vdCB0byBy
ZXdyaXRlIHRoZQ0KICAgSVB2NiAgW1JGQzI0NjBdIEZsb3cgTGFiZWwgb2YgYWxsIHBhY2tldHMg
ZW50ZXJpbmcgb3IgbGVhdmluZyB0aGUgUlBMDQogICBkb21haW4gaW4gYm90aCBkaXJlY3Rpb25z
LCBmcm9tIGFuZCB0b3dhcmRzIHRoZSBJbnRlcm5ldCwgcmVnYXJkbGVzcw0KICAgb2YgdGhlIG9y
aWdpbmFsIHNldHRpbmcuICBUaGlzIG1heSBzZWVtIGNvbnRyYWRpY3Rvcnkgd2l0aCB0aGUgSVB2
Ng0KICAgRmxvdyBMYWJlbCBTcGVjaWZpY2F0aW9uICBbUkZDNjQzN10gd2hpY2ggc3RpcHVsYXRl
cyB0aGF0IG9uY2UgaXQgaXMNCiAgIHNldCwgdGhlIEZsb3cgTGFiZWwgaXMgbGVmdCB1bmNoYW5n
ZWQ7IGJ1dCB0aGUgUkZDIGFsc28gaW5kaWNhdGVzIGENCiAgIHZpb2xhdGlvbiB0byB0aGUgcnVs
ZSBjYW4gYmUgYWNjZXB0ZWQgZm9yIGNvbXBlbGxpbmcgcmVhc29ucywgYW5kDQogICB0aGF0IHNl
Y3VyaXR5IGlzIGEgY2FzZSBqdXN0aWZ5aW5nIHN1Y2ggYSB2aW9sYXRpb24uDQoNCiAgIFRoaXMg
c3BlY2lmaWNhdGlvbiBzdWdnZXN0cyB0aGF0IGVuZXJneS1zYXZpbmcsIHdoaWNoIGlzIHRoZSBj
cnV4IG9mDQogICBtb3N0IExMTiBhcHBsaWNhdGlvbnMsIGlzIGFub3RoZXIgY29tcGVsbGluZyBy
ZWFzb24gZm9yIGEgdmlvbGF0aW9uDQogICB0byB0aGUgYWZvcmVtZW50aW9uZWQgcnVsZSwgYW5k
IHRoYXQgdGhlIHZpb2xhdGlvbiBpcyBhY2NlcHRhYmxlIGFzDQogICBsb25nIGFzIDEpIGl0IGlz
IGNvbnRhaW5lZCB3aXRoaW4gdGhlIFJQTCBkb21haW4gYW5kIDIpIHRoZSBJUHY2IEZsb3cNCiAg
IExhYmVsIGlzIHJld3JpdHRlbiBpbiBhIG1hbm5lciB0aGF0IGNvbmZvcm1zIHRoZSBwcmVzY3Jp
cHRpb25zIG9mDQogICBbUkZDNjQzN10uDQoNCiINCg0KSSdtIGFkZGluZyBzb21lIG1vcmUgdGV4
dCB0byBhZGRyZXNzIHlvdXIgcG9pbnRzIDIgYW5kIDMsIGJ1dCBpdCBzZWVtcyB0byBtZSB0aGF0
IHRoZSBhYm92ZSBpcyB3aGF0IGFkZHJlc3NlcyB0aGUgY29yZSBvZiB5b3VyIHN1Z2dlc3Rpb24u
DQpEb2VzIHRoYXQgc2VlbSBPSz8NCg0KQ2hlZXJzLA0KDQpQYXNjYWwNCg0KPiAtLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBCcmlhbiBFIENhcnBlbnRlciBbbWFpbHRvOmJyaWFu
LmUuY2FycGVudGVyQGdtYWlsLmNvbV0NCj4gU2VudDogdmVuZHJlZGkgMiBtYWkgMjAxNCAwMTo1
Mg0KPiBUbzogUGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KQ0KPiBDYzogNm1hbkBpZXRmLm9yZzsg
NnRpc2NoQGlldGYub3JnOyByb2xsOyBYYXZpZXIgVmlsYWpvc2FuYTsgSW5lcyBSb2JsZXMNCj4g
U3ViamVjdDogUmU6IFs2dGlzY2hdIFtSb2xsXSBTdXBwb3J0IG9mIGZsb3cgbGFiZWwgdG8gY2Fy
cnkgdGhlIFJQTCBpbmZvcm1hdGlvbg0KPiBpbiBkYXRhIHBhY2tldHMNCj4gDQo+IE9uIDE4LzA0
LzIwMTQgMDI6MjcsIFBhc2NhbCBUaHViZXJ0IChwdGh1YmVydCkgd3JvdGU6DQo+ID4gRGVhciBh
bGw7DQo+ID4NCj4gPiBDb25zaWRlcmluZyB0aGUgc3VwcG9ydCB3ZSBoYXZlIGF0IDZUaVNDSCBh
bmQgUk9MTCBmb3IgdGhlIHdvcmssIEkNCj4gcHVibGlzaGVkIGRyYWZ0LXRodWJlcnQtNm1hbi1m
bG93LWxhYmVsLWZvci1ycGwtMDAudHh0IHRvIHRoZSA2TUFOIFdHLg0KPiA+IFRoZSBtYWluIGRp
c2N1c3Npb24gaXMgcHJvYmFibHkgdG8gY29uZmlybSB3aGV0aGVyIG91ciBwcm9wb3NlZCB1c2Ug
b2YNCj4gdGhlIGZsb3cgbGFiZWwgaW5zaWRlIHRoZSBSUEwgZG9tYWluIGlzIGNvbXBhdGlibGUg
d2l0aCB0aGUgZ29hbHMgdGhhdCBhcmUNCj4gYWNoaWV2ZWQgYnkgUkZDNjQzNy4gTGV0IHVzIGNv
bnRpbnVlIHRoZSBkaXNjdXNzaW9uIHRoZXJlIGZyb20gbm93IG9uLg0KPiANCj4gVGhlIHByb3Bv
c2FsIHJlYWxseSBkb2VzIHRocmVlIHRoaW5nczoNCj4gDQo+IDEuIEFzc2VydHMgKGltcGxpY2l0
bHkpIHRoYXQgYSBST0xMIGRvbWFpbiBpcyByZWFsbHksIHRydWx5LCBhYnNvbHV0ZWx5IHNlcGFy
YXRlZA0KPiBmcm9tIHRoZSBJbnRlcm5ldCBhdCBsYXllciAzIGV4Y2VwdCBmb3IgdHJhZmZpYyB0
aHJvdWdoIGl0cyByb290IG5vZGUgKGFjdGluZyBhcw0KPiBhIGJvcmRlciByb3V0ZXIpLg0KPiAN
Cj4gSSB0aGluayB0aGF0IG5lZWRzIHRvIGJlIHN0YXRlZCB2ZXJ5IGV4cGxpY2l0bHkgYXMgYSBm
dW5kYW1lbnRhbCByZXF1aXJlbWVudA0KPiBmb3IgdGhpcyBzcGVjIHRvIGJlIGFjY2VwdGFibGUu
DQo+IA0KPiAyLiBJdCByZWNvbW1lbmRzIHRoYXQgdGhlIHJvb3QgcmV3cml0ZXMgdGhlIGZsb3cg
bGFiZWwgb24gb3V0Ym91bmQgcGFja2V0cw0KPiBhY2NvcmRpbmcgdG8gdGhlIHByb3Zpc2lvbnMg
aW4gUkZDIDY0MzcuDQo+IFRoZSBzbGlnaHQgZGV2aWF0aW9uIGZyb20gUkZDIDY0MzcgcHVyaXNt
IHRoZXJlIGlzIHRoYXQgaXQgdHJlYXRzIHRoZSBleGlzdGluZw0KPiBmbG93IGxhYmVsIG9uIHRo
ZSBwYWNrZXRzIGFzIGlmIGl0IHdhcyB6ZXJvLg0KPiANCj4gMy4gSXQgcmVxdWlyZXMgdGhhdCB0
aGUgcm9vdCByZXdyaXRlcyB0aGUgZmxvdyBsYWJlbCBvbiBpbmJvdW5kIHBhY2tldHMgZXZlbiBp
Zg0KPiB0aGV5IGFyZSBhbHJlYWR5IHNldCB0byBub24temVyby4NCj4gVGhhdCBpcyBpbmRlZWQg
YSB2aW9sYXRpb24gb2YgUkZDIDY0MzcuIEJ1dCBpdCBpcyBhIHZpb2xhdGlvbiB3ZSBoYXZlIGFs
cmVhZHkNCj4gYWNjZXB0ZWQgaW4gYW5vdGhlciBjYXNlOiAiZm9yIGNvbXBlbGxpbmcgb3BlcmF0
aW9uYWwgc2VjdXJpdHkgcmVhc29ucyIuDQo+IFdoYXQncyBsb3N0PyBUaGUgYWJpbGl0eSBmb3Ig
bm9kZXMgaW5zaWRlIHRoZSBST0xMIGRvbWFpbiB0byBwZXJmb3JtIGZsb3ctDQo+IGxhYmVsIGJh
c2VkIGxvYWQgYmFsYW5jaW5nIGZvciBzdWNoIGluYm91bmQgcGFja2V0cy4gSSB0aGluayBpdCdz
IGZvciBST0xMIGFuZA0KPiA2VElTQ0ggdG8gc2F5IHdoZXRoZXIgdGhhdCBsb3NzIG1hdHRlcnMu
DQo+IA0KPiBJbiBteSBvcGluaW9uLCB3ZSBzaG91bGRuJ3QgYmUgcmVsaWdpb3VzIGFib3V0IHRo
aXMgYXMgbG9uZyBhcyBwb2ludCAxIGlzDQo+IGd1YXJhbnRlZWQuIEkgZG9uJ3Qgc2VlIGFueSBy
aXNrcyB0byB0aGUgZ2VuZXJpYyB1c2Ugb2YgdGhlIGZsb3cgbGFiZWwuDQo+IA0KPiBJIHRoaW5r
IHRoZSBsYW5ndWFnZSBhcm91bmQgdGhlIHJlbGF0aW9uc2hpcCB3aXRoIFJGQyA2NDM3IGlzIGEg
Yml0IGRlZmVuc2l2ZQ0KPiBhdCB0aGUgbW9tZW50IGFuZCBjb3VsZCBwcm9iYWJseSBiZSBhIGJp
dCBzaW1wbGVyIGFuZCBjbGVhcmVyLiAoIlRoZQ0KPiBmb2xsb3dpbmcgZXhjZXB0aW9ucyB0byB0
aGUgcnVsZXMgaW4gW1JGQzY0MzddIGFyZSBtYWRlOi4uLiIpLiBJJ2QgaGF2ZSBhDQo+IHByZWZl
cmVuY2UgZm9yIGRvaW5nIHRoYXQgd2l0aG91dCBhIGZvcm1hbCB1cGRhdGUgdG8gNjQzNywgYmVj
YXVzZSBpdCdzIG9ubHkNCj4gUlBMIGltcGxlbWVudG9ycyB3aG8gbmVlZCB0byBjaGFuZ2UgYW55
dGhpbmcuDQo+IA0KPiAgICAgQnJpYW4NCj4gDQo+ID4gQ2hlZXJzLA0KPiA+DQo+ID4gUGFzY2Fs
DQo+ID4NCj4gPiBGcm9tOiB4dmlsYWpvc2FuYUBnbWFpbC5jb20gW21haWx0bzp4dmlsYWpvc2Fu
YUBnbWFpbC5jb21dIE9uIEJlaGFsZg0KPiA+IE9mIFhhdmllciBWaWxham9zYW5hDQo+ID4gU2Vu
dDogamV1ZGkgMTcgYXZyaWwgMjAxNCAxMDowMA0KPiA+IFRvOiBJbmVzIFJvYmxlcw0KPiA+IENj
OiBQYXNjYWwgVGh1YmVydCAocHRodWJlcnQpOyA2dGlzY2hAaWV0Zi5vcmc7IHJvbGwNCj4gPiBT
dWJqZWN0OiBSZTogWzZ0aXNjaF0gW1JvbGxdIFN1cHBvcnQgb2YgZmxvdyBsYWJlbCB0byBjYXJy
eSB0aGUgUlBMDQo+ID4gaW5mb3JtYXRpb24gaW4gZGF0YSBwYWNrZXRzDQo+ID4NCj4gPiArMSBJ
IHRoaW5rIHRoaXMgaXMgbW9yZSB0aGFuIG5lZWRlZC4gSW4gYWRkaXRpb24gUkZDIDYyODIgZGVm
aW5lcyBob3cNCj4gaGVhZGVyIGNvbXByZXNzaW9uIG5lZWRzIHRvIGJlIGhhbmRsZWQgdG9nZXRo
ZXIgd2l0aCBleHRlbnNpb24gaGVhZGVycy4gSQ0KPiB0aGluayB0aGlzIGlzIG5vdCBjbGVhciBh
bmQgbGVhZHMgdG8gY29uZnVzaW9ucyAoYWZlY3RpbmcgYWxyZWFkeSBzb21lDQo+IHdpcmVzaGFy
ayBkaXNzZWN0b3JzKS4gVGhlIHVzZSBvZiBmbG93IGxhYmVsIHdpbGwgc29sdmUgc2V2ZXJhbCBw
cm9ibGVtcyBhdA0KPiBvbmNlLg0KPiA+DQo+ID4gWC4NCj4gPg0KPiA+DQo+ID4NCj4gPiAyMDE0
LTA0LTE2IDIyOjQ0IEdNVCswMjowMCBJbmVzIFJvYmxlcw0KPiA8bWFyaWFpbmVzcm9ibGVzQGdv
b2dsZW1haWwuY29tPG1haWx0bzptYXJpYWluZXNyb2JsZXNAZ29vZ2xlbWFpbC5jb20NCj4gPj46
DQo+ID4gKzENCj4gPg0KPiA+IEluZXMNCj4gPg0KPiA+IDIwMTQtMDQtMTUgMjE6MTkgR01ULTAz
OjAwIFFpbiBXYW5nDQo+IDxxaW53YW5nNnRvcEB5YWhvby5jb208bWFpbHRvOnFpbndhbmc2dG9w
QHlhaG9vLmNvbT4+Og0KPiA+ICsxDQo+ID4NCj4gPiBRaW4NCj4gPiBPbiBXZWRuZXNkYXksIEFw
cmlsIDE2LCAyMDE0IDE6NDcgQU0sIFByb2YuIERpZWdvIER1am92bmUNCj4gPGRpZWdvLmR1am92
bmVAbWFpbC51ZHAuY2w8bWFpbHRvOmRpZWdvLmR1am92bmVAbWFpbC51ZHAuY2w+PiB3cm90ZToN
Cj4gPiArMSAhDQo+ID4NCj4gPiAyMDE0LTA0LTE1IDEyOjI1IEdNVC0wMzowMCBUb20gUGhpbm5l
eQ0KPiA8dG9tLnBoaW5uZXlAY294Lm5ldDxtYWlsdG86dG9tLnBoaW5uZXlAY294Lm5ldD4+Og0K
PiA+ICsxIGZvciBzdXJlLiBUaGUgZmxvdyBsYWJlbCBoYXMgYWx3YXlzIGJlZW4gdGhlIHByZWZl
cmFibGUgbWV0aG9kIGZvciBtZSwNCj4gYW5kIEkgc3VzcGVjdCBmb3Igb3RoZXJzIHdpdGgga25v
d2xlZGdlIG9mIGhvdyBpdCBpcyB1c2VkIGluIElTQTEwMC4xMWEuDQo+ID4gPT09DQo+ID4NCj4g
PiBPbiAyMDE0LjA0LjE1IDA3PHRlbDoyMDE0LjA0LjE1JTIwMDc+OjI1LCBQYXNjYWwgVGh1YmVy
dCAocHRodWJlcnQpDQo+IHdyb3RlOg0KPiA+IERlYXIgYWxsOg0KPiA+DQo+ID4gQXMgc29tZSBv
ZiB5b3UgcmVtZW1iZXIsIHRoZSBSUEwgc3BlY2lmaWNhdGlvbiBoYXMgY2hhbmdlZCBvdmVyIHRp
bWUNCj4gV1JUIHRvIHRoZSBsb2NhdGlvbiBvZiB0aGUgaW5mb3JtYXRpb24gdGhhdCBSUEwgcGxh
Y2VzIGluIHRoZSBkYXRhIHBhY2tldHMuDQo+IFdlIHN0YXJ0ZWQgd2l0aCB0aGUgZmxvdyBsYWJl
bCBidXQgdGhlc2Ugd2VyZSB0aGUgZGF5cyB3aGVuIHdoYXQgYmVjYW1lDQo+IFJGQyA2NDM3IHdh
cyBiZWluZyBkZWZpbmVkIGF0IDZNQU4sIHNvIHdlIHNoaWVkIGF3YXkgYW5kIGRlZmluZWQgdGhl
DQo+IEhiSCB0ZWNobmlxdWUgdGhhdCBpcyBub3cgc3BlY2lmaWVkIGFzIFJGQyA2NTUzLg0KPiA+
DQo+ID4gV2XigJlsbCBub3RlIHRoYXQgdGhlIFJQTCBvcHRpb24gZGVmaW5lZCBpbiBSRkMgNjU1
MyB0YWtlcyA2IG9jdGV0cywgYW5kIHdpdGgNCj4gdGhlIEhiSCBoZHIgd2UgZW5kIHVwIHdpdGgg
OCBleHRyYSBvY3RldHMuIEFuIGV4dHJhIElQLWluLUlQIGVuY2Fwc3VsYXRpb24gaXMNCj4gcmVx
dWlyZWQgb24gdG9wIG9mIHRoYXQgdW5sZXNzIGJvdGggZW5kcG9pbnRzIGFyZSBpbiB0aGUgc2Ft
ZSBSUEwgZG9tYWluLg0KPiBBbGwgdGhpcyBvdmVyaGVhZCBtYXkgYmUgYWNjZXB0YWJsZSB3aGVu
IHBvd2VyIGlzIGF2YWlsYWJsZSBhbmQgdGhlIFBIWQ0KPiBhbGxvd3MgZm9yIGxhcmdlciBmcmFt
ZXMsIGJ1dCBpbiB0cmFkaXRpb25hbCBiYXR0ZXJ5LW9wZXJhdGVkIDE1LjQgd2l0aCB+IDgwDQo+
IGJ5dGVzIHVzYWJsZSBwZXIgZnJhbWUsIG15IGV4cGVyaWVuY2UgZnJvbSBpbnRlZ3JhdGluZyA2
TG9XUEFOIEhDIHdpdGgNCj4gSVNBMTAwLjExYSBzYXlzIHRoYXQgYWxsIHRoZXNlIGV4dHJhIGJ5
dGVzIHdpbGwgYmUgb24gdGhlIHdheSBvZiB0aGUgNlRpU0NIDQo+IGFkb3B0aW9uLg0KPiA+DQo+
ID4gU3RpbGwsIGJvdGggUkZDIDY1NTAgYW5kIFJGQyA2NTUyIGFyZSBkZXNpZ25lZCB0byBhbGxv
dyBmb3IgYW4gYWx0ZXJuYXRlDQo+IHRlY2huaXF1ZSBhbmQgaW4gcGFydGljdWxhciBmb3IgdGhl
IHVzZSBvZiB0aGUgZmxvdyBsYWJlbCwgYXMgaXMgZWxhYm9yYXRlZCBpbg0KPiBodHRwOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC10aHViZXJ0LXJvbGwtZmxvdy1sYWJlbC0wMiAuIFVzaW5n
IHRoZSBmbG93DQo+IGxhYmVsIHJlZHVjZXMgdGhlIGNvc3Qgb2YgdGhlIFJQTCBpbmZvcm1hdGlv
biBkcmFtYXRpY2FsbHksIGRvd24gdG8gYSBsZXZlbA0KPiB0aGF0IGlzIHByb2JhYmx5IGFjY2Vw
dGFibGUgZm9yIHRoZSB0YXJnZXQgU0RPcy4NCj4gPg0KPiA+IFNvIG15IHBsYW4gZm9yIG5vdyBp
cyB0byBtb3ZlIHRoZSBmbG93IGxhYmVsIGRyYWZ0IHRvIDZNQU4gYW5kIHByZXBhcmUNCj4gZm9y
IGEgaG90IHNlYXNvbiwgYW5kIEnigJltIGxvb2tpbmcgZm9yIHN1cHBvcnQgZnJvbSBib3RoIDZU
aVNDSCBhbmQgUk9MTCB0bw0KPiBiYWNrIG1lIHVwIGZyb20gdGhlIHN0YXJ0LiAgWWVzLCB5b3Ug
Y2FuIGhlbHAhDQo+ID4NCj4gPiBQbGVhc2UgKzEgaWYgeW91IGFncmVlIHdlIG5lZWQgdGhpcyB3
b3JrIHRvIGhhcHBlbiwgYW5kL29yIHByb3ZpZGUgYW55DQo+IHN1Z2dlc3Rpb24uDQo+ID4NCj4g
PiBDaGVlcnMsDQo+ID4NCj4gPiBQYXNjYWwNCj4gPg0KPiA+DQo+ID4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPg0KPiA+IDZ0aXNjaCBtYWlsaW5n
IGxpc3QNCj4gPg0KPiA+IDZ0aXNjaEBpZXRmLm9yZzxtYWlsdG86NnRpc2NoQGlldGYub3JnPg0K
PiA+DQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby82dGlzY2gNCj4g
Pg0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gPiA2dGlzY2ggbWFpbGluZyBsaXN0DQo+ID4gNnRpc2NoQGlldGYub3JnPG1haWx0bzo2
dGlzY2hAaWV0Zi5vcmc+DQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by82dGlzY2gNCj4gPg0KPiA+DQo+ID4NCj4gPiAtLQ0KPiA+IERJRUdPIERVSk9WTkUNCj4gPiBB
Y2Fkw6ltaWNvIEVzY3VlbGEgZGUgSW5nZW5pZXLDrWEgZW4gSW5mb3Jtw6F0aWNhIHkgVGVsZWNv
bXVuaWNhY2lvbmVzDQo+ID4gRmFjdWx0YWQgZGUgSW5nZW5pZXLDrWEgVURQDQo+ID4gd3d3Lmlu
Z2VuaWVyaWEudWRwLmNsPGh0dHA6Ly93d3cuaW5nZW5pZXJpYS51ZHAuY2wvPg0KPiA+ICg1NiAy
KSA2NzYgODEyNTx0ZWw6JTI4NTYlMjAyJTI5JTIwNjc2JTIwODEyNT4NCj4gPg0KPiA+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gNnRpc2NoIG1h
aWxpbmcgbGlzdA0KPiA+IDZ0aXNjaEBpZXRmLm9yZzxtYWlsdG86NnRpc2NoQGlldGYub3JnPg0K
PiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vNnRpc2NoDQo+ID4NCj4g
Pg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
ID4gUm9sbCBtYWlsaW5nIGxpc3QNCj4gPiBSb2xsQGlldGYub3JnPG1haWx0bzpSb2xsQGlldGYu
b3JnPg0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcm9sbA0KPiA+
DQo+ID4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiA+IDZ0aXNjaCBtYWlsaW5nIGxpc3QNCj4gPiA2dGlzY2hAaWV0Zi5vcmc8bWFpbHRvOjZ0
aXNjaEBpZXRmLm9yZz4NCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
LzZ0aXNjaA0KPiA+DQoNCg==


From nobody Mon May 12 18:07:13 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ECEB1A07DD; Mon, 12 May 2014 18:07:09 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bhONV4s9iuz1; Mon, 12 May 2014 18:07:06 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 61D9C1A07DC; Mon, 12 May 2014 18:07:06 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id bj1so8194212pad.41 for <multiple recipients>; Mon, 12 May 2014 18:07:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lm6v0JVrboZEEq3ZrENlkaUMbOxng3Cd8e9YYYFrzJM=; b=mG2ed2t8t31e7YkPSnHFDmNC9v9yqxZsF0xhZ6kdUgnFpWk/W5ZD0eG0qB6SJtYPqY piAJDTrwMTgk3wRvicbz6CSBOR7StL79GNaNYscTkjS0R7aQjDQvf4u6sjs5HN0x9R/P t2TsRrqxu40bOi6UImtkgLmPqkqZt3uUqlEEMXrmUKDHodalPk0p+SIZYolj/UuVsgHQ ne6WIz2Yry5DONTtMR0sqkFCkt4ui6Tm78Lknbjy1JW5ODbL6HMdWg9ofig63uCb6Hwl cds1bdXlAOxBukS/d1mPw4oaWbrDa4CBcfsd9Oz0mTBoB7BsLQNcK3PYdm6AbaBw0ka5 QxiA==
X-Received: by 10.66.140.6 with SMTP id rc6mr59951845pab.87.1399943220292; Mon, 12 May 2014 18:07:00 -0700 (PDT)
Received: from [130.216.38.108] (sc-cs-567-laptop.cs.auckland.ac.nz. [130.216.38.108]) by mx.google.com with ESMTPSA id gz11sm25094941pbd.1.2014.05.12.18.06.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 12 May 2014 18:06:59 -0700 (PDT)
Message-ID: <53717031.1010800@gmail.com>
Date: Tue, 13 May 2014 13:06:57 +1200
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: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL information in data packets
References: <534D4F7A.3040605@cox.net>	<CAH7SZV9WeQmuaHvUZ35_ySL4ak4+SDfbmpMbXgqQL+C833sTGw@mail.gmail.com>	<1397607559.92815.YahooMailNeo@web120004.mail.ne1.yahoo.com>	<CAP+sJUfx6=-22+A_=M_v3iSf6piGeyHkF2_BPm2ntbWnCEhTSw@mail.gmail.com> <CAMsDxWRgNoWdaRaZz=tOuWQ+ucCfFE7EnHxbbjBvBR64xoF_dQ@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD842605A64@xmb-rcd-x01.cisco.com> <5362DE09.9010405@gmail.com> <E045AECD98228444A58C61C200AE1BD84265698A@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD84265698A@xmb-rcd-x01.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/jyuBiaoiGls5ddwSGaLiQboJ7wg
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, roll <roll@ietf.org>, Pat Kinney <pat.kinney@KINNEYCONSULTINGLLC.COM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 01:07:09 -0000

On 13/05/2014 01:32, Pascal Thubert (pthubert) wrote:
> Hi Brian:
>=20
> Thanks a bunch for your review and support:
>=20
> To address your issues, what would you think about:

Yes, IMHO it's clear and allows for a clear decision.

Thanks
    Brian

>=20
> "=20
>=20
> 1.1.  Applicability
>=20
>    This specification applies to a RPL [RFC6282] domain that forms a
>    stub LLN and is connected to the Internet by and only by its RPL
>    root(s), which act(s) as Border Router(s) for the LLN. With RPL, a
>    root is the bottleneck for all the traffic between the Internet and
>    the Destination-Oriented Directed Acyclic Graph (DODAG) that it
>    serves.
>=20
>    In that context, the specification entitles a RPL root to rewrite th=
e
>    IPv6  [RFC2460] Flow Label of all packets entering or leaving the RP=
L
>    domain in both directions, from and towards the Internet, regardless=

>    of the original setting.  This may seem contradictory with the IPv6
>    Flow Label Specification  [RFC6437] which stipulates that once it is=

>    set, the Flow Label is left unchanged; but the RFC also indicates a
>    violation to the rule can be accepted for compelling reasons, and
>    that security is a case justifying such a violation.
>=20
>    This specification suggests that energy-saving, which is the crux of=

>    most LLN applications, is another compelling reason for a violation
>    to the aforementioned rule, and that the violation is acceptable as
>    long as 1) it is contained within the RPL domain and 2) the IPv6 Flo=
w
>    Label is rewritten in a manner that conforms the prescriptions of
>    [RFC6437].
>=20
> "
>=20
> I'm adding some more text to address your points 2 and 3, but it seems =
to me that the above is what addresses the core of your suggestion.
> Does that seem OK?
>=20
> Cheers,
>=20
> Pascal
>=20
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: vendredi 2 mai 2014 01:52
>> To: Pascal Thubert (pthubert)
>> Cc: 6man@ietf.org; 6tisch@ietf.org; roll; Xavier Vilajosana; Ines Robl=
es
>> Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL in=
formation
>> in data packets
>>
>> On 18/04/2014 02:27, Pascal Thubert (pthubert) wrote:
>>> Dear all;
>>>
>>> Considering the support we have at 6TiSCH and ROLL for the work, I
>> published draft-thubert-6man-flow-label-for-rpl-00.txt to the 6MAN WG.=

>>> The main discussion is probably to confirm whether our proposed use o=
f
>> the flow label inside the RPL domain is compatible with the goals that=
 are
>> achieved by RFC6437. Let us continue the discussion there from now on.=

>>
>> The proposal really does three things:
>>
>> 1. Asserts (implicitly) that a ROLL domain is really, truly, absolutel=
y separated
>> from the Internet at layer 3 except for traffic through its root node =
(acting as
>> a border router).
>>
>> I think that needs to be stated very explicitly as a fundamental requi=
rement
>> for this spec to be acceptable.
>>
>> 2. It recommends that the root rewrites the flow label on outbound pac=
kets
>> according to the provisions in RFC 6437.
>> The slight deviation from RFC 6437 purism there is that it treats the =
existing
>> flow label on the packets as if it was zero.
>>
>> 3. It requires that the root rewrites the flow label on inbound packet=
s even if
>> they are already set to non-zero.
>> That is indeed a violation of RFC 6437. But it is a violation we have =
already
>> accepted in another case: "for compelling operational security reasons=
".
>> What's lost? The ability for nodes inside the ROLL domain to perform f=
low-
>> label based load balancing for such inbound packets. I think it's for =
ROLL and
>> 6TISCH to say whether that loss matters.
>>
>> In my opinion, we shouldn't be religious about this as long as point 1=
 is
>> guaranteed. I don't see any risks to the generic use of the flow label=
=2E
>>
>> I think the language around the relationship with RFC 6437 is a bit de=
fensive
>> at the moment and could probably be a bit simpler and clearer. ("The
>> following exceptions to the rules in [RFC6437] are made:..."). I'd hav=
e a
>> preference for doing that without a formal update to 6437, because it'=
s only
>> RPL implementors who need to change anything.
>>
>>     Brian
>>
>>> Cheers,
>>>
>>> Pascal
>>>
>>> From: xvilajosana@gmail.com [mailto:xvilajosana@gmail.com] On Behalf
>>> Of Xavier Vilajosana
>>> Sent: jeudi 17 avril 2014 10:00
>>> To: Ines Robles
>>> Cc: Pascal Thubert (pthubert); 6tisch@ietf.org; roll
>>> Subject: Re: [6tisch] [Roll] Support of flow label to carry the RPL
>>> information in data packets
>>>
>>> +1 I think this is more than needed. In addition RFC 6282 defines how=

>> header compression needs to be handled together with extension headers=
=2E I
>> think this is not clear and leads to confusions (afecting already some=

>> wireshark dissectors). The use of flow label will solve several proble=
ms at
>> once.
>>> X.
>>>
>>>
>>>
>>> 2014-04-16 22:44 GMT+02:00 Ines Robles
>> <mariainesrobles@googlemail.com<mailto:mariainesrobles@googlemail.com
>>>> :
>>> +1
>>>
>>> Ines
>>>
>>> 2014-04-15 21:19 GMT-03:00 Qin Wang
>> <qinwang6top@yahoo.com<mailto:qinwang6top@yahoo.com>>:
>>> +1
>>>
>>> Qin
>>> On Wednesday, April 16, 2014 1:47 AM, Prof. Diego Dujovne
>> <diego.dujovne@mail.udp.cl<mailto:diego.dujovne@mail.udp.cl>> wrote:
>>> +1 !
>>>
>>> 2014-04-15 12:25 GMT-03:00 Tom Phinney
>> <tom.phinney@cox.net<mailto:tom.phinney@cox.net>>:
>>> +1 for sure. The flow label has always been the preferable method for=
 me,
>> and I suspect for others with knowledge of how it is used in ISA100.11=
a.
>>> =3D=3D=3D
>>>
>>> On 2014.04.15 07<tel:2014.04.15%2007>:25, Pascal Thubert (pthubert)
>> wrote:
>>> Dear all:
>>>
>>> As some of you remember, the RPL specification has changed over time
>> WRT to the location of the information that RPL places in the data pac=
kets.
>> We started with the flow label but these were the days when what becam=
e
>> RFC 6437 was being defined at 6MAN, so we shied away and defined the
>> HbH technique that is now specified as RFC 6553.
>>> We=E2=80=99ll note that the RPL option defined in RFC 6553 takes 6 oc=
tets, and with
>> the HbH hdr we end up with 8 extra octets. An extra IP-in-IP encapsula=
tion is
>> required on top of that unless both endpoints are in the same RPL doma=
in.
>> All this overhead may be acceptable when power is available and the PH=
Y
>> allows for larger frames, but in traditional battery-operated 15.4 wit=
h ~ 80
>> bytes usable per frame, my experience from integrating 6LoWPAN HC with=

>> ISA100.11a says that all these extra bytes will be on the way of the 6=
TiSCH
>> adoption.
>>> Still, both RFC 6550 and RFC 6552 are designed to allow for an altern=
ate
>> technique and in particular for the use of the flow label, as is elabo=
rated in
>> http://tools.ietf.org/html/draft-thubert-roll-flow-label-02 . Using th=
e flow
>> label reduces the cost of the RPL information dramatically, down to a =
level
>> that is probably acceptable for the target SDOs.
>>> So my plan for now is to move the flow label draft to 6MAN and prepar=
e
>> for a hot season, and I=E2=80=99m looking for support from both 6TiSCH=
 and ROLL to
>> back me up from the start.  Yes, you can help!
>>> Please +1 if you agree we need this work to happen, and/or provide an=
y
>> suggestion.
>>> Cheers,
>>>
>>> Pascal
>>>
>>>
>>> _______________________________________________
>>>
>>> 6tisch mailing list
>>>
>>> 6tisch@ietf.org<mailto:6tisch@ietf.org>
>>>
>>> https://www.ietf.org/mailman/listinfo/6tisch
>>>
>>>
>>> _______________________________________________
>>> 6tisch mailing list
>>> 6tisch@ietf.org<mailto:6tisch@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/6tisch
>>>
>>>
>>>
>>> --
>>> DIEGO DUJOVNE
>>> Acad=C3=A9mico Escuela de Ingenier=C3=ADa en Inform=C3=A1tica y Telec=
omunicaciones
>>> Facultad de Ingenier=C3=ADa UDP
>>> www.ingenieria.udp.cl<http://www.ingenieria.udp.cl/>
>>> (56 2) 676 8125<tel:%2856%202%29%20676%208125>
>>>
>>> _______________________________________________
>>> 6tisch mailing list
>>> 6tisch@ietf.org<mailto:6tisch@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/6tisch
>>>
>>>
>>> _______________________________________________
>>> Roll mailing list
>>> Roll@ietf.org<mailto:Roll@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/roll
>>>
>>>
>>> _______________________________________________
>>> 6tisch mailing list
>>> 6tisch@ietf.org<mailto:6tisch@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/6tisch
>>>
>=20


From nobody Tue May 13 02:26:26 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 342B11A0010; Tue, 13 May 2014 02:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PJJDcxwc2e4; Tue, 13 May 2014 02:26:23 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0B91A0012; Tue, 13 May 2014 02:26:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3330; q=dns/txt; s=iport; t=1399973177; x=1401182777; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=evDKEIQMSSlWLKau+u4ln7pzcmXnzW7b6GNykuYj5tY=; b=LOb2tS+ZnurxQ7Co+aMcxkfHZCjcH8mqP+fqn2ECqKxFwvZFMtOBfxCk OgUdIsdCMWf/RN1lrTG06XZV4w6eFIfA6bRHhOQ3m/HCjRvqggni8Siix OuWAc0akw/p/8Vk++XEYxLI1SThZCs21UybSxezlx54DY8yl9D3wk6sFv Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar0GAIDkcVOtJV2U/2dsb2JhbABZgwZPUQeCZ8MLARmBBBZ0giUBAQEEIxFDAgwEAgEIEQQBAQMCBh0DAgICMBQBBgEBBQMCBA4FCAGIOAgFrCKkVheBKox3MQcGgm82gRUEmwSRS4M2bYFC
X-IronPort-AV: E=Sophos;i="4.97,1042,1389744000"; d="scan'208";a="43347976"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-8.cisco.com with ESMTP; 13 May 2014 09:26:17 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s4D9QHL4000665 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 13 May 2014 09:26:17 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.238]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0123.003; Tue, 13 May 2014 04:26:16 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: FW: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt
Thread-Topic: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt
Thread-Index: AQHPboxRAM7nFZ++3UC8TcXZbob1AZs+O9Fg
Date: Tue, 13 May 2014 09:26:16 +0000
Deferred-Delivery: Tue, 13 May 2014 09:26:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD842658563@xmb-rcd-x01.cisco.com>
References: <20140513091837.28963.29591.idtracker@ietfa.amsl.com>
In-Reply-To: <20140513091837.28963.29591.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.52]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/VZRJsEseyB14lQT153jD3ya11nM
Cc: roll <roll@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>, Pat Kinney <pat.kinney@KINNEYCONSULTINGLLC.COM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 09:26:25 -0000

RGVhciBhbGw6DQoNClRoaXMgbmV3IHZlcnNpb24gYWRkcmVzc2VzIEJyaWFuJ3MgY29uY2VybnMs
IGluIHBhcnRpY3VsYXIgdGhlIGxhbmd1YWdlIHRoYXQgcmVsYXRlcyB0aGlzIHByb3Bvc2FsIHdp
dGggdGhlIEZsb3cgTGFiZWwgU3BlY2lmaWNhdGlvbiAoUkZDIDY0MzcpLg0KSXQgaXMgbWFkZSBj
bGVhcmVyIHRoYXQgdGhpcyBpcyBhIGRldmlhdGlvbiBzdWNoIGFzIGFscmVhZHkgdG9sZXJhdGVk
IGZvciBzZWN1cml0eSByZWFzb25zLCBhbmQgdGhhdCB0aGUgY29tcGVsbGluZyByZWFzb24gaXMg
ZW5lcmd5IHNhdmluZy4NClRoZSBwcm9wb3NhbCBvbmx5IGltcGFjdHMgdGhlIHVzZSBvZiB0aGUg
ZmxvdyBsYWJlbCBpbnNpZGUgdGhlIExMTiBhbmQgZG9lcyBub3QgcmVzdWx0IGluIGEgZGV0ZXJp
b3JhdGlvbiBvZiB0aGUgYXBwbGljYXRpb24gb2YgUkZDIDY0MzcgaW5zaWRlIHRoZSBJbnRlcm5l
dC4gDQpUaGUgcHJvcG9zYWwgaXMgc3VwcG9ydGVkIGJ5IGluZGl2aWR1YWxzIHBhcnRpY2lwYXRp
bmcgdG8gTExOIHJlbGF0ZWQgZ3JvdXBzIGF0IHRoZSBJRVRGIChjYydlZCkgYW5kIGV4dGVybmFs
IFNET3MgKElTQTEwMCkuDQoNClRoZSBxdWVzdGlvbiBpcyBub3cgd2hldGhlciB3ZSBzaG91bGQg
Y29tcGxldGUgdGhlIHdvcmsgYXQgNk1BTiBvciBtb3ZlIGJhY2sgdG8gUk9MTC4NCg0KV2hhdCBk
byB5b3UgdGhpbms/DQoNClBhc2NhbA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpG
cm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0
Zi5vcmddIA0KU2VudDogbWFyZGkgMTMgbWFpIDIwMTQgMTE6MTkNClRvOiBQYXNjYWwgVGh1YmVy
dCAocHRodWJlcnQpOyBQYXNjYWwgVGh1YmVydCAocHRodWJlcnQpDQpTdWJqZWN0OiBOZXcgVmVy
c2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXRodWJlcnQtNm1hbi1mbG93LWxhYmVsLWZvci1y
cGwtMDIudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXRodWJlcnQtNm1hbi1m
bG93LWxhYmVsLWZvci1ycGwtMDIudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVk
IGJ5IFBhc2NhbCBUaHViZXJ0IGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0K
TmFtZToJCWRyYWZ0LXRodWJlcnQtNm1hbi1mbG93LWxhYmVsLWZvci1ycGwNClJldmlzaW9uOgkw
Mg0KVGl0bGU6CQlUaGUgSVB2NiBGbG93IExhYmVsIHdpdGhpbiBhIFJQTCBkb21haW4NCkRvY3Vt
ZW50IGRhdGU6CTIwMTQtMDUtMTMNCkdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpQYWdl
czoJCTExDQpVUkw6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtdGh1YmVydC02bWFuLWZsb3ctbGFiZWwtZm9yLXJwbC0wMi50eHQNClN0YXR1czog
ICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC10aHViZXJ0LTZt
YW4tZmxvdy1sYWJlbC1mb3ItcnBsLw0KSHRtbGl6ZWQ6ICAgICAgIGh0dHA6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LXRodWJlcnQtNm1hbi1mbG93LWxhYmVsLWZvci1ycGwtMDINCkRpZmY6
ICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC10aHViZXJ0
LTZtYW4tZmxvdy1sYWJlbC1mb3ItcnBsLTAyDQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1bWVu
dCBwcmVzZW50IGhvdyB0aGUgRmxvdyBMYWJlbCBjYW4gYmUgdXNlZCBpbnNpZGUgYSBSUEwNCiAg
IGRvbWFpbiBhcyBhIHJlcGxhY2VtZW50IHRvIHRoZSBSUEwgb3B0aW9uIGFuZCBwcm92aWRlcyBy
dWxlcyBmb3IgdGhlDQogICByb290IHRvIHNldCBhbmQgcmVzZXQgdGhlIEZsb3cgTGFiZWwgd2hl
biBmb3J3YXJkaW5nIGJldHdlZW4gdGhlDQogICBpbnNpZGUgb2YgUlBMIGRvbWFpbiBhbmQgdGhl
IGxhcmdlciBJbnRlcm5ldCwgaW4gYm90aCBkaXJlY3Rpb24uDQogICBUaGlzIG5ldyBvcGVyYXRp
b24gc2F2ZXMgNDQgYml0cyBpbiBlYWNoIGZyYW1lLCBhbmQgYW4gZXZlbnR1YWwgSVAtDQogICBp
bi1JUCBlbmNhcHN1bGF0aW9uIHdpdGhpbiB0aGUgUlBMIGRvbWFpbiB0aGF0IGlzIHJlcXVpcmVk
IGZvciBhbGwNCiAgIHBhY2tldHMgdGhhdCByZWFjaCBvdXRzaWRlIG9mIHRoZSBSUEwgZG9tYWlu
Lg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBt
YXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1
bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xz
LmlldGYub3JnLg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=


From iyadalmasry@gmail.com  Tue May 13 21:44:16 2014
Return-Path: <iyadalmasry@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4F41A0227 for <ipv6@ietfa.amsl.com>; Tue, 13 May 2014 21:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rf-gB4JlKhAp for <ipv6@ietfa.amsl.com>; Tue, 13 May 2014 21:44:14 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1177C1A0226 for <ipv6@ietf.org>; Tue, 13 May 2014 21:44:13 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hm4so7354439wib.4 for <ipv6@ietf.org>; Tue, 13 May 2014 21:44:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=LSYldxHcfkjgFxbgepH60P1Em0uXt9vnoCwO4nePGc8=; b=z8R8pvkQ9+IDMdGMzN44TWi2LlHMdlNhIbm4HNDh8EPoK9niWHaeFxfeJXq4bwWc45 bWQQKMvk9nY8Rze+myyoNvi9BrxmEkk9YYoSWJY6HevWzp3lyRVdcEUlccBasE05zpMt YY0n9hbSVwTYzBUXL7DTd7c/EuedBhNpVUdRubL2/TlNpXkksTMRSd5J7Mikfhvx/TEP 36sKYMRkD/3XzVkdWYrO/dMmqofCMEjw1F2Ns18/K0PBZoVWJgAPmgZ4Nxhx17sn8cw5 2DeRHuwFQma6JhYwsrJ5XKlI7mIharCfahV6i5sTBd0VhCGU64bOMM/ihJp83yl57aLZ vrcg==
MIME-Version: 1.0
X-Received: by 10.194.62.210 with SMTP id a18mr1049472wjs.4.1400042647045; Tue, 13 May 2014 21:44:07 -0700 (PDT)
Sender: iyadalmasry@gmail.com
Received: by 10.180.212.74 with HTTP; Tue, 13 May 2014 21:44:06 -0700 (PDT)
Date: Wed, 14 May 2014 07:44:06 +0300
X-Google-Sender-Auth: e5tMt-aBw5d_yANADjjZovcQaHI
Message-ID: <CAOBnBFzf_CAFXuU1xOjUD_X-COLxz1ghuanTTc7+Npdj2skwtg@mail.gmail.com>
Subject: some question in subneting
From: iyad almasry <iy@yemen.net.ye>
To: ipv6@ietf.org, pthubert@cisco.com
Content-Type: multipart/alternative; boundary=047d7b5d4bf4a5cad804f954d4ee
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/CEaUaWT_I0lxSm5UuAFNTQL3BuM
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 04:46:26 -0000

--047d7b5d4bf4a5cad804f954d4ee
Content-Type: text/plain; charset=UTF-8

Hello

I am NIR and I have some question
1)For dualstack wich beter to use DHCP or private IP for every customer and
can I use DHCP for IPv4 with nating with privet IPv6 ?
2)For one customer that he/she have one subnet /64 how he will make some
subneting with some  rule or firewall between has computer if he get DHCP
IPv6 ?

 thank you
-- 


Iyad ALmasry
Deputy of data network manager
Ministery Of Telecom. & Information Technology
Public Telecom. Corporation
YemenNet
Phone: +967 1 331011
Mobile: +967 777112580
Fax: +967 1 331350

--047d7b5d4bf4a5cad804f954d4ee
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br clear=3D"all"><div><div>Hello=C2=A0</div><div><br></di=
v><div>I am NIR and I have some question</div><div>1)For dualstack wich bet=
er to use DHCP or private IP for every customer and can I use DHCP for IPv4=
 with nating with privet IPv6 ?</div>
<div>2)For one customer that he/she have one subnet /64 how he will make so=
me subneting with some =C2=A0rule or firewall between has computer if he ge=
t DHCP IPv6 ?</div><div><br></div><div>=C2=A0thank you=C2=A0</div></div>-- =
<br><br><br>
Iyad ALmasry<br>Deputy of data network manager <br>Ministery Of Telecom. &a=
mp; Information Technology <br>Public Telecom. Corporation<br>YemenNet<br>P=
hone: +967 1 331011<br>Mobile: +967 777112580<br>Fax: +967 1 331350<br>
 <br>=20
</div>

--047d7b5d4bf4a5cad804f954d4ee--


From nobody Thu May 15 05:43:27 2014
Return-Path: <evyncke@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E06151A0015 for <ipv6@ietfa.amsl.com>; Thu, 15 May 2014 05:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.852
X-Spam-Level: 
X-Spam-Status: No, score=-9.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TN5834k5z37S for <ipv6@ietfa.amsl.com>; Thu, 15 May 2014 05:43:22 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4237D1A0072 for <ipv6@ietf.org>; Thu, 15 May 2014 05:43:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3676; q=dns/txt; s=iport; t=1400157795; x=1401367395; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=VNtAIoxkxFp0BCDkf+fJfdic4yRXffKM88DTxcqO7IQ=; b=mHPLZ4pWVis8O4taAtcGY2am9GxwxbjuGHzrc0DryA4XngD+3mPXFINP WhZ8glP2YKj06DJMLa0PPoD8VySLGWj+Um3aefAX4AOEnWGKMfdOMgA90 wrNiXzyP3SqPkrIlEgxppJdS4nj+BNSlnf7ByrOK5xKHEhItBtEbWW7g+ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAC22dFOtJA2G/2dsb2JhbABZgwaBJ4JowjABGXYWdIIlAQEBBCMRRRACAQYCGAICCBcHAgICMBUQAgQBDQWIQZAanCCkeBeBKoxxGBsHgnWBSwEDlViDeZMUgXeBP4Iw
X-IronPort-AV: E=Sophos;i="4.97,1059,1389744000"; d="scan'208";a="44100471"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-4.cisco.com with ESMTP; 15 May 2014 12:43:14 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s4FChEeR028762 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 15 May 2014 12:43:14 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.121]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Thu, 15 May 2014 07:43:14 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Brian Haberman <brian@innovationslab.net>
Subject: Re: Last Call: <draft-ietf-opsec-lla-only-07.txt> (Using Only Link-Local Addressing Inside an IPv6 Network) to Informational RFC
Thread-Topic: Last Call: <draft-ietf-opsec-lla-only-07.txt> (Using Only Link-Local Addressing Inside an IPv6 Network) to Informational RFC
Thread-Index: AQHPSCghSqU/ORYRVEyPqUU/a1DTLZryUC6AgFALUQA=
Date: Thu, 15 May 2014 12:43:13 +0000
Message-ID: <CF9A82D3.1B4A5%evyncke@cisco.com>
References: <20140324155135.3745.38775.idtracker@ietfa.amsl.com> <53317A37.7040007@innovationslab.net> <CAJE_bqdwPGr07qcLhVYdwXx-z=MstbFHSd0vFvqgJX9czM+f7A@mail.gmail.com>
In-Reply-To: <CAJE_bqdwPGr07qcLhVYdwXx-z=MstbFHSd0vFvqgJX9czM+f7A@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.1.140326
x-originating-ip: [10.55.185.75]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5D31608E6AA2514B8F096911AC2A4D08@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/LuzASSQQBixLk78SuT4kRwI9Dbw
Cc: 6man WG <ipv6@ietf.org>, "draft-ietf-opsec-lla-only@tools.ietf.org" <draft-ietf-opsec-lla-only@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 12:43:24 -0000

SmlubWVpLA0KDQpUaGFua3MgZm9yIHNwb3R0aW5nIHRoZSBwb29ybHkgd3JpdHRlbiB0ZXh0IGFi
b3V0IExMQSAmIHNjb3BlLiBXZSBoYXZlDQpjaGFuZ2VkIG91ciBJLUQgaW4gb3JkZXIgdG8gcmV1
c2UgeW91ciBwcm9wb3NhbA0KDQotw6lyaWMgJiBtaWNoYWVsDQoNCk9uIDI1LzAzLzE0IDE3OjIx
LCAi56We5piO6YGU5ZOJIiA8amlubWVpQHdpZGUuYWQuanA+IHdyb3RlOg0KDQo+QXQgVHVlLCAy
NSBNYXIgMjAxNCAwODo0NDozOSAtMDQwMCwNCj5CcmlhbiBIYWJlcm1hbiA8YnJpYW5AaW5ub3Zh
dGlvbnNsYWIubmV0PiB3cm90ZToNCj4NCj4+ICAgICAgVGhlIElFVEYgTGFzdCBDYWxsIGp1c3Qg
c3RhcnRlZCBvbiB0aGlzIGRvY3VtZW50LiAgUGxlYXNlIHJldmlldw0KPj4gYW5kIGNvbW1lbnQu
DQo+DQo+SSBkb24ndCBzdWJzY3JpYmUgdG8gdGhlIG9wc2VjIE1MIHNvIEknbSBvbmx5IHJlc3Bv
bmRpbmcgaGVyZS4NCj4NCj5JIGhhdmUgb25lIHNtYWxsIGNvbW1lbnQ6IEkgdGhpbmsgdGhpcyBz
ZW50ZW5jZSBvZiBTZWN0aW9uIDIuMyBuZWVkcw0KPnNvbWUgbW9yZSBjbGFyaWZpY2F0aW9uL2Nv
cnJlY3Rpb246DQo+DQo+ICAgSG93ZXZlciwgdGhpcw0KPiAgIHN0YXRpYyBMTEEgY29uZmlndXJh
dGlvbiBtYXkgYmUgbW9yZSBjb21wbGV4IHRvIG9wZXJhdGUgdGhhbg0KPiAgIHN0YXRpY2FsbHkg
Y29uZmlndXJlZCBncmVhdGVyIHRoYW4gbGluay1sb2NhbCBhZGRyZXNzZXMsIGJlY2F1c2UgdGhl
DQo+ICAgbGluayBzY29wZSBtdXN0IGFsc28gYmUgY29uc2lkZXJlZCwgYXMgaW4gdGhpcyBleGFt
cGxlOiAnQkdQIG5laWdoYm9yDQo+ICAgZmU4MDo6MSVldGgwIGlzIGRvd24nLg0KPg0KPi0gRmly
c3Qgb2ZmLCBpdCdzIG5vdCBjbGVhciB3aGF0ICJ0aGUgbGluayBzY29wZSBtdXN0IGFsc28gYmUN
Cj4gIGNvbnNpZGVyZWQiIG1lYW5zLiAgV2l0aCB0aGUgZXhhbXBsZSBvZiBmZTgwOjoxJWV0aDAs
IEkgZ3Vlc3MgaXQNCj4gIHRyaWVzIHRvIHRhbGsgYWJvdXQgdGhlIGFtYmlndWl0eSBvZiBMTEFz
LiAgQnV0LCBpbiBwcmluY2lwbGUsIHN1Y2gNCj4gIGFtYmlndWl0eSBpcyBub3Qgc3BlY2lmaWMg
dG8gc3RhdGljYWxseSBjb25maWd1cmVkIExMQXMuICBTbyBJIGFsc28NCj4gIGd1ZXNzIGl0J3Mg
YWxzbyBiYXNlZCBvbiB0aGUgaW1wbGljaXQgYXNzdW1wdGlvbiB0aGF0IHN0YXRpY2FsbHkNCj4g
IGNvbmZpZ3VyZWQgaW50ZXJmYWNlIGlkIChzdWNoIGFzICI6OjEiKSB0ZW5kcyB0byBiZSBsZXNz
IHVuaXF1ZSB0aGFuDQo+ICBFVUktNjQgYmFzZWQgSUlEcywgdGh1cyB0ZW5kcyB0byBiZSBtb3Jl
IGFtYmlndW91cyBpbiBwcmFjdGljZS4gIElmDQo+ICB0aGlzIGlzIHdoYXQgdGhpcyBzZW50ZW5j
ZSB0cmllcyB0byBzYXksIEkgYWdyZWUsIGJ1dCBvbmUgd291bGQgbmVlZA0KPiAgcXVpdGUgYSBs
b3Qgb2Ygc3BlY3VsYXRpb24gdG8gcmVhY2ggdGhpcyB1bmRlcnN0YW5kaW5nLg0KPi0gT24gdGhl
IG90aGVyIGhhbmQsIGlmIHRoaXMgc2VudGVuY2UgdHJpZXMgdG8gc2F5IHNvbWV0aGluZw0KPiAg
ZGlmZmVyZW50LCB0aGVuIEkgZGlkbid0IGdldCBpdCwgc28gKGFzc3VtaW5nIEknbSBub3QgdGhl
IG9ubHkgb25lKQ0KPiAgaXQgd291bGQgbmVlZCBjbGFyaWZpY2F0aW9uIGFueXdheTotKQ0KPi0g
YXNzdW1pbmcgbXkgZ3Vlc3MgaW4gdGhlIGZpcnN0IGJ1bGxldCBpcyBjb3JyZWN0LCAidGhlIGxp
bmsgc2NvcGUiDQo+ICBpbiB0aGlzIGNvbnRleHQgaXMgbm90IHJlYWxseSB0aGUgYWNjdXJhdGUg
dGVybSBwZXIgUkZDIDQwMDcuICBUaGlzDQo+ICBzaG91bGQgYmUgInRoZSBsaW5rICh6b25lKSBp
bmRleCIgKCJzY29wZSIgbWVhbnMgYSB0eXBlIG9mIHNjb3BlLA0KPiAgc3VjaCBhcyAibGluayIg
b3IgInNpdGUiKS4gIEknZCBhbHNvIHN1Z2dlc3QgYWRkaW5nIGEgcmVmZXJlbmNlIHRvDQo+ICB0
aGUgUkZDLCBzaW5jZSB0aGUgcmVhZGVyIG1heSBub3QgYmUgZmFtaWxpYXIgd2l0aCB0aGUgJyVl
dGgwJw0KPiAgbm90YXRpb24uDQo+DQo+Q29tYmluaW5nIHRoZXNlLCBJJ2Qgc3VnZ2VzdCAoYmFz
ZWQgb24gbXkgZ3Vlc3NlZCB1bmRlcnN0YW5kaW5nKQ0KPnJldmlzaW5nIHRoZSBzZW50ZW5jZSBh
cyBmb2xsb3dzOg0KPg0KPiAgIEhvd2V2ZXIsIHRoaXMNCj4gICBzdGF0aWMgTExBIGNvbmZpZ3Vy
YXRpb24gbWF5IGJlIG1vcmUgY29tcGxleCB0byBvcGVyYXRlIHRoYW4NCj4gICBzdGF0aWNhbGx5
IGNvbmZpZ3VyZWQgZ3JlYXRlciB0aGFuIGxpbmstbG9jYWwgYWRkcmVzc2VzLCBiZWNhdXNlDQo+
ICAgTExBcyBhcmUgaW5oZXJlbnRseSBhbWJpZ3VvdXMgZm9yIGEgbXVsdGktbGluayBub2RlIHN1
Y2ggYXMgYQ0KPiAgIHJvdXRlciBhbmQgdGVuZCB0byBiZSBtb3JlIHNvIHdoZW4gdGhlIGludGVy
ZmFjZSBJRCBpcyBjb25maWd1cmVkDQo+ICAgc3RhdGljYWxseS4gIFRvIGRlYWwgd2l0aCB0aGUg
YW1iaWd1aXR5LCB0aGUgbGluayB6b25lIGluZGV4IG11c3QNCj4gICBhbHNvIGJlIGNvbnNpZGVy
ZWQgZXhwbGljaXRseSwgZS5nLiwgdXNpbmcgdGhlIGV4dGVuZGVkIHRleHR1YWwNCj4gICBub3Rh
dGlvbiBkZXNjcmliZWQgaW4gW1JGQzQwMDddIGFzIGluIHRoaXMgZXhhbXBsZTogJ0JHUCBuZWln
aGJvcg0KPiAgIGZlODA6OjElZXRoMCBpcyBkb3duJy4NCj4NCj4tLQ0KPkpJTk1FSSwgVGF0dXlh
DQoNCg==


From nobody Thu May 15 12:06:30 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595031A0198 for <ipv6@ietfa.amsl.com>; Thu, 15 May 2014 12:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZRBTHxOehTlD for <ipv6@ietfa.amsl.com>; Thu, 15 May 2014 12:06:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 5F9EC1A00E1 for <ipv6@ietf.org>; Thu, 15 May 2014 12:06:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 605FD180015; Thu, 15 May 2014 12:05:20 -0700 (PDT)
To: fgont@si6networks.com, brian@innovationslab.net, ted.lemon@nominum.com, bob.hinden@gmail.com, otroan@employees.org
Subject: [Technical Errata Reported] RFC6946 (3988)
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140515190520.605FD180015@rfc-editor.org>
Date: Thu, 15 May 2014 12:05:20 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/qpP1CGO5UZAgEwx1dqQqnmS62A0
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 19:06:29 -0000

The following errata report has been submitted for RFC6946,
"Processing of IPv6 "Atomic" Fragments".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6946&eid=3988

--------------------------------------
Type: Technical
Reported by: Panos Kampanakis <pkampana@cisco.com>

Section: 4

Original Text
-------------
...MUST NOT be discarded upon receipt of... 

Corrected Text
--------------
...MUST be discarded upon receipt of... 

Notes
-----


Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6946 (draft-ietf-6man-ipv6-atomic-fragments-04)
--------------------------------------
Title               : Processing of IPv6 "Atomic" Fragments
Publication Date    : May 2013
Author(s)           : F. Gont
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Thu May 15 12:31:39 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C0FA1A0317 for <ipv6@ietfa.amsl.com>; Thu, 15 May 2014 12:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtQbxXZsWAGc for <ipv6@ietfa.amsl.com>; Thu, 15 May 2014 12:31:34 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A7071A030E for <ipv6@ietf.org>; Thu, 15 May 2014 12:31:34 -0700 (PDT)
Received: from [189.221.252.135] (helo=[192.168.0.243]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <fgont@si6networks.com>) id 1Wl1N8-0004VD-UJ; Thu, 15 May 2014 21:31:19 +0200
Message-ID: <537515FB.6010301@si6networks.com>
Date: Thu, 15 May 2014 14:31:07 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: RFC Errata System <rfc-editor@rfc-editor.org>,  brian@innovationslab.net, ted.lemon@nominum.com, bob.hinden@gmail.com,  otroan@employees.org
Subject: Re: [Technical Errata Reported] RFC6946 (3988)
References: <20140515190520.605FD180015@rfc-editor.org>
In-Reply-To: <20140515190520.605FD180015@rfc-editor.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/sLSkvzOz8DcHaiO__8fA8Leakgg
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 19:31:37 -0000

Folks,

I've reviewed the errata report, and suggest to reject it:

The text in the RFC s correct: since atomic fragments must not be mized
with normal traffic, receipt of an atomic fragment must not cause the
discard of "normal" fragments that employ the same {src ip, dst ip, Frag
ID}.

Thanks,
Fernando




On 05/15/2014 02:05 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC6946,
> "Processing of IPv6 "Atomic" Fragments".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6946&eid=3988
> 
> --------------------------------------
> Type: Technical
> Reported by: Panos Kampanakis <pkampana@cisco.com>
> 
> Section: 4
> 
> Original Text
> -------------
> ...MUST NOT be discarded upon receipt of... 
> 
> Corrected Text
> --------------
> ...MUST be discarded upon receipt of... 
> 
> Notes
> -----
> 
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC6946 (draft-ietf-6man-ipv6-atomic-fragments-04)
> --------------------------------------
> Title               : Processing of IPv6 "Atomic" Fragments
> Publication Date    : May 2013
> Author(s)           : F. Gont
> Category            : PROPOSED STANDARD
> Source              : IPv6 Maintenance
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


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





From nobody Thu May 15 18:39:55 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4A61A06D9; Thu, 15 May 2014 18:39:52 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GCx1eV8PkJ_x; Thu, 15 May 2014 18:39:49 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C90951A06A8; Thu, 15 May 2014 18:39:49 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id uo5so1865877pbc.28 for <multiple recipients>; Thu, 15 May 2014 18:39:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ratcyS0Gr8lCsirt7RRbacoxcNWhEoBNgKwUSSgxELs=; b=PDq9zLMafZw8MyJDbaIS1t5wWHKugnlMVxzXath9rznBeVl5sS6OfVtRlK4TdevUUk 94089euREXbS3Jq9t+UCnjwso12c+Bmadmf/IdmWbnIRGeRXIWsG4rEuyZt0DFwCNEyg y/spnOQZst8WqZsUEIBT+GFr1AdM53yGkUtjD7uV70VgzkZGWdS1vu1utZXu4VF6A7NA PWZ/4fxVPo/PogF503B/GT+2Uyz+vVZ4ynzeGVzPD9uVD6+CsIE6LTMsDbeeNjfLsNpW XaNohyCTduj1W4C1sGD7VCKAI+y6MCYvmMqnV0qES12jjZJl4o6R2mWEVuSp0Yc+eaxH 3/Xw==
X-Received: by 10.66.151.144 with SMTP id uq16mr17057793pab.68.1400204382677;  Thu, 15 May 2014 18:39:42 -0700 (PDT)
Received: from [192.168.178.20] (101.200.69.111.dynamic.snap.net.nz. [111.69.200.101]) by mx.google.com with ESMTPSA id iv2sm11433813pbc.19.2014.05.15.18.39.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 15 May 2014 18:39:41 -0700 (PDT)
Message-ID: <53756C64.6090900@gmail.com>
Date: Fri, 16 May 2014 13:39:48 +1200
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: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: FW: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt
References: <20140513091837.28963.29591.idtracker@ietfa.amsl.com> <E045AECD98228444A58C61C200AE1BD842658563@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD842658563@xmb-rcd-x01.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/8BEZvB-Gl_2pEV3oZZls4qzyOOc
Cc: roll <roll@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>, Pat Kinney <pat.kinney@KINNEYCONSULTINGLLC.COM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 01:39:52 -0000

On 13/05/2014 21:26, Pascal Thubert (pthubert) wrote:
> Dear all:
> 
> This new version addresses Brian's concerns, in particular the language that relates this proposal with the Flow Label Specification (RFC 6437).
> It is made clearer that this is a deviation such as already tolerated for security reasons, and that the compelling reason is energy saving.
> The proposal only impacts the use of the flow label inside the LLN and does not result in a deterioration of the application of RFC 6437 inside the Internet. 
> The proposal is supported by individuals participating to LLN related groups at the IETF (cc'ed) and external SDOs (ISA100).

I'm happy with the new Applicability section. However, there is an editing
problem with the first sentence of its final paragraph (some words need to
be deleted, I suspect).

> The question is now whether we should complete the work at 6MAN or move back to ROLL.
> 
> What do you think?

IMHO, since this does not formally update a 6man document, I don't think
it's required to be processed by 6man - but a special WGLC in 6man would be
reasonable in any case, to avoid unexpected issues at IETF Last Call.
However, that's only one person's opinion.

Since 6man is not meeting in Toronto, please let us know if the draft
will be discussed elsewhere.

    Brian

> 
> Pascal
> 
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
> Sent: mardi 13 mai 2014 11:19
> To: Pascal Thubert (pthubert); Pascal Thubert (pthubert)
> Subject: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt
> 
> 
> A new version of I-D, draft-thubert-6man-flow-label-for-rpl-02.txt
> has been successfully submitted by Pascal Thubert and posted to the IETF repository.
> 
> Name:		draft-thubert-6man-flow-label-for-rpl
> Revision:	02
> Title:		The IPv6 Flow Label within a RPL domain
> Document date:	2014-05-13
> Group:		Individual Submission
> Pages:		11
> URL:            http://www.ietf.org/internet-drafts/draft-thubert-6man-flow-label-for-rpl-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-thubert-6man-flow-label-for-rpl/
> Htmlized:       http://tools.ietf.org/html/draft-thubert-6man-flow-label-for-rpl-02
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-thubert-6man-flow-label-for-rpl-02
> 
> Abstract:
>    This document present how the Flow Label can be used inside a RPL
>    domain as a replacement to the RPL option and provides rules for the
>    root to set and reset the Flow Label when forwarding between the
>    inside of RPL domain and the larger Internet, in both direction.
>    This new operation saves 44 bits in each frame, and an eventual IP-
>    in-IP encapsulation within the RPL domain that is required for all
>    packets that reach outside of the RPL domain.
> 
>                                                                                   
> 
> 
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Thu May 15 20:15:25 2014
Return-Path: <john.mann@monash.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B53121A00DC for <ipv6@ietfa.amsl.com>; Thu, 15 May 2014 20:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level: 
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3YJrT5mJv3Oj for <ipv6@ietfa.amsl.com>; Thu, 15 May 2014 20:15:19 -0700 (PDT)
Received: from na3sys009aog123.obsmtp.com (na3sys009aog123.obsmtp.com [74.125.149.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11D5D1A0080 for <ipv6@ietf.org>; Thu, 15 May 2014 20:15:19 -0700 (PDT)
Received: from mail-qg0-f41.google.com ([209.85.192.41]) (using TLSv1) by na3sys009aob123.postini.com ([74.125.148.12]) with SMTP ID DSNKU3WCv76AKskxCDyEO3cF2nnF3DuO+gVq@postini.com; Thu, 15 May 2014 20:15:12 PDT
Received: by mail-qg0-f41.google.com with SMTP id j5so3303602qga.14 for <ipv6@ietf.org>; Thu, 15 May 2014 20:15:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=qh7A9fsIPOmTn5RZv0tH3CXOZ7tu+yZsNQUdHCSDbIU=; b=FsCTzDYHv+ppLmvL0VQvXFZ9d2bkM2SPod24a3Vnroh6hQE5z6MIpSye6mEj6dw9v/ 2yGXrp0RFJq1P8UPI9zD1kZPFvhLNxwVMB/9kQUyQXLRCd7/5U5LAeBxi4J2YLmM4OaB p0HjZKpms43N7e7Ob5a4y5aI/OXpOXF1vroW3U80ovOrs4oC5Ig+7sq+Jn/kdPMrYKe3 woBWJzif4eZ7aDXtuGaHSgllsKzwvSffjw1EhYBcW/8p7S+QCC40SrtKvyWkYKamyQTY 7/gpWepKpa5QliwE8TEtXojY81/QQfJDlw/CWJFrKzDQu7V9stSQYfLB5bQz6aaxf1Rh okXw==
X-Gm-Message-State: ALoCoQmTcPlyQriRphsNEuAAaU4QNwW3MPOpUSTW4rt0iytjIICo8APc4iOz14ptN4gWbxa4A2Npw5VBwhmy/LXTQM9Y4GPQrsWygpwFMhwWwtxcHNOxq3LSSAKmFg1JN+bewkRxetHs
X-Received: by 10.140.40.239 with SMTP id x102mr20688452qgx.16.1400210111353;  Thu, 15 May 2014 20:15:11 -0700 (PDT)
X-Received: by 10.140.40.239 with SMTP id x102mr20688439qgx.16.1400210111250;  Thu, 15 May 2014 20:15:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.51.235 with HTTP; Thu, 15 May 2014 20:14:51 -0700 (PDT)
In-Reply-To: <CAOBnBFzf_CAFXuU1xOjUD_X-COLxz1ghuanTTc7+Npdj2skwtg@mail.gmail.com>
References: <CAOBnBFzf_CAFXuU1xOjUD_X-COLxz1ghuanTTc7+Npdj2skwtg@mail.gmail.com>
From: John Mann <john.mann@monash.edu>
Date: Fri, 16 May 2014 13:14:51 +1000
Message-ID: <CA+OBy1MB+wacthHrm52PLr6m9Y8GA6KkbyuqDht_xdTjhfM1wA@mail.gmail.com>
Subject: Re: some question in subneting
To: iyad almasry <iy@yemen.net.ye>
Content-Type: multipart/alternative; boundary=001a11c12a1a4ad96304f97bd286
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/sKXODBx3JdO3TKq_goM-bBVyHI8
Cc: pthubert@cisco.com, IETF IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 03:15:21 -0000

--001a11c12a1a4ad96304f97bd286
Content-Type: text/plain; charset=UTF-8

Hi,

On 14 May 2014 14:44, iyad almasry <iy@yemen.net.ye> wrote:

>
> Hello
>
> I am NIR and I have some question
>

You didn't say what type of network environment you are working in.
I will assume you are an ISP providing service over wired infrastructure.


> 1)For dualstack wich beter to use DHCP or private IP for every customer
> and can I use DHCP for IPv4 with nating with privet IPv6 ?
>

Inside each customer's network, I think it is better to use
- (customer-defined) Private IPv4 addresses, with NAT to the Internet
- Global Unicast IPv6 Addresses (public), assigned using DHCP-PD, with a
firewall controlling traffic from the Internet.

For the external interface of each customer's border router,
- IPv4 address could be assigned by ISP's DHCPv4 server
- IPv6 could be generated via SLAAC or from ISP's DHCPv6 server.

2)For one customer that he/she have one subnet /64 how he will make some
> subneting with some  rule or firewall between has computer if he get DHCP
> IPv6 ?
>

It is much better to allocate an IPv6 /56 (or /48) to each customer, and
then let them do their own subnetting using /64s.
See: tools.ietf.org/html/rfc6177

IPv6 subnets are plentiful and not expensive.

===
For a generic ISP service, I would advise against using just Unique Local
Address (private) IPv6 and NPTv6 or NAT66 to get to the Internet.
I think this introduces extra difficulties, and no benefit over a stateful
firewall.

===
There are lots of resources available to aid in designing a Dual-stack IPv6
ISP service,
and papers presented at conferences explaining what people did and what
worked or not.

A quick Google search turns up these suggestions:

tools.ietf.org/html/rfc6036

tools.ietf.org/html/rfc4864
tools.ietf.org/html/rfc6092

en.wikipedia.org/wiki/IPv6_deployment

www.txv6tf.org/wp-content/uploads/2010/08/Asadullah-Tutorial-TXv6TF_SP_IPv6.pdf
www.ipspace.net/Roadmap/IPv6_webinars

Thanks,
    John



>  thank you
> --
>
>
> Iyad ALmasry
> Deputy of data network manager
> Ministery Of Telecom. & Information Technology
> Public Telecom. Corporation
> YemenNet
> Phone: +967 1 331011
> Mobile: +967 777112580
> Fax: +967 1 331350
>

--001a11c12a1a4ad96304f97bd286
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On 14 May 2014 14:44, iyad almasry <span dir=3D"ltr">&lt;<a href=3D"mail=
to:iy@yemen.net.ye" target=3D"_blank">iy@yemen.net.ye</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex">

<div dir=3D"ltr"><br clear=3D"all"><div><div>Hello=C2=A0</div><div><br></di=
v><div>I am NIR and I have some question</div></div></div></blockquote><div=
><br></div><div>You didn&#39;t say what type of network environment you are=
 working in.</div>

<div>I will assume you are an ISP providing service over wired infrastructu=
re.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204)=
;border-left-style:solid;padding-left:1ex">

<div dir=3D"ltr"><div><div>1)For dualstack wich beter to use DHCP or privat=
e IP for every customer and can I use DHCP for IPv4 with nating with privet=
 IPv6 ?</div></div></div></blockquote><div><br></div><div>Inside each custo=
mer&#39;s network, I think it is better to use=C2=A0</div>

<div>- (customer-defined) Private IPv4 addresses, with NAT to the Internet<=
/div><div>- Global Unicast IPv6 Addresses (public), assigned using DHCP-PD,=
 with a firewall controlling traffic from the Internet.</div><div>=C2=A0</d=
iv>

<div>For the external interface of each customer&#39;s border router,</div>=
<div>- IPv4 address could be assigned by ISP&#39;s DHCPv4 server</div><div>=
- IPv6 could be generated via SLAAC or from ISP&#39;s DHCPv6 server.=C2=A0<=
/div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex"><div dir=3D"ltr"><div>
<div>2)For one customer that he/she have one subnet /64 how he will make so=
me subneting with some =C2=A0rule or firewall between has computer if he ge=
t DHCP IPv6 ?</div></div></div></blockquote><div><br></div><div>It is much =
better to allocate an IPv6 /56 (or /48) to each customer, and then let them=
 do their own subnetting using /64s.</div>

<div>See: <a href=3D"http://tools.ietf.org/html/rfc6177">tools.ietf.org/htm=
l/rfc6177</a></div><div><br></div><div>IPv6 subnets are plentiful and not e=
xpensive.</div><div><br></div><div>=3D=3D=3D</div><div>For a generic ISP se=
rvice, I would advise against using just Unique Local Address (private) IPv=
6 and NPTv6 or NAT66 to get to the Internet.</div>

<div>I think this introduces extra difficulties, and no benefit over a stat=
eful firewall.<br></div><div><br></div><div>=3D=3D=3D</div><div>There are l=
ots of resources available to aid in designing a Dual-stack IPv6 ISP servic=
e,</div>

<div>and papers presented at conferences explaining what people did and wha=
t worked or not.</div><div><br></div><div>A quick Google search turns up th=
ese suggestions:</div><div><br></div><div><a href=3D"http://tools.ietf.org/=
html/rfc6036">tools.ietf.org/html/rfc6036</a><br>

</div><div><br></div><div><a href=3D"http://tools.ietf.org/html/rfc4864">to=
ols.ietf.org/html/rfc4864</a><br></div><div><a href=3D"http://tools.ietf.or=
g/html/rfc6092">tools.ietf.org/html/rfc6092</a><br></div><div><br></div><di=
v>

<a href=3D"http://en.wikipedia.org/wiki/IPv6_deployment">en.wikipedia.org/w=
iki/IPv6_deployment</a><br></div><div><br></div><div><a href=3D"http://www.=
txv6tf.org/wp-content/uploads/2010/08/Asadullah-Tutorial-TXv6TF_SP_IPv6.pdf=
">www.txv6tf.org/wp-content/uploads/2010/08/Asadullah-Tutorial-TXv6TF_SP_IP=
v6.pdf</a><br>

</div><div><a href=3D"http://www.ipspace.net/Roadmap/IPv6_webinars">www.ips=
pace.net/Roadmap/IPv6_webinars</a><br></div><div><br></div><div>Thanks,</di=
v><div>=C2=A0 =C2=A0 John</div><div><br></div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:=
1ex">

<div dir=3D"ltr"><div><div>=C2=A0thank you=C2=A0</div></div><span class=3D"=
"><font color=3D"#888888">-- <br><br><br>
Iyad ALmasry<br>Deputy of data network manager <br>Ministery Of Telecom. &a=
mp; Information Technology <br>Public Telecom. Corporation<br>YemenNet<br>P=
hone: <a href=3D"tel:%2B967%201%20331011" value=3D"+9671331011" target=3D"_=
blank">+967 1 331011</a><br>

Mobile: <a href=3D"tel:%2B967%20777112580" value=3D"+967777112580" target=
=3D"_blank">+967 777112580</a><br>Fax: <a href=3D"tel:%2B967%201%20331350" =
value=3D"+9671331350" target=3D"_blank">+967 1 331350</a><br></font></span>=
</div></blockquote>

</div><br></div></div>

--001a11c12a1a4ad96304f97bd286--


From nobody Fri May 16 05:14:58 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC291A022A; Fri, 16 May 2014 05:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuDADBMU7sqI; Fri, 16 May 2014 05:14:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 3A9811A021C; Fri, 16 May 2014 05:14:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BA5A7180016; Fri, 16 May 2014 05:13:30 -0700 (PDT)
To: pkampana@cisco.com, fgont@si6networks.com
Subject: [Errata Rejected] RFC6946 (3988)
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140516121330.BA5A7180016@rfc-editor.org>
Date: Fri, 16 May 2014 05:13:30 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ZYz0LpeIZte40--ozPZx04abv2o
Cc: brian@innovationslab.net, ipv6@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 12:14:42 -0000

The following errata report has been rejected for RFC6946,
"Processing of IPv6 "Atomic" Fragments".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6946&eid=3988

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Panos Kampanakis <pkampana@cisco.com>
Date Reported: 2014-05-15
Rejected by: Brian Haberman (IESG)

Section: 4

Original Text
-------------
...MUST NOT be discarded upon receipt of... 

Corrected Text
--------------
...MUST be discarded upon receipt of... 

Notes
-----

 --VERIFIER NOTES-- 
The text in the RFC is correct.  Atomic fragments should not affect the re-assembly of legitimate fragments present in the re-assembly buffer.   

--------------------------------------
RFC6946 (draft-ietf-6man-ipv6-atomic-fragments-04)
--------------------------------------
Title               : Processing of IPv6 "Atomic" Fragments
Publication Date    : May 2013
Author(s)           : F. Gont
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Fri May 16 05:21:39 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C45CC1A0230; Fri, 16 May 2014 05:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_35=0.6, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NbZutWzTuJsT; Fri, 16 May 2014 05:21:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB631A0216; Fri, 16 May 2014 05:21:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BB3D4180015; Fri, 16 May 2014 05:20:21 -0700 (PDT)
To: msweet@apple.com, brian.e.carpenter@gmail.com, cheshire@apple.com, bob.hinden@gmail.com
Subject: [Errata Rejected] RFC6874 (3632)
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140516122021.BB3D4180015@rfc-editor.org>
Date: Fri, 16 May 2014 05:20:21 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/jpgXPFNVmFEdY0LjpygGBWBHTVI
Cc: brian@innovationslab.net, ipv6@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 12:21:34 -0000

The following errata report has been rejected for RFC6874,
"Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3632

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Michael Sweet <msweet@apple.com>
Date Reported: 2013-05-23
Rejected by: Brian Haberman (IESG)

Section: 3

Original Text
-------------
  Such bare "%" signs are for user interface convenience, and need to
  be turned into properly encoded characters (where "%25" encodes "%")
  before the URI is used in any protocol or HTML document.  However,
  URIs including a ZoneID have no meaning outside the originating node.
  It would therefore be highly desirable for a browser to remove the
  ZoneID from a URI before including that URI in an HTTP request.


Corrected Text
--------------
  Such bare "%" signs are for user interface convenience, and need to
  be turned into properly encoded characters (where "%25" encodes "%")
  before the URI is used in any protocol or HTML document.  HTTP Clients
  MUST include a ZoneID in any URIs provided in an HTTP request since
  HTTP Servers will need it when generating URIs, otherwise the IPv6
  address will not be usable by the Client.


Notes
-----
NOTE: PLEASE DO NOT REJECT THIS ERRATA BEFORE FURTHER REVIEW. I WILL BE SUBMITTING A NEW DRAFT PROPOSING THESE CHANGES; THIS ERRATA CAN SERVE AS PUBLIC NOTICE OF POTENTIAL CHANGES TO THE RFC.

The client uses the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care about the zoneid but the client depends on it (for link local anyways).

The client can supply the zoneid in the Host header. For example, the following illustrates a typical IPP request using the previously recommended IPvFuture format (which CUPS implements and uses):

   POST /ipp/print HTTP/1.1
   Host: [v1.fe80::1234+en0]:631
   Content-Type: application/ipp
   Transfer-Coding: chunked

   ... IPP request ...

The printer then validates the Host header and responds with URIs containing the same Host value in any reported IPv6 link-local URIs.

The key issue is one of context - the client *may* be able to query the interface used for a particular socket connection but it probably can't (easily) cache and map this information in the URIs that are embedded in the content returned by the printer, particularly when the client may have to process said content from a variety of sources - IPP is also supported over a USB transport, HTML can be read from disk, etc.  Clients are usually unable to connect to a given IPv6 link local address without the zoneid information to tell them which network interface to use.  And typically the only reason clients use an IPv6 link local address is because it was handed to them by a discovery protocol like WS-Discovery...

Requiring the client to rewrite all URIs is a tremendous burden and is error-prone.  Requiring the server to use the Host header is cheap in comparison.  Having the server validate and use the Host value also helps interoperability since existing clients may not support the new IPv6addrz format - for example, CUPS doesn't support it since it validates URIs and Host values using the ABNF in RFC 3986/STD 66.

The Host header mechanism has been standard practice outside the IETF for several years now. It is part of IPP Everywhere (Printer Working Group), Wi-Fi Direct Print Services (Wi-Fi Alliance), IPP USB (USB Implementers Forum), and AirPrint (Apple).  It solves the problem of client-side routing of IPv6 link local addresses that are used in URIs embedded in content returned by printers and other embedded devices.

Hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years. The new format is incompatible with parsers that use the ABNF in STD 66 (aka RFC 3986) and prevents the use of the Host header in HTTP requests to provide a backwards-compatible IPv6 implementation.
 --VERIFIER NOTES-- 
The errata system is not intended as a notification system for potentially new work.   

--------------------------------------
RFC6874 (draft-ietf-6man-uri-zoneid-06)
--------------------------------------
Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
Publication Date    : February 2013
Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Fri May 16 06:13:27 2014
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD161A0089 for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 06:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xdII9TgQ01tQ for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 06:13:23 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D6A31A006E for <ipv6@ietf.org>; Fri, 16 May 2014 06:13:23 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 540038810D; Fri, 16 May 2014 06:13:16 -0700 (PDT)
Received: from 102521021.rude2.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id F131A71C0002; Fri, 16 May 2014 06:13:15 -0700 (PDT)
Message-ID: <53760EDD.5010905@innovationslab.net>
Date: Fri, 16 May 2014 09:13:01 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: 6man WG <ipv6@ietf.org>, draft-ietf-6man-multicast-scopes@tools.ietf.org
Subject: AD Evaluation: draft-ietf-6man-multicast-scopes
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="0mPxwinheL3BL3gIGAotaV77qKW8MlrqQ"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/6Hj8-d8PJsN-NVBsMzHHs95EmTY
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 13:13:25 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--0mPxwinheL3BL3gIGAotaV77qKW8MlrqQ
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

All,
     I have completed my AD Evaluation of
draft-ietf-6man-multicast-scopes as a part of the publication process.
This is clearly written document and I thank the author for that.  I
only have a few issues that I would like addressed before moving this to
IETF Last Call.

1. I am curious about the inclusion of section 5 in this document.
Based on the guidance in section 3, shouldn't
draft-ietf-roll-trickle-mcast be the document defining the scop 3 usage?

2. A nit in the IANA section... It references section 1 for the scope
table, but that table is in section 2.

3. As for the new IANA registry... Is there really an expectation that
the multicast scopes will be updated enough to justify the registry? A
big reason why many of the scopes are marked unassigned is so that
network operators can use those scopes as they see fit within the
networks under their control. Given that this document updates the two
RFCs that describe the scopes, is the registry needed?

Regards,
Brian


--0mPxwinheL3BL3gIGAotaV77qKW8MlrqQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJTdg7sAAoJEBOZRqCi7goq2HgIAI2mnDIKSdknQUeRz7vjH3f2
XN1fYn+Fiux3uG8z0LG+tlz0DBeAg9ThF+hSVrKCa5ioY9t22GciYC+EYZF7jfLc
0sOTwbbp7/eiwvY5LK5EzaNDU4NJ+Ta51iR+k8Th5qsVoI6CGUmCRcUWhjEt5JDr
m0UqZij5Fc1psTF6aYT0+IEbg4Vi5eDGK+E7RWr65LLDpdqy/Wp5PS8tFFO+Gim4
FCN+WFlMLWKghwXhmf6+2akuUpcwD54QHeS3wlN7/PLB3PB9wU216R+oBqr0Sn/w
X6HnWYpX6v5Z4wszxV1QWfx6JGMAOQrGM3bz5UYGiUH3P4UvCSqa64DqAXJM8Gk=
=SYon
-----END PGP SIGNATURE-----

--0mPxwinheL3BL3gIGAotaV77qKW8MlrqQ--


From nobody Fri May 16 06:39:03 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48A161A0253 for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 06:39:00 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cy1QVINmM6C8 for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 06:38:57 -0700 (PDT)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B63CA1A024D for <ipv6@ietf.org>; Fri, 16 May 2014 06:38:57 -0700 (PDT)
Received: by mail-qg0-f46.google.com with SMTP id q108so4097098qgd.19 for <ipv6@ietf.org>; Fri, 16 May 2014 06:38:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ycmOTjfHruMMxMBBmObpZHdve50Cb0WN4JJCKKkQn7Y=; b=T2q48gIOAvWm7UOEt+dhrQFrWGYjPmPy1phY6DqqsSFMpsSrI/ym0LZQUfsZQqbg1a XO30sHlIM5rP66Un7UF3JDcn6mZy6nfXpjyX3DN17P0tNmCQlkhvnOvnwNAbPtGF7uBn vQGaK7TwEHJT0Z7L8rDQh7dlzCqjv/FC3y313MLsvTzPBHSBXYKHizFQVSnAfKQ4virj XXHClg1HIemGeUG5Eo1wn1glKCrO6zYIAoQja85bQvpzioK/3E9hDbEWmSvASiFfKSYH DFptqE1z2OwO/KxsLZMVj7GtBpmuieXIUZglju/zWI4Lu9IHMc/V1/ZhttSgRe/68kB+ BuxA==
X-Received: by 10.140.81.146 with SMTP id f18mr23916526qgd.47.1400247529980; Fri, 16 May 2014 06:38:49 -0700 (PDT)
Received: from [10.86.246.74] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id y9sm12969326qad.48.2014.05.16.06.38.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 May 2014 06:38:47 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: AD Evaluation: draft-ietf-6man-multicast-scopes
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <53760EDD.5010905@innovationslab.net>
Date: Fri, 16 May 2014 09:38:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <69A0A6BA-82DA-402E-93B1-18293506D46A@gmail.com>
References: <53760EDD.5010905@innovationslab.net>
To: Haberman Brian <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/NiKdijjwgBzqAq73jvA6qlrJM8E
Cc: draft-ietf-6man-multicast-scopes@tools.ietf.org, 6man WG <ipv6@ietf.org>, roll-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 13:39:00 -0000

Responses in-line...

On May 16, 2014, at 9:13 AM 5/16/14, Brian Haberman =
<brian@innovationslab.net> wrote:

> All,
>     I have completed my AD Evaluation of
> draft-ietf-6man-multicast-scopes as a part of the publication process.
> This is clearly written document and I thank the author for that.  I
> only have a few issues that I would like addressed before moving this =
to
> IETF Last Call.
>=20
> 1. I am curious about the inclusion of section 5 in this document.
> Based on the guidance in section 3, shouldn't
> draft-ietf-roll-trickle-mcast be the document defining the scop 3 =
usage?

My recollection is that the roll WG discussed at least three options for =
publishing the definition of scop 3:

1) in this document
2) in draft-ietf-roll-trickle-mcast
3) in a separate RFC

Again working from memory, and hoping the roll WG chairs can help my =
memory, there was thought to be no substantive difference between 1 and =
2 and, pragmatically, publishing the definition in this document was =
less disruptive.

I see that draft-ietf-roll-trickle-mcast is also currently with the IESG =
and, if desired, it would probably be easy enough to move the definition =
from this document to draft-ietf-roll-trickle-mcast at this time.
>=20
> 2. A nit in the IANA section... It references section 1 for the scope
> table, but that table is in section 2.

Thanks; will be fixed in next rev.

>=20
> 3. As for the new IANA registry... Is there really an expectation that
> the multicast scopes will be updated enough to justify the registry? A
> big reason why many of the scopes are marked unassigned is so that
> network operators can use those scopes as they see fit within the
> networks under their control. Given that this document updates the two
> RFCs that describe the scopes, is the registry needed?

The motivation for a new registry was not so much future updates to =
other scopes, but rather that it would be useful to have the definitions =
for scop 3 in one place and the list of all the definitions in the IANA =
repository rather than just in an RFC (that has updated other RFCs).

- Ralph

>=20
> Regards,
> Brian
>=20


From nobody Fri May 16 07:41:42 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3AB1A0097 for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 07:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GWYJr2HYXDQY for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 07:41:32 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 860711A007B for <ipv6@ietf.org>; Fri, 16 May 2014 07:41:32 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id E0DFD2002A; Fri, 16 May 2014 10:43:28 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 7D5A663B1C; Fri, 16 May 2014 10:41:20 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 64C3D63B17; Fri, 16 May 2014 10:41:20 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Haberman Brian <brian@innovationslab.net>
Subject: Re: AD Evaluation: draft-ietf-6man-multicast-scopes
In-Reply-To: <69A0A6BA-82DA-402E-93B1-18293506D46A@gmail.com>
References: <53760EDD.5010905@innovationslab.net> <69A0A6BA-82DA-402E-93B1-18293506D46A@gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 16 May 2014 10:41:20 -0400
Message-ID: <13430.1400251280@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/bgIKhRMqP1x-YVD8tJG1Dlzy4KE
Cc: draft-ietf-6man-multicast-scopes@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>, 6man WG <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, roll-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 14:41:34 -0000

--=-=-=


Ralph Droms <rdroms.ietf@gmail.com> wrote:
    >> All,
    >> I have completed my AD Evaluation of
    >> draft-ietf-6man-multicast-scopes as a part of the publication process.
    >> This is clearly written document and I thank the author for that.  I
    >> only have a few issues that I would like addressed before moving this to
    >> IETF Last Call.
    >>
    >> 1. I am curious about the inclusion of section 5 in this document.
    >> Based on the guidance in section 3, shouldn't
    >> draft-ietf-roll-trickle-mcast be the document defining the scop 3 usage?

    > My recollection is that the roll WG discussed at least three options
    > for publishing the definition of scop 3:

    > 1) in this document
    > 2) in draft-ietf-roll-trickle-mcast
    > 3) in a separate RFC

    > Again working from memory, and hoping the roll WG chairs can help my
    > memory, there was thought to be no substantive difference between 1 and
    > 2 and, pragmatically, publishing the definition in this document was
    > less disruptive.

There was also some view that scope 3 might have meaning beyond
trickle-mcast, and that "this document" need a 6man stamp and it would be
easier to get 6man to focus on just that part.
And, we thought that roll-trickle-mcast would be long done by now.

    > I see that draft-ietf-roll-trickle-mcast is also currently with the
    > IESG and, if desired, it would probably be easy enough to move the
    > definition from this document to draft-ietf-roll-trickle-mcast at this
    > time.

Adrian has a private comment on the document that he has to work through.
That could delay the document more, and so it might make sense to just let
multicast-scopes proceed now.

    >> 2. A nit in the IANA section... It references section 1 for the scope
    >> table, but that table is in section 2.

    > Thanks; will be fixed in next rev.

    > The motivation for a new registry was not so much future updates to
    > other scopes, but rather that it would be useful to have the
    > definitions for scop 3 in one place and the list of all the definitions
    > in the IANA repository rather than just in an RFC (that has updated
    > other RFCs).

I also agree: people are getting trained to go to IANA's web site for the
latest reference, and it's good to encourage that.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/


--=-=-=
Content-Type: application/pgp-signature

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

iQEVAwUBU3YjkICLcPvd0N1lAQL66AgAvSFhMZL6aGLgwF99d1a6H3IAfsv9S8OU
PNiUFJIVK/44VDuaknxPxWiL/uMTLzFP+909qritaUoItfyL+uacdfRqXXnqc/LV
BQNW5odOCSFwSAva/4VuNcnLPvVLt431taykLs/pUtEnVnKDgRmutYyCJu4T+fEs
K3GQdu//TpzLS8ofFHVZQbljBi2qn4i4FhgEk1/OThzEyYlKAtqoQtcZxVdbCH2x
26BWz3JDk6A6umjggjeEtJnplBB6vIQJwnT+J8m/DrfytPJNR29INMIQ8r/OK2lE
Tk+W6egaO+R04+JiRdeN9AijqBlbXp+20RTitJWQvW2bMgGKByBCqg==
=MTTr
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri May 16 08:32:46 2014
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DEDF1A02BF for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 08:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X5xvqcaHDa8G for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 08:32:12 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B34E1A029C for <ipv6@ietf.org>; Fri, 16 May 2014 08:32:12 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 0821A8810D; Fri, 16 May 2014 08:32:05 -0700 (PDT)
Received: from 102521021.rude2.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 2B13E71C0002; Fri, 16 May 2014 08:32:04 -0700 (PDT)
Message-ID: <53762F74.80108@innovationslab.net>
Date: Fri, 16 May 2014 11:32:04 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: AD Evaluation: draft-ietf-6man-multicast-scopes
References: <53760EDD.5010905@innovationslab.net> <69A0A6BA-82DA-402E-93B1-18293506D46A@gmail.com> <13430.1400251280@sandelman.ca>
In-Reply-To: <13430.1400251280@sandelman.ca>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dIRkMr46R5mfVqEloav4rVImRCE1SVFaT"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/rBX54_BNy38to0EQMRODwyR0XM4
Cc: draft-ietf-6man-multicast-scopes@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>, 6man WG <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, roll-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 15:32:31 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--dIRkMr46R5mfVqEloav4rVImRCE1SVFaT
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Michael & Ralph,

On 5/16/14 10:41 AM, Michael Richardson wrote:
>=20
> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>     >> All,
>     >> I have completed my AD Evaluation of
>     >> draft-ietf-6man-multicast-scopes as a part of the publication pr=
ocess.
>     >> This is clearly written document and I thank the author for that=
=2E  I
>     >> only have a few issues that I would like addressed before moving=
 this to
>     >> IETF Last Call.
>     >>
>     >> 1. I am curious about the inclusion of section 5 in this documen=
t.
>     >> Based on the guidance in section 3, shouldn't
>     >> draft-ietf-roll-trickle-mcast be the document defining the scop =
3 usage?
>=20
>     > My recollection is that the roll WG discussed at least three opti=
ons
>     > for publishing the definition of scop 3:
>=20
>     > 1) in this document
>     > 2) in draft-ietf-roll-trickle-mcast
>     > 3) in a separate RFC
>=20
>     > Again working from memory, and hoping the roll WG chairs can help=
 my
>     > memory, there was thought to be no substantive difference between=
 1 and
>     > 2 and, pragmatically, publishing the definition in this document =
was
>     > less disruptive.
>=20
> There was also some view that scope 3 might have meaning beyond
> trickle-mcast, and that "this document" need a 6man stamp and it would =
be
> easier to get 6man to focus on just that part.
> And, we thought that roll-trickle-mcast would be long done by now.
>=20
>     > I see that draft-ietf-roll-trickle-mcast is also currently with t=
he
>     > IESG and, if desired, it would probably be easy enough to move th=
e
>     > definition from this document to draft-ietf-roll-trickle-mcast at=
 this
>     > time.
>=20
> Adrian has a private comment on the document that he has to work throug=
h.
> That could delay the document more, and so it might make sense to just =
let
> multicast-scopes proceed now.
>=20
>     >> 2. A nit in the IANA section... It references section 1 for the =
scope
>     >> table, but that table is in section 2.
>=20
>     > Thanks; will be fixed in next rev.
>=20
>     > The motivation for a new registry was not so much future updates =
to
>     > other scopes, but rather that it would be useful to have the
>     > definitions for scop 3 in one place and the list of all the defin=
itions
>     > in the IANA repository rather than just in an RFC (that has updat=
ed
>     > other RFCs).
>=20
> I also agree: people are getting trained to go to IANA's web site for t=
he
> latest reference, and it's good to encourage that.

Given the above, the document seems ready to go to IETF Last Call modulo
fixing up the reference to the table.  I will put this in Revised ID
needed state so that change can be made.  Once a new version pops out, I
will start IETF LC.

Regards,
Brian



--dIRkMr46R5mfVqEloav4rVImRCE1SVFaT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJTdi90AAoJEBOZRqCi7goqTMoH/03X/306wIInK7gaI1hijIv5
aywNQsIKc6CLLqNEb/3GltW+IhLgWpG9MxVrnSupGD3LzS9Z3iL/TwL2Tdpcc7cf
I6LaABoNfnheiXqWnNj3oIKuJF1NYtPrnAl+GsVvNYcnQMk5vSHdHRUfpoVAnrSe
3kHLpC674h9z/XieZoEP1u36bq9dYu/5kf7itrGhE2tzrfow2d6W9vIo6MYv4ekD
AnhrZOheXoBryx3prcTjTDrn5vahsq9k0Q+JHQKlsO11t7mbONaArKLTaObiEREp
3pWJG29YxNJMMLnE2aNjUpgWo0L/5FYF7vP9M00IFrsKcl3mrAAtc8sUMG1Ej3w=
=p7tw
-----END PGP SIGNATURE-----

--dIRkMr46R5mfVqEloav4rVImRCE1SVFaT--


From nobody Fri May 16 08:48:25 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17D801A031B; Fri, 16 May 2014 08:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hONoyFqZFeMD; Fri, 16 May 2014 08:48:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 04F8E1A029C; Fri, 16 May 2014 08:48:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-multicast-scopes-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140516154822.20849.27776.idtracker@ietfa.amsl.com>
Date: Fri, 16 May 2014 08:48:22 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/-V64ybN_j47XrnFgRD2PlDL114Q
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 15:48:23 -0000

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

        Title           : IPv6 Multicast Address Scopes
        Author          : Ralph Droms
	Filename        : draft-ietf-6man-multicast-scopes-05.txt
	Pages           : 6
	Date            : 2014-05-16

Abstract:
   This document updates the definitions of IPv6 multicast scopes.  This
   document updates RFC 4007 and RFC 4291


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-multicast-scopes/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-multicast-scopes-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multicast-scopes-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Fri May 16 08:50:13 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0524C1A0322 for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 08:50:11 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KnfXfSBXcGX for <ipv6@ietfa.amsl.com>; Fri, 16 May 2014 08:50:09 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 362C11A0306 for <ipv6@ietf.org>; Fri, 16 May 2014 08:50:09 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id e16so4531543qcx.41 for <ipv6@ietf.org>; Fri, 16 May 2014 08:50:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9PMTq+LYk7nlDpuG6n1tiHIPkMoOWXFHLmEB8eK7i90=; b=Mtkq/IMJnAnjiUH4We5VvE/nCesJ5/TkBZ0glmtbMGmrUpFkRm1cjpsultIWgQa7aM t2+7URvJAUAdysaVM3EqC4nhjZPNmPhaHs6mPVsqYAktqrPcfDK169qo65+qzDyOZX/M Ie3dw42quaLInFqnKdsFb10KyyTL7Ggp8NFdY8t4mBlQ6hNJQPmaJrHvF15Zp/4N18QX ifwrFnGo/j4sPIO1M7r5rfJD0bCajAOVWdiDM6e0hV2qQI5dP2Pkgyk6ZTY4pUOHcA5O aE8VtozHDbtg4XvyHDmpHEk6uX3GNZmiwCaTvIvYxI++LA/td/9xk10kJ3sRwG/WwRYP GUYA==
X-Received: by 10.224.125.74 with SMTP id x10mr20989125qar.99.1400255401296; Fri, 16 May 2014 08:50:01 -0700 (PDT)
Received: from [10.86.246.74] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id e5sm5356846qgf.6.2014.05.16.08.49.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 May 2014 08:49:58 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: AD Evaluation: draft-ietf-6man-multicast-scopes
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <53762F74.80108@innovationslab.net>
Date: Fri, 16 May 2014 11:49:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FF01AA8-E011-4AF5-AFA0-3C2C00961C88@gmail.com>
References: <53760EDD.5010905@innovationslab.net> <69A0A6BA-82DA-402E-93B1-18293506D46A@gmail.com> <13430.1400251280@sandelman.ca> <53762F74.80108@innovationslab.net>
To: Haberman Brian <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/AzlbcYPR2M819e02NOHTJ4VW8ek
Cc: draft-ietf-6man-multicast-scopes@tools.ietf.org, Michael Richardson <mcr+ietf@sandelman.ca>, roll-chairs@tools.ietf.org, 6man WG <ipv6@ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 15:50:11 -0000

The new rev has been uploaded with the reference to section 2 fixed.

- Ralph

On May 16, 2014, at 11:32 AM 5/16/14, Brian Haberman =
<brian@innovationslab.net> wrote:

> Michael & Ralph,
>=20
> On 5/16/14 10:41 AM, Michael Richardson wrote:
>>=20
>> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>>>> All,
>>>> I have completed my AD Evaluation of
>>>> draft-ietf-6man-multicast-scopes as a part of the publication =
process.
>>>> This is clearly written document and I thank the author for that.  =
I
>>>> only have a few issues that I would like addressed before moving =
this to
>>>> IETF Last Call.
>>>>=20
>>>> 1. I am curious about the inclusion of section 5 in this document.
>>>> Based on the guidance in section 3, shouldn't
>>>> draft-ietf-roll-trickle-mcast be the document defining the scop 3 =
usage?
>>=20
>>> My recollection is that the roll WG discussed at least three options
>>> for publishing the definition of scop 3:
>>=20
>>> 1) in this document
>>> 2) in draft-ietf-roll-trickle-mcast
>>> 3) in a separate RFC
>>=20
>>> Again working from memory, and hoping the roll WG chairs can help my
>>> memory, there was thought to be no substantive difference between 1 =
and
>>> 2 and, pragmatically, publishing the definition in this document was
>>> less disruptive.
>>=20
>> There was also some view that scope 3 might have meaning beyond
>> trickle-mcast, and that "this document" need a 6man stamp and it =
would be
>> easier to get 6man to focus on just that part.
>> And, we thought that roll-trickle-mcast would be long done by now.
>>=20
>>> I see that draft-ietf-roll-trickle-mcast is also currently with the
>>> IESG and, if desired, it would probably be easy enough to move the
>>> definition from this document to draft-ietf-roll-trickle-mcast at =
this
>>> time.
>>=20
>> Adrian has a private comment on the document that he has to work =
through.
>> That could delay the document more, and so it might make sense to =
just let
>> multicast-scopes proceed now.
>>=20
>>>> 2. A nit in the IANA section... It references section 1 for the =
scope
>>>> table, but that table is in section 2.
>>=20
>>> Thanks; will be fixed in next rev.
>>=20
>>> The motivation for a new registry was not so much future updates to
>>> other scopes, but rather that it would be useful to have the
>>> definitions for scop 3 in one place and the list of all the =
definitions
>>> in the IANA repository rather than just in an RFC (that has updated
>>> other RFCs).
>>=20
>> I also agree: people are getting trained to go to IANA's web site for =
the
>> latest reference, and it's good to encourage that.
>=20
> Given the above, the document seems ready to go to IETF Last Call =
modulo
> fixing up the reference to the table.  I will put this in Revised ID
> needed state so that change can be made.  Once a new version pops out, =
I
> will start IETF LC.
>=20
> Regards,
> Brian
>=20
>=20


From nobody Fri May 16 09:19:36 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 051CA1A02A8; Fri, 16 May 2014 09:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id piRcs-P0Zhqo; Fri, 16 May 2014 09:19:32 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 68EB31A027D; Fri, 16 May 2014 09:19:31 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-6man-multicast-scopes-05.txt> (IPv6 Multicast Address Scopes) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20140516161931.17929.9224.idtracker@ietfa.amsl.com>
Date: Fri, 16 May 2014 09:19:31 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Rm5cXHNajkoEn7H1jyWaDjdYy2U
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 May 2014 16:19:34 -0000

The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document:
- 'IPv6 Multicast Address Scopes'
  <draft-ietf-6man-multicast-scopes-05.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-05-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document updates the definitions of IPv6 multicast scopes.  This
   document updates RFC 4007 and RFC 4291




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-6man-multicast-scopes/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-6man-multicast-scopes/ballot/


No IPR declarations have been submitted directly on this I-D.



From nobody Mon May 19 12:20:55 2014
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEA2A1A00EA for <ipv6@ietfa.amsl.com>; Mon, 19 May 2014 12:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Level: 
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UZ8_boGxY_Sb for <ipv6@ietfa.amsl.com>; Mon, 19 May 2014 12:20:52 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DB621A01DD for <6man@ietf.org>; Mon, 19 May 2014 12:20:52 -0700 (PDT)
Received: by mail-lb0-f169.google.com with SMTP id s7so4451531lbd.0 for <6man@ietf.org>; Mon, 19 May 2014 12:20:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=jfMzctfmcwZGBaxxMGHM18r+Z/sfY/adwz+FPMzVaws=; b=YHED86TbmFADOkjBjpYRpO7b5enNIKIT+rohKOtxdzXfbPsfakbop14edgSyvuLg0F GMber5p/8eOP8LwtfLLaBaLEQTu1sRuO3B7I775JOYyaSTDJzEoJ+8mvnMQdQ7Z3s6F6 ywPf8uwyP0lGtSxZNLvLaGAWdy/S7loNdT4szHZSfit4hIoXtq+EnREJ1ObJ1+kA8tpU 1T989VgCmH7SumrL+UifiKawuIbEk0JXdjyljKgMr9GRXTMHiEAqD0iJ1VbA86BPM1ER QMs80IEqwaflFTD8HkTHipNxHI9S0VLYuISGQYyHINiOMdhQ44M2eJGlqFw4B7gku86T LqKA==
MIME-Version: 1.0
X-Received: by 10.112.77.166 with SMTP id t6mr8025300lbw.53.1400527250848; Mon, 19 May 2014 12:20:50 -0700 (PDT)
Received: by 10.114.27.106 with HTTP; Mon, 19 May 2014 12:20:50 -0700 (PDT)
Date: Mon, 19 May 2014 14:20:50 -0500
Message-ID: <CAC8QAccFgwdVhoDYW7gHWi64cO8m0ZmbvoqDLAUyiYvsjLFP6g@mail.gmail.com>
Subject: Re: New Version Notification for draft-sarikaya-6man-next-hop-ra-01.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: =?UTF-8?Q?Dan_L=C3=BCdtke?= <maildanrl@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/NnopcFWGeelJNN9c7-9g-vYFIB4
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 May 2014 19:20:54 -0000

Hi Dan, Brian, all,

I revised the draft based on your comments. The details are below.
Please check it and let me know your comments:

A new version of I-D, draft-sarikaya-6man-next-hop-ra-01.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Name:           draft-sarikaya-6man-next-hop-ra
Revision:       01
Title:          IPv6 RA Options for Next Hop Routes
Document date:  2014-05-19
Group:          Individual Submission
Pages:          12
URL:
http://www.ietf.org/internet-drafts/draft-sarikaya-6man-next-hop-ra-01.txt
Status:
https://datatracker.ietf.org/doc/draft-sarikaya-6man-next-hop-ra/
Htmlized:       http://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-=
01
Diff:
http://www.ietf.org/rfcdiff?url2=3Ddraft-sarikaya-6man-next-hop-ra-01

On Sun, Feb 23, 2014 at 9:35 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 15/02/2014 06:35, Dan L=C3=BCdtke wrote:
>> Hi,
>>
>> I have very mixed feelings regarding this draft and I have not yet
>> decided whether it is me or the draft :)
>
> It's probably the fact that the community is very divided as to whether
> this, or a DHCPv6 based solution, is the right one for delivering
> routing information to hosts. Personally I see advantages in defining
> enough in RA that a DHCPv6-free network is possible, but it only
> makes sense if we insist that routing information capable of delivery
> by RA and that capable of delivery by DHCPv6 have *exactly* the same
> semantics (even if the syntax of the messages is different).
> ...
>
>> I also have the feeling that consuming 7 numbers from the registry for
>> new options is a bit too greedy. Do you see any way to reduce the
>> consumption of this very limited resource? I think it would help
>> supporting the draft a lot.
>
> Since an address is the same thing as a /128 prefix, I would
> think that the address TLVs could be replaced by prefixes,
> which would save at least a couple of option numbers. If that
> isn't enough, it would have to go to subtypes.
>
>     Brian
>


From nobody Mon May 19 22:50:14 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5D821A028C; Mon, 19 May 2014 22:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i3lRRQDvFYKQ; Mon, 19 May 2014 22:50:06 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C84431A0295; Mon, 19 May 2014 22:50:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6402; q=dns/txt; s=iport; t=1400565006; x=1401774606; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=LYUVBrkILF6oLcfkRQvCZMXil+7B/P2LggULLBi/DrY=; b=Gv9Pdyh3lUme7GSn7cacmEgD38gyAH6CY+ukbI7tmulygEDo5tOYcGE6 4AXZyvAQ55MJuGi7CSP1LLn369ioSNiOSla5/vTneNXCBqOhuxfnSKXtU S4QmRyf5FRMsb2Tgx0RJnuoK3EPnSsLK+LHURe3Zi08qys5keeWCXh0LR k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIIAGTselOtJV2b/2dsb2JhbABZgwZRUQeCablshzsBGX0WdIIlAQEBBAEBASAROgkCDAQCAQgRBAEBAQICBh0DAgICHwYLFAEHAQgCBA4FCAGIJAMRCAWtbp4qDYYvF4Eqiw+BZBYbBwaCbzaBFQSXbIMxi3KFboF4gUBtgUM
X-IronPort-AV: E=Sophos;i="4.98,871,1392163200"; d="scan'208";a="326352007"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP; 20 May 2014 05:50:00 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s4K5o09O022772 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 20 May 2014 05:50:00 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.6]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Tue, 20 May 2014 00:50:00 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: FW: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt
Thread-Topic: FW: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt
Thread-Index: AQHPboxRAM7nFZ++3UC8TcXZbob1AZs+O9FggASKWQCABjn0sA==
Date: Tue, 20 May 2014 05:49:58 +0000
Deferred-Delivery: Tue, 20 May 2014 05:49:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD84266CC43@xmb-rcd-x01.cisco.com>
References: <20140513091837.28963.29591.idtracker@ietfa.amsl.com> <E045AECD98228444A58C61C200AE1BD842658563@xmb-rcd-x01.cisco.com> <53756C64.6090900@gmail.com>
In-Reply-To: <53756C64.6090900@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.22.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/s6DuCsbt88Auzui1SLJYAguE1zw
Cc: roll <roll@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>, Pat Kinney <pat.kinney@KINNEYCONSULTINGLLC.COM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 05:50:09 -0000

VGhhbmtzIGEgYnVuY2ggQnJpYW4hDQoNClNpbmNlIHRoaXMgY2hhbmdlcyBhIE1BWSBOT1QgaW4g
YSBNVVNUIE5PVCwgSSBwdWJsaXNoZWQgYW4gMDMuDQoNClRoZSB0ZXh0IGlzIG5vdzoNCg0KICAg
VGhpcyBzcGVjaWZpY2F0aW9uIGFsc28gYWxsb3dzIHRoYXQgcmVnYXJkbGVzcyBvZiBpdHMgb3Jp
Z2luYWwNCiAgIHNldHRpbmcsIGEgcm9vdCBvZiBhIFJQTCBkb21haW4gTUFZIHNldCB0aGUgRmxv
dyBMYWJlbCBvZiBJUHY2DQogICBwYWNrZXRzIHRoYXQgZXhpdCB0aGUgUlBMIGRvbWFpbiBpbiBh
IG1hbm5lciB0aGF0IFNIT1VMRCBjb25mb3JtIHRvDQogICB0aGUgcHJlc2NyaXB0aW9ucyBpbiBb
UkZDNjQzN10uICBUaGVyZWZvcmUgYSBzb3VyY2UgaW4gdGhlIFJQTCBkb21haW4NCiAgIE1VU1Qg
Tk9UIGFzc3VtZSB0aGF0IGl0cyBzZXR0aW5nIG9mIHRoZSBGbG93IExhYmVsIGJlIHByZXNlcnZl
ZCBlbmQtDQogICB0by1lbmQuICBGcm9tIHRoZXJlLCB0aGUgY2FwYWJpbGl0eSBieSBSUEwgcm91
dGVycyBpbnNpZGUgdGhlIExMTiB0bw0KICAgYWx0ZXIgYSBub24temVybyBGbG93IExhYmVsIGJl
dHdlZW4gdGhlIHNvdXJjZSBhbmQgdGhlIHJvb3QgaXMNCiAgIGFub3RoZXIgbWlub3IgZGV2aWF0
aW9uIHRvIFtSRkM2NDM3XSB0aGF0IGlzIGFsc28gYWNjZXB0YWJsZSBzaW5jZSBpdA0KICAgaXMg
dHJhbnNwYXJlbnQgdG8gdGhlIGNvcmUgb2YgdGhlIEludGVybmV0Lg0KDQpBZ2FpbiwgbWFueSB0
aGFua3MuDQoNCkknbGwgZm9sbG93IHVwIHdpdGggdGhlIGNoYWlycyBhYm91dCB0aGUgaWRlYSBv
ZiBhIHNwZWNpYWwgV0dMQyBpbiA2bWFuLg0KDQpQYXNjYWwNCg0KPiAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPiBGcm9tOiBCcmlhbiBFIENhcnBlbnRlciBbbWFpbHRvOmJyaWFuLmUuY2Fy
cGVudGVyQGdtYWlsLmNvbV0NCj4gU2VudDogdmVuZHJlZGkgMTYgbWFpIDIwMTQgMDM6NDANCj4g
VG86IFBhc2NhbCBUaHViZXJ0IChwdGh1YmVydCkNCj4gQ2M6IGlwdjZAaWV0Zi5vcmc7IHJvbGw7
IDZ0aXNjaEBpZXRmLm9yZzsgUGF0IEtpbm5leQ0KPiBTdWJqZWN0OiBSZTogRlc6IE5ldyBWZXJz
aW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtdGh1YmVydC02bWFuLWZsb3ctbGFiZWwtDQo+IGZv
ci1ycGwtMDIudHh0DQo+IA0KPiBPbiAxMy8wNS8yMDE0IDIxOjI2LCBQYXNjYWwgVGh1YmVydCAo
cHRodWJlcnQpIHdyb3RlOg0KPiA+IERlYXIgYWxsOg0KPiA+DQo+ID4gVGhpcyBuZXcgdmVyc2lv
biBhZGRyZXNzZXMgQnJpYW4ncyBjb25jZXJucywgaW4gcGFydGljdWxhciB0aGUgbGFuZ3VhZ2UN
Cj4gdGhhdCByZWxhdGVzIHRoaXMgcHJvcG9zYWwgd2l0aCB0aGUgRmxvdyBMYWJlbCBTcGVjaWZp
Y2F0aW9uIChSRkMgNjQzNykuDQo+ID4gSXQgaXMgbWFkZSBjbGVhcmVyIHRoYXQgdGhpcyBpcyBh
IGRldmlhdGlvbiBzdWNoIGFzIGFscmVhZHkgdG9sZXJhdGVkIGZvcg0KPiBzZWN1cml0eSByZWFz
b25zLCBhbmQgdGhhdCB0aGUgY29tcGVsbGluZyByZWFzb24gaXMgZW5lcmd5IHNhdmluZy4NCj4g
PiBUaGUgcHJvcG9zYWwgb25seSBpbXBhY3RzIHRoZSB1c2Ugb2YgdGhlIGZsb3cgbGFiZWwgaW5z
aWRlIHRoZSBMTE4gYW5kDQo+IGRvZXMgbm90IHJlc3VsdCBpbiBhIGRldGVyaW9yYXRpb24gb2Yg
dGhlIGFwcGxpY2F0aW9uIG9mIFJGQyA2NDM3IGluc2lkZSB0aGUNCj4gSW50ZXJuZXQuDQo+ID4g
VGhlIHByb3Bvc2FsIGlzIHN1cHBvcnRlZCBieSBpbmRpdmlkdWFscyBwYXJ0aWNpcGF0aW5nIHRv
IExMTiByZWxhdGVkDQo+IGdyb3VwcyBhdCB0aGUgSUVURiAoY2MnZWQpIGFuZCBleHRlcm5hbCBT
RE9zIChJU0ExMDApLg0KPiANCj4gSSdtIGhhcHB5IHdpdGggdGhlIG5ldyBBcHBsaWNhYmlsaXR5
IHNlY3Rpb24uIEhvd2V2ZXIsIHRoZXJlIGlzIGFuIGVkaXRpbmcNCj4gcHJvYmxlbSB3aXRoIHRo
ZSBmaXJzdCBzZW50ZW5jZSBvZiBpdHMgZmluYWwgcGFyYWdyYXBoIChzb21lIHdvcmRzIG5lZWQg
dG8NCj4gYmUgZGVsZXRlZCwgSSBzdXNwZWN0KS4NCj4gDQo+ID4gVGhlIHF1ZXN0aW9uIGlzIG5v
dyB3aGV0aGVyIHdlIHNob3VsZCBjb21wbGV0ZSB0aGUgd29yayBhdCA2TUFOIG9yDQo+IG1vdmUg
YmFjayB0byBST0xMLg0KPiA+DQo+ID4gV2hhdCBkbyB5b3UgdGhpbms/DQo+IA0KPiBJTUhPLCBz
aW5jZSB0aGlzIGRvZXMgbm90IGZvcm1hbGx5IHVwZGF0ZSBhIDZtYW4gZG9jdW1lbnQsIEkgZG9u
J3QgdGhpbmsNCj4gaXQncyByZXF1aXJlZCB0byBiZSBwcm9jZXNzZWQgYnkgNm1hbiAtIGJ1dCBh
IHNwZWNpYWwgV0dMQyBpbiA2bWFuIHdvdWxkDQo+IGJlIHJlYXNvbmFibGUgaW4gYW55IGNhc2Us
IHRvIGF2b2lkIHVuZXhwZWN0ZWQgaXNzdWVzIGF0IElFVEYgTGFzdCBDYWxsLg0KPiBIb3dldmVy
LCB0aGF0J3Mgb25seSBvbmUgcGVyc29uJ3Mgb3Bpbmlvbi4NCj4gDQo+IFNpbmNlIDZtYW4gaXMg
bm90IG1lZXRpbmcgaW4gVG9yb250bywgcGxlYXNlIGxldCB1cyBrbm93IGlmIHRoZSBkcmFmdCB3
aWxsIGJlDQo+IGRpc2N1c3NlZCBlbHNld2hlcmUuDQo+IA0KPiAgICAgQnJpYW4NCj4gDQo+ID4N
Cj4gPiBQYXNjYWwNCj4gPg0KPiA+DQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4g
PiBGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNA
aWV0Zi5vcmddDQo+ID4gU2VudDogbWFyZGkgMTMgbWFpIDIwMTQgMTE6MTkNCj4gPiBUbzogUGFz
Y2FsIFRodWJlcnQgKHB0aHViZXJ0KTsgUGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KQ0KPiA+IFN1
YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3INCj4gPiBkcmFmdC10aHViZXJ0LTZt
YW4tZmxvdy1sYWJlbC1mb3ItcnBsLTAyLnR4dA0KPiA+DQo+ID4NCj4gPiBBIG5ldyB2ZXJzaW9u
IG9mIEktRCwgZHJhZnQtdGh1YmVydC02bWFuLWZsb3ctbGFiZWwtZm9yLXJwbC0wMi50eHQNCj4g
PiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFBhc2NhbCBUaHViZXJ0IGFuZCBw
b3N0ZWQgdG8gdGhlIElFVEYNCj4gcmVwb3NpdG9yeS4NCj4gPg0KPiA+IE5hbWU6CQlkcmFmdC10
aHViZXJ0LTZtYW4tZmxvdy1sYWJlbC1mb3ItcnBsDQo+ID4gUmV2aXNpb246CTAyDQo+ID4gVGl0
bGU6CQlUaGUgSVB2NiBGbG93IExhYmVsIHdpdGhpbiBhIFJQTCBkb21haW4NCj4gPiBEb2N1bWVu
dCBkYXRlOgkyMDE0LTA1LTEzDQo+ID4gR3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4g
PiBQYWdlczoJCTExDQo+ID4gVVJMOiAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50
ZXJuZXQtZHJhZnRzL2RyYWZ0LXRodWJlcnQtNm1hbi1mbG93LQ0KPiBsYWJlbC1mb3ItcnBsLTAy
LnR4dA0KPiA+IFN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC10aHViZXJ0LTZtYW4tZmxvdy0NCj4gbGFiZWwtZm9yLXJwbC8NCj4gPiBIdG1saXpl
ZDogICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtdGh1YmVydC02bWFuLWZs
b3ctbGFiZWwtZm9yLQ0KPiBycGwtMDINCj4gPiBEaWZmOiAgICAgICAgICAgaHR0cDovL3d3dy5p
ZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtdGh1YmVydC02bWFuLWZsb3ctbGFiZWwtDQo+IGZv
ci1ycGwtMDINCj4gPg0KPiA+IEFic3RyYWN0Og0KPiA+ICAgIFRoaXMgZG9jdW1lbnQgcHJlc2Vu
dCBob3cgdGhlIEZsb3cgTGFiZWwgY2FuIGJlIHVzZWQgaW5zaWRlIGEgUlBMDQo+ID4gICAgZG9t
YWluIGFzIGEgcmVwbGFjZW1lbnQgdG8gdGhlIFJQTCBvcHRpb24gYW5kIHByb3ZpZGVzIHJ1bGVz
IGZvciB0aGUNCj4gPiAgICByb290IHRvIHNldCBhbmQgcmVzZXQgdGhlIEZsb3cgTGFiZWwgd2hl
biBmb3J3YXJkaW5nIGJldHdlZW4gdGhlDQo+ID4gICAgaW5zaWRlIG9mIFJQTCBkb21haW4gYW5k
IHRoZSBsYXJnZXIgSW50ZXJuZXQsIGluIGJvdGggZGlyZWN0aW9uLg0KPiA+ICAgIFRoaXMgbmV3
IG9wZXJhdGlvbiBzYXZlcyA0NCBiaXRzIGluIGVhY2ggZnJhbWUsIGFuZCBhbiBldmVudHVhbCBJ
UC0NCj4gPiAgICBpbi1JUCBlbmNhcHN1bGF0aW9uIHdpdGhpbiB0aGUgUlBMIGRvbWFpbiB0aGF0
IGlzIHJlcXVpcmVkIGZvciBhbGwNCj4gPiAgICBwYWNrZXRzIHRoYXQgcmVhY2ggb3V0c2lkZSBv
ZiB0aGUgUlBMIGRvbWFpbi4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+IFBsZWFzZSBub3RlIHRo
YXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mDQo+IHN1
Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJs
ZSBhdCB0b29scy5pZXRmLm9yZy4NCj4gPg0KPiA+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+ID4N
Cj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KPiA+IElFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlz
dA0KPiA+IGlwdjZAaWV0Zi5vcmcNCj4gPiBBZG1pbmlzdHJhdGl2ZSBSZXF1ZXN0czogaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHY2DQo+ID4gLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4g
Pg0K


From nobody Wed May 21 00:35:12 2014
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD9EA1A0829 for <ipv6@ietfa.amsl.com>; Wed, 21 May 2014 00:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BFNCApAo50EV for <ipv6@ietfa.amsl.com>; Wed, 21 May 2014 00:35:09 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id C73131A0825 for <6man@ietf.org>; Wed, 21 May 2014 00:35:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 1213487006F; Wed, 21 May 2014 09:35:07 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBdNL5kAxi8s; Wed, 21 May 2014 09:35:06 +0200 (CEST)
Received: from Rays-iMac.local (unknown [IPv6:2001:470:1f15:73a:8d50:3f2:b606:bb79]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id C60F1870044; Wed, 21 May 2014 09:35:06 +0200 (CEST)
Message-ID: <537C571F.7050709@globis.net>
Date: Wed, 21 May 2014 09:34:55 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: sarikaya@ieee.org
Subject: Re: Re: New Version Notification for draft-sarikaya-6man-next-hop-ra-01.txt
References: <CAC8QAccFgwdVhoDYW7gHWi64cO8m0ZmbvoqDLAUyiYvsjLFP6g@mail.gmail.com>
In-Reply-To: <CAC8QAccFgwdVhoDYW7gHWi64cO8m0ZmbvoqDLAUyiYvsjLFP6g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/DvJR_2W01F4l0ZZUpmfASNy9DbA
Cc: =?ISO-8859-1?Q?Dan_L=FCdtke?= <maildanrl@gmail.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 07:35:11 -0000

Behcet Sarikaya wrote:
> Hi Dan, Brian, all,
>
> I revised the draft based on your comments. The details are below.
> Please check it and let me know your comments:
>
> A new version of I-D, draft-sarikaya-6man-next-hop-ra-01.txt
> has been successfully submitted by Behcet Sarikaya and posted to the
> IETF repository.
>
> Name:           draft-sarikaya-6man-next-hop-ra
> Revision:       01
> Title:          IPv6 RA Options for Next Hop Routes
> Document date:  2014-05-19
> Group:          Individual Submission
> Pages:          12
> URL:
> http://www.ietf.org/internet-drafts/draft-sarikaya-6man-next-hop-ra-01.txt
> Status:
> https://datatracker.ietf.org/doc/draft-sarikaya-6man-next-hop-ra/
> Htmlized:       http://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-01
> Diff:
> http://www.ietf.org/rfcdiff?url2=aft-sarikaya-6man-next-hop-ra-01
>
> On Sun, Feb 23, 2014 at 9:35 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com>  wrote:
>> On 15/02/2014 06:35, Dan Lüdtke wrote:
>>> Hi,
>>>
>>> I have very mixed feelings regarding this draft and I have not yet
>>> decided whether it is me or the draft :)
>> It's probably the fact that the community is very divided as to whether
>> this, or a DHCPv6 based solution, is the right one for delivering
>> routing information to hosts. Personally I see advantages in defining
>> enough in RA that a DHCPv6-free network is possible, but it only
>> makes sense if we insist that routing information capable of delivery
>> by RA and that capable of delivery by DHCPv6 have *exactly* the same
>> semantics (even if the syntax of the messages is different).
>> ...
>>
>>> I also have the feeling that consuming 7 numbers from the registry for
>>> new options is a bit too greedy. Do you see any way to reduce the
>>> consumption of this very limited resource? I think it would help
>>> supporting the draft a lot.
>> Since an address is the same thing as a /128 prefix, I would
>> think that the address TLVs could be replaced by prefixes,
>> which would save at least a couple of option numbers. If that
>> isn't enough, it would have to go to subtypes.
>>
>>      Brian
>>
>
I have read this draft. Generally I see the need to inform hosts with 
multiple interfaces about SADR routes.

Will the amount of information required in the worst case deployment fit 
in RA?
In a single frame?
If not, are we storing up more problems for the future than it solves 
(packet loss, re-ordering).

I also think the source address option in Section 9 should explicitly be 
defined as a prefix, given many people's requirement to support multiple 
IIDs per interface (for privacy etc.).

How would the metrics in this draft interact with RA prf and more 
specific routes (RFC 4191)?

AFAICS this scheme is only meant for multi-homed hosts.

I further question how to handle mobile devices with multiple interfaces 
that become routers.

Aren't we rapidly approaching the point where running a routing protocol 
(between the infra and a mobile device acting as a stub router) is 
appropriate?

regards,
RayH
-- 
Regards,
RayH


From nobody Thu May 22 14:10:44 2014
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 061971A028F for <ipv6@ietfa.amsl.com>; Thu, 22 May 2014 14:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UFd8g9ZbeoJ3 for <ipv6@ietfa.amsl.com>; Thu, 22 May 2014 14:10:41 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1B751A0283 for <6man@ietf.org>; Thu, 22 May 2014 14:10:41 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id i57so3523322yha.12 for <6man@ietf.org>; Thu, 22 May 2014 14:10:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=z/lnG8m9+RVU1ITh19ex6vPLu2viXRMpp6VP+FADtU0=; b=QOjKCisUCLp09sXW0Wu7EFmjpCM/8Fv5CeK/FkQM1F5fYlLEfrZLrE3tj06Fash7zH 4cubAETo37qe2vUX2krq2DPrlrF7721xmKe6//VkXf+JS/STCBURe0U3IH6cpia/dcsl m3BQsB9jrmrjORTwRn9V1U7SQeLJU010SNhKRLHynLWKmQXPydXiH8bTX+0+yUUH/+Xe XLgKAXGfLjje/NAdtcXRnLG+23nRqSZvr6UF9MdpVa5GM0t6PGv0K2bFXLfIkYuyXJKD QnoWPlR/jmoJgMvaWHoymHppLvG/fyhLz0HXHPqBurSIRhM1RaUw+Zqoy3E6Gdx5x+J9 1fSA==
MIME-Version: 1.0
X-Received: by 10.236.128.180 with SMTP id f40mr332884yhi.71.1400793039802; Thu, 22 May 2014 14:10:39 -0700 (PDT)
Received: by 10.170.126.18 with HTTP; Thu, 22 May 2014 14:10:39 -0700 (PDT)
In-Reply-To: <537C571F.7050709@globis.net>
References: <CAC8QAccFgwdVhoDYW7gHWi64cO8m0ZmbvoqDLAUyiYvsjLFP6g@mail.gmail.com> <537C571F.7050709@globis.net>
Date: Thu, 22 May 2014 16:10:39 -0500
Message-ID: <CAC8QAcd3i3gpD3bPOBaqZAwUm1MD4rbX4boBREDYDHJTkseSyA@mail.gmail.com>
Subject: Re: Re: New Version Notification for draft-sarikaya-6man-next-hop-ra-01.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ray Hunter <v6ops@globis.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/mgXCLvCDAnlhlhDU0QT5bWScjko
Cc: =?UTF-8?Q?Dan_L=C3=BCdtke?= <maildanrl@gmail.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 21:10:43 -0000

Hi Ray,

Thanks for your comments. Please find my replies inline below.

Regards,

Behcet

On Wed, May 21, 2014 at 2:34 AM, Ray Hunter <v6ops@globis.net> wrote:
> Behcet Sarikaya wrote:
>>
>> Hi Dan, Brian, all,
>>
>> I revised the draft based on your comments. The details are below.
>> Please check it and let me know your comments:
>>
>> A new version of I-D, draft-sarikaya-6man-next-hop-ra-01.txt
>> has been successfully submitted by Behcet Sarikaya and posted to the
>> IETF repository.
>>
>> Name:           draft-sarikaya-6man-next-hop-ra
>> Revision:       01
>> Title:          IPv6 RA Options for Next Hop Routes
>> Document date:  2014-05-19
>> Group:          Individual Submission
>> Pages:          12
>> URL:
>> http://www.ietf.org/internet-drafts/draft-sarikaya-6man-next-hop-ra-01.t=
xt
>> Status:
>> https://datatracker.ietf.org/doc/draft-sarikaya-6man-next-hop-ra/
>> Htmlized:
>> http://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-01
>> Diff:
>> http://www.ietf.org/rfcdiff?url2=3Daft-sarikaya-6man-next-hop-ra-01
>>
>>
>> On Sun, Feb 23, 2014 at 9:35 PM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com>  wrote:
>>>
>>> On 15/02/2014 06:35, Dan L=C3=BCdtke wrote:
>>>>
>>>> Hi,
>>>>
>>>> I have very mixed feelings regarding this draft and I have not yet
>>>> decided whether it is me or the draft :)
>>>
>>> It's probably the fact that the community is very divided as to whether
>>> this, or a DHCPv6 based solution, is the right one for delivering
>>> routing information to hosts. Personally I see advantages in defining
>>> enough in RA that a DHCPv6-free network is possible, but it only
>>> makes sense if we insist that routing information capable of delivery
>>> by RA and that capable of delivery by DHCPv6 have *exactly* the same
>>> semantics (even if the syntax of the messages is different).
>>> ...
>>>
>>>> I also have the feeling that consuming 7 numbers from the registry for
>>>> new options is a bit too greedy. Do you see any way to reduce the
>>>> consumption of this very limited resource? I think it would help
>>>> supporting the draft a lot.
>>>
>>> Since an address is the same thing as a /128 prefix, I would
>>> think that the address TLVs could be replaced by prefixes,
>>> which would save at least a couple of option numbers. If that
>>> isn't enough, it would have to go to subtypes.
>>>
>>>      Brian
>>>
>>
> I have read this draft. Generally I see the need to inform hosts with
> multiple interfaces about SADR routes.
>
> Will the amount of information required in the worst case deployment fit =
in
> RA?
> In a single frame?
> If not, are we storing up more problems for the future than it solves
> (packet loss, re-ordering).
>

The longest option is 56 octets. Why should it not fit in RA in a
single Ethernet frame?
Even if all the options in the draft are used in the same RA, it takes
240 octets which is totally unlikely.
So I think we are not storing up more problems for the future.

> I also think the source address option in Section 9 should explicitly be
> defined as a prefix, given many people's requirement to support multiple
> IIDs per interface (for privacy etc.).

Sure, then use the source prefix option in Section 10.

>
> How would the metrics in this draft interact with RA prf and more specifi=
c
> routes (RFC 4191)?

The metric field is very much like prf in RFC 4191 but it is 8 bits
long and a lot easier to process (see Dan's mail).

>
> AFAICS this scheme is only meant for multi-homed hosts.
>

Yes.

> I further question how to handle mobile devices with multiple interfaces
> that become routers.
>
> Aren't we rapidly approaching the point where running a routing protocol
> (between the infra and a mobile device acting as a stub router) is
> appropriate?

The draft addresses host configuration and router configuration is out of s=
cope.

>
> regards,
> RayH
> --
> Regards,
> RayH
>


From nobody Thu May 22 16:39:57 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A32871A024B for <ipv6@ietfa.amsl.com>; Thu, 22 May 2014 16:39:56 -0700 (PDT)
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=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9hfRfx3JrQNc for <ipv6@ietfa.amsl.com>; Thu, 22 May 2014 16:39:52 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E4491A0248 for <6man@ietf.org>; Thu, 22 May 2014 16:39:52 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rp16so3186725pbb.6 for <6man@ietf.org>; Thu, 22 May 2014 16:39:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=mBHBYMClM6nfZcO6DLoLorl6oh7lC3QlmczJ/g2t81o=; b=FwlqTUaT93U0iQyEv2oQUDiF7IyP2RBLTBh3qo/WB1F3F7kWYMJWIr0TmQirZFJxUg ww5arbTPzx8hcoHbgwAMbF7cDtockp1Mk8Eft5fV8lsAvswQBONaLGXLb2Uoz/ULR9Rc SfYp39EV1D67mHeN4WaG/NDo/gG98pbUq3UJX2h9KfnxddqZ6XiCjCmsNQ5j28JTL9yv DyJMGGXa+JG1zRRQC7KVqGuSAOom3QXuME9fGatGTCjqPLQx5I2jKlptCpvudLHPhrNC lUY6wM2LhScIkDjKPiUxf48j/9rBkYO8Xp49LBlCABFqrrqvR9bI+E4lfnVq82PqH7xp NqNA==
X-Received: by 10.66.249.7 with SMTP id yq7mr1236086pac.26.1400801990600; Thu, 22 May 2014 16:39:50 -0700 (PDT)
Received: from [192.168.178.23] (215.199.69.111.dynamic.snap.net.nz. [111.69.199.215]) by mx.google.com with ESMTPSA id ao4sm1430968pbc.51.2014.05.22.16.39.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 22 May 2014 16:39:50 -0700 (PDT)
Message-ID: <537E8ACE.9090702@gmail.com>
Date: Fri, 23 May 2014 11:39:58 +1200
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: sarikaya@ieee.org
Subject: Re: New Version Notification for draft-sarikaya-6man-next-hop-ra-01.txt
References: <CAC8QAccFgwdVhoDYW7gHWi64cO8m0ZmbvoqDLAUyiYvsjLFP6g@mail.gmail.com> <537C571F.7050709@globis.net> <CAC8QAcd3i3gpD3bPOBaqZAwUm1MD4rbX4boBREDYDHJTkseSyA@mail.gmail.com>
In-Reply-To: <CAC8QAcd3i3gpD3bPOBaqZAwUm1MD4rbX4boBREDYDHJTkseSyA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/huyLD1PYgzt1ZdrGEeFVNRmGlww
Cc: =?UTF-8?B?RGFuIEzDvGR0a2U=?= <maildanrl@gmail.com>, Ray Hunter <v6ops@globis.net>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 23:39:56 -0000

On 23/05/2014 09:10, Behcet Sarikaya wrote:
> Hi Ray,

<snip>

>>> On Sun, Feb 23, 2014 at 9:35 PM, Brian E Carpenter
>>> <brian.e.carpenter@gmail.com>  wrote:
>>>> On 15/02/2014 06:35, Dan L=C3=BCdtke wrote:
>>>>> Hi,
>>>>>
>>>>> I have very mixed feelings regarding this draft and I have not yet
>>>>> decided whether it is me or the draft :)
>>>> It's probably the fact that the community is very divided as to whet=
her
>>>> this, or a DHCPv6 based solution, is the right one for delivering
>>>> routing information to hosts. Personally I see advantages in definin=
g
>>>> enough in RA that a DHCPv6-free network is possible, but it only
>>>> makes sense if we insist that routing information capable of deliver=
y
>>>> by RA and that capable of delivery by DHCPv6 have *exactly* the same=

>>>> semantics (even if the syntax of the messages is different).
>>>> ...
>>>>
>>>>> I also have the feeling that consuming 7 numbers from the registry =
for
>>>>> new options is a bit too greedy. Do you see any way to reduce the
>>>>> consumption of this very limited resource? I think it would help
>>>>> supporting the draft a lot.
>>>> Since an address is the same thing as a /128 prefix, I would
>>>> think that the address TLVs could be replaced by prefixes,
>>>> which would save at least a couple of option numbers. If that
>>>> isn't enough, it would have to go to subtypes.
>>>>
>>>>      Brian
>>>>
>> I have read this draft. Generally I see the need to inform hosts with
>> multiple interfaces about SADR routes.
>>
>> Will the amount of information required in the worst case deployment f=
it in
>> RA?
>> In a single frame?
>> If not, are we storing up more problems for the future than it solves
>> (packet loss, re-ordering).
>>
>=20
> The longest option is 56 octets. Why should it not fit in RA in a
> single Ethernet frame?
> Even if all the options in the draft are used in the same RA, it takes
> 240 octets which is totally unlikely.
> So I think we are not storing up more problems for the future.

OK, assuming only one particular Next Hop is handled at a time.
Are you assuming that if N Next Hops are to be announced, they will
be in N separate messages? If not your worst case would be N*240 octets,
wouldn't it?

In the real world it seems unlikely that N will exceed 3 or 4, so it
would still fit in the IPv6 MTU. But all the same, maybe this needs
to be clarified.

>> I also think the source address option in Section 9 should explicitly =
be
>> defined as a prefix, given many people's requirement to support multip=
le
>> IIDs per interface (for privacy etc.).
>=20
> Sure, then use the source prefix option in Section 10.

But why not merge the two? Prefix length 128 signals a single
address, in any case.

>> How would the metrics in this draft interact with RA prf and more spec=
ific
>> routes (RFC 4191)?
>=20
> The metric field is very much like prf in RFC 4191 but it is 8 bits
> long and a lot easier to process (see Dan's mail).
>=20
>> AFAICS this scheme is only meant for multi-homed hosts.
>>
>=20
> Yes.

More precisely, for multi-addressed hosts. It would be applicable
in a number of scenarios, including RFC7157 (section 6.2) and MIF.

>=20
>> I further question how to handle mobile devices with multiple interfac=
es
>> that become routers.
>>
>> Aren't we rapidly approaching the point where running a routing protoc=
ol
>> (between the infra and a mobile device acting as a stub router) is
>> appropriate?
>=20
> The draft addresses host configuration and router configuration is out =
of scope.

Right, but this is a grey area. SADR information could very well be
distributed by a routing protocol, or any kind of configuration
protocol, as well as by DHCP or RA. That's why clarity on the semantics
of SADR is needed, so that all methods are functionally equivalent.

In Ray's scenario, if a host decides it wants to be a router, I think
that giving it SADR information is the least of our worries.

     Brian


From nobody Fri May 23 04:03:47 2014
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2EE71A00CD for <ipv6@ietfa.amsl.com>; Fri, 23 May 2014 04:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tv-5WtpELDCu for <ipv6@ietfa.amsl.com>; Fri, 23 May 2014 04:03:41 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id D310F1A0081 for <6man@ietf.org>; Fri, 23 May 2014 04:03:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 919EB87005F; Fri, 23 May 2014 13:03:38 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pvHqG6yw6zFH; Fri, 23 May 2014 13:03:38 +0200 (CEST)
Received: from Rays-iMac.local (unknown [IPv6:2001:470:1f15:73a:c58:3a43:1778:e6f5]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 471B3870044; Fri, 23 May 2014 13:03:38 +0200 (CEST)
Message-ID: <537F2AFE.7000309@globis.net>
Date: Fri, 23 May 2014 13:03:26 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Version Notification for draft-sarikaya-6man-next-hop-ra-01.txt
References: <CAC8QAccFgwdVhoDYW7gHWi64cO8m0ZmbvoqDLAUyiYvsjLFP6g@mail.gmail.com> <537C571F.7050709@globis.net> <CAC8QAcd3i3gpD3bPOBaqZAwUm1MD4rbX4boBREDYDHJTkseSyA@mail.gmail.com> <537E8ACE.9090702@gmail.com>
In-Reply-To: <537E8ACE.9090702@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/6wf-GmN1yh7DRNtqM6lq1Y0va3s
Cc: =?UTF-8?B?RGFuIEzDvGR0a2U=?= <maildanrl@gmail.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 11:03:44 -0000

> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
> 23 May 2014 01:39
> On 23/05/2014 09:10, Behcet Sarikaya wrote:
>> Hi Ray,
>
> <snip>
>
>>>> On Sun, Feb 23, 2014 at 9:35 PM, Brian E Carpenter
>>>> <brian.e.carpenter@gmail.com>   wrote:
>>>>> On 15/02/2014 06:35, Dan LÃ¼dtke wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I have very mixed feelings regarding this draft and I have not yet
>>>>>> decided whether it is me or the draft :)
>>>>> It's probably the fact that the community is very divided as to whether
>>>>> this, or a DHCPv6 based solution, is the right one for delivering
>>>>> routing information to hosts. Personally I see advantages in defining
>>>>> enough in RA that a DHCPv6-free network is possible, but it only
>>>>> makes sense if we insist that routing information capable of delivery
>>>>> by RA and that capable of delivery by DHCPv6 have *exactly* the same
>>>>> semantics (even if the syntax of the messages is different).
>>>>> ...
>>>>>
>>>>>> I also have the feeling that consuming 7 numbers from the registry for
>>>>>> new options is a bit too greedy. Do you see any way to reduce the
>>>>>> consumption of this very limited resource? I think it would help
>>>>>> supporting the draft a lot.
>>>>> Since an address is the same thing as a /128 prefix, I would
>>>>> think that the address TLVs could be replaced by prefixes,
>>>>> which would save at least a couple of option numbers. If that
>>>>> isn't enough, it would have to go to subtypes.
>>>>>
>>>>>       Brian
>>>>>
>>> I have read this draft. Generally I see the need to inform hosts with
>>> multiple interfaces about SADR routes.
>>>
>>> Will the amount of information required in the worst case deployment fit in
>>> RA?
>>> In a single frame?
>>> If not, are we storing up more problems for the future than it solves
>>> (packet loss, re-ordering).
>>>
>> The longest option is 56 octets. Why should it not fit in RA in a
>> single Ethernet frame?
>> Even if all the options in the draft are used in the same RA, it takes
>> 240 octets which is totally unlikely.
>> So I think we are not storing up more problems for the future.
>
> OK, assuming only one particular Next Hop is handled at a time.
> Are you assuming that if N Next Hops are to be announced, they will
> be in N separate messages? If not your worst case would be N*240 octets,
> wouldn't it?
Exactly.

Does the draft propose to build up the routing table piecemeal in 
consecutive RA messages one destination prefix at a time, or create a 
single (potentially huge) RA message containing the entire routing table 
sourced from this router?

If the message grows >> 1 frame, what's the chances of it being received 
and re-assembled in it's entirety?

How do you time out old prefix entries? How do you time out information 
learned from old neighbors?

These are all real-world problems that are solved in routing protocols.
> In the real world it seems unlikely that N will exceed 3 or 4, so it
> would still fit in the IPv6 MTU. But all the same, maybe this needs
> to be clarified.
IMHO I think any assumption on routing table size is premature. 
http://tools.ietf.org/html/draft-ietf-6man-why64 Section 3.2 states that 
some enterprises run flat IGP routing tables without route aggregation.
>>> I also think the source address option in Section 9 should explicitly be
>>> defined as a prefix, given many people's requirement to support multiple
>>> IIDs per interface (for privacy etc.).
>> Sure, then use the source prefix option in Section 10.
>
> But why not merge the two? Prefix length 128 signals a single
> address, in any case.
Exactly.
>>> How would the metrics in this draft interact with RA prf and more specific
>>> routes (RFC 4191)?
>> The metric field is very much like prf in RFC 4191 but it is 8 bits
>> long and a lot easier to process (see Dan's mail).
>>
>>> AFAICS this scheme is only meant for multi-homed hosts.
>>>
>> Yes.
>
> More precisely, for multi-addressed hosts. It would be applicable
> in a number of scenarios, including RFC7157 (section 6.2) and MIF.
Ack.
>>> I further question how to handle mobile devices with multiple interfaces
>>> that become routers.
>>>
>>> Aren't we rapidly approaching the point where running a routing protocol
>>> (between the infra and a mobile device acting as a stub router) is
>>> appropriate?
>> The draft addresses host configuration and router configuration is out of scope.

I have a 3G mobile phone (not yet IPv6). I have a cable TV operator that 
provides access to 500000 wifi hotspots "for free" (not yet IPv6).
I also want to use my phone as a wireless access point (tethering) 
whilst riding in the train.

These applications are all possible with IPv4 + NAT. But I do not see 
how this draft will make these use cases any more feasible with IPv6.
> Right, but this is a grey area. SADR information could very well be
> distributed by a routing protocol, or any kind of configuration
> protocol, as well as by DHCP or RA. That's why clarity on the semantics
> of SADR is needed, so that all methods are functionally equivalent.
Agreed. Otherwise we are very quickly going to get quagmired in issues 
like "administrative distance" between competing information for the 
same prefix, depending on how the SADR table is learned.
> In Ray's scenario, if a host decides it wants to be a router, I think
> that giving it SADR information is the least of our worries.
>
>       Brian
OK but the problem of distributing SADR routes to mobile devices acting 
as routers is still one that needs to be solved.
And it seems odd to me that a mobile device has to switch to a 
completely different mode just because tethering is enabled.


-- 
Regards,
RayH


From nobody Fri May 23 06:55:45 2014
Return-Path: <maildanrl@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 448431A0196 for <ipv6@ietfa.amsl.com>; Fri, 23 May 2014 06:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sxt5368G44J3 for <ipv6@ietfa.amsl.com>; Fri, 23 May 2014 06:49:44 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12D3F1A04A4 for <6man@ietf.org>; Fri, 23 May 2014 06:49:43 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id f8so874937wiw.2 for <6man@ietf.org>; Fri, 23 May 2014 06:49:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=cUlBmt+2k7h1FFYmBe/04ev7uoiR01g37Umt8Z9SVD4=; b=F55krO8/WLvHPC2K9kT10heE0W1IyX4qRIc8QVcT9nmqx9YKPFMfzc0U+/7KE4y3O3 Bl6+WUDvi56QxPtq1hgRTEXhpQr2Tad+9yyCo+WkqFswrghfJL46T56pYEl06t583fiO YoX5AmukYTUz8yTzPFHanVFmqwvQm39jhLmWyi+q3T1/xSv3rA0NR7bg/LA5LsNje1h0 HL3uaxh3530AtD/B7iyvOWeaYlzTx7PFjF3zk5NAu1KOhfQ4h2VoiOalC2w/v7j/tFxe xNq4yADLNKp4u6R5MIYDJsFJ8fOEzbVir9vem3z/1Hx7uZB6LInU50e3wmttxpuwT/fp jUeQ==
X-Received: by 10.180.126.8 with SMTP id mu8mr3544750wib.10.1400852981255; Fri, 23 May 2014 06:49:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.111.194 with HTTP; Fri, 23 May 2014 06:49:21 -0700 (PDT)
From: =?UTF-8?Q?Dan_L=C3=BCdtke?= <maildanrl@gmail.com>
Date: Fri, 23 May 2014 15:49:21 +0200
Message-ID: <CAAfuxnKWh+5GoD9VMqrAQxKu6Xd-WsCa1GsmpV6oH55gGF=imA@mail.gmail.com>
Subject: ratools for protocol hackers and protocl engineers
To: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com>, "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/WKhqVQcLDBvYSibJdOj38Dmx4-s
X-Mailman-Approved-At: Fri, 23 May 2014 06:55:40 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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 May 2014 13:49:47 -0000

Hi guys,

i think we need more (at least two) and better (at least trying to
stick to the RFCs) IPv6 software for the most important tasks in the
network. One example is the sending of RAs. I was not satisfied with
what was on the market and decided to write an alternative. Now
administrators have more choice. But I am also an IPv6 hacker, this is
why I added an "experimental option" to the software. This is for the
guys from ipv6-hackers, 6man, ipv6-ops and all those who love to use
super-exotic mega-special options in their RAs :)

Here is an example to to advertise a manually crafted link-MTU option
on interface "dummy0":

    # Router Advertisement `ra@dummy0'
    ra@dummy0 create
    ra@dummy0 set minimum-interval 0h0m3s
    ra@dummy0 set maximum-interval 0h0m10s
    ra@dummy0 enable

    # Experimental Option `exp0@dummy0':
    exp0@dummy0 create
    exp0@dummy0 set type 5
    exp0@dummy0 set payload 00000000ff00
    exp0@dummy0 enable

Result: http://bayimg.com/GaoGMAAFf

Now think of all the cool things we can craft to confuse nodes on the link!

Learn more about ratools:
- Repository: https://github.com/danrl/ratools
- Documentation: https://www.nonattached.net/ratools/index.html

Cheers

Dan

Protip: Make use of the new bash completion script!
--=20
Dan L=C3=BCdtke
http://www.danrl.de


From nobody Mon May 26 15:12:21 2014
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CB1E1A02B3 for <ipv6@ietfa.amsl.com>; Mon, 26 May 2014 15:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9zIbvIGhu92 for <ipv6@ietfa.amsl.com>; Mon, 26 May 2014 15:12:18 -0700 (PDT)
Received: from mail-yk0-x235.google.com (mail-yk0-x235.google.com [IPv6:2607:f8b0:4002:c07::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3E271A02A5 for <6man@ietf.org>; Mon, 26 May 2014 15:12:18 -0700 (PDT)
Received: by mail-yk0-f181.google.com with SMTP id 131so6508251ykp.12 for <6man@ietf.org>; Mon, 26 May 2014 15:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=lA/6WebyBJLZv1peesw/9mRJN3cS88L8Iw9wNR7EqFE=; b=mMRAN9Ev29aSHb/TpHc4y8qekGjxi/W5pOzTQVc+fbfNDdh4JMPGwgpcdN5tk5LE/D rXnnkl5ytOPXu2bTKirA2gJ2gJsLWLqN2WAscCr0SjBSeAaIVo86bTeUsxBcv41HOX1W cuWqcnuRxJUqqsmxBiVh4KSwGvEujjJ1PLwF8jHpYhcbykXKG0w2imSQ6vEk5vA+0Sn2 32D6epwM5LlqDosGpRj24dIF5bJITCe1uQKzBuPg3KFT0a69jfzAr3t/8c56m832Wa9x qKFH8FCJ0uBvfj4/BE1eS9Xaxe9Z+6zZceiowVmvUJSeeUFzMkSr4/R+lcqRCGRFt51G movg==
MIME-Version: 1.0
X-Received: by 10.236.129.43 with SMTP id g31mr39029025yhi.86.1401142335503; Mon, 26 May 2014 15:12:15 -0700 (PDT)
Received: by 10.170.126.18 with HTTP; Mon, 26 May 2014 15:12:15 -0700 (PDT)
In-Reply-To: <537F2AFE.7000309@globis.net>
References: <CAC8QAccFgwdVhoDYW7gHWi64cO8m0ZmbvoqDLAUyiYvsjLFP6g@mail.gmail.com> <537C571F.7050709@globis.net> <CAC8QAcd3i3gpD3bPOBaqZAwUm1MD4rbX4boBREDYDHJTkseSyA@mail.gmail.com> <537E8ACE.9090702@gmail.com> <537F2AFE.7000309@globis.net>
Date: Mon, 26 May 2014 17:12:15 -0500
Message-ID: <CAC8QAceaPX8G6oXTU8UgJd+UAXqNhRkWwuZhoHaxgT7jPgAvpA@mail.gmail.com>
Subject: Re: New Version Notification for draft-sarikaya-6man-next-hop-ra-01.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ray Hunter <v6ops@globis.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/lJK_qahkcf4jv9wPVAXcXMDKS90
Cc: =?UTF-8?Q?Dan_L=C3=BCdtke?= <maildanrl@gmail.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 May 2014 22:12:20 -0000

On Fri, May 23, 2014 at 6:03 AM, Ray Hunter <v6ops@globis.net> wrote:
>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>> 23 May 2014 01:39
>>
>> On 23/05/2014 09:10, Behcet Sarikaya wrote:
>>>
>>> Hi Ray,
>>
>>
>> <snip>
>>
>>>>> On Sun, Feb 23, 2014 at 9:35 PM, Brian E Carpenter
>>>>> <brian.e.carpenter@gmail.com>   wrote:
>>>>>>
>>>>>> On 15/02/2014 06:35, Dan L=C3=BCdtke wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have very mixed feelings regarding this draft and I have not yet
>>>>>>> decided whether it is me or the draft :)
>>>>>>
>>>>>> It's probably the fact that the community is very divided as to
>>>>>> whether
>>>>>> this, or a DHCPv6 based solution, is the right one for delivering
>>>>>> routing information to hosts. Personally I see advantages in definin=
g
>>>>>> enough in RA that a DHCPv6-free network is possible, but it only
>>>>>> makes sense if we insist that routing information capable of deliver=
y
>>>>>> by RA and that capable of delivery by DHCPv6 have *exactly* the same
>>>>>> semantics (even if the syntax of the messages is different).
>>>>>> ...
>>>>>>
>>>>>>> I also have the feeling that consuming 7 numbers from the registry
>>>>>>> for
>>>>>>> new options is a bit too greedy. Do you see any way to reduce the
>>>>>>> consumption of this very limited resource? I think it would help
>>>>>>> supporting the draft a lot.
>>>>>>
>>>>>> Since an address is the same thing as a /128 prefix, I would
>>>>>> think that the address TLVs could be replaced by prefixes,
>>>>>> which would save at least a couple of option numbers. If that
>>>>>> isn't enough, it would have to go to subtypes.
>>>>>>
>>>>>>       Brian
>>>>>>
>>>> I have read this draft. Generally I see the need to inform hosts with
>>>> multiple interfaces about SADR routes.
>>>>
>>>> Will the amount of information required in the worst case deployment f=
it
>>>> in
>>>> RA?
>>>> In a single frame?
>>>> If not, are we storing up more problems for the future than it solves
>>>> (packet loss, re-ordering).
>>>>
>>> The longest option is 56 octets. Why should it not fit in RA in a
>>> single Ethernet frame?
>>> Even if all the options in the draft are used in the same RA, it takes
>>> 240 octets which is totally unlikely.
>>> So I think we are not storing up more problems for the future.
>>
>>
>> OK, assuming only one particular Next Hop is handled at a time.
>> Are you assuming that if N Next Hops are to be announced, they will
>> be in N separate messages? If not your worst case would be N*240 octets,
>> wouldn't it?
>
> Exactly.
>
> Does the draft propose to build up the routing table piecemeal in
> consecutive RA messages one destination prefix at a time, or create a sin=
gle
> (potentially huge) RA message containing the entire routing table sourced
> from this router?
>
> If the message grows >> 1 frame, what's the chances of it being received =
and
> re-assembled in it's entirety?

[behcet] I will add some text in the next revision on RA size issue
considering the above comments  with the following understanding,
please check:

I think that if it fits in one frame the router should create a single
RA message. If it does not then configuring in consecutive RA messages
should be considered, avoiding any re-assembly issues.


>
> How do you time out old prefix entries? How do you time out information
> learned from old neighbors?
>
> These are all real-world problems that are solved in routing protocols.
>
>> In the real world it seems unlikely that N will exceed 3 or 4, so it
>> would still fit in the IPv6 MTU. But all the same, maybe this needs
>> to be clarified.
>
> IMHO I think any assumption on routing table size is premature.
> http://tools.ietf.org/html/draft-ietf-6man-why64 Section 3.2 states that
> some enterprises run flat IGP routing tables without route aggregation.
>
>>>> I also think the source address option in Section 9 should explicitly =
be
>>>> defined as a prefix, given many people's requirement to support multip=
le
>>>> IIDs per interface (for privacy etc.).
>>>
>>> Sure, then use the source prefix option in Section 10.
>>
>>
>> But why not merge the two? Prefix length 128 signals a single
>> address, in any case.
>
> Exactly.

[behcet] Yes, will do it in the next rev.
>
>>>> How would the metrics in this draft interact with RA prf and more
>>>> specific
>>>> routes (RFC 4191)?
>>>
>>> The metric field is very much like prf in RFC 4191 but it is 8 bits
>>> long and a lot easier to process (see Dan's mail).
>>>
>>>> AFAICS this scheme is only meant for multi-homed hosts.
>>>>
>>> Yes.
>>
>>
>> More precisely, for multi-addressed hosts. It would be applicable
>> in a number of scenarios, including RFC7157 (section 6.2) and MIF.
>
> Ack.
>
>>>> I further question how to handle mobile devices with multiple interfac=
es
>>>> that become routers.
>>>>
>>>> Aren't we rapidly approaching the point where running a routing protoc=
ol
>>>> (between the infra and a mobile device acting as a stub router) is
>>>> appropriate?
>>>
>>> The draft addresses host configuration and router configuration is out =
of
>>> scope.
>
>
> I have a 3G mobile phone (not yet IPv6). I have a cable TV operator that
> provides access to 500000 wifi hotspots "for free" (not yet IPv6).
> I also want to use my phone as a wireless access point (tethering) whilst
> riding in the train.
>
> These applications are all possible with IPv4 + NAT. But I do not see how
> this draft will make these use cases any more feasible with IPv6.
>
>> Right, but this is a grey area. SADR information could very well be
>> distributed by a routing protocol, or any kind of configuration
>> protocol, as well as by DHCP or RA. That's why clarity on the semantics
>> of SADR is needed, so that all methods are functionally equivalent.
>
> Agreed. Otherwise we are very quickly going to get quagmired in issues li=
ke
> "administrative distance" between competing information for the same pref=
ix,
> depending on how the SADR table is learned.
>
>> In Ray's scenario, if a host decides it wants to be a router, I think
>> that giving it SADR information is the least of our worries.
>>
>>       Brian
>
> OK but the problem of distributing SADR routes to mobile devices acting a=
s
> routers is still one that needs to be solved.

[behcet] As RFC 7157 says, RAs as in this draft can be used.
Also routing protocols like RIPng, OSPFv3 can be used.


> And it seems odd to me that a mobile device has to switch to a completely
> different mode just because tethering is enabled.
>

[behcet] I don't understand this. Please clarify.

>
> --
> Regards,
> RayH
>


From nobody Wed May 28 02:25:09 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D1EB1A0041; Wed, 28 May 2014 02:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmwp1R_kOdQh; Wed, 28 May 2014 02:25:06 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 179251A0404; Wed, 28 May 2014 02:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12616; q=dns/txt; s=iport; t=1401269103; x=1402478703; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=CPYXYtVypE6OPef6vEzcVjd37d8GXfyW695hqo+Q7I0=; b=eXPNKzAxpR3IU2LgTUcJCYYKyuQRlf3lvJwpdXGBhcfdERISEXsc8QE0 tZtvQ1SJD+LgUrNjNevICGjRHFTmufIeJUKLAVGc/vl+0tWuR7li6IAmc Zm5/86RpHonx0Fs4hedJP2LPOq1YK+WK4P+PPHOPETtnxzCCyLm67j7CG k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkMFAMeqhVOtJA2B/2dsb2JhbABZgkJFUliCa783ARlyFnSCJQEBAQQjCkwQAgEIEQQBAQsdAwICAjAUCQgCBAENBQiIJgMRsSGedA2FUReMPIE+JxYbBgGCdTaBFQStHIM4gW1C
X-IronPort-AV: E=Sophos; i="4.98,927,1392163200"; d="scan'208,217"; a="47853936"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-6.cisco.com with ESMTP; 28 May 2014 09:25:02 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s4S9P2f1031102 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 28 May 2014 09:25:02 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.203]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Wed, 28 May 2014 04:25:02 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Ines Robles (mariainesrobles@googlemail.com)" <mariainesrobles@googlemail.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: RE: [Roll] IETF 90 - Toronto - Draft to be presented - Slides in advance
Thread-Topic: [Roll] IETF 90 - Toronto - Draft to be presented - Slides in advance
Thread-Index: AQHPeRJAt/Qti64KoEKQcPJnQsVf+ZtVunLA
Date: Wed, 28 May 2014 09:25:01 +0000
Deferred-Delivery: Wed, 28 May 2014 09:25:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD8426B8502@xmb-rcd-x01.cisco.com>
References: <CAP+sJUcrzr5gBoK3vDg7c3JcwrfW88rSQYfhimLyFgwLStxo6g@mail.gmail.com> <CAP+sJUcjPE=YbmNV=EJBR=dfsqvFjh_tZ6+JBCZu2WuTSAB7+Q@mail.gmail.com>
In-Reply-To: <CAP+sJUcjPE=YbmNV=EJBR=dfsqvFjh_tZ6+JBCZu2WuTSAB7+Q@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.52]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD8426B8502xmbrcdx01ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/vCpua7GXFpwuukkmOpcYbrhFaHA
Cc: roll <roll@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2014 09:25:07 -0000

--_000_E045AECD98228444A58C61C200AE1BD8426B8502xmbrcdx01ciscoc_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSW5lcyAoYW5kIE1pY2hhZWwpOg0KDQpJ4oCZZCB3aXNoIHRvIGhhdmUgYSBzbG90IHRvIGRp
c2N1c3MgdGhlIGZsb3cgbGFiZWwgZHJhZnQgdGhhdCBpcyBjdXJyZW50bHkgd29ya2VkIG9uIGF0
IDZNQU4uDQpTaW5jZSA2TUFOIGRvZXMgbm90IG1lZXQgaW4gVG9yb250bywgaXQgbWFrZXMgc2Vu
c2UgdG8gZGlzY3VzcyBhdCBST0xMIGFib3V0IHRoZSBwcm9zcGVjdHMgZm9yIHRoaXMgd29yay4N
CldpbGwgdW5pY2FzdCB0aGUgc2xpZGVzIHNlcGFyYXRlbHkuDQoNCkNoZWVycywNCg0KUGFzY2Fs
DQoNCkZyb206IFJvbGwgW21haWx0bzpyb2xsLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBP
ZiBJbmVzIFJvYmxlcw0KU2VudDogbHVuZGkgMjYgbWFpIDIwMTQgMjA6NDINClRvOiByb2xsDQpD
YzogTWljaGFlbCBSaWNoYXJkc29uDQpTdWJqZWN0OiBSZTogW1JvbGxdIElFVEYgOTAgLSBUb3Jv
bnRvIC0gRHJhZnQgdG8gYmUgcHJlc2VudGVkIC0gU2xpZGVzIGluIGFkdmFuY2UNCg0KSGVsbG8s
DQoNClRoaXMgaXMgYSBraW5kbHkgcmVtaW5kZXIsDQoNCkR1ZSB0byB0aGUgbGltaXRlZCBkdXJh
dGlvbiBvZiB0aGUgbWVldGluZyAoMSBob3VyIG1vcmUgb3IgbGVzcyksIHdlIHJlcXVpcmUgcGxl
YXNlIHRoZSBzbGlkZXMgaW4gYWR2YW5jZSwgdG8gZGVjaWRlIGlmIHRoZSBkcmFmdHMgd2lsbCBi
ZSBwcmVzZW50ZWQgb3Igbm90LiBQbGVhc2UsIHdlIHJlcXVpcmUgdGhlIHNsaWRlcyBiZWZvcmUg
MDYvMDYvMjAxNC4NCg0KVGhhbmtzIGFuZCBSZWdhcmRzLA0KDQpNaWNoYWVsICYgSW5lcy4NCg0K
MjAxNC0wNS0wOCAxNjoyOCBHTVQrMDM6MDAgSW5lcyBSb2JsZXMgPG1hcmlhaW5lc3JvYmxlc0Bn
b29nbGVtYWlsLmNvbTxtYWlsdG86bWFyaWFpbmVzcm9ibGVzQGdvb2dsZW1haWwuY29tPj46DQoN
Cg0KSGVsbG8sDQoNCg0KV2Ugd291bGQgbGlrZSB0byBrbm93IHBsZWFzZSwgd2hpY2ggZHJhZnRz
IGRlc2lyZSBiZSBwcmVzZW50ZWQgaW4gdGhlIE5leHQgTWVldGluZzogSUVURiA5MCwgSnVseSAy
MC0yNSwgMjAxNA0KDQoNCkR1ZSB0byB0aGUgbGltaXRlZCBkdXJhdGlvbiBvZiB0aGUgbWVldGlu
ZyAoMSBob3VyIG1vcmUgb3IgbGVzcyksIHdlIHJlcXVpcmUgcGxlYXNlIHRoZSBzbGlkZXMgaW4g
YWR2YW5jZSwgdG8gZGVjaWRlIGlmIHRoZSBkcmFmdHMgd2lsbCBiZSBwcmVzZW50ZWQgb3Igbm90
LiBQbGVhc2UsIHdlIHJlcXVpcmUgdGhlIHNsaWRlcyBiZWZvcmUgMDYvMDYvMjAxNC4NCg0KDQpB
ZnRlciB0aGUgZGVjaXNpb24gKGJhc2VkIG9uIHRoZSBzbGlkZXMgb2J0YWluZWQpLCB3ZSB3aWxs
IGxldCB5b3Uga25vdyBhYm91dCB3aGljaCAgZHJhZnRzIHdpbGwgYmUgaW5jbHVkZWQgaW4gdGhl
IG1lZXRpbmcuDQoNCg0KVGhhbmsgeW91IHZlcnkgbXVjaCBpbiBhZHZhbmNlLA0KDQpNaWNoYWVs
ICYgSW5lcy4NCg0K

--_000_E045AECD98228444A58C61C200AE1BD8426B8502xmbrcdx01ciscoc_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowY207DQoJZm9udC1zaXplOjEy
LjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uRW1h
aWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBw
dDsNCgltYXJnaW46NzAuODVwdCA3MC44NXB0IDcwLjg1cHQgNzAuODVwdDt9DQpkaXYuV29yZFNl
Y3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAv
Pg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxh
eW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwv
bzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVO
LVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9u
MSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+SGkgSW5lcyAoYW5kIE1pY2hhZWwpOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SeKAmWQgd2lzaCB0
byBoYXZlIGEgc2xvdCB0byBkaXNjdXNzIHRoZSBmbG93IGxhYmVsIGRyYWZ0IHRoYXQgaXMgY3Vy
cmVudGx5IHdvcmtlZCBvbiBhdCA2TUFOLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5T
aW5jZSA2TUFOIGRvZXMgbm90IG1lZXQgaW4gVG9yb250bywgaXQgbWFrZXMgc2Vuc2UgdG8gZGlz
Y3VzcyBhdCBST0xMIGFib3V0IHRoZSBwcm9zcGVjdHMgZm9yIHRoaXMgd29yay48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+V2lsbCB1bmljYXN0IHRoZSBzbGlkZXMgc2VwYXJhdGVseS48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRlIiIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj5DaGVlcnMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRlIiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJGUiIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PlBhc2NhbDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBj
bSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBSb2xs
IFttYWlsdG86cm9sbC1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5JbmVz
IFJvYmxlczxicj4NCjxiPlNlbnQ6PC9iPiBsdW5kaSAyNiBtYWkgMjAxNCAyMDo0Mjxicj4NCjxi
PlRvOjwvYj4gcm9sbDxicj4NCjxiPkNjOjwvYj4gTWljaGFlbCBSaWNoYXJkc29uPGJyPg0KPGI+
U3ViamVjdDo8L2I+IFJlOiBbUm9sbF0gSUVURiA5MCAtIFRvcm9udG8gLSBEcmFmdCB0byBiZSBw
cmVzZW50ZWQgLSBTbGlkZXMgaW4gYWR2YW5jZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IZWxsbyw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoaXMgaXMgYSBraW5kbHkgcmVtaW5kZXIsPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPkR1ZSB0byB0aGUgbGltaXRlZCBkdXJhdGlvbiBvZiB0aGUgbWVldGlu
ZyAoMSBob3VyIG1vcmUgb3IgbGVzcyksIHdlIHJlcXVpcmUgcGxlYXNlIHRoZSBzbGlkZXMgaW4g
YWR2YW5jZSwgdG8gZGVjaWRlIGlmIHRoZSBkcmFmdHMgd2lsbCBiZSBwcmVzZW50ZWQgb3Igbm90
LiBQbGVhc2UsIHdlIHJlcXVpcmUNCiB0aGUgc2xpZGVzIGJlZm9yZSAwNi8wNi8yMDE0Ljwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
VGhhbmtzIGFuZCBSZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5NaWNoYWVsICZhbXA7IEluZXMuPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90
dG9tOjEyLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+MjAxNC0wNS0wOCAxNjoyOCBHTVQmIzQzOzAzOjAwIEluZXMgUm9ibGVzICZsdDs8YSBo
cmVmPSJtYWlsdG86bWFyaWFpbmVzcm9ibGVzQGdvb2dsZW1haWwuY29tIiB0YXJnZXQ9Il9ibGFu
ayI+bWFyaWFpbmVzcm9ibGVzQGdvb2dsZW1haWwuY29tPC9hPiZndDs6PG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjBjbTttYXJnaW4tcmlnaHQ6MS4wcHQ7bWFyZ2luLWJv
dHRvbTowY207bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdCI+DQo8c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5IZWxsbyw8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6MGNtO21hcmdpbi1yaWdodDoxLjBwdDttYXJnaW4tYm90dG9tOjBjbTttYXJnaW4t
bGVmdDowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0Ij4NCjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPldlIHdvdWxkIGxpa2UgdG8ga25vdyBwbGVhc2UsIHdoaWNoIGRyYWZ0cyBkZXNpcmUgYmUg
cHJlc2VudGVkIGluIHRoZSBOZXh0IE1lZXRpbmc6DQo8c3BhbiBzdHlsZT0iYmFja2dyb3VuZDoj
RkZGRkNDIj5JRVRGIDkwLCBKdWx5IDIwLTI1LCAyMDE0PC9zcGFuPjwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDowY207bWFyZ2luLXJpZ2h0OjEuMHB0O21hcmdpbi1ib3R0
b206MGNtO21hcmdpbi1sZWZ0OjBjbTttYXJnaW4tYm90dG9tOi4wMDAxcHQiPg0KPHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90OyI+RHVlIHRvIHRoZSBsaW1pdGVkIGR1cmF0aW9uIG9mIHRoZSBtZWV0
aW5nICgxIGhvdXIgbW9yZSBvciBsZXNzKSwgd2UgcmVxdWlyZSBwbGVhc2UgdGhlIHNsaWRlcyBp
biBhZHZhbmNlLCB0byBkZWNpZGUgaWYgdGhlIGRyYWZ0cyB3aWxsIGJlIHByZXNlbnRlZCBvciBu
b3QuIFBsZWFzZSwgd2UgcmVxdWlyZSB0aGUgc2xpZGVzIGJlZm9yZQ0KIDA2LzA2LzIwMTQuPC9z
cGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8cCBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjBjbTttYXJnaW4tcmlnaHQ6MS4w
cHQ7bWFyZ2luLWJvdHRvbTowY207bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi1ib3R0b206LjAwMDFw
dCI+DQo8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5BZnRlciB0aGUgZGVjaXNpb24gKGJhc2Vk
IG9uIHRoZSBzbGlkZXMgb2J0YWluZWQpLCB3ZSB3aWxsIGxldCB5b3Uga25vdyBhYm91dCB3aGlj
aCAmbmJzcDtkcmFmdHMgd2lsbCBiZSBpbmNsdWRlZCBpbiB0aGUgbWVldGluZy48L3NwYW4+PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6MGNtO21hcmdpbi1yaWdodDoxLjBwdDttYXJn
aW4tYm90dG9tOjBjbTttYXJnaW4tbGVmdDowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0Ij4NCjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPlRoYW5rIHlvdSB2ZXJ5IG11Y2ggaW4gYWR2YW5jZSw8
L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQo8c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5NaWNoYWVsICZhbXA7IEluZXMuPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_E045AECD98228444A58C61C200AE1BD8426B8502xmbrcdx01ciscoc_--


From nobody Wed May 28 02:42:22 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 070E11A089E; Wed, 28 May 2014 02:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EayIL4MYQgGz; Wed, 28 May 2014 02:42:19 -0700 (PDT)
Received: from mail-vc0-x233.google.com (mail-vc0-x233.google.com [IPv6:2607:f8b0:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 898461A089A; Wed, 28 May 2014 02:42:18 -0700 (PDT)
Received: by mail-vc0-f179.google.com with SMTP id im17so12143146vcb.10 for <multiple recipients>; Wed, 28 May 2014 02:42:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ied8SooHXAvxaQyh9syHAhyQuk/VRhbc+Krexjma8gY=; b=jgigIhx7VZaXlTNpT/EQgrkBfhmoe9PD6TnQHiRpA3qMyLhMcLg/pWk0k1mBelhUc8 eaKUxgHTe5EPPZiXfj39RuCer4s6A5wrAlyyr7w02uqyiNYiQB5HqJtCPLv2+MwvMXni 2QuwFmw3LCdzhpbS88GbgtrFKqmxsueNypnw35cyxnsli8nXGpzzFVuEMyltilcEPrhf yYlkL3GfV8FwUISI3gYNGraUS5A33y3JaY5/7tiF7/dXVrK71E810gf7qrBzDbeBm2NU bpHcXFr0JtzizK9b6471psNoh2r1tnFKBs8lJhFmuIjcT3BQK0m/AxGAhMyiDJt031LX jnIg==
MIME-Version: 1.0
X-Received: by 10.58.196.231 with SMTP id ip7mr543703vec.47.1401270134496; Wed, 28 May 2014 02:42:14 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Wed, 28 May 2014 02:42:14 -0700 (PDT)
In-Reply-To: <E045AECD98228444A58C61C200AE1BD8426B8502@xmb-rcd-x01.cisco.com>
References: <CAP+sJUcrzr5gBoK3vDg7c3JcwrfW88rSQYfhimLyFgwLStxo6g@mail.gmail.com> <CAP+sJUcjPE=YbmNV=EJBR=dfsqvFjh_tZ6+JBCZu2WuTSAB7+Q@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD8426B8502@xmb-rcd-x01.cisco.com>
Date: Wed, 28 May 2014 12:42:14 +0300
Message-ID: <CAP+sJUejX9o=bCd1cUZSWWFQ7EFF4tvULH3odyW0wTJeeYESSA@mail.gmail.com>
Subject: Re: [Roll] IETF 90 - Toronto - Draft to be presented - Slides in advance
From: Ines  Robles <mariainesrobles@googlemail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b6dc7a499e3dc04fa72a03a
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/8PrE4WlxiS19-kCsDkdED1zkrIo
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, roll <roll@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2014 09:42:20 -0000

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

Hi Pascal,

Ok, Thank you very much.

Best Regards,


2014-05-28 12:25 GMT+03:00 Pascal Thubert (pthubert) <pthubert@cisco.com>:

>  Hi Ines (and Michael):
>
>
>
> I=E2=80=99d wish to have a slot to discuss the flow label draft that is c=
urrently
> worked on at 6MAN.
>
> Since 6MAN does not meet in Toronto, it makes sense to discuss at ROLL
> about the prospects for this work.
>
> Will unicast the slides separately.
>
>
>
> Cheers,
>
>
>
> Pascal
>
>
>
> *From:* Roll [mailto:roll-bounces@ietf.org] *On Behalf Of *Ines Robles
> *Sent:* lundi 26 mai 2014 20:42
> *To:* roll
> *Cc:* Michael Richardson
> *Subject:* Re: [Roll] IETF 90 - Toronto - Draft to be presented - Slides
> in advance
>
>
>
> Hello,
>
>
>
> This is a kindly reminder,
>
>
>
> Due to the limited duration of the meeting (1 hour more or less), we
> require please the slides in advance, to decide if the drafts will be
> presented or not. Please, we require the slides before 06/06/2014.
>
>
>
> Thanks and Regards,
>
>
>
> Michael & Ines.
>
>
>
> 2014-05-08 16:28 GMT+03:00 Ines Robles <mariainesrobles@googlemail.com>:
>
>
>
> Hello,
>
>
>
> We would like to know please, which drafts desire be presented in the Nex=
t
> Meeting: IETF 90, July 20-25, 2014
>
>
>
> Due to the limited duration of the meeting (1 hour more or less), we
> require please the slides in advance, to decide if the drafts will be
> presented or not. Please, we require the slides before 06/06/2014.
>
>
>
> After the decision (based on the slides obtained), we will let you know
> about which  drafts will be included in the meeting.
>
>
>
> Thank you very much in advance,
>
>
> Michael & Ines.
>
>
>

--047d7b6dc7a499e3dc04fa72a03a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Pascal,<div><br></div><div>Ok, Thank you very much.</di=
v><div><br></div><div>Best Regards,</div><div class=3D"gmail_extra"><br><br=
><div class=3D"gmail_quote">2014-05-28 12:25 GMT+03:00 Pascal Thubert (pthu=
bert) <span dir=3D"ltr">&lt;<a href=3D"mailto:pthubert@cisco.com" target=3D=
"_blank">pthubert@cisco.com</a>&gt;</span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Ines (and Michael):<u>=
</u><u></u></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"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I=E2=80=99d wish to have =
a slot to discuss the flow label draft that is currently worked on at 6MAN.=
<u></u><u></u></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">Since 6MAN does not meet =
in Toronto, it makes sense to discuss at ROLL about the prospects for this =
work.<u></u><u></u></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">Will unicast the slides s=
eparately.<u></u><u></u></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"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Cheers,<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Pascal<u></u>=
<u></u></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"><u></u>=C2=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<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;"> Roll [ma=
ilto:<a href=3D"mailto:roll-bounces@ietf.org" target=3D"_blank">roll-bounce=
s@ietf.org</a>]
<b>On Behalf Of </b>Ines Robles<br>
<b>Sent:</b> lundi 26 mai 2014 20:42<br>
<b>To:</b> roll<br>
<b>Cc:</b> Michael Richardson<br>
<b>Subject:</b> Re: [Roll] IETF 90 - Toronto - Draft to be presented - Slid=
es in advance<u></u><u></u></span></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Hello,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This is a kindly reminder,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Due to the limited duration of the meetin=
g (1 hour more or less), we require please the slides in advance, to decide=
 if the drafts will be presented or not. Please, we require
 the slides before 06/06/2014.</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks and Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Michael &amp; Ines.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=C2=A0<u></u><=
/p>
<div>
<p class=3D"MsoNormal">2014-05-08 16:28 GMT+03:00 Ines Robles &lt;<a href=
=3D"mailto:mariainesrobles@googlemail.com" target=3D"_blank">mariainesroble=
s@googlemail.com</a>&gt;:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p style=3D"margin-right:1.0pt;margin-bottom:0cm;margin-left:0cm;margin-bot=
tom:.0001pt">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">Hello,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p style=3D"margin-right:1.0pt;margin-bottom:0cm;margin-left:0cm;margin-bot=
tom:.0001pt">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">We would like to know please, which drafts desire be presented i=
n the Next Meeting:
<span style=3D"background:#ffffcc">IETF 90, July 20-25, 2014</span></span><=
u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p style=3D"margin-right:1.0pt;margin-bottom:0cm;margin-left:0cm;margin-bot=
tom:.0001pt">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">Due to the limited duration of the meeting (1 hour more or less)=
, we require please the slides in advance, to decide if the drafts will be =
presented or not. Please, we require the slides before
 06/06/2014.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p style=3D"margin-right:1.0pt;margin-bottom:0cm;margin-left:0cm;margin-bot=
tom:.0001pt">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">After the decision (based on the slides obtained), we will let y=
ou know about which =C2=A0drafts will be included in the meeting.</span><u>=
</u><u></u></p>

<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p style=3D"margin-right:1.0pt;margin-bottom:0cm;margin-left:0cm;margin-bot=
tom:.0001pt">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">Thank you very much in advance,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><br>
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;">Michael &amp; Ines.</span><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div></div>

--047d7b6dc7a499e3dc04fa72a03a--

