Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE)' to Proposed Standard
Eric Rosen <erosen@cisco.com> Tue, 05 September 2006 16:55 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GKeCy-0003Gq-7u; Tue, 05 Sep 2006 12:55:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GKeCx-0003GQ-87 for idr@ietf.org; Tue, 05 Sep 2006 12:55:31 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKeCw-0004s3-19 for idr@ietf.org; Tue, 05 Sep 2006 12:55:31 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 05 Sep 2006 09:55:30 -0700
X-IronPort-AV: i="4.08,215,1154934000"; d="scan'208"; a="39954647:sNHT29057736"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k85GtTKW015471; Tue, 5 Sep 2006 12:55:29 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k85GtTdM016255; Tue, 5 Sep 2006 12:55:29 -0400 (EDT)
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE)' to Proposed Standard
In-reply-to: Your message of Fri, 25 Aug 2006 11:28:15 -0700. <200608251828.k7PISFg11936@merlot.juniper.net>
Date: Tue, 05 Sep 2006 12:55:29 -0400
Message-ID: <1400.1157475329@cisco.com>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: a=rsa-sha1; q=dns; l=1167; t=1157475329; x=1158339329; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=erosen@cisco.com; z=From:Eric=20Rosen=20<erosen@cisco.com> |Subject:Re=3A=20[Idr]=20Re=3A=20Last=20Call=3A=20'Connecting=20IPv6=20Islands=20 over=20IPv4=20MPLS=20using=20IPv6=20Provider=20Edge=20Routers=20(6PE)'=20to =20Proposed=20Standard=20 |To:Yakov=20Rekhter=20<yakov@juniper.net>; X=v=3Dcisco.com=3B=20h=3DC5SRiRVsnFvoGajblrEtu5sRvBk=3D; b=iG1h/lcWcLTpiG7GAqTJ1/v5CEPiI+YEt0cFPUhebRTSUaPADpJZ9pdNX9PIFq4p4givf2zP S2A1Mp8zoL8whqdRJLPbBzJK21D21DEZVUa+K5mUv6Fk9Rq/oiqqhZ2I;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=erosen@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Errors-To: idr-bounces@ietf.org
Yakov> the current/original encoding already provides a way to distinguish Yakov> between IPv4 and IPv6 addresses ... the NH Length field is used to Yakov> distinguish between IPv4 and IPv6 as the NH. Gee, I thought that the use of TLV encoding was a fairly well-accepted technique in protocol design. Is there some added value to be gained from not including a type field? I guess someone might consider "lack of extensibility" to be an added value ;-) On the other hand, one could one say that omitting the type field does not restrict extensibility, because if one has a new type to send one can always make sure it has a hitherto unused length, even if this requires adding padding. The only problem would be that whoever has to write that spec would probably die from embarrassment. Yakov> the current/original encoding provides yet another way to distingush Yakov> between IPv4 and IPv6 as the NH addresses - use two different SAFIs Oh good, more SAFIs. Well, what's simpler, adding more SAFIs or using a type field? ;-) Even using the length would be better than adding more SAFIs. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] Last Call: 'Connecting IPv6 Islands over IP… The IESG
- [Idr] Re: Last Call: 'Connecting IPv6 Islands ove… Bill Fenner
- [Idr] Re: Last Call: 'Connecting IPv6 Islands ove… Bill Fenner
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Yakov Rekhter
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… David Ward
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… David Ward
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Yakov Rekhter
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… David Ward
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Yakov Rekhter
- Re: [Softwires] Re: [Idr] Re: Last Call: 'Connect… Pekka Savola
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… David Ward
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Yakov Rekhter
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… David Ward
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Eric Rosen
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Francois Le Faucheur
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… David Ward
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Francois Le Faucheur
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Robert Raszuk
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Francois Le Faucheur
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Robert Raszuk
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Francois Le Faucheur
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Robert Raszuk
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Francois Le Faucheur
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… David Ward
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Francois Le Faucheur
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Yakov Rekhter
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Yakov Rekhter
- Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands… Francois Le Faucheur