From idr-bounces@ietf.org  Fri Feb  1 01:06:13 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 249123A68A0;
	Fri,  1 Feb 2008 01:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.282
X-Spam-Level: 
X-Spam-Status: No, score=0.282 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448,
	URIBL_RHS_DOB=1.083]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RDIYMQgkBo9C; Fri,  1 Feb 2008 01:06:12 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F19F3A68D8;
	Fri,  1 Feb 2008 01:06:12 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 104863A68B5
	for <idr@core3.amsl.com>; Fri,  1 Feb 2008 01:06:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UeD57CR6J6Jp for <idr@core3.amsl.com>;
	Fri,  1 Feb 2008 01:06:10 -0800 (PST)
Received: from limes.NIC.DTAG.DE (limes.NIC.DTAG.DE [194.25.1.113])
	by core3.amsl.com (Postfix) with ESMTP id AA3433A68E2
	for <idr@ietf.org>; Fri,  1 Feb 2008 01:06:04 -0800 (PST)
Received: from kronos.NIC.DTAG.DE (kronos.NIC.DTAG.DE [194.25.1.92])
	by limes.NIC.DTAG.DE (8.8.5/8.8.3) with ESMTP id KAA16636;
	Fri, 1 Feb 2008 10:07:35 +0100 (MET)
Received: from x55.NIC.DTAG.DE (x55.NIC.DTAG.DE [194.25.1.180])
	by kronos.NIC.DTAG.DE (8.8.5/8.7.1) with ESMTP id KAA27990;
	Fri, 1 Feb 2008 10:07:34 +0100 (MET)
Received: (from maho@localhost)
	by x55.NIC.DTAG.DE (8.12.8+Sun/8.12.8/Submit) id m1197X8T001936;
	Fri, 1 Feb 2008 10:07:33 +0100 (MET)
Date: Fri, 1 Feb 2008 10:07:33 +0100
From: Martin Horneffer <maho@nic.dtag.de>
To: Vishwas Manral <vishwas.ietf@gmail.com>
Message-ID: <20080201090733.GA1929@nic.dtag.de>
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
User-Agent: Mutt/1.4i
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Vishwas,

just a quick question from an operator's point of view: what is your
consideration of how a P device (IPv4/MPLS only) should do the
load-sharing for 6PE traffic in case of ECMP?

If I got it correctly 6PE allows the egress PE to use different labels
which would make it easy for a P device to load-share. It does not
have to, though...

Best regards, Martin


On Thu, Jan 31, 2008 at 09:32:01AM -0800, Vishwas Manral wrote:
> Hi Jan,
> =

> Unlike in BGP MPLS IP VPN, the label does not tell any interface as we
> finally look up the only routing table the IPv6 routing table. We do
> not have the VRF concept here. That is the reason we do not need any
> presignaled label. The 6PE draft mentions why we need the top label
> very clearly.
> =

> However they have wrongly decided to signal a label with each route
> instead of just using the IPv6 Explicit NULL label.
> =

> Thanks,
> Vishwas
> =

> On Jan 31, 2008 9:00 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
> >
> >
> >
> > Hi Vishwas,
> >
> > I believe you refer to this part of 6PE spec:
> >
> >    The label bound by MP-BGP to the IPv6 prefix indicates to the egress
> >    6PE Router that the packet is an IPv6 packet.  This label advertised
> >    by the egress 6PE Router with MP-BGP MAY be an arbitrary label value,
> >    which identifies an IPv6 routing context or outgoing interface to
> >    send the packet to, or MAY be the IPv6 Explicit Null Label.  An
> >    ingress 6PE Router MUST be able to accept any such advertised label.
> >
> > I don't know what is the envisaged use of Explicit Null here - but I wo=
uld think
> > it is for some other purposes since to deliver the packet to the VPN th=
is is
> > still needed "identifies an IPv6 routing context or outgoing interface =
to".
> >
> > Jan
> >
> >
> >
> >
> > _________________________________________________________________
> > Share what Santa brought you
> > https://www.mycooluncool.com
> =

> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr

-- =

Dr. Martin Horneffer
T-Com Center Technology Engineering
Internet Backbone Architecture

Deutsche Telekom AG
Supervisory Board: Dr. Klaus Zumwinkel (Chairman)
Board of Management: Ren=E9 Obermann (Chairman),
Dr. Karl-Gerhard Eick (Deputy Chairman),
Hamid Akhavan, Timotheus H=F6ttges, Thomas Sattelberger
Commercial register: Amtsgericht Bonn HRB 6794,
corporate seat: Bonn
WEEEreg.no: DE50478376
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr
From mailman-bounces@core3.amsl.com  Fri Feb  1 05:09:20 2008
Return-Path: <mailman-bounces@core3.amsl.com>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F4D328D936
	for <ietfarch-idr-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id s0fExShNWOPS for <ietfarch-idr-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:09:06 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0918428D939
	for <idr-archive@megatron.ietf.org>; Fri,  1 Feb 2008 05:01:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: idr-archive@megatron.ietf.org
X-No-Archive: yes
Message-ID: <mailman.3194.1201870849.31726.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:00:49 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/idr/idr-archive%40megatron.ietf.org
From mailman-bounces@core3.amsl.com  Fri Feb  1 05:09:41 2008
Return-Path: <mailman-bounces@core3.amsl.com>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E51328CC3E
	for <ietfarch-idr-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:09:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RKUZ3OTjds9E for <ietfarch-idr-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:09:15 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 88D2B28C74E
	for <idr-archive@megatron.ietf.org>; Fri,  1 Feb 2008 05:01:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: idr-archive@megatron.ietf.org
X-No-Archive: yes
Message-ID: <mailman.3194.1201870850.31733.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:00:50 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/idr/idr-archive%40megatron.ietf.org
From idr-bounces@ietf.org  Fri Feb  1 09:27:15 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B153C28C1B6;
	Fri,  1 Feb 2008 09:27:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level: 
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5
	tests=[AWL=-0.033, BAYES_00=-2.599, URIBL_RHS_DOB=1.083]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ybnEhKtPBPYO; Fri,  1 Feb 2008 09:27:14 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A1D5B3A68F6;
	Fri,  1 Feb 2008 09:27:14 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19C733A6882
	for <idr@core3.amsl.com>; Fri,  1 Feb 2008 09:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id i8iojqxLE6gi for <idr@core3.amsl.com>;
	Fri,  1 Feb 2008 09:27:12 -0800 (PST)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183])
	by core3.amsl.com (Postfix) with ESMTP id B386928C2CF
	for <idr@ietf.org>; Fri,  1 Feb 2008 09:25:04 -0800 (PST)
Received: by el-out-1112.google.com with SMTP id j27so607720elf.25
	for <idr@ietf.org>; Fri, 01 Feb 2008 09:26:39 -0800 (PST)
Received: by 10.142.52.9 with SMTP id z9mr2323818wfz.201.1201886798419;
	Fri, 01 Feb 2008 09:26:38 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Fri, 1 Feb 2008 09:26:38 -0800 (PST)
Message-ID: <77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
Date: Fri, 1 Feb 2008 09:26:38 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Martin Horneffer" <maho@nic.dtag.de>
In-Reply-To: <20080201090733.GA1929@nic.dtag.de>
MIME-Version: 1.0
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
	<20080201090733.GA1929@nic.dtag.de>
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Martin,

The load sharing and everything else on the of P devices will still
work the same way. So we would have for example LDP running on the P
routers giving out labels for FEC's just the same way. The P device
works on the outer Tunnel label and its functionality will not change
in my view.

There is a case of having different labels for preventing one IPv6
lookup in some cases but in case we had the ECMP case we would have to
use the IPv6 header lookup and use the inner label as an IPv6 Explicit
NULL label.

Do let me know if I missed the point?

Thanks,
Vishwas

On Feb 1, 2008 1:07 AM, Martin Horneffer <maho@nic.dtag.de> wrote:
> Hi Vishwas,
>
> just a quick question from an operator's point of view: what is your
> consideration of how a P device (IPv4/MPLS only) should do the
> load-sharing for 6PE traffic in case of ECMP?
>
> If I got it correctly 6PE allows the egress PE to use different labels
> which would make it easy for a P device to load-share. It does not
> have to, though...
>
> Best regards, Martin
>
>
>
> On Thu, Jan 31, 2008 at 09:32:01AM -0800, Vishwas Manral wrote:
> > Hi Jan,
> >
> > Unlike in BGP MPLS IP VPN, the label does not tell any interface as we
> > finally look up the only routing table the IPv6 routing table. We do
> > not have the VRF concept here. That is the reason we do not need any
> > presignaled label. The 6PE draft mentions why we need the top label
> > very clearly.
> >
> > However they have wrongly decided to signal a label with each route
> > instead of just using the IPv6 Explicit NULL label.
> >
> > Thanks,
> > Vishwas
> >
> > On Jan 31, 2008 9:00 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
> > >
> > >
> > >
> > > Hi Vishwas,
> > >
> > > I believe you refer to this part of 6PE spec:
> > >
> > >    The label bound by MP-BGP to the IPv6 prefix indicates to the egre=
ss
> > >    6PE Router that the packet is an IPv6 packet.  This label advertis=
ed
> > >    by the egress 6PE Router with MP-BGP MAY be an arbitrary label val=
ue,
> > >    which identifies an IPv6 routing context or outgoing interface to
> > >    send the packet to, or MAY be the IPv6 Explicit Null Label.  An
> > >    ingress 6PE Router MUST be able to accept any such advertised labe=
l.
> > >
> > > I don't know what is the envisaged use of Explicit Null here - but I =
would think
> > > it is for some other purposes since to deliver the packet to the VPN =
this is
> > > still needed "identifies an IPv6 routing context or outgoing interfac=
e to".
> > >
> > > Jan
> > >
> > >
> > >
> > >
> > > _________________________________________________________________
> > > Share what Santa brought you
> > > https://www.mycooluncool.com
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www1.ietf.org/mailman/listinfo/idr
>
> --
> Dr. Martin Horneffer
> T-Com Center Technology Engineering
> Internet Backbone Architecture
>
> Deutsche Telekom AG
> Supervisory Board: Dr. Klaus Zumwinkel (Chairman)
> Board of Management: Ren=E9 Obermann (Chairman),
> Dr. Karl-Gerhard Eick (Deputy Chairman),
> Hamid Akhavan, Timotheus H=F6ttges, Thomas Sattelberger
> Commercial register: Amtsgericht Bonn HRB 6794,
> corporate seat: Bonn
> WEEEreg.no: DE50478376
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr
From idr-bounces@ietf.org  Fri Feb  1 10:33:26 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 792BF3A6917;
	Fri,  1 Feb 2008 10:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=0.225,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tO2GKi7KGYZo; Fri,  1 Feb 2008 10:33:25 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC6A33A683D;
	Fri,  1 Feb 2008 10:33:24 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A36673A67B1
	for <idr@core3.amsl.com>; Fri,  1 Feb 2008 10:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ydMM+HlmChY2 for <idr@core3.amsl.com>;
	Fri,  1 Feb 2008 10:33:22 -0800 (PST)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.228])
	by core3.amsl.com (Postfix) with ESMTP id BE3553A68B1
	for <idr@ietf.org>; Fri,  1 Feb 2008 10:33:21 -0800 (PST)
Received: by wr-out-0506.google.com with SMTP id 50so1497983wri.25
	for <idr@ietf.org>; Fri, 01 Feb 2008 10:34:56 -0800 (PST)
Received: by 10.142.88.20 with SMTP id l20mr2412831wfb.72.1201890895199;
	Fri, 01 Feb 2008 10:34:55 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Fri, 1 Feb 2008 10:34:55 -0800 (PST)
Message-ID: <77ead0ec0802011034r164d9cf7l999b8ed4b94279cf@mail.gmail.com>
Date: Fri, 1 Feb 2008 10:34:55 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Kalpesh Zinjuwadia" <kzinjuwadia@force10networks.com>
In-Reply-To: <44ED058B21DF294ABE394CABE5C1B52102775B3B@EXCH-CLUSTER-03.force10networks.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <002f01c8647c$9dafb700$9d000a0a@samitacD600>
	<44ED058B21DF294ABE394CABE5C1B52102775B3B@EXCH-CLUSTER-03.force10networks.com>
Cc: idr@ietf.org, quaizar.vohra@gmail.com
Subject: Re: [Idr] Comments on RFC4893
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi,

There is just one small part I wanted to clarify.

> Clarification 3
> ============
> Section 3 of RFC4893 states:
> "NEW BGP speakers carry AS path information expressed in terms of
> 4-octet Autonomous Systems numbers by using the existing AS_PATH
> attribute, except that each AS number in this attribute is encoded not
> as a 2-octet, but as a 4-octet entity."
>  o-------------------o----------------------o-------------------
>   NEW1                NEW2               OLD2                    OLD3
> =====> Route Adv
>
> In the above sequence of configuration, how does the OLD2 process the
> 4byte ASN value in the AS_PATH  put by NEW1 ? The OLD BGP implementation
> is expected to use 2byte ASN value.  Please clarify.
> Should not it be easy and backward compatible if NEW BGP speakers always
> use AS4_PATH for 4byte ASN and use AS_PATH only when the ASNs
> are mappable to 2bytes?
>
> Kalpesh> NEW1 & NEW2 will exchange update with 4-byte AS-PATH & AGGR
> attributes. However, when NEW2 advertises update to OLD2, it will split
> 4-byte AS-PATH attribute into 2-byte AS-PATH and 4-byte AS4-PATH using
> the steps mentioned in RFC. Same goes for AGGR attribute. OLD2 & OLD3
> will treat AS4-PATH & AS4-AGGR attributes as unknown opt-trans and pass
> it further.

When the New router sends the update with the old router, it converts the 4 byte
AS-Path to 2 byte AS-Path, with procedures mentioned in the RFC. As the OLD
routers do not understand the AS4_PATH they will just opaquely forward the
AS4_PATH attribute - which is an optional Transitive attribute.
We will then get the same value in the attribute when an OLD router
communicates
with a new. The idea is to transport 4-byte AS numbers Opaquely and
translating at
the edge the AS_PATH attribute to carry only 2 byte AS-Numbers (by using
AS-TRANS value).

Thanks,
Vishwas

On Jan 31, 2008 8:15 PM, Kalpesh Zinjuwadia
<kzinjuwadia@force10networks.com> wrote:
> Some comments inline.
>
> Thanks,
> Kalpesh
>
>
> -----Original Message-----
> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of
> Samita Chakrabarti
> Sent: Thursday, January 31, 2008 6:46 PM
> To: idr@ietf.org; quaizar.vohra@gmail.com; enkechen@cisco.com
> Subject: [Idr] Comments on RFC4893
>
> Hello Quaizar and Enke:
>
> While reviewing RFC4893 (4-byte AS Number support for BGP), I have
> encountered several questions related to interoperability and
> implementation.
>
> I am listing them below; my apology if they are already discussed in
> this
> list before. (I am new in this mailing list)
>
> It seems to me that the RFC has ambiguity in several places that needs
> to be
> corrected from implementation perspective. Is there a plan for a
> revision?
>
> Regards,
> -Samita
> ------------------------------------------------------------------------
> ----
> ------------------------------------------------------------------------
> ----
> RFC4893 is unclear about the processing of "My ASN" field in the OPEN
> message. Section 3
>  mentions about the capability message for 4byte ASN support:
>
> "The Capability that is used by a BGP speaker to convey to its BGP peer
> the
> 4-octet Autonomous System number
>  capability, also carries the 4-octet Autonomous System number of the
> speaker in the Capability Value field of the
>  Capability Optional Parameter. The Capability Length field of the
> Capability is set to 4. "
>
> and
> "We denote this special AS number as AS_TRANS for ease of description in
> the
> rest of this
>  specification. This AS number is also placed in the "My Autonomous
> System"
> field of the
> OPEN message originated by a NEW BGP speaker, if the speaker does not
> have a
>  (globally unique) 2-octet AS number."
>
>
> Clarification 1:
> ============
> In section 4 it describes the interaction between NEW BGP speakers; it
> discusses the UPDATE
> message processing with
> NEW and OLD BGP speakers. But  it does not discuss the OPEN message
> send/recv in details;
> the following cases need clarification:
> 1) NEW BGP speakers interactions: If the BGP speaker has a 2byte unique
> ASN
> it uses the
>    2 byte ASN in the "My ASN" field of OPEN message. If the BGP speaker
> has
> a 4 byte
>    non-mappable AS number, then it  uses AS_TRANS in "My ASN" field of
> OPEN
> message.
> 2) Receiving OPEN message: If a NEW BGP speaker receives a OPEN message
> with
> extended ASN
>    capability, then it ignores the "My ASN" field of OPEN message and
> uses
> the 4byte ASN
>    value in the capability message. [ this will clarify the
>    ambiguity  and increases interoperability ]
>
> Kalpesh> NEW BGP speaker (R1) will always put the 4-BYTE-AS capability
> in the Open message, unless it's acting as OLD. "My AS" will contain the
> actual AS if it's mappable to 2-byte field; else it will contain
> AS-TRANS. OLD speaker (R2) will use AS-TRANS as R1's AS. NEW speaker
> (R3) will use the ASN in the capability as R1's AS. R3 may also put
> sanity check such as "My AS" can be AS-TRANS iff R1's actual ASN is
> 4-byte non-mappable.
>
>
> Clarification 2:
> =============
> Scenario for AS_PATH.
>
> o-------------------o-------------------o----------------------o--------
> -o
>  OLD                     NEW                   NEW           OLD
> NEW
>  (50)                    (5000)             (65666)      (101)
> (65777)
>
> The RFC says that :
> "4.2.1. BGP Peering Note that peering between a NEW BGP speaker and an
> OLD
> one is possible
> only if the NEW BGP speaker has a 2-octet AS number. However, this
> document
> does not assume
> that an Autonomous System with NEW speakers has to have a globally
> unique
> 2-octet AS number - AS_TRANS
> could be used instead (even if a multiple Autonomous System would use
> it)."
> -------
> From the above text it is not clear whether a NEW BGP speaker with 4byte
> non-mappable ASN
>  can talk to the OLD BGP speaker or not.Practically it is not possible
> to
> communicate with
>  OLD and NEW BGP peer with non-mappable 4byte ASN (see the above
> scenario
> where both peers of
> a OLD BGP are NEW with 4byte ASN). I assume that the RFC recommends :
>      1)  If the NEW BGP speaker has a unique 2 byte ASN or a
> 2-byte-mappable
> 4byte ASN, it
>            SHOULD use the 2 byte ASN in the "My ASN field" for OPEN
> message.
>      2) The NEW BGP with non-mappable 4byte ASN SHOULD not peer with OLD
> BGP
> speaker;
>            this can easily produce routing loop or loss of ASN value in
> the
> PATH.
>
> Kalpesh> I don't know if I understand your question completely. However,
> I don't think RFC puts any restriction on NEW BGP speaker with
> non-mappable 4-byte ASN to communicate with OLD & NEW BGP speakers at
> the same time. In your case, NEW speaker w/ ASN 65666 will communicate
> differently with NEW speaker w/ ASN 5000 and OLD speaker w/ ASN 101.
> Each speaker pair should be is treated independently and not confused
> with others.
>
>
> Clarification 3
> ============
> Section 3 of RFC4893 states:
> "NEW BGP speakers carry AS path information expressed in terms of
> 4-octet
> Autonomous Systems
>  numbers by using the existing AS_PATH attribute, except that each AS
> number
> in this
>  attribute is encoded not as a 2-octet, but as a 4-octet entity."
>
>  o-------------------o----------------------o-------------------
>   NEW1                NEW2               OLD2                    OLD3
> =====> Route Adv
>
> In the above sequence of configuration, how does the OLD2 process the
> 4byte
> ASN value in
> the AS_PATH  put by NEW1 ? The OLD BGP implementation is expected to use
> 2byte ASN value.
>  Please clarify.
> Should not it be easy and backward compatible if NEW BGP speakers always
> use
> AS4_PATH for
> 4byte ASN and use AS_PATH only when the ASNs are mappable to 2bytes?
>
> Kalpesh> NEW1 & NEW2 will exchange update with 4-byte AS-PATH & AGGR
> attributes. However, when NEW2 advertises update to OLD2, it will split
> 4-byte AS-PATH attribute into 2-byte AS-PATH and 4-byte AS4-PATH using
> the steps mentioned in RFC. Same goes for AGGR attribute. OLD2 & OLD3
> will treat AS4-PATH & AS4-AGGR attributes as unknown opt-trans and pass
> it further.
>
>
> Clarification 4
> ================
>
> When the NEW BGP speaker has a non-mappable 4byte unique AS number and
> it is
> peering with an OLD BGP
> speaker, only then should it use AS_TRANS in AS_PATH and a corresponding
> AS4_PATH 4byte
>  AS number?
> This should simplify reconstructing the AS number from both AS_PATH and
> AS4_PATH and also
> is in sync with AS4_AGGREGATOR processing as described in the RFC.
>
> Kalpesh> NEW speaker will generate AS4-PATH only if the AS-PATH to be
> sent to OLD peer has at least 1 non-mappable 4-byte ASN. Hence, a NEW
> speaker with 2-byte mappable AS may generate AS4-PATH if reqd.
>
> section 4.2.2:
> "When communicating with an OLD BGP speaker, a NEW speaker MUST send
>    the AS path information in the AS_PATH attribute encoded with 2-octet
>    AS numbers.  The NEW speaker MUST also send the AS path information
>    in the AS4_PATH attribute (encoded with 4-octet AS numbers), except
>    for the case where the entire AS path information is composed of 2-
>    octet AS numbers only.  In this case, the NEW speaker SHOULD NOT send
>    the AS4_PATH attribute."
>
> The above rule is confusing from the implementation perspective. How
> about
> making it simple by doing the same thing as AS_AGGREGATOR (as follows) ?
>
>   "Similarly, if the NEW speaker has to send the AGGREGATOR attribute,
>    and if the aggregating Autonomous System's AS number is truly 4-
>    octets, then the speaker constructs the AS4_AGGREGATOR attributes by
>    taking the attribute length and attribute value from the AGGREGATOR
>    attribute and placing them into the attribute length and attribute
>    value of the AS4_AGGREGATOR attribute, and sets the AS number field
>    in the existing AGGREGATOR attribute to the reserved AS number,
>    AS_TRANS.  Note that if the AS number is 2-octets only, then the
>    AS4_AGGREGATOR attribute SHOULD NOT be sent."
>
> I assume that "truly 4-octet" means it is higher than 65535.
>
> Kalpesh> I think conditions mentioned for generating AS4-PATH & AS4-AGGR
> are inherently same. For AS-PATH all ASN in it are considered for AGGR
> the aggregating ASN is considered.
>
> Yes "truly 4-octet" ASN means ASN > 65535.
>
> Clarification 5
> ===================
>
> Should the NEW BGP speaker send a NOTIFICATION with error code =2 and
> subcode=7
> (unsupported capability) when it receives a OPEN message with AS_TRANS
> but
> without
> any corresponding capability message ?
>
> Kalpesh> RFC doesn't discuss how NEW speaker should behave when OLD
> speaker uses AS-TRANS in "My AS" field. Behavior is implementation
> dependent.
>
> Similarly, should a NEW BGP speaker with AS number higher than 65535,
> send a
>
> NOTIFICATION to a OLD BGP speaker with error code =2 and subcode=7,
> before
> closing the
> peering connection ?
>
> Kalpesh> What caused NEW BGP speaker to close the connection with OLD
> peer? If same as previous question, again it's implementation dependent.
>
>
> IMHO, the above NOTIFICATION is helpful for transition phase.
>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> http://www.ietf.org/mailman/listinfo/idr
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> http://www.ietf.org/mailman/listinfo/idr
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org  Fri Feb  1 11:50:45 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DEE53A697F;
	Fri,  1 Feb 2008 11:50:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1QzuLhOYZebC; Fri,  1 Feb 2008 11:50:44 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12FCE3A6978;
	Fri,  1 Feb 2008 11:50:44 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C35D3A6888
	for <idr@core3.amsl.com>; Fri,  1 Feb 2008 11:50:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ErUhtaxcfRux for <idr@core3.amsl.com>;
	Fri,  1 Feb 2008 11:50:41 -0800 (PST)
Received: from gateway.ipinfusion.com (mail.ipinfusion.com [65.223.109.2])
	by core3.amsl.com (Postfix) with ESMTP id AD8023A6886
	for <idr@ietf.org>; Fri,  1 Feb 2008 11:50:41 -0800 (PST)
Received: from samitacD600 ([10.10.0.157])
	by gateway.ipinfusion.com (8.11.6/8.11.6) with ESMTP id m11Jpi414292;
	Fri, 1 Feb 2008 11:51:44 -0800
From: "Samita Chakrabarti" <samitac@ipinfusion.com>
To: "'Kalpesh Zinjuwadia'" <kzinjuwadia@force10networks.com>, <idr@ietf.org>, 
	<quaizar.vohra@gmail.com>, <enkechen@cisco.com>
References: <002f01c8647c$9dafb700$9d000a0a@samitacD600>
	<44ED058B21DF294ABE394CABE5C1B52102775B3B@EXCH-CLUSTER-03.force10networks.com>
Date: Fri, 1 Feb 2008 11:51:54 -0800
Message-ID: <001401c8650b$e8a39760$9d000a0a@samitacD600>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AchkfJnFg0bX62edRpC+ThO14/0EDgAB9ayQACBsYzA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <44ED058B21DF294ABE394CABE5C1B52102775B3B@EXCH-CLUSTER-03.force10networks.com>
Subject: Re: [Idr] Comments on RFC4893
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Kalpesh,

Thanks for the response. Please see in-line.


>----
>
>Clarification 1:
>============
>In section 4 it describes the interaction between NEW BGP speakers; it
>discusses the UPDATE
>message processing with
>NEW and OLD BGP speakers. But  it does not discuss the OPEN message
>send/recv in details;
>the following cases need clarification:
>1) NEW BGP speakers interactions: If the BGP speaker has a 2byte unique
>ASN
>it uses the
>   2 byte ASN in the "My ASN" field of OPEN message. If the BGP speaker
>has
>a 4 byte
>   non-mappable AS number, then it  uses AS_TRANS in "My ASN" field of
>OPEN
>message.
>2) Receiving OPEN message: If a NEW BGP speaker receives a OPEN message
>with
>extended ASN
>   capability, then it ignores the "My ASN" field of OPEN message and
>uses
>the 4byte ASN
>   value in the capability message. [ this will clarify the
>   ambiguity  and increases interoperability ]
>
>Kalpesh> NEW BGP speaker (R1) will always put the 4-BYTE-AS capability
>in the Open message, unless it's acting as OLD. "My AS" will contain the
>actual AS if it's mappable to 2-byte field; else it will contain
>AS-TRANS. OLD speaker (R2) will use AS-TRANS as R1's AS.
[SC>] 
[SC>]  Yes. We are saying the same thing. But the point is that the RFC is
not very clear about sending/receiving "My ASN" value in the OPEN message
and it should be clarified.

Kalpesh> NEW speaker
>(R3) will use the ASN in the capability as R1's AS. R3 may also put
>sanity check such as "My AS" can be AS-TRANS iff R1's actual ASN is
>4-byte non-mappable.
>
[SC>] 
[SC>] What is your topology in this example? Is R3 peering with both R1 and
R2?  The question is should we allow R2 to peer with non-mappable ASN BGP
speaker in the following scenario?

    R1 (ASN=65566)-----R2(100)-------------R3(77777)-----R4(400)
     NEW              OLD BGP               NEW            OLD BGP
In this example, R4 finds loop in ASN path, because it can only understand
2byte AS_TRANS.  R4 sees <23456, 100, 23456> in ASN PATH.

The RFC in section 4.2.1 is very liberal about the specification; I think,
the RFC at least should recommend some valid scenarios and discourage things
that can cause interoperability or confusion in the BGP path.


>a OLD BGP are NEW with 4byte ASN). I assume that the RFC recommends :
>     1)  If the NEW BGP speaker has a unique 2 byte ASN or a
>2-byte-mappable
>4byte ASN, it
>           SHOULD use the 2 byte ASN in the "My ASN field" for OPEN
>message.
>     2) The NEW BGP with non-mappable 4byte ASN SHOULD not peer with OLD
>BGP
>speaker;
>           this can easily produce routing loop or loss of ASN value in
>the
>PATH.
>
>Kalpesh> I don't know if I understand your question completely. However,
>I don't think RFC puts any restriction on NEW BGP speaker with
>non-mappable 4-byte ASN to communicate with OLD & NEW BGP speakers at
>the same time. In your case, NEW speaker w/ ASN 65666 will communicate
>differently with NEW speaker w/ ASN 5000 and OLD speaker w/ ASN 101.
>Each speaker pair should be is treated independently and not confused
>with others.
>
>
[SC>] 
      Please see the previous example  of R1-R2-R3-R4 scenario.


>
>Kalpesh> NEW1 & NEW2 will exchange update with 4-byte AS-PATH & AGGR
>attributes. However, when NEW2 advertises update to OLD2, it will split
>4-byte AS-PATH attribute into 2-byte AS-PATH and 4-byte AS4-PATH using
>the steps mentioned in RFC. Same goes for AGGR attribute. OLD2 & OLD3
>will treat AS4-PATH & AS4-AGGR attributes as unknown opt-trans and pass
>it further.
>
>
[SC>] 
 
Yes. Again the RFC needs more clarification here, as well. 


>Clarification 4
>================
>
>When the NEW BGP speaker has a non-mappable 4byte unique AS number and
>it is
>peering with an OLD BGP
>speaker, only then should it use AS_TRANS in AS_PATH and a corresponding
>AS4_PATH 4byte
> AS number?
>This should simplify reconstructing the AS number from both AS_PATH and
>AS4_PATH and also
>is in sync with AS4_AGGREGATOR processing as described in the RFC.
>
>Kalpesh> NEW speaker will generate AS4-PATH only if the AS-PATH to be
>sent to OLD peer has at least 1 non-mappable 4-byte ASN. Hence, a NEW
>speaker with 2-byte mappable AS may generate AS4-PATH if reqd.
[SC>] 
[SC>] 
      OK. It is now clarified. 
>
>section 4.2.2:
>"When communicating with an OLD BGP speaker, a NEW speaker MUST send
>   the AS path information in the AS_PATH attribute encoded with 2-octet
>   AS numbers.  The NEW speaker MUST also send the AS path information
>   in the AS4_PATH attribute (encoded with 4-octet AS numbers), except
>   for the case where the entire AS path information is composed of 2-
>   octet AS numbers only.  In this case, the NEW speaker SHOULD NOT send
>   the AS4_PATH attribute."
>
>The above rule is confusing from the implementation perspective. How
>about
>making it simple by doing the same thing as AS_AGGREGATOR (as follows) ?
>
>  "Similarly, if the NEW speaker has to send the AGGREGATOR attribute,
>   and if the aggregating Autonomous System's AS number is truly 4-
>   octets, then the speaker constructs the AS4_AGGREGATOR attributes by
>   taking the attribute length and attribute value from the AGGREGATOR
>   attribute and placing them into the attribute length and attribute
>   value of the AS4_AGGREGATOR attribute, and sets the AS number field
>   in the existing AGGREGATOR attribute to the reserved AS number,
>   AS_TRANS.  Note that if the AS number is 2-octets only, then the
>   AS4_AGGREGATOR attribute SHOULD NOT be sent."
>
>I assume that "truly 4-octet" means it is higher than 65535.
>
>Kalpesh> I think conditions mentioned for generating AS4-PATH & AS4-AGGR
>are inherently same. For AS-PATH all ASN in it are considered for AGGR
>the aggregating ASN is considered.
>
[SC>] 
[SC>]  Conditions for AS4_PATH and AS4_AGGR should be the same; again this
part is a bit unclear in the RFC.


>Yes "truly 4-octet" ASN means ASN > 65535.
[SC>] 
[SC>] This is also subject to interpretation in the RFC.

>
>Clarification 5
>===================
>
>Should the NEW BGP speaker send a NOTIFICATION with error code =2 and
>subcode=7
>(unsupported capability) when it receives a OPEN message with AS_TRANS
>but
>without
>any corresponding capability message ?
>
>Kalpesh> RFC doesn't discuss how NEW speaker should behave when OLD
>speaker uses AS-TRANS in "My AS" field. Behavior is implementation
>dependent.
>
[SC>] 
[SC>] Please note the above situation can also happen from a faulty or
misbehaving NEW BGP speaker with non-mappable 4b ASN. Since AS_TRANS is a
reserved value and not assigned to anyone, if the OLD BGP speaker somehow
uses this value in the OPEN message, it must not be accepted either.
IMHO, this NOTIFICATION case is a valid one and should be documented.

-Samita


_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org  Fri Feb  1 12:22:21 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D50D73A69A4;
	Fri,  1 Feb 2008 12:22:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.316
X-Spam-Level: 
X-Spam-Status: No, score=-4.316 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_23=0.6,
	RCVD_IN_DNSWL_MED=-4, URIBL_RHS_DOB=1.083]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id l57ZC5E9mnHZ; Fri,  1 Feb 2008 12:22:20 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA0F028C169;
	Fri,  1 Feb 2008 12:22:20 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEF123A69B0
	for <idr@core3.amsl.com>; Fri,  1 Feb 2008 12:22:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 028bI0ForNYg for <idr@core3.amsl.com>;
	Fri,  1 Feb 2008 12:22:18 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 169253A6976
	for <idr@ietf.org>; Fri,  1 Feb 2008 12:22:18 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 01 Feb 2008 12:23:53 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m11KNrSj029507; 
	Fri, 1 Feb 2008 12:23:53 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m11KNIaP007830;
	Fri, 1 Feb 2008 20:23:48 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Feb 2008 15:23:43 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 1 Feb 2008 15:23:01 -0500
Message-ID: <15B86BC7352F864BB53A47B540C089B604DAB2EE@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] 6PE-Alt draft
Thread-Index: AchkGjrqr4FjiH+uRXa8pIh8ZiZzdAA9Bjyg
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>,
	"Jan Novak" <jjjnovak@hotmail.com>
X-OriginalArrivalTime: 01 Feb 2008 20:23:43.0041 (UTC)
	FILETIME=[56CFF310:01C86510]
Authentication-Results: sj-dkim-1; header.From=rajiva@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: idr@ietf.org, "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>,
	Ooms Dirk <dirk@onesparrow.com>
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Vishwas,

Good discussion. 
It was interesting to see the following excerpt wrt 6VPE - 

> become IPv6 and the network may still have IPv4. If the assumption
> that each device in the IPv6 networks has a Global IPv6 address (not
> that IPv6 site local has been deprecated), we can do without the
> entire BGP MPLS IPv6 VPN functionality.

Assuming PE-to-PE tunneling is still in place, yah, you are right from
the routing perspective in 6VPE. But how would we prohibit one IPv6 site
communicating with another IPv6 site belonging to different enterprises.

AFAIK, the benefit of having VRF is beyond just the routing. And that's
one of the key components of BGP IP VPN functionality. 6VPE indeed has
merits. 

Perhaps, you intended to point to something else in BGP IPv6 VPN
functionality.

Cheers,
Rajiv 

> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com] 
> Sent: Thursday, January 31, 2008 10:01 AM
> To: Jan Novak
> Cc: idr@ietf.org; Francois Le Faucheur (flefauch); Ooms Dirk
> Subject: Re: [Idr] 6PE-Alt draft
> 
> Hi Jan,
> 
> I am CC'ing the authors of the 6PE draft to get their views. Let me
> explain the draft in greater detail however.
> 
> In 6PE, MP-BGP SAFI family label is used to exchange routes between 2
> 6PE routers (a new AFI/ SAFI combination is defined). Each route is
> attached with a label (which may be the IPv6 Explicit NULL label). In
> the data-plane this label is used as the inner label and the other
> label is the tunnel label, which gets the packet from source PE to
> destination PE. Once the packet gets to the destination PE, the inner
> label is looked up and a POP operation is done on it and the IPv6
> header is looked up in the routing table.
> 
> With 6PE-Alt, no additional signaling mechanism is required. All we
> need to do is instead of using the signaled label as the inner label,
> we use the IPv6 Explicit NULL label. The same operations happen as 6PE
> without any explicit signaling of the labels with each route. It helps
> prevent all the excess signaling and still providing the exact same
> functionality. We are using the meaning implied in the "Explicit NULL
> Label". We do not need to signal anything here.
> 
> As an alternate, if you notice in IPv6, the end sites/ devices will
> become IPv6 and the network may still have IPv4. If the assumption
> that each device in the IPv6 networks has a Global IPv6 address (not
> that IPv6 site local has been deprecated), we can do without the
> entire BGP MPLS IPv6 VPN functionality.
> 
> Thanks,
> Vishwas
> 
> On Jan 31, 2008 6:31 AM, Vishwas Manral 
> <vishwas.ietf@gmail.com> wrote:
> > Hi Jan,
> >
> > You may be missing the scope of the document. There is a 
> discussion in
> > the v6ops group too which .
> >
> > The idea is simple. We do not need to define a new AFI/ SAFI
> > combination to achieve the 6PE functionality. We can just use the
> > meaning implied in the IPv6 Explicit NULL label. The 6PE 
> RFC does talk
> > about allowing signaling for the Explicit NULL label in 
> which case the
> > dataplane functionality becomes just the same, but in 6PE 
> even that is
> > signaled using BGP extensions defined in RFC3107.
> >
> > Thanks,
> > Vishwas
> >
> >
> > On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
> > >
> > >
> > > Hi,
> > >
> > > Just out of curiosity - lets say you have two IPv4 VPNs with
> > > overlapping set of Pes and both of them want to provide 6PE
> > > service.
> > > When the explicit-null encapsulated packets from two different
> > > VPNs (but same PE) arrive to the other side PE - how do you
> > > decide which is which - e.g. which packet should be shipped to
> > > which VPN ??
> > >
> > > Jan
> > >
> > >
> > > _________________________________________________________________
> > > Telly addicts unite!
> > > http://www.searchgamesbox.com/tvtown.shtml
> >
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr
> 
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org  Fri Feb  1 12:27:39 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A996B28C33C;
	Fri,  1 Feb 2008 12:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id t8OdAb+XjNnv; Fri,  1 Feb 2008 12:27:38 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 43AF528C24D;
	Fri,  1 Feb 2008 12:27:38 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DC9228C1D3
	for <idr@core3.amsl.com>; Fri,  1 Feb 2008 12:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8qekeRJXH9jF for <idr@core3.amsl.com>;
	Fri,  1 Feb 2008 12:27:35 -0800 (PST)
Received: from mx.force10networks.com (corp.force10networks.com
	[64.186.164.204])
	by core3.amsl.com (Postfix) with ESMTP id AB7F328C246
	for <idr@ietf.org>; Fri,  1 Feb 2008 12:27:35 -0800 (PST)
Received: from EXCH-CLUSTER-03.force10networks.com ([10.11.0.53]) by
	mx.force10networks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 1 Feb 2008 12:28:33 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 1 Feb 2008 12:28:33 -0800
Message-ID: <44ED058B21DF294ABE394CABE5C1B52101303B07@EXCH-CLUSTER-03.force10networks.com>
In-Reply-To: <001401c8650b$e8a39760$9d000a0a@samitacD600>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] Comments on RFC4893
Thread-Index: AchkfJnFg0bX62edRpC+ThO14/0EDgAB9ayQACBsYzAAAi4IsA==
References: <002f01c8647c$9dafb700$9d000a0a@samitacD600>
	<44ED058B21DF294ABE394CABE5C1B52102775B3B@EXCH-CLUSTER-03.force10networks.com>
	<001401c8650b$e8a39760$9d000a0a@samitacD600>
From: "Kalpesh Zinjuwadia" <kzinjuwadia@force10networks.com>
To: "Samita Chakrabarti" <samitac@ipinfusion.com>, <idr@ietf.org>,
	<quaizar.vohra@gmail.com>, <enkechen@cisco.com>
X-OriginalArrivalTime: 01 Feb 2008 20:28:33.0345 (UTC)
	FILETIME=[03D8D310:01C86511]
Subject: Re: [Idr] Comments on RFC4893
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Comments inline.

Thanks,
Kalpesh

-----Original Message-----
From: Samita Chakrabarti [mailto:samitac@ipinfusion.com] 
Sent: Friday, February 01, 2008 11:52 AM
To: Kalpesh Zinjuwadia; idr@ietf.org; quaizar.vohra@gmail.com;
enkechen@cisco.com
Cc: 'Samita Chakrabarti'
Subject: RE: [Idr] Comments on RFC4893

Hi Kalpesh,

Thanks for the response. Please see in-line.


>----
>
>Clarification 1:
>============
>In section 4 it describes the interaction between NEW BGP speakers; it
>discusses the UPDATE
>message processing with
>NEW and OLD BGP speakers. But  it does not discuss the OPEN message
>send/recv in details;
>the following cases need clarification:
>1) NEW BGP speakers interactions: If the BGP speaker has a 2byte unique
>ASN
>it uses the
>   2 byte ASN in the "My ASN" field of OPEN message. If the BGP speaker
>has
>a 4 byte
>   non-mappable AS number, then it  uses AS_TRANS in "My ASN" field of
>OPEN
>message.
>2) Receiving OPEN message: If a NEW BGP speaker receives a OPEN message
>with
>extended ASN
>   capability, then it ignores the "My ASN" field of OPEN message and
>uses
>the 4byte ASN
>   value in the capability message. [ this will clarify the
>   ambiguity  and increases interoperability ]
>
>Kalpesh> NEW BGP speaker (R1) will always put the 4-BYTE-AS capability
>in the Open message, unless it's acting as OLD. "My AS" will contain
the
>actual AS if it's mappable to 2-byte field; else it will contain
>AS-TRANS. OLD speaker (R2) will use AS-TRANS as R1's AS.
[SC>] 
[SC>]  Yes. We are saying the same thing. But the point is that the RFC
is
not very clear about sending/receiving "My ASN" value in the OPEN
message
and it should be clarified.

<<Kalpesh>> I don't think there is any ambiguity in RFC for this. Can
you elaborate what's not clear to you?



Kalpesh> NEW speaker
>(R3) will use the ASN in the capability as R1's AS. R3 may also put
>sanity check such as "My AS" can be AS-TRANS iff R1's actual ASN is
>4-byte non-mappable.
>
[SC>] 
[SC>] What is your topology in this example? Is R3 peering with both R1
and
R2?  The question is should we allow R2 to peer with non-mappable ASN
BGP
speaker in the following scenario?

    R1 (ASN=65566)-----R2(100)-------------R3(77777)-----R4(400)
     NEW              OLD BGP               NEW            OLD BGP
In this example, R4 finds loop in ASN path, because it can only
understand
2byte AS_TRANS.  R4 sees <23456, 100, 23456> in ASN PATH.

The RFC in section 4.2.1 is very liberal about the specification; I
think,
the RFC at least should recommend some valid scenarios and discourage
things
that can cause interoperability or confusion in the BGP path.

<<Kalpesh>> BGP speaker will only check for it's local AS in the
received AS-PATH and doesn't worry about multiple occurrence of other
ASes. Pl go thru RFC 4271, sec 9.1.2, 3rd para on pg 78.

>a OLD BGP are NEW with 4byte ASN). I assume that the RFC recommends :
>     1)  If the NEW BGP speaker has a unique 2 byte ASN or a
>2-byte-mappable
>4byte ASN, it
>           SHOULD use the 2 byte ASN in the "My ASN field" for OPEN
>message.
>     2) The NEW BGP with non-mappable 4byte ASN SHOULD not peer with
OLD
>BGP
>speaker;
>           this can easily produce routing loop or loss of ASN value in
>the
>PATH.
>
>Kalpesh> I don't know if I understand your question completely.
However,
>I don't think RFC puts any restriction on NEW BGP speaker with
>non-mappable 4-byte ASN to communicate with OLD & NEW BGP speakers at
>the same time. In your case, NEW speaker w/ ASN 65666 will communicate
>differently with NEW speaker w/ ASN 5000 and OLD speaker w/ ASN 101.
>Each speaker pair should be is treated independently and not confused
>with others.
>
>
[SC>] 
      Please see the previous example  of R1-R2-R3-R4 scenario.

<<Kalpesh>> My previous comment should clarify your doubt.

>
>Kalpesh> NEW1 & NEW2 will exchange update with 4-byte AS-PATH & AGGR
>attributes. However, when NEW2 advertises update to OLD2, it will split
>4-byte AS-PATH attribute into 2-byte AS-PATH and 4-byte AS4-PATH using
>the steps mentioned in RFC. Same goes for AGGR attribute. OLD2 & OLD3
>will treat AS4-PATH & AS4-AGGR attributes as unknown opt-trans and pass
>it further.
>
>
[SC>] 
 
Yes. Again the RFC needs more clarification here, as well. 

<<Kalpesh>> Pl elaborate if you see any ambiguity here.

>Clarification 4
>================
>
>When the NEW BGP speaker has a non-mappable 4byte unique AS number and
>it is
>peering with an OLD BGP
>speaker, only then should it use AS_TRANS in AS_PATH and a
corresponding
>AS4_PATH 4byte
> AS number?
>This should simplify reconstructing the AS number from both AS_PATH and
>AS4_PATH and also
>is in sync with AS4_AGGREGATOR processing as described in the RFC.
>
>Kalpesh> NEW speaker will generate AS4-PATH only if the AS-PATH to be
>sent to OLD peer has at least 1 non-mappable 4-byte ASN. Hence, a NEW
>speaker with 2-byte mappable AS may generate AS4-PATH if reqd.
[SC>] 
[SC>] 
      OK. It is now clarified. 
>
>section 4.2.2:
>"When communicating with an OLD BGP speaker, a NEW speaker MUST send
>   the AS path information in the AS_PATH attribute encoded with
2-octet
>   AS numbers.  The NEW speaker MUST also send the AS path information
>   in the AS4_PATH attribute (encoded with 4-octet AS numbers), except
>   for the case where the entire AS path information is composed of 2-
>   octet AS numbers only.  In this case, the NEW speaker SHOULD NOT
send
>   the AS4_PATH attribute."
>
>The above rule is confusing from the implementation perspective. How
>about
>making it simple by doing the same thing as AS_AGGREGATOR (as follows)
?
>
>  "Similarly, if the NEW speaker has to send the AGGREGATOR attribute,
>   and if the aggregating Autonomous System's AS number is truly 4-
>   octets, then the speaker constructs the AS4_AGGREGATOR attributes by
>   taking the attribute length and attribute value from the AGGREGATOR
>   attribute and placing them into the attribute length and attribute
>   value of the AS4_AGGREGATOR attribute, and sets the AS number field
>   in the existing AGGREGATOR attribute to the reserved AS number,
>   AS_TRANS.  Note that if the AS number is 2-octets only, then the
>   AS4_AGGREGATOR attribute SHOULD NOT be sent."
>
>I assume that "truly 4-octet" means it is higher than 65535.
>
>Kalpesh> I think conditions mentioned for generating AS4-PATH &
AS4-AGGR
>are inherently same. For AS-PATH all ASN in it are considered for AGGR
>the aggregating ASN is considered.
>
[SC>] 
[SC>]  Conditions for AS4_PATH and AS4_AGGR should be the same; again
this
part is a bit unclear in the RFC.


>Yes "truly 4-octet" ASN means ASN > 65535.
[SC>] 
[SC>] This is also subject to interpretation in the RFC.

<<Kalpesh>> I think "truly 4-octet ASN" always means same in RFC. Do you
notice different interpretation in RFC?

>
>Clarification 5
>===================
>
>Should the NEW BGP speaker send a NOTIFICATION with error code =2 and
>subcode=7
>(unsupported capability) when it receives a OPEN message with AS_TRANS
>but
>without
>any corresponding capability message ?
>
>Kalpesh> RFC doesn't discuss how NEW speaker should behave when OLD
>speaker uses AS-TRANS in "My AS" field. Behavior is implementation
>dependent.
>
[SC>] 
[SC>] Please note the above situation can also happen from a faulty or
misbehaving NEW BGP speaker with non-mappable 4b ASN. Since AS_TRANS is
a
reserved value and not assigned to anyone, if the OLD BGP speaker
somehow
uses this value in the OPEN message, it must not be accepted either.
IMHO, this NOTIFICATION case is a valid one and should be documented.

<<Kalpesh>> Again, the behavior is implementation dependent.
-Samita


_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org  Fri Feb  1 12:52:23 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 97FF528C24F;
	Fri,  1 Feb 2008 12:52:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.538
X-Spam-Level: 
X-Spam-Status: No, score=-1.538 tagged_above=-999 required=5
	tests=[AWL=-0.798, BAYES_20=-0.74]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9KlPkKH2AMiA; Fri,  1 Feb 2008 12:52:22 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD65D28C3CA;
	Fri,  1 Feb 2008 12:52:17 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38D4B28C46B
	for <idr@core3.amsl.com>; Fri,  1 Feb 2008 12:52:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iBJwNkLVvmOC for <idr@core3.amsl.com>;
	Fri,  1 Feb 2008 12:52:14 -0800 (PST)
Received: from gateway.ipinfusion.com (mail.ipinfusion.com [65.223.109.2])
	by core3.amsl.com (Postfix) with ESMTP id 232CD28C575
	for <idr@ietf.org>; Fri,  1 Feb 2008 12:50:42 -0800 (PST)
Received: from samitacD600 ([10.10.0.157])
	by gateway.ipinfusion.com (8.11.6/8.11.6) with ESMTP id m11Kq0415533;
	Fri, 1 Feb 2008 12:52:00 -0800
From: "Samita Chakrabarti" <samitac@ipinfusion.com>
To: "'Kalpesh Zinjuwadia'" <kzinjuwadia@force10networks.com>, <idr@ietf.org>, 
	<quaizar.vohra@gmail.com>, <enkechen@cisco.com>
References: <002f01c8647c$9dafb700$9d000a0a@samitacD600>
	<44ED058B21DF294ABE394CABE5C1B52102775B3B@EXCH-CLUSTER-03.force10networks.com>
	<001401c8650b$e8a39760$9d000a0a@samitacD600>
	<44ED058B21DF294ABE394CABE5C1B52101303B07@EXCH-CLUSTER-03.force10networks.com>
Date: Fri, 1 Feb 2008 12:52:10 -0800
Message-ID: <001e01c86514$53cb1ab0$9d000a0a@samitacD600>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AchkfJnFg0bX62edRpC+ThO14/0EDgAB9ayQACBsYzAAAi4IsAAA66Kw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <44ED058B21DF294ABE394CABE5C1B52101303B07@EXCH-CLUSTER-03.force10networks.com>
Subject: Re: [Idr] Comments on RFC4893
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Kalpesh,



>[SC>]  Yes. We are saying the same thing. But the point is that the RFC
>is
>not very clear about sending/receiving "My ASN" value in the OPEN
>message
>and it should be clarified.
>
><<Kalpesh>> I don't think there is any ambiguity in RFC for this. Can
>you elaborate what's not clear to you?
>

[SC>] 
I'd like to see a section on OPEN message on sending and receiving clearly
for example. I am hearing questions and problems in understanding from the
engineers who are implementing this RFC. I have been involved with IETF
process for a long time and wish to see a revision of this RFC which does
not generate clarification questions for those who did not get involved
during the development of this RFC.


-Samita


_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org  Fri Feb  1 13:28:17 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0480E28C1D1;
	Fri,  1 Feb 2008 13:28:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.06
X-Spam-Level: 
X-Spam-Status: No, score=-1.06 tagged_above=-999 required=5 tests=[AWL=-0.744,
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_23=0.6,
	URIBL_RHS_DOB=1.083]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id O2jXf3iMGO5I; Fri,  1 Feb 2008 13:28:15 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B08393A6915;
	Fri,  1 Feb 2008 13:28:15 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EADD33A6915
	for <idr@core3.amsl.com>; Fri,  1 Feb 2008 13:28:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7V+rXk1rDzCm for <idr@core3.amsl.com>;
	Fri,  1 Feb 2008 13:28:14 -0800 (PST)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224])
	by core3.amsl.com (Postfix) with ESMTP id D07443A68A6
	for <idr@ietf.org>; Fri,  1 Feb 2008 13:28:13 -0800 (PST)
Received: by wr-out-0506.google.com with SMTP id 50so1623981wri.25
	for <idr@ietf.org>; Fri, 01 Feb 2008 13:29:48 -0800 (PST)
Received: by 10.142.212.19 with SMTP id k19mr2548222wfg.224.1201901387226;
	Fri, 01 Feb 2008 13:29:47 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Fri, 1 Feb 2008 13:29:47 -0800 (PST)
Message-ID: <77ead0ec0802011329x705024e3ubb514e9556238eb6@mail.gmail.com>
Date: Fri, 1 Feb 2008 13:29:47 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
In-Reply-To: <15B86BC7352F864BB53A47B540C089B604DAB2EE@xmb-rtp-20b.amer.cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<15B86BC7352F864BB53A47B540C089B604DAB2EE@xmb-rtp-20b.amer.cisco.com>
Cc: idr@ietf.org, Jan Novak <jjjnovak@hotmail.com>,
	Ooms Dirk <dirk@onesparrow.com>,
	"Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Rajeev,

I agree the security part of VRF is incomparable. However what about
the use of route distinguisher (RD) when the routes themselves are
unique.

That is the reason the draft does not say it is replacing
BGP-MPLS-IPv6 VPN, it says it could be used as an alternative to
getting the same functionality, without having to actually implement
the entire big peace of code required for the same, with added
policies.

Thanks,
Vishwas

On Feb 1, 2008 12:23 PM, Rajiv Asati (rajiva) <rajiva@cisco.com> wrote:
> Hi Vishwas,
>
> Good discussion.
> It was interesting to see the following excerpt wrt 6VPE -
>
> > become IPv6 and the network may still have IPv4. If the assumption
> > that each device in the IPv6 networks has a Global IPv6 address (not
> > that IPv6 site local has been deprecated), we can do without the
> > entire BGP MPLS IPv6 VPN functionality.
>
> Assuming PE-to-PE tunneling is still in place, yah, you are right from
> the routing perspective in 6VPE. But how would we prohibit one IPv6 site
> communicating with another IPv6 site belonging to different enterprises.
>
> AFAIK, the benefit of having VRF is beyond just the routing. And that's
> one of the key components of BGP IP VPN functionality. 6VPE indeed has
> merits.
>
> Perhaps, you intended to point to something else in BGP IPv6 VPN
> functionality.
>
> Cheers,
> Rajiv
>
>
> > -----Original Message-----
> > From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> > Sent: Thursday, January 31, 2008 10:01 AM
> > To: Jan Novak
> > Cc: idr@ietf.org; Francois Le Faucheur (flefauch); Ooms Dirk
> > Subject: Re: [Idr] 6PE-Alt draft
> >
> > Hi Jan,
> >
> > I am CC'ing the authors of the 6PE draft to get their views. Let me
> > explain the draft in greater detail however.
> >
> > In 6PE, MP-BGP SAFI family label is used to exchange routes between 2
> > 6PE routers (a new AFI/ SAFI combination is defined). Each route is
> > attached with a label (which may be the IPv6 Explicit NULL label). In
> > the data-plane this label is used as the inner label and the other
> > label is the tunnel label, which gets the packet from source PE to
> > destination PE. Once the packet gets to the destination PE, the inner
> > label is looked up and a POP operation is done on it and the IPv6
> > header is looked up in the routing table.
> >
> > With 6PE-Alt, no additional signaling mechanism is required. All we
> > need to do is instead of using the signaled label as the inner label,
> > we use the IPv6 Explicit NULL label. The same operations happen as 6PE
> > without any explicit signaling of the labels with each route. It helps
> > prevent all the excess signaling and still providing the exact same
> > functionality. We are using the meaning implied in the "Explicit NULL
> > Label". We do not need to signal anything here.
> >
> > As an alternate, if you notice in IPv6, the end sites/ devices will
> > become IPv6 and the network may still have IPv4. If the assumption
> > that each device in the IPv6 networks has a Global IPv6 address (not
> > that IPv6 site local has been deprecated), we can do without the
> > entire BGP MPLS IPv6 VPN functionality.
> >
> > Thanks,
> > Vishwas
> >
> > On Jan 31, 2008 6:31 AM, Vishwas Manral
> > <vishwas.ietf@gmail.com> wrote:
> > > Hi Jan,
> > >
> > > You may be missing the scope of the document. There is a
> > discussion in
> > > the v6ops group too which .
> > >
> > > The idea is simple. We do not need to define a new AFI/ SAFI
> > > combination to achieve the 6PE functionality. We can just use the
> > > meaning implied in the IPv6 Explicit NULL label. The 6PE
> > RFC does talk
> > > about allowing signaling for the Explicit NULL label in
> > which case the
> > > dataplane functionality becomes just the same, but in 6PE
> > even that is
> > > signaled using BGP extensions defined in RFC3107.
> > >
> > > Thanks,
> > > Vishwas
> > >
> > >
> > > On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
> > > >
> > > >
> > > > Hi,
> > > >
> > > > Just out of curiosity - lets say you have two IPv4 VPNs with
> > > > overlapping set of Pes and both of them want to provide 6PE
> > > > service.
> > > > When the explicit-null encapsulated packets from two different
> > > > VPNs (but same PE) arrive to the other side PE - how do you
> > > > decide which is which - e.g. which packet should be shipped to
> > > > which VPN ??
> > > >
> > > > Jan
> > > >
> > > >
> > > > _________________________________________________________________
> > > > Telly addicts unite!
> > > > http://www.searchgamesbox.com/tvtown.shtml
> > >
> >
>
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www1.ietf.org/mailman/listinfo/idr
> >
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr



From idr-bounces@ietf.org  Sun Feb  3 08:02:30 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 776AE3A6C8D;
	Sun,  3 Feb 2008 08:02:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[AWL=0.108,
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_23=0.6,
	RCVD_IN_DNSWL_MED=-4, URIBL_RHS_DOB=1.083]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EkyPtz48B15c; Sun,  3 Feb 2008 08:02:29 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3177E3A6C73;
	Sun,  3 Feb 2008 08:02:29 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C4813A6C73
	for <idr@core3.amsl.com>; Sun,  3 Feb 2008 08:02:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nKdan9+dMXR1 for <idr@core3.amsl.com>;
	Sun,  3 Feb 2008 08:02:26 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 167E63A6C6F
	for <idr@ietf.org>; Sun,  3 Feb 2008 08:02:26 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.25,298,1199682000"; d="scan'208";a="85357683"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 03 Feb 2008 11:03:57 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m13G3vqh023843; 
	Sun, 3 Feb 2008 11:03:57 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m13G3ui3010773; 
	Sun, 3 Feb 2008 16:03:57 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 3 Feb 2008 11:03:56 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 3 Feb 2008 11:03:56 -0500
Message-ID: <15B86BC7352F864BB53A47B540C089B604DAB4DB@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <77ead0ec0802011329x705024e3ubb514e9556238eb6@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] 6PE-Alt draft
Thread-Index: AchlGZctdmM8cIfjR2GrfWVeU6o6TQAM3OTw
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 03 Feb 2008 16:03:56.0927 (UTC)
	FILETIME=[619730F0:01C8667E]
Authentication-Results: rtp-dkim-2; header.From=rajiva@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: idr@ietf.org, Jan Novak <jjjnovak@hotmail.com>,
	Ooms Dirk <dirk@onesparrow.com>,
	"Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Vishwas,

> I agree the security part of VRF is incomparable. However what about
> the use of route distinguisher (RD) when the routes themselves are
> unique.

RD is certainly quite useful even if the VPN routes are unique.

Please consider the multi-homed VPN site in a BGP/VPN network having
route reflector(s). Even if the VPN routes (advertised by the
multi-homed VPN site) are unique, without RD, each remote PE routers in
the BGP/VPN network would get only one path to the VPN route (because
the Route Reflector would select and advertise only the bestpath). This
means no traffic loadsharing to the route(s) in multi-homed VPN site.

With RD, the loadsharing can be easily provided, assuming unique RD per
VRF per PE is put in place. This is already a common practice in
deployments out there.

Anyway, we digress from the main point in which your draft is proposing
an alternative to the 6PE, not to the 6VPE. 

Cheers,
Rajiv

PS: This could have also been solved if the BGP route reflector
advertised multiple paths besides the bestpath.


> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com] 
> Sent: Friday, February 01, 2008 4:30 PM
> To: Rajiv Asati (rajiva)
> Cc: Jan Novak; idr@ietf.org; Francois Le Faucheur (flefauch); 
> Ooms Dirk
> Subject: Re: [Idr] 6PE-Alt draft
> 
> Hi Rajeev,
> 
> I agree the security part of VRF is incomparable. However what about
> the use of route distinguisher (RD) when the routes themselves are
> unique.
> 
> That is the reason the draft does not say it is replacing
> BGP-MPLS-IPv6 VPN, it says it could be used as an alternative to
> getting the same functionality, without having to actually implement
> the entire big peace of code required for the same, with added
> policies.
> 
> Thanks,
> Vishwas
> 
> On Feb 1, 2008 12:23 PM, Rajiv Asati (rajiva) 
> <rajiva@cisco.com> wrote:
> > Hi Vishwas,
> >
> > Good discussion.
> > It was interesting to see the following excerpt wrt 6VPE -
> >
> > > become IPv6 and the network may still have IPv4. If the assumption
> > > that each device in the IPv6 networks has a Global IPv6 
> address (not
> > > that IPv6 site local has been deprecated), we can do without the
> > > entire BGP MPLS IPv6 VPN functionality.
> >
> > Assuming PE-to-PE tunneling is still in place, yah, you are 
> right from
> > the routing perspective in 6VPE. But how would we prohibit 
> one IPv6 site
> > communicating with another IPv6 site belonging to different 
> enterprises.
> >
> > AFAIK, the benefit of having VRF is beyond just the 
> routing. And that's
> > one of the key components of BGP IP VPN functionality. 6VPE 
> indeed has
> > merits.
> >
> > Perhaps, you intended to point to something else in BGP IPv6 VPN
> > functionality.
> >
> > Cheers,
> > Rajiv
> >
> >
> > > -----Original Message-----
> > > From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> > > Sent: Thursday, January 31, 2008 10:01 AM
> > > To: Jan Novak
> > > Cc: idr@ietf.org; Francois Le Faucheur (flefauch); Ooms Dirk
> > > Subject: Re: [Idr] 6PE-Alt draft
> > >
> > > Hi Jan,
> > >
> > > I am CC'ing the authors of the 6PE draft to get their 
> views. Let me
> > > explain the draft in greater detail however.
> > >
> > > In 6PE, MP-BGP SAFI family label is used to exchange 
> routes between 2
> > > 6PE routers (a new AFI/ SAFI combination is defined). 
> Each route is
> > > attached with a label (which may be the IPv6 Explicit 
> NULL label). In
> > > the data-plane this label is used as the inner label and the other
> > > label is the tunnel label, which gets the packet from source PE to
> > > destination PE. Once the packet gets to the destination 
> PE, the inner
> > > label is looked up and a POP operation is done on it and the IPv6
> > > header is looked up in the routing table.
> > >
> > > With 6PE-Alt, no additional signaling mechanism is 
> required. All we
> > > need to do is instead of using the signaled label as the 
> inner label,
> > > we use the IPv6 Explicit NULL label. The same operations 
> happen as 6PE
> > > without any explicit signaling of the labels with each 
> route. It helps
> > > prevent all the excess signaling and still providing the 
> exact same
> > > functionality. We are using the meaning implied in the 
> "Explicit NULL
> > > Label". We do not need to signal anything here.
> > >
> > > As an alternate, if you notice in IPv6, the end sites/ 
> devices will
> > > become IPv6 and the network may still have IPv4. If the assumption
> > > that each device in the IPv6 networks has a Global IPv6 
> address (not
> > > that IPv6 site local has been deprecated), we can do without the
> > > entire BGP MPLS IPv6 VPN functionality.
> > >
> > > Thanks,
> > > Vishwas
> > >
> > > On Jan 31, 2008 6:31 AM, Vishwas Manral
> > > <vishwas.ietf@gmail.com> wrote:
> > > > Hi Jan,
> > > >
> > > > You may be missing the scope of the document. There is a
> > > discussion in
> > > > the v6ops group too which .
> > > >
> > > > The idea is simple. We do not need to define a new AFI/ SAFI
> > > > combination to achieve the 6PE functionality. We can 
> just use the
> > > > meaning implied in the IPv6 Explicit NULL label. The 6PE
> > > RFC does talk
> > > > about allowing signaling for the Explicit NULL label in
> > > which case the
> > > > dataplane functionality becomes just the same, but in 6PE
> > > even that is
> > > > signaled using BGP extensions defined in RFC3107.
> > > >
> > > > Thanks,
> > > > Vishwas
> > > >
> > > >
> > > > On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > Just out of curiosity - lets say you have two IPv4 VPNs with
> > > > > overlapping set of Pes and both of them want to provide 6PE
> > > > > service.
> > > > > When the explicit-null encapsulated packets from two different
> > > > > VPNs (but same PE) arrive to the other side PE - how do you
> > > > > decide which is which - e.g. which packet should be shipped to
> > > > > which VPN ??
> > > > >
> > > > > Jan
> > > > >
> > > > >
> > > > > 
> _________________________________________________________________
> > > > > Telly addicts unite!
> > > > > http://www.searchgamesbox.com/tvtown.shtml
> > > >
> > >
> >
> > > _______________________________________________
> > > Idr mailing list
> > > Idr@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/idr
> > >
> >
> 
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Sun Feb  3 13:29:08 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D39E3A6D4B;
	Sun,  3 Feb 2008 13:29:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level: 
X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[AWL=1.207,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vBo7oWhwKaph; Sun,  3 Feb 2008 13:29:07 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84A283A6D34;
	Sun,  3 Feb 2008 13:29:02 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D63843A6D26
	for <idr@core3.amsl.com>; Sun,  3 Feb 2008 13:29:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QQWIVIf91YOw for <idr@core3.amsl.com>;
	Sun,  3 Feb 2008 13:29:00 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175])
	by core3.amsl.com (Postfix) with ESMTP id 994773A6D48
	for <idr@ietf.org>; Sun,  3 Feb 2008 13:28:36 -0800 (PST)
Received: from source ([66.129.224.36]) by exprod7ob111.postini.com
	([64.18.6.12]) with SMTP; Sun, 03 Feb 2008 13:29:51 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Sun, 3 Feb 2008 13:28:15 -0800
Received: from [172.26.250.99] ([172.26.250.99])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m13LSDq27336;
	Sun, 3 Feb 2008 13:28:13 -0800 (PST)
	(envelope-from raszuk@juniper.net)
Message-ID: <47A631EC.80703@juniper.net>
Date: Sun, 03 Feb 2008 13:28:12 -0800
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl><77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com><77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com><BAY120-W1856D92C0C10B950241B43D8370@phx.gbl><77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com><20080201090733.GA1929@nic.dtag.de>
	<77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
In-Reply-To: <77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
X-OriginalArrivalTime: 03 Feb 2008 21:28:15.0548 (UTC)
	FILETIME=[AFD51FC0:01C866AB]
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Vishwas,

 > The P device works on the outer Tunnel label and its functionality
 > will not change in my view.

I must say that your view here is incorrect.

There are hardware implementations just like Martin pointed out which 
take not the only top most but _entire_label_stack_ in the mpls packets 
into considerations when hashing in P routers for load sharing purposes.

As far as I can see your proposal breaks this as the second label will 
be always the same thus all packets going to single PE will always take 
the same path.

To address this you would need to change implementations of those P 
routers mpls switching vectors to also consider IPv6 header which is a 
non starter operationally.

Cheers,
R.

> Hi Martin,
> 
> The load sharing and everything else on the of P devices will still
> work the same way. So we would have for example LDP running on the P
> routers giving out labels for FEC's just the same way. The P device
> works on the outer Tunnel label and its functionality will not change
> in my view.
> 
> There is a case of having different labels for preventing one IPv6
> lookup in some cases but in case we had the ECMP case we would have to
> use the IPv6 header lookup and use the inner label as an IPv6 Explicit
> NULL label.
> 
> Do let me know if I missed the point?
> 
> Thanks,
> Vishwas

_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Sun Feb  3 14:53:35 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0060B3A6D4D;
	Sun,  3 Feb 2008 14:53:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.206
X-Spam-Level: 
X-Spam-Status: No, score=-2.206 tagged_above=-999 required=5 tests=[AWL=0.393,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qmSW5thqX+kG; Sun,  3 Feb 2008 14:53:34 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 109A63A6D1A;
	Sun,  3 Feb 2008 14:53:34 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 460A13A6D1A
	for <idr@core3.amsl.com>; Sun,  3 Feb 2008 14:53:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id d0WKORzYjuPn for <idr@core3.amsl.com>;
	Sun,  3 Feb 2008 14:53:31 -0800 (PST)
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183])
	by core3.amsl.com (Postfix) with ESMTP id 68B763A6C71
	for <idr@ietf.org>; Sun,  3 Feb 2008 14:53:31 -0800 (PST)
Received: by py-out-1112.google.com with SMTP id x19so2018746pyg.24
	for <idr@ietf.org>; Sun, 03 Feb 2008 14:55:06 -0800 (PST)
Received: by 10.142.156.2 with SMTP id d2mr3122334wfe.219.1202079305755;
	Sun, 03 Feb 2008 14:55:05 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Sun, 3 Feb 2008 14:55:05 -0800 (PST)
Message-ID: <77ead0ec0802031455s300978bfn8d10b142376f315@mail.gmail.com>
Date: Sun, 3 Feb 2008 14:55:05 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: raszuk@juniper.net
In-Reply-To: <47A631EC.80703@juniper.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
	<20080201090733.GA1929@nic.dtag.de>
	<77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
	<47A631EC.80703@juniper.net>
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

 Hi Robert/ Martin,

That is an interesting point you bring out.  What you say does make sense.

I agree if load balancing is based on the labels it will not help load
share in case of 6PE-Alt - if we use a constant label. Anyway I would
assume the load sharing mechanism is configurable (what fields to use
to hash) and works within the scope of the router.

Thanks,
Vishwas

On Feb 3, 2008 1:28 PM, Robert Raszuk <raszuk@juniper.net> wrote:
> Hi Vishwas,
>
>  > The P device works on the outer Tunnel label and its functionality
>  > will not change in my view.
>
> I must say that your view here is incorrect.
>
> There are hardware implementations just like Martin pointed out which
> take not the only top most but _entire_label_stack_ in the mpls packets
> into considerations when hashing in P routers for load sharing purposes.
>
> As far as I can see your proposal breaks this as the second label will
> be always the same thus all packets going to single PE will always take
> the same path.
>
> To address this you would need to change implementations of those P
> routers mpls switching vectors to also consider IPv6 header which is a
> non starter operationally.
>
> Cheers,
> R.
>
>
> > Hi Martin,
> >
> > The load sharing and everything else on the of P devices will still
> > work the same way. So we would have for example LDP running on the P
> > routers giving out labels for FEC's just the same way. The P device
> > works on the outer Tunnel label and its functionality will not change
> > in my view.
> >
> > There is a case of having different labels for preventing one IPv6
> > lookup in some cases but in case we had the ECMP case we would have to
> > use the IPv6 header lookup and use the inner label as an IPv6 Explicit
> > NULL label.
> >
> > Do let me know if I missed the point?
> >
> > Thanks,
> > Vishwas
>
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Sun Feb  3 15:02:01 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C5FBC3A6D39;
	Sun,  3 Feb 2008 15:02:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.297
X-Spam-Level: 
X-Spam-Status: No, score=-6.297 tagged_above=-999 required=5 tests=[AWL=0.302,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kHYGUgG+fR0x; Sun,  3 Feb 2008 15:02:00 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4EF73A6D50;
	Sun,  3 Feb 2008 15:02:00 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C759A3A6D39
	for <idr@core3.amsl.com>; Sun,  3 Feb 2008 15:01:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mhcKnkBU0UqE for <idr@core3.amsl.com>;
	Sun,  3 Feb 2008 15:01:58 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159])
	by core3.amsl.com (Postfix) with ESMTP id E28393A6C98
	for <idr@ietf.org>; Sun,  3 Feb 2008 15:01:53 -0800 (PST)
Received: from source ([66.129.224.36]) by exprod7ob103.postini.com
	([64.18.6.12]) with SMTP; Sun, 03 Feb 2008 15:03:29 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 3 Feb 2008 15:02:21 -0800
Received: from [172.26.250.99] ([172.26.250.99])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m13N2Jq42262;
	Sun, 3 Feb 2008 15:02:19 -0800 (PST)
	(envelope-from raszuk@juniper.net)
Message-ID: <47A647FA.9040909@juniper.net>
Date: Sun, 03 Feb 2008 15:02:18 -0800
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
	<20080201090733.GA1929@nic.dtag.de>
	<77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
	<47A631EC.80703@juniper.net>
	<77ead0ec0802031455s300978bfn8d10b142376f315@mail.gmail.com>
In-Reply-To: <77ead0ec0802031455s300978bfn8d10b142376f315@mail.gmail.com>
X-OriginalArrivalTime: 03 Feb 2008 23:02:21.0822 (UTC)
	FILETIME=[D54629E0:01C866B8]
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Vishwas,

Unfortunately it is not configurable ... as it is done at the forwarding 
layer in hardware ASICs in some implementations I am familiar with.

In fact some just hash on first and last label in stack some indeed 
could hash only on first two or three and some could go up to the IP 
header (if this is IP which is a big question at the P router).

Cheers,
R.

> 
>  Hi Robert/ Martin,
> 
> That is an interesting point you bring out.  What you say does make sense.
> 
> I agree if load balancing is based on the labels it will not help load
> share in case of 6PE-Alt - if we use a constant label. Anyway I would
> assume the load sharing mechanism is configurable (what fields to use
> to hash) and works within the scope of the router.
> 
> Thanks,
> Vishwas
> 
> On Feb 3, 2008 1:28 PM, Robert Raszuk <raszuk@juniper.net> wrote:
>  > Hi Vishwas,
>  >
>  >  > The P device works on the outer Tunnel label and its functionality
>  >  > will not change in my view.
>  >
>  > I must say that your view here is incorrect.
>  >
>  > There are hardware implementations just like Martin pointed out which
>  > take not the only top most but _entire_label_stack_ in the mpls packets
>  > into considerations when hashing in P routers for load sharing purposes.
>  >
>  > As far as I can see your proposal breaks this as the second label will
>  > be always the same thus all packets going to single PE will always take
>  > the same path.
>  >
>  > To address this you would need to change implementations of those P
>  > routers mpls switching vectors to also consider IPv6 header which is a
>  > non starter operationally.
>  >
>  > Cheers,
>  > R.
>  >
>  >
>  > > Hi Martin,
>  > >
>  > > The load sharing and everything else on the of P devices will still
>  > > work the same way. So we would have for example LDP running on the P
>  > > routers giving out labels for FEC's just the same way. The P device
>  > > works on the outer Tunnel label and its functionality will not change
>  > > in my view.
>  > >
>  > > There is a case of having different labels for preventing one IPv6
>  > > lookup in some cases but in case we had the ECMP case we would have to
>  > > use the IPv6 header lookup and use the inner label as an IPv6 Explicit
>  > > NULL label.
>  > >
>  > > Do let me know if I missed the point?
>  > >
>  > > Thanks,
>  > > Vishwas
>  >
>  >
> 

_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Sun Feb  3 15:43:42 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EE8373A6D4E;
	Sun,  3 Feb 2008 15:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.156
X-Spam-Level: 
X-Spam-Status: No, score=-2.156 tagged_above=-999 required=5 tests=[AWL=0.443,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Wy8JKAiIxWNp; Sun,  3 Feb 2008 15:43:42 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04F253A6CC0;
	Sun,  3 Feb 2008 15:43:42 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B481C3A6CC0
	for <idr@core3.amsl.com>; Sun,  3 Feb 2008 15:43:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MlNt4Yu9wNW8 for <idr@core3.amsl.com>;
	Sun,  3 Feb 2008 15:43:39 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180])
	by core3.amsl.com (Postfix) with ESMTP id D3F473A6CAD
	for <idr@ietf.org>; Sun,  3 Feb 2008 15:43:39 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id k40so4185466wah.25
	for <idr@ietf.org>; Sun, 03 Feb 2008 15:45:14 -0800 (PST)
Received: by 10.142.188.4 with SMTP id l4mr3134477wff.151.1202082314517;
	Sun, 03 Feb 2008 15:45:14 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Sun, 3 Feb 2008 15:45:14 -0800 (PST)
Message-ID: <77ead0ec0802031545k687fc293jfa9fd7dd9ea8da6e@mail.gmail.com>
Date: Sun, 3 Feb 2008 15:45:14 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: raszuk@juniper.net
In-Reply-To: <47A647FA.9040909@juniper.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
	<20080201090733.GA1929@nic.dtag.de>
	<77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
	<47A631EC.80703@juniper.net>
	<77ead0ec0802031455s300978bfn8d10b142376f315@mail.gmail.com>
	<47A647FA.9040909@juniper.net>
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Robert,

I am unaware of the ASIC's you work on, but I guess the entire idea is
that micro-flows do not get reordered and yet use load balancing.

I will update the 6PE-Alt draft with the information you have given.

Thanks,
Vishwas

On Feb 3, 2008 3:02 PM, Robert Raszuk <raszuk@juniper.net> wrote:
> Hi Vishwas,
>
> Unfortunately it is not configurable ... as it is done at the forwarding
> layer in hardware ASICs in some implementations I am familiar with.
>
> In fact some just hash on first and last label in stack some indeed
> could hash only on first two or three and some could go up to the IP
> header (if this is IP which is a big question at the P router).
>
> Cheers,
> R.
>
>
> >
> >  Hi Robert/ Martin,
> >
> > That is an interesting point you bring out.  What you say does make sense.
> >
> > I agree if load balancing is based on the labels it will not help load
> > share in case of 6PE-Alt - if we use a constant label. Anyway I would
> > assume the load sharing mechanism is configurable (what fields to use
> > to hash) and works within the scope of the router.
> >
> > Thanks,
> > Vishwas
> >
> > On Feb 3, 2008 1:28 PM, Robert Raszuk <raszuk@juniper.net> wrote:
> >  > Hi Vishwas,
> >  >
> >  >  > The P device works on the outer Tunnel label and its functionality
> >  >  > will not change in my view.
> >  >
> >  > I must say that your view here is incorrect.
> >  >
> >  > There are hardware implementations just like Martin pointed out which
> >  > take not the only top most but _entire_label_stack_ in the mpls packets
> >  > into considerations when hashing in P routers for load sharing purposes.
> >  >
> >  > As far as I can see your proposal breaks this as the second label will
> >  > be always the same thus all packets going to single PE will always take
> >  > the same path.
> >  >
> >  > To address this you would need to change implementations of those P
> >  > routers mpls switching vectors to also consider IPv6 header which is a
> >  > non starter operationally.
> >  >
> >  > Cheers,
> >  > R.
> >  >
> >  >
> >  > > Hi Martin,
> >  > >
> >  > > The load sharing and everything else on the of P devices will still
> >  > > work the same way. So we would have for example LDP running on the P
> >  > > routers giving out labels for FEC's just the same way. The P device
> >  > > works on the outer Tunnel label and its functionality will not change
> >  > > in my view.
> >  > >
> >  > > There is a case of having different labels for preventing one IPv6
> >  > > lookup in some cases but in case we had the ECMP case we would have to
> >  > > use the IPv6 header lookup and use the inner label as an IPv6 Explicit
> >  > > NULL label.
> >  > >
> >  > > Do let me know if I missed the point?
> >  > >
> >  > > Thanks,
> >  > > Vishwas
> >  >
> >  >
> >
>
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Sun Feb  3 19:58:39 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7B3C3A6DA9;
	Sun,  3 Feb 2008 19:58:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.266
X-Spam-Level: 
X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[AWL=0.333,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id W51Sx3VHEto8; Sun,  3 Feb 2008 19:58:38 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B6C6E3A6CEC;
	Sun,  3 Feb 2008 19:58:38 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4EB53A6CEC
	for <idr@core3.amsl.com>; Sun,  3 Feb 2008 19:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j65LD9OYoL30 for <idr@core3.amsl.com>;
	Sun,  3 Feb 2008 19:58:37 -0800 (PST)
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181])
	by core3.amsl.com (Postfix) with ESMTP id CA2523A6A82
	for <idr@ietf.org>; Sun,  3 Feb 2008 19:58:36 -0800 (PST)
Received: by py-out-1112.google.com with SMTP id x19so2105836pyg.24
	for <idr@ietf.org>; Sun, 03 Feb 2008 20:00:11 -0800 (PST)
Received: by 10.142.232.20 with SMTP id e20mr3170475wfh.59.1202097610838;
	Sun, 03 Feb 2008 20:00:10 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Sun, 3 Feb 2008 20:00:10 -0800 (PST)
Message-ID: <77ead0ec0802032000p4b09c2e4j4f6bbc804a8526a6@mail.gmail.com>
Date: Sun, 3 Feb 2008 20:00:10 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: raszuk@juniper.net
In-Reply-To: <47A647FA.9040909@juniper.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
	<20080201090733.GA1929@nic.dtag.de>
	<77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
	<47A631EC.80703@juniper.net>
	<77ead0ec0802031455s300978bfn8d10b142376f315@mail.gmail.com>
	<47A647FA.9040909@juniper.net>
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi  Robert/ Martin,

One more question.

So are you saying the implementations you know provides a separate
label for each route, or is it per peer?  I guess it is the later, but
just want to reconfirm the same.

Thanks,
Vishwas

On Feb 3, 2008 3:02 PM, Robert Raszuk <raszuk@juniper.net> wrote:
> Hi Vishwas,
>
> Unfortunately it is not configurable ... as it is done at the forwarding
> layer in hardware ASICs in some implementations I am familiar with.
>
> In fact some just hash on first and last label in stack some indeed
> could hash only on first two or three and some could go up to the IP
> header (if this is IP which is a big question at the P router).
>
> Cheers,
> R.
>
>
> >
> >  Hi Robert/ Martin,
> >
> > That is an interesting point you bring out.  What you say does make sense.
> >
> > I agree if load balancing is based on the labels it will not help load
> > share in case of 6PE-Alt - if we use a constant label. Anyway I would
> > assume the load sharing mechanism is configurable (what fields to use
> > to hash) and works within the scope of the router.
> >
> > Thanks,
> > Vishwas
> >
> > On Feb 3, 2008 1:28 PM, Robert Raszuk <raszuk@juniper.net> wrote:
> >  > Hi Vishwas,
> >  >
> >  >  > The P device works on the outer Tunnel label and its functionality
> >  >  > will not change in my view.
> >  >
> >  > I must say that your view here is incorrect.
> >  >
> >  > There are hardware implementations just like Martin pointed out which
> >  > take not the only top most but _entire_label_stack_ in the mpls packets
> >  > into considerations when hashing in P routers for load sharing purposes.
> >  >
> >  > As far as I can see your proposal breaks this as the second label will
> >  > be always the same thus all packets going to single PE will always take
> >  > the same path.
> >  >
> >  > To address this you would need to change implementations of those P
> >  > routers mpls switching vectors to also consider IPv6 header which is a
> >  > non starter operationally.
> >  >
> >  > Cheers,
> >  > R.
> >  >
> >  >
> >  > > Hi Martin,
> >  > >
> >  > > The load sharing and everything else on the of P devices will still
> >  > > work the same way. So we would have for example LDP running on the P
> >  > > routers giving out labels for FEC's just the same way. The P device
> >  > > works on the outer Tunnel label and its functionality will not change
> >  > > in my view.
> >  > >
> >  > > There is a case of having different labels for preventing one IPv6
> >  > > lookup in some cases but in case we had the ECMP case we would have to
> >  > > use the IPv6 header lookup and use the inner label as an IPv6 Explicit
> >  > > NULL label.
> >  > >
> >  > > Do let me know if I missed the point?
> >  > >
> >  > > Thanks,
> >  > > Vishwas
> >  >
> >  >
> >
>
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Sun Feb  3 23:50:52 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3DE763A6DE7;
	Sun,  3 Feb 2008 23:50:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.498
X-Spam-Level: 
X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[AWL=0.101,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0n0Bl0WtcRck; Sun,  3 Feb 2008 23:50:51 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 672BC3A6DC0;
	Sun,  3 Feb 2008 23:50:51 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1687C3A6C96
	for <idr@core3.amsl.com>; Sun,  3 Feb 2008 23:50:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8hB6SoO8HB7U for <idr@core3.amsl.com>;
	Sun,  3 Feb 2008 23:50:49 -0800 (PST)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155])
	by core3.amsl.com (Postfix) with ESMTP id A97063A6DC0
	for <idr@ietf.org>; Sun,  3 Feb 2008 23:50:45 -0800 (PST)
Received: from source ([66.129.224.36]) by exprod7ob101.postini.com
	([64.18.6.12]) with SMTP; Sun, 03 Feb 2008 23:52:07 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Sun, 3 Feb 2008 23:49:50 -0800
Received: from [172.26.250.99] ([172.26.250.99])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m147nmq40988;
	Sun, 3 Feb 2008 23:49:49 -0800 (PST)
	(envelope-from raszuk@juniper.net)
Message-ID: <47A6C39A.2010709@juniper.net>
Date: Sun, 03 Feb 2008 23:49:46 -0800
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
	<20080201090733.GA1929@nic.dtag.de>
	<77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
	<47A631EC.80703@juniper.net>
	<77ead0ec0802031455s300978bfn8d10b142376f315@mail.gmail.com>
	<47A647FA.9040909@juniper.net>
	<77ead0ec0802032000p4b09c2e4j4f6bbc804a8526a6@mail.gmail.com>
In-Reply-To: <77ead0ec0802032000p4b09c2e4j4f6bbc804a8526a6@mail.gmail.com>
X-OriginalArrivalTime: 04 Feb 2008 07:49:50.0825 (UTC)
	FILETIME=[858CC590:01C86702]
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Vishwas,

What VPN label allocation scheme to use is often left to the operator by 
the CLI. From P router load balancing point of view the worst is per vrf 
granularity ... your draft proposes per PE.

Cheers,
R.

> Hi  Robert/ Martin,
> 
> One more question.
> 
> So are you saying the implementations you know provides a separate
> label for each route, or is it per peer?  I guess it is the later, but
> just want to reconfirm the same.
> 
> Thanks,
> Vishwas
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Tue Feb  5 15:50:14 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 039C23A6821;
	Tue,  5 Feb 2008 15:50:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.63
X-Spam-Level: 
X-Spam-Status: No, score=-5.63 tagged_above=-999 required=5 tests=[AWL=-0.323,
	BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CX61fclb5MhM; Tue,  5 Feb 2008 15:50:13 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 702823A6A11;
	Tue,  5 Feb 2008 15:47:04 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5349F3A6A11
	for <idr@core3.amsl.com>; Tue,  5 Feb 2008 15:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1Kd96CK+i5Me for <idr@core3.amsl.com>;
	Tue,  5 Feb 2008 15:47:02 -0800 (PST)
Received: from mx4.ca.afilias.info (vgateway.libertyrms.info [207.219.45.62])
	by core3.amsl.com (Postfix) with ESMTP id C0D293A6CDE
	for <idr@ietf.org>; Tue,  5 Feb 2008 15:45:31 -0800 (PST)
Received: from briand-vpn.int.libertyrms.com ([10.1.7.90])
	by mx4.ca.afilias.info with esmtp (Exim 4.22) id 1JMXVI-0004WI-8e
	for idr@ietf.org; Tue, 05 Feb 2008 18:47:04 -0500
Message-ID: <47A8F56C.4080608@ca.afilias.info>
Date: Tue, 05 Feb 2008 18:46:52 -0500
From: Brian Dickson <briand@ca.afilias.info>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
CC: idr@ietf.org
References: <002f01c8647c$9dafb700$9d000a0a@samitacD600>	<44ED058B21DF294ABE394CABE5C1B52102775B3B@EXCH-CLUSTER-03.force10networks.com>	<001401c8650b$e8a39760$9d000a0a@samitacD600>	<44ED058B21DF294ABE394CABE5C1B52101303B07@EXCH-CLUSTER-03.force10networks.com>	<001e01c86514$53cb1ab0$9d000a0a@samitacD600>
	<47A7B1F2.6020104@apnic.net>
In-Reply-To: <47A7B1F2.6020104@apnic.net>
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
Subject: [Idr] New ID and request for time slot
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

I've put together a new draft, with the (ambitious!) goal of addressing 
a few of the outstanding BGP issues:
- wedgies
- persistent oscillations
- path hunting.

I've included most of the supporting examples for the first two, which 
are clearly smaller in scope.

I'll be doing more work (between now and IETF-71) to produce example 
cases for the path hunting problem (w.r.t. the new draft).
My hope is this can reduce the level of induced churn caused by path 
hunting.

I'd respectfully request a slot in Philly to present this material.

Comments are obviously welcome, as well as any pointers to tools for 
evaluating path hunting behavior.

Obviously, adding new attributes isn't something to be done lightly, but 
if the results are compelling enough, it may be an appropriate path to take.

I'd appreciate it if we can first look to see if the results are 
compelling, before getting into whether they are compelling enough. :-)

Thanks,

Brian Dickson

> A new version of I-D, draft-dickson-idr-second-best-backup-00.txt has 
> been successfuly submitted by Brian Dickson and posted to the IETF 
> repository.
>
> Filename:        draft-dickson-idr-second-best-backup
> Revision:        00
> Title:           Enhanced BGP Capabilities for Exchanging Second-best 
> and Back-up Paths
> Creation_date:   2008-02-05
> WG ID:           Independent Submission
> Number_of_pages: 20
>
> Abstract:
> This Internet Draft describes an enhanced way to exchange prefix
> information, to permit multiple copies of a prefix with different
> paths to be announced and withdrawn.
>
> This negotiated capability provides faster local (inter-AS) and
> global (intra-AS) convergence, reduces path-hunting, improves route-
> reflector behaviour, including eliminating both persistent
> oscillations and BGP "wedgies".
>
> Additional prefix instances have new optional transtive BGP
> attributes, to control path selection.
>
> Withdrawl of prefixes will require path attributes.
>
> Benefits are seen both when deployed intra-AS, and on inter-AS
> peering.
> Author's Note
>
> This Internet Draft is intended to result in this draft or a related
> draft(s) being placed on the Standards Track for idr.

_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Tue Feb  5 16:22:12 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 151FE3A6885;
	Tue,  5 Feb 2008 16:22:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.639
X-Spam-Level: 
X-Spam-Status: No, score=-5.639 tagged_above=-999 required=5 tests=[AWL=0.960,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cH4Q9wdM4uVk; Tue,  5 Feb 2008 16:22:11 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77B543A67EE;
	Tue,  5 Feb 2008 16:22:10 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BA6A3A6780
	for <idr@core3.amsl.com>; Tue,  5 Feb 2008 16:22:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id g2rNwNmEZ4Hv for <idr@core3.amsl.com>;
	Tue,  5 Feb 2008 16:22:07 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 6169C3A6886
	for <idr@ietf.org>; Tue,  5 Feb 2008 16:21:20 -0800 (PST)
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 05 Feb 2008 19:22:53 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m160MqFc017203; 
	Tue, 5 Feb 2008 19:22:52 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m160MqMR029809; 
	Wed, 6 Feb 2008 00:22:52 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Feb 2008 19:22:52 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 5 Feb 2008 19:22:52 -0500
Message-ID: <15B86BC7352F864BB53A47B540C089B604E0BABF@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <47A8F56C.4080608@ca.afilias.info>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] New ID and request for time slot
Thread-Index: AchoUiA3Z9aRUhm4QSyAKPineHwpWgAAs5gw
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Brian Dickson" <briand@ca.afilias.info>
X-OriginalArrivalTime: 06 Feb 2008 00:22:52.0575 (UTC)
	FILETIME=[697412F0:01C86856]
Authentication-Results: rtp-dkim-1; header.From=rajiva@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: idr@ietf.org
Subject: Re: [Idr] New ID and request for time slot
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Brian,

The draft-dickson-idr-second-best-backup is not yet available for
reading. I am certainly curious about whether and how it differs from
the add-paths draft -
http://tools.ietf.org/html/draft-walton-bgp-add-paths-05

Cheers,
Rajiv 

> -----Original Message-----
> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On 
> Behalf Of Brian Dickson
> Sent: Tuesday, February 05, 2008 6:47 PM
> Cc: idr@ietf.org
> Subject: [Idr] New ID and request for time slot
> 
> I've put together a new draft, with the (ambitious!) goal of 
> addressing 
> a few of the outstanding BGP issues:
> - wedgies
> - persistent oscillations
> - path hunting.
> 
> I've included most of the supporting examples for the first 
> two, which 
> are clearly smaller in scope.
> 
> I'll be doing more work (between now and IETF-71) to produce example 
> cases for the path hunting problem (w.r.t. the new draft).
> My hope is this can reduce the level of induced churn caused by path 
> hunting.
> 
> I'd respectfully request a slot in Philly to present this material.
> 
> Comments are obviously welcome, as well as any pointers to tools for 
> evaluating path hunting behavior.
> 
> Obviously, adding new attributes isn't something to be done 
> lightly, but 
> if the results are compelling enough, it may be an 
> appropriate path to take.
> 
> I'd appreciate it if we can first look to see if the results are 
> compelling, before getting into whether they are compelling 
> enough. :-)
> 
> Thanks,
> 
> Brian Dickson
> 
> > A new version of I-D, 
> draft-dickson-idr-second-best-backup-00.txt has 
> > been successfuly submitted by Brian Dickson and posted to the IETF 
> > repository.
> >
> > Filename:        draft-dickson-idr-second-best-backup
> > Revision:        00
> > Title:           Enhanced BGP Capabilities for Exchanging 
> Second-best 
> > and Back-up Paths
> > Creation_date:   2008-02-05
> > WG ID:           Independent Submission
> > Number_of_pages: 20
> >
> > Abstract:
> > This Internet Draft describes an enhanced way to exchange prefix
> > information, to permit multiple copies of a prefix with different
> > paths to be announced and withdrawn.
> >
> > This negotiated capability provides faster local (inter-AS) and
> > global (intra-AS) convergence, reduces path-hunting, improves route-
> > reflector behaviour, including eliminating both persistent
> > oscillations and BGP "wedgies".
> >
> > Additional prefix instances have new optional transtive BGP
> > attributes, to control path selection.
> >
> > Withdrawl of prefixes will require path attributes.
> >
> > Benefits are seen both when deployed intra-AS, and on inter-AS
> > peering.
> > Author's Note
> >
> > This Internet Draft is intended to result in this draft or a related
> > draft(s) being placed on the Standards Track for idr.
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> http://www.ietf.org/mailman/listinfo/idr
> 
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Tue Feb  5 16:51:59 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC5893A6843;
	Tue,  5 Feb 2008 16:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.276
X-Spam-Level: 
X-Spam-Status: No, score=-6.276 tagged_above=-999 required=5 tests=[AWL=0.323,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gajLBu76ZRGL; Tue,  5 Feb 2008 16:51:58 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D3EF3A67B7;
	Tue,  5 Feb 2008 16:51:58 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 57B673A63D3
	for <idr@core3.amsl.com>; Tue,  5 Feb 2008 16:51:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1qloW-Qm4r4I for <idr@core3.amsl.com>;
	Tue,  5 Feb 2008 16:51:55 -0800 (PST)
Received: from mx4.ca.afilias.info (vgateway.libertyrms.info [207.219.45.62])
	by core3.amsl.com (Postfix) with ESMTP id E91D83A6833
	for <idr@ietf.org>; Tue,  5 Feb 2008 16:51:26 -0800 (PST)
Received: from briand-vpn.int.libertyrms.com ([10.1.7.90])
	by mx4.ca.afilias.info with esmtp (Exim 4.22)
	id 1JMYX4-0007rM-Pu; Tue, 05 Feb 2008 19:52:58 -0500
Message-ID: <47A904DF.1040908@ca.afilias.info>
Date: Tue, 05 Feb 2008 19:52:47 -0500
From: Brian Dickson <briand@ca.afilias.info>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
References: <15B86BC7352F864BB53A47B540C089B604E0BABF@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <15B86BC7352F864BB53A47B540C089B604E0BABF@xmb-rtp-20b.amer.cisco.com>
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
Cc: idr@ietf.org
Subject: Re: [Idr] New ID and request for time slot
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Rajiv Asati (rajiva) wrote:
> Hi Brian,
>
> The draft-dickson-idr-second-best-backup is not yet available for
> reading. 
Here's the link to the -00 version:
http://www.ietf.org/internet-drafts/draft-dickson-idr-second-best-backup-00.txt
> I am certainly curious about whether and how it differs from
> the add-paths draft -
> http://tools.ietf.org/html/draft-walton-bgp-add-paths-05
>
>   
Well, a quick review of add-paths seems to indicate several important 
differences:
- add-paths appears limited in scope to route-reflectors, but does so 
very well
- second-best-backup focuses more on inter-AS effects and direct 
intra-AS behavior

I expect that the two would in fact complement each other very effectively.

How exactly they would/could be merged may not be obvious just yet, but 
I don't see
any fundamental hurdles.

Certainly, it points to lots of things there that I will likely need to 
include in subsequent versions,
such as IANA considerations, references, etc. :-)

Thanks for pointing it out, I hadn't seen it before now.

Brian
> Cheers,
> Rajiv 
>
>   
>> -----Original Message-----
>> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On 
>> Behalf Of Brian Dickson
>> Sent: Tuesday, February 05, 2008 6:47 PM
>> Cc: idr@ietf.org
>> Subject: [Idr] New ID and request for time slot
>>
>> I've put together a new draft, with the (ambitious!) goal of 
>> addressing 
>> a few of the outstanding BGP issues:
>> - wedgies
>> - persistent oscillations
>> - path hunting.
>>
>> I've included most of the supporting examples for the first 
>> two, which 
>> are clearly smaller in scope.
>>
>> I'll be doing more work (between now and IETF-71) to produce example 
>> cases for the path hunting problem (w.r.t. the new draft).
>> My hope is this can reduce the level of induced churn caused by path 
>> hunting.
>>
>> I'd respectfully request a slot in Philly to present this material.
>>
>> Comments are obviously welcome, as well as any pointers to tools for 
>> evaluating path hunting behavior.
>>
>> Obviously, adding new attributes isn't something to be done 
>> lightly, but 
>> if the results are compelling enough, it may be an 
>> appropriate path to take.
>>
>> I'd appreciate it if we can first look to see if the results are 
>> compelling, before getting into whether they are compelling 
>> enough. :-)
>>
>> Thanks,
>>
>> Brian Dickson
>>
>>     
>>> A new version of I-D, 
>>>       
>> draft-dickson-idr-second-best-backup-00.txt has 
>>     
>>> been successfuly submitted by Brian Dickson and posted to the IETF 
>>> repository.
>>>
>>> Filename:        draft-dickson-idr-second-best-backup
>>> Revision:        00
>>> Title:           Enhanced BGP Capabilities for Exchanging 
>>>       
>> Second-best 
>>     
>>> and Back-up Paths
>>> Creation_date:   2008-02-05
>>> WG ID:           Independent Submission
>>> Number_of_pages: 20
>>>
>>> Abstract:
>>> This Internet Draft describes an enhanced way to exchange prefix
>>> information, to permit multiple copies of a prefix with different
>>> paths to be announced and withdrawn.
>>>
>>> This negotiated capability provides faster local (inter-AS) and
>>> global (intra-AS) convergence, reduces path-hunting, improves route-
>>> reflector behaviour, including eliminating both persistent
>>> oscillations and BGP "wedgies".
>>>
>>> Additional prefix instances have new optional transtive BGP
>>> attributes, to control path selection.
>>>
>>> Withdrawl of prefixes will require path attributes.
>>>
>>> Benefits are seen both when deployed intra-AS, and on inter-AS
>>> peering.
>>> Author's Note
>>>
>>> This Internet Draft is intended to result in this draft or a related
>>> draft(s) being placed on the Standards Track for idr.
>>>       
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> http://www.ietf.org/mailman/listinfo/idr
>>
>>     

_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Tue Feb  5 23:35:00 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC38E3A6A1B;
	Tue,  5 Feb 2008 23:35:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level: 
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=0.067,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SUK67f86hLtf; Tue,  5 Feb 2008 23:34:59 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C33CD3A67F5;
	Tue,  5 Feb 2008 23:34:59 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5430F3A67F5
	for <idr@core3.amsl.com>; Tue,  5 Feb 2008 23:34:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id E++nVR5TtMLE for <idr@core3.amsl.com>;
	Tue,  5 Feb 2008 23:34:57 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163])
	by core3.amsl.com (Postfix) with ESMTP id ED9913A67AF
	for <idr@ietf.org>; Tue,  5 Feb 2008 23:34:32 -0800 (PST)
Received: from source ([66.129.224.36]) by exprod7ob105.postini.com
	([64.18.6.12]) with SMTP; Tue, 05 Feb 2008 23:36:04 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Feb 2008 23:35:16 -0800
Received: from [172.26.250.99] ([172.26.250.99])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m167Z8q18732;
	Tue, 5 Feb 2008 23:35:12 -0800 (PST)
	(envelope-from raszuk@juniper.net)
Message-ID: <47A96329.2030805@juniper.net>
Date: Tue, 05 Feb 2008 23:35:05 -0800
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Brian Dickson <briand@ca.afilias.info>
References: <15B86BC7352F864BB53A47B540C089B604E0BABF@xmb-rtp-20b.amer.cisco.com>
	<47A904DF.1040908@ca.afilias.info>
In-Reply-To: <47A904DF.1040908@ca.afilias.info>
X-OriginalArrivalTime: 06 Feb 2008 07:35:16.0047 (UTC)
	FILETIME=[D0F7BDF0:01C86892]
Cc: idr@ietf.org
Subject: Re: [Idr] New ID and request for time slot
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Brian,

Thx for the pointer to your draft.

It seems to me that draft-walton when combined with simply sending best 
external path (the latter some bgp implementations already support 
today) when IBGP learned path wins as the best do address all problems 
you are listing in section 1.

Could you point out what would be missing provided one would use above 
tools without additional capabilities or without need to modify bgp best 
path selection algorithm ?

Thx,
R.

> Rajiv Asati (rajiva) wrote:
>  > Hi Brian,
>  >
>  > The draft-dickson-idr-second-best-backup is not yet available for
>  > reading.
> Here's the link to the -00 version:
> http://www.ietf.org/internet-drafts/draft-dickson-idr-second-best-backup-00.txt
>  > I am certainly curious about whether and how it differs from
>  > the add-paths draft -
>  > http://tools.ietf.org/html/draft-walton-bgp-add-paths-05
>  >
>  >  
> Well, a quick review of add-paths seems to indicate several important
> differences:
> - add-paths appears limited in scope to route-reflectors, but does so
> very well
> - second-best-backup focuses more on inter-AS effects and direct
> intra-AS behavior
> 
> I expect that the two would in fact complement each other very effectively.
> 
> How exactly they would/could be merged may not be obvious just yet, but
> I don't see
> any fundamental hurdles.
> 
> Certainly, it points to lots of things there that I will likely need to
> include in subsequent versions,
> such as IANA considerations, references, etc. :-)
> 
> Thanks for pointing it out, I hadn't seen it before now.
> 
> Brian
>  > Cheers,
>  > Rajiv
>  >
>  >  
>  >> -----Original Message-----
>  >> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On
>  >> Behalf Of Brian Dickson
>  >> Sent: Tuesday, February 05, 2008 6:47 PM
>  >> Cc: idr@ietf.org
>  >> Subject: [Idr] New ID and request for time slot
>  >>
>  >> I've put together a new draft, with the (ambitious!) goal of
>  >> addressing
>  >> a few of the outstanding BGP issues:
>  >> - wedgies
>  >> - persistent oscillations
>  >> - path hunting.
>  >>
>  >> I've included most of the supporting examples for the first
>  >> two, which
>  >> are clearly smaller in scope.
>  >>
>  >> I'll be doing more work (between now and IETF-71) to produce example
>  >> cases for the path hunting problem (w.r.t. the new draft).
>  >> My hope is this can reduce the level of induced churn caused by path
>  >> hunting.
>  >>
>  >> I'd respectfully request a slot in Philly to present this material.
>  >>
>  >> Comments are obviously welcome, as well as any pointers to tools for
>  >> evaluating path hunting behavior.
>  >>
>  >> Obviously, adding new attributes isn't something to be done
>  >> lightly, but
>  >> if the results are compelling enough, it may be an
>  >> appropriate path to take.
>  >>
>  >> I'd appreciate it if we can first look to see if the results are
>  >> compelling, before getting into whether they are compelling
>  >> enough. :-)
>  >>
>  >> Thanks,
>  >>
>  >> Brian Dickson
>  >>
>  >>    
>  >>> A new version of I-D,
>  >>>      
>  >> draft-dickson-idr-second-best-backup-00.txt has
>  >>    
>  >>> been successfuly submitted by Brian Dickson and posted to the IETF
>  >>> repository.
>  >>>
>  >>> Filename:        draft-dickson-idr-second-best-backup
>  >>> Revision:        00
>  >>> Title:           Enhanced BGP Capabilities for Exchanging
>  >>>      
>  >> Second-best
>  >>    
>  >>> and Back-up Paths
>  >>> Creation_date:   2008-02-05
>  >>> WG ID:           Independent Submission
>  >>> Number_of_pages: 20
>  >>>
>  >>> Abstract:
>  >>> This Internet Draft describes an enhanced way to exchange prefix
>  >>> information, to permit multiple copies of a prefix with different
>  >>> paths to be announced and withdrawn.
>  >>>
>  >>> This negotiated capability provides faster local (inter-AS) and
>  >>> global (intra-AS) convergence, reduces path-hunting, improves route-
>  >>> reflector behaviour, including eliminating both persistent
>  >>> oscillations and BGP "wedgies".
>  >>>
>  >>> Additional prefix instances have new optional transtive BGP
>  >>> attributes, to control path selection.
>  >>>
>  >>> Withdrawl of prefixes will require path attributes.
>  >>>
>  >>> Benefits are seen both when deployed intra-AS, and on inter-AS
>  >>> peering.
>  >>> Author's Note
>  >>>
>  >>> This Internet Draft is intended to result in this draft or a related
>  >>> draft(s) being placed on the Standards Track for idr.
>  >>>      
>  >> _______________________________________________
>  >> Idr mailing list
>  >> Idr@ietf.org
>  >> http://www.ietf.org/mailman/listinfo/idr
>  >>
>  >>    
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> http://www.ietf.org/mailman/listinfo/idr
> 

_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Wed Feb  6 05:19:04 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95A053A6E33;
	Wed,  6 Feb 2008 05:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Rh+nUd9vtWrR; Wed,  6 Feb 2008 05:19:04 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 362CE3A6DF8;
	Wed,  6 Feb 2008 05:19:01 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C3E033A6BDC
	for <idr@core3.amsl.com>; Wed,  6 Feb 2008 05:19:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MISVQPbV83PZ for <idr@core3.amsl.com>;
	Wed,  6 Feb 2008 05:19:00 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171])
	by core3.amsl.com (Postfix) with ESMTP id 02A1F3A6D11
	for <idr@ietf.org>; Wed,  6 Feb 2008 05:18:55 -0800 (PST)
Received: from source ([66.129.224.36]) by exprod7ob109.postini.com
	([64.18.6.12]) with SMTP; Wed, 06 Feb 2008 05:20:27 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 6 Feb 2008 05:20:27 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m16DKKq20988;
	Wed, 6 Feb 2008 05:20:24 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200802061320.m16DKKq20988@magenta.juniper.net>
To: Brian Dickson <briand@ca.afilias.info>
In-Reply-To: Your message of "Tue, 05 Feb 2008 18:46:52 EST."
	<47A8F56C.4080608@ca.afilias.info> 
MIME-Version: 1.0
Content-ID: <34442.1202304020.1@juniper.net>
Date: Wed, 06 Feb 2008 05:20:20 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 06 Feb 2008 13:20:27.0610 (UTC)
	FILETIME=[0A0573A0:01C868C3]
Cc: idr@ietf.org
Subject: Re: [Idr] New ID and request for time slot
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Brian,

> I've put together a new draft, with the (ambitious!) goal of addressing 
> a few of the outstanding BGP issues:
> - wedgies
> - persistent oscillations
> - path hunting.
> 
> I've included most of the supporting examples for the first two, which 
> are clearly smaller in scope.
> 
> I'll be doing more work (between now and IETF-71) to produce example 
> cases for the path hunting problem (w.r.t. the new draft).
> My hope is this can reduce the level of induced churn caused by path 
> hunting.
> 
> I'd respectfully request a slot in Philly to present this material.

Sure. Just let Sue and myself how much time would you like for
your presentation.

Yakov.
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Fri Feb  8 02:30:19 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A42E28C202;
	Fri,  8 Feb 2008 02:30:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id x2jw5W7tRwLV; Fri,  8 Feb 2008 02:30:18 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FDBE28C1F6;
	Fri,  8 Feb 2008 02:30:18 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 72CC528C1A4
	for <idr@core3.amsl.com>; Fri,  8 Feb 2008 02:30:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6H2UKWK5vvM8 for <idr@core3.amsl.com>;
	Fri,  8 Feb 2008 02:30:16 -0800 (PST)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177])
	by core3.amsl.com (Postfix) with ESMTP id 8C06F28C199
	for <idr@ietf.org>; Fri,  8 Feb 2008 02:30:16 -0800 (PST)
Received: from source ([66.129.224.36]) by exprod7ob112.postini.com
	([64.18.6.12]) with SMTP; Fri, 08 Feb 2008 02:31:41 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 8 Feb 2008 02:31:37 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m18AVcq75199
	for <idr@ietf.org>; Fri, 8 Feb 2008 02:31:38 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200802081031.m18AVcq75199@magenta.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-ID: <34730.1202466698.1@juniper.net>
Date: Fri, 08 Feb 2008 02:31:38 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 08 Feb 2008 10:31:37.0053 (UTC)
	FILETIME=[C890A0D0:01C86A3D]
Subject: [Idr]  IETF 71
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Folks,
 
Its about time to start thinking about agenda items for the next
IETF. Please forward any IDR agenda items you might have to Sue and
myself. The deadline is February 26, 2008.

And if you plan to make a presentation, please also keep in mind
the rule "no Internet Draft - no time slot".

Sue & Yakov.
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Wed Feb 13 15:27:41 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6738C3A6FDB;
	Wed, 13 Feb 2008 15:27:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.141
X-Spam-Level: 
X-Spam-Status: No, score=0.141 tagged_above=-999 required=5 tests=[AWL=-1.511,
	BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	J_CHICKENPOX_92=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZMIqweXg1zjg; Wed, 13 Feb 2008 15:27:40 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 75A2E3A6E84;
	Wed, 13 Feb 2008 15:27:40 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C5E03A6E84
	for <idr@core3.amsl.com>; Wed, 13 Feb 2008 15:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4g9VDa8b3FnR for <idr@core3.amsl.com>;
	Wed, 13 Feb 2008 15:27:38 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173])
	by core3.amsl.com (Postfix) with ESMTP id 8806D3A6D6E
	for <idr@ietf.org>; Wed, 13 Feb 2008 15:27:38 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 25so27140wfa.31
	for <idr@ietf.org>; Wed, 13 Feb 2008 15:29:01 -0800 (PST)
Received: by 10.142.50.15 with SMTP id x15mr489047wfx.169.1202945341061;
	Wed, 13 Feb 2008 15:29:01 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Wed, 13 Feb 2008 15:29:00 -0800 (PST)
Message-ID: <77ead0ec0802131529t13af9092nb837d24824abe758@mail.gmail.com>
Date: Wed, 13 Feb 2008 15:29:00 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: raszuk@juniper.net
In-Reply-To: <47A6C39A.2010709@juniper.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
	<20080201090733.GA1929@nic.dtag.de>
	<77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
	<47A631EC.80703@juniper.net>
	<77ead0ec0802031455s300978bfn8d10b142376f315@mail.gmail.com>
	<47A647FA.9040909@juniper.net>
	<77ead0ec0802032000p4b09c2e4j4f6bbc804a8526a6@mail.gmail.com>
	<47A6C39A.2010709@juniper.net>
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Robert/ Martin,

I thought over the load balancing case, which seems to be the only
advantage(it is anyway not guaranteed - but best effort) of the 6PE.

Another way to just get the behavior with 6PE of getting different
hashes for a label stack for same tunnel label is to use the label
stack more affectively.

So we can have a label stack which could have either Explicit NULL
IPv6 label, or a combination of Explicit NULL IPv6 label and Explicit
NULL IPv4 label, with the bottom of stack being the Explicit NULL IPv6
label.

Thanks,
Vishwas

On Feb 3, 2008 11:49 PM, Robert Raszuk <raszuk@juniper.net> wrote:
> Hi Vishwas,
>
> What VPN label allocation scheme to use is often left to the operator by
> the CLI. From P router load balancing point of view the worst is per vrf
> granularity ... your draft proposes per PE.
>
> Cheers,
> R.
>
> > Hi  Robert/ Martin,
> >
>
> > One more question.
> >
> > So are you saying the implementations you know provides a separate
> > label for each route, or is it per peer?  I guess it is the later, but
> > just want to reconfirm the same.
> >
> > Thanks,
> > Vishwas
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Wed Feb 13 15:29:19 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 278DE3A701D;
	Wed, 13 Feb 2008 15:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.793
X-Spam-Level: 
X-Spam-Status: No, score=-0.793 tagged_above=-999 required=5
	tests=[AWL=-0.356, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ydn2N9-JNxXN; Wed, 13 Feb 2008 15:29:18 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 115B43A6D6E;
	Wed, 13 Feb 2008 15:29:18 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7800E3A6FF7
	for <idr@core3.amsl.com>; Wed, 13 Feb 2008 15:29:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AKRuxvQCmPqI for <idr@core3.amsl.com>;
	Wed, 13 Feb 2008 15:29:16 -0800 (PST)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183])
	by core3.amsl.com (Postfix) with ESMTP id 37A053A68DB
	for <idr@ietf.org>; Wed, 13 Feb 2008 15:29:03 -0800 (PST)
Received: by el-out-1112.google.com with SMTP id j27so259041elf.25
	for <idr@ietf.org>; Wed, 13 Feb 2008 15:30:24 -0800 (PST)
Received: by 10.142.232.20 with SMTP id e20mr485864wfh.187.1202945423791;
	Wed, 13 Feb 2008 15:30:23 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Wed, 13 Feb 2008 15:30:23 -0800 (PST)
Message-ID: <77ead0ec0802131530w489f63f6m29edd451b4c1d0a6@mail.gmail.com>
Date: Wed, 13 Feb 2008 15:30:23 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: raszuk@juniper.net
In-Reply-To: <47A6C39A.2010709@juniper.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
	<77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
	<20080201090733.GA1929@nic.dtag.de>
	<77ead0ec0802010926k6e57424eoc6ad1328eb65774c@mail.gmail.com>
	<47A631EC.80703@juniper.net>
	<77ead0ec0802031455s300978bfn8d10b142376f315@mail.gmail.com>
	<47A647FA.9040909@juniper.net>
	<77ead0ec0802032000p4b09c2e4j4f6bbc804a8526a6@mail.gmail.com>
	<47A6C39A.2010709@juniper.net>
Cc: idr@ietf.org
Subject: Re: [Idr] 6PE-Alt draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Robert,

Of course we could use another set of reserved labels (after taking it
from IANA) for Explicit NULL IPv6 label and Explicit NULL IPv4 label.

Thanks,
Vishwas

On Feb 3, 2008 11:49 PM, Robert Raszuk <raszuk@juniper.net> wrote:
> Hi Vishwas,
>
> What VPN label allocation scheme to use is often left to the operator by
> the CLI. From P router load balancing point of view the worst is per vrf
> granularity ... your draft proposes per PE.
>
> Cheers,
> R.
>
> > Hi  Robert/ Martin,
> >
>
> > One more question.
> >
> > So are you saying the implementations you know provides a separate
> > label for each route, or is it per peer?  I guess it is the later, but
> > just want to reconfirm the same.
> >
> > Thanks,
> > Vishwas
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Mon Feb 18 03:53:14 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EDA83A6CCE;
	Mon, 18 Feb 2008 03:53:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.519
X-Spam-Level: 
X-Spam-Status: No, score=-1.519 tagged_above=-999 required=5
	tests=[AWL=-1.082, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id COTne+Wvc4Gf; Mon, 18 Feb 2008 03:53:14 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D746328C37F;
	Mon, 18 Feb 2008 03:52:48 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74C5428C372
	for <idr@core3.amsl.com>; Mon, 18 Feb 2008 03:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RkbHluJVztKA for <idr@core3.amsl.com>;
	Mon, 18 Feb 2008 03:52:46 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 1258028C3B7
	for <idr@ietf.org>; Mon, 18 Feb 2008 03:52:23 -0800 (PST)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m1IBqGdI075575
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <idr@ietf.org>; Mon, 18 Feb 2008 12:52:17 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Message-Id: <9E974148-E332-45AB-AB80-283A244182D9@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: idr <idr@ietf.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 18 Feb 2008 12:52:17 +0100
References: <20080218113944.DD87728C0F4@core3.amsl.com>
X-Mailer: Apple Mail (2.919.2)
Subject: [Idr] draft-van-beijnum-idr-iac-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi,

A while ago I had a short discussion with Robert Raszuk about (the  
lack of) an inter-AS metric, and he asked me to write my idea up in a  
draft. I did. Let me know what you think.

Iljitsch

Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: 18 februari 2008 12:39:44 GMT+01:00
> To: iljitsch@muada.com
> Subject: New Version Notification for draft-van-beijnum-idr-iac-00
>
>
> A new version of I-D, draft-van-beijnum-idr-iac-00.txt has been  
> successfuly submitted by Iljitsch van Beijnum and posted to the IETF  
> repository.
>
> Filename:	 draft-van-beijnum-idr-iac
> Revision:	 00
> Title:		 A BGP Inter-AS Cost Attribute
> Creation_date:	 2008-02-18
> WG ID:		 Independent Submission
> Number_of_pages: 6
>
> Abstract:
> Although BGP implementations have extensive path selection
> algorithms, in practice operators have trouble performing
> satisfactory traffic engineering of incoming traffic based on BGP
> attributes that are taken into account in the path selection
> algorithm alone.  For this reason, many ASes deaggregate their
> address range(s) into smaller blocks and announce these blocks
> differently to different neighboring ASes in order to arrive at the
> desired traffic flow.  This practice contributes to the growth of the
> global routing table, which drives up capital expenditures for
> networks engaging in inter-domain routing.  This memo introduces a
> new inter-domain metric that supports finer-grained traffic
> engineering than current BGP attributes, most notably, the AS path.

_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Mon Feb 25 12:53:58 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C00D528C4A5;
	Mon, 25 Feb 2008 12:53:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.184
X-Spam-Level: 
X-Spam-Status: No, score=-3.184 tagged_above=-999 required=5
	tests=[AWL=-2.747, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ROTcpK1ixjdd; Mon, 25 Feb 2008 12:53:57 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54DA628C5B4;
	Mon, 25 Feb 2008 12:46:37 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 01AE628C5AB
	for <idr@core3.amsl.com>; Mon, 25 Feb 2008 12:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UDMZLBncqFvJ for <idr@core3.amsl.com>;
	Mon, 25 Feb 2008 12:46:35 -0800 (PST)
Received: from mx4.ca.afilias.info (vgateway.libertyrms.info [207.219.45.62])
	by core3.amsl.com (Postfix) with ESMTP id 01EE328C671
	for <idr@ietf.org>; Mon, 25 Feb 2008 12:39:40 -0800 (PST)
Received: from briand-vpn.int.libertyrms.com ([10.1.7.90])
	by mx4.ca.afilias.info with esmtp (Exim 4.22) id 1JTk6o-0005vQ-8b
	for idr@ietf.org; Mon, 25 Feb 2008 15:39:34 -0500
Message-ID: <47C3277E.5060502@ca.afilias.info>
Date: Mon, 25 Feb 2008 15:39:26 -0500
From: Brian Dickson <briand@ca.afilias.info>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: idr <idr@ietf.org>
References: <20080218113944.DD87728C0F4@core3.amsl.com>
	<9E974148-E332-45AB-AB80-283A244182D9@muada.com>
In-Reply-To: <9E974148-E332-45AB-AB80-283A244182D9@muada.com>
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
Subject: [Idr] draft-dickson-idr-second-best-backup-01
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

draft-dickson-idr-second-best-backup-01 has been posted to the expected place:
http://www.ietf.org/internet-drafts/draft-dickson-idr-second-best-backup-01.txt

There have been some rather substantial changes made to parts of it, especially as far as how withdrawals are structured, and matched to updates.

Also, the capabilities have been rolled together, since one type (backup) relies on the other to achieve the goal of preventing wedgies.

For IETF-71, I'll be doing some comparisons between this and other proposals (e.g. the walton add-paths one).

In the meantime, feedback is welcome, although no updates will occur between now and the impending IETF meeting. :-)

Thanks for your patience and feedback.

Brian Dickson


_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Wed Feb 27 05:54:53 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 847D528C29D;
	Wed, 27 Feb 2008 05:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.21
X-Spam-Level: 
X-Spam-Status: No, score=-3.21 tagged_above=-999 required=5 tests=[AWL=-2.773,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iy-kpzNW75Iz; Wed, 27 Feb 2008 05:54:49 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B103C3A6CF3;
	Wed, 27 Feb 2008 05:54:49 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 226033A6A12
	for <idr@core3.amsl.com>; Wed, 27 Feb 2008 05:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id REiVsUjw9YBV for <idr@core3.amsl.com>;
	Wed, 27 Feb 2008 05:54:48 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175])
	by core3.amsl.com (Postfix) with ESMTP id CFD933A68EC
	for <idr@ietf.org>; Wed, 27 Feb 2008 05:54:47 -0800 (PST)
Received: from source ([66.129.224.36]) by exprod7ob111.postini.com
	([64.18.6.12]) with SMTP; Wed, 27 Feb 2008 05:52:26 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Feb 2008 05:51:46 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m1RDpkq36803
	for <idr@ietf.org>; Wed, 27 Feb 2008 05:51:46 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200802271351.m1RDpkq36803@magenta.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-ID: <57238.1204120306.1@juniper.net>
Date: Wed, 27 Feb 2008 05:51:46 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 27 Feb 2008 13:51:46.0229 (UTC)
	FILETIME=[E470B650:01C87947]
Subject: [Idr] preliminary agenda
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Folks,

I just uploaded a preliminary agenda for the IDR WG meeting.

Yakov.
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Wed Feb 27 20:04:41 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA4753A6E7D;
	Wed, 27 Feb 2008 20:04:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.637
X-Spam-Level: 
X-Spam-Status: No, score=-0.637 tagged_above=-999 required=5
	tests=[AWL=-0.200, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 99KS2Ryt9iMw; Wed, 27 Feb 2008 20:04:35 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AAE543A6E60;
	Wed, 27 Feb 2008 20:04:35 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7320C3A6E7D
	for <idr@core3.amsl.com>; Wed, 27 Feb 2008 20:04:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id N6dMEdTYC+NN for <idr@core3.amsl.com>;
	Wed, 27 Feb 2008 20:04:28 -0800 (PST)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.181])
	by core3.amsl.com (Postfix) with ESMTP id 65DAE3A68C8
	for <idr@ietf.org>; Wed, 27 Feb 2008 20:04:28 -0800 (PST)
Received: by el-out-1112.google.com with SMTP id j27so4239431elf.25
	for <idr@ietf.org>; Wed, 27 Feb 2008 20:04:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	bh=jTHtWARk74wlSqaqfFsE+NyYnn7NxweLKG0NFDtMsIo=;
	b=w0Vz+YwTeAfvq3sIY7tQgS0eujZ63jw7O0zBDPVfrbi5oKRAgh13h/+2jd4WQCCo0KWGJ5czTSu4FGTabKBkR+bj6eqVrFRJTfuargalW8mS2R1mpWyx39292KtjZi4/4izfTqVePjAQu3mvFNxzm2lYxxhwO4I5RV0zsPhcxno=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=nPX5LHKWZF4BdOKoCqZJ9s32QXhqYpyHIx9vB3Gle69wpga/TaZH7Jd9ZAbT9xEZTclWGQAmseFxzOkQ5hpVrZ93Dzdy4/7biPLjy4mWOWIMyb5ekSHZNk60IiJciXZYfrO8j79+PtpsGvT2C6d42aozTUuB1Pg5/2jv5xL1j+0=
Received: by 10.114.81.1 with SMTP id e1mr8567734wab.11.1204171455879;
	Wed, 27 Feb 2008 20:04:15 -0800 (PST)
Received: by 10.114.241.4 with HTTP; Wed, 27 Feb 2008 20:04:15 -0800 (PST)
Message-ID: <77ead0ec0802272004r776fec76yb80df62b8f7b684b@mail.gmail.com>
Date: Wed, 27 Feb 2008 20:04:15 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: idr <idr@ietf.org>, sidr <sidr@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_31239_5771214.1204171455873"
Subject: [Idr] Issues with SIDR
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

------=_Part_31239_5771214.1204171455873
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi folks,

As part of the discussion in OPSEC with Stephen Kent and others, I
looked at the SIDR infrastructure as well as soBGP document.

I found easy ways to just get over all the security
infrastructure(PKI) and still being able to do all the attacks as we
can currently. Please have a look at the discussion below and let me
know your comments.

Thanks,
Vishwas

---------- Forwarded message ----------
From: Vishwas Manral <vishwas.ietf@gmail.com>
Date: Wed, Feb 27, 2008 at 7:13 PM
Subject: Re: [OPSEC] pccw as17557 leak...
To: Stephen Kent <kent@bbn.com>
Cc: Roland Dobbins <rdobbins@cisco.com>, opsec wg mailing list <opsec@ietf.org>


Hi Steve,

 Thanks a lot for the comments. I agree it can be a good first step but
 not sure what the future holds.

 I am not sure if a heavy solution like this is required which only
 gives reasonable security. What about the CPU DoS attacks that can be
 result when new random routes are injected into a domain.

 Thanks again,
 Vishwas



 On Wed, Feb 27, 2008 at 7:07 PM, Stephen Kent <kent@bbn.com> wrote:
 > At 5:12 PM -0800 2/27/08, Vishwas Manral wrote:
 >  >Hi folks,
 >  >
 >  >I looked at the SIDR documents in brief. It can probably be used to
 >  >help prevent any attacks caused due to non-malicious intent.
 >  >
 >  >I found easy ways to get over the SIDR security when done with a
 >  >malicious intent. SIDR just tells the mapping between AFI, AF and AS
 >  >number which can originate the same. However the choosing of a route
 >  >by BGP does not depend on these fields alone. So if a malicious router
 >  >changed the attributes attached to an NLRI update so that it becomes
 >  >the chosen AS to the prefix (of course without changing the
 >  >originating AS field). It can still redirect all the traffic to itself
 >  >for the prefix and then do whatever malicious it wants to do,
 >  >including just drop the packet.
 >  >
 >  >In this way still achieving the attack, but this time for sure with
 >  >malicious intent.
 >  >
 >  >Thanks,
 >  >Vishwas
 >
 >
 >  Your example of how an AS can tamper with a route, without changing
 >  the origin AS assertion is correct. I think the SIDR WG participants
 >  understand that.
 >  The work so far i SIDR focuses on establishing an infrastructure that
 >  will enable more comprehensive routing security capabilities in the
 >  future.  Both the soBGP and SBGP proposal need this sort of
 >  infrastructure, so it is viewed as a reasonable initial effort.
 >
 >  I also agree with your observation that the infrastructure makes it
 >  potentially easier to distinguish between some forms of attacks vs.
 >  accidental routing errors, and that, in itself, seems valuable too.
 >
 >  Steve
 >

------=_Part_31239_5771214.1204171455873
Content-Type: text/plain; name=draft-manral-sidr-limitations-00.txt
Content-Transfer-Encoding: base64
X-Attachment-Id: f_fd6shs8j0
Content-Disposition: attachment;
 filename=draft-manral-sidr-limitations-00.txt

ICAgICAgICAgICAgICAgICAgIA0KSW50ZXJuZXQgRW5naW5lZXJpbmcgVGFzayBGb3JjZSAgICAg
ICAgICAgICAgICAgICAgICAgICAgIFZpc2h3YXMgTWFucmFsDQpJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBJUEluZnVzaW9uIEluYy4NCklu
dGVuZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICANCkV4cGlyZXM6IEF1Z3VzdCAyNywgMjAwOCAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgRmVicnVhcnkgMjcsIDIwMDgNCg0KDQogICAgICAgICAgICAgICAgICAgICBT
ZWN1cml0eSBsaW1pdGF0aW9ucyBvZiBTSURSDQogICAgICAgICAgICAgICAgICAgICAgIA0KICAg
ICAgICAgICAgICAgICAgIGRyYWZ0LW1hbnJhbC1zaWRyLWxpbWl0YXRpb25zLTAwDQoNClN0YXR1
cyBvZiB0aGlzIE1lbW8NCg0KICAgQnkgc3VibWl0dGluZyB0aGlzIEludGVybmV0LURyYWZ0LCBl
YWNoIGF1dGhvciByZXByZXNlbnRzIHRoYXQgYW55DQogICBhcHBsaWNhYmxlIHBhdGVudCBvciBv
dGhlciBJUFIgY2xhaW1zIG9mIHdoaWNoIGhlIG9yIHNoZSBpcyBhd2FyZQ0KICAgaGF2ZSBiZWVu
IG9yIHdpbGwgYmUgZGlzY2xvc2VkLCBhbmQgYW55IG9mIHdoaWNoIGhlIG9yIHNoZSBiZWNvbWVz
DQogICBhd2FyZSB3aWxsIGJlIGRpc2Nsb3NlZCwgaW4gYWNjb3JkYW5jZSB3aXRoIFNlY3Rpb24g
NiBvZiBCQ1AgNzkuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMg
b2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nDQogICBUYXNrIEZvcmNlIChJRVRGKSwgaXRzIGFy
ZWFzLCBhbmQgaXRzIHdvcmtpbmcgZ3JvdXBzLiAgTm90ZSB0aGF0DQogICBvdGhlciBncm91cHMg
bWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC0NCiAgIERy
YWZ0cy4NCg0KICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9y
IGEgbWF4aW11bSBvZiBzaXggbW9udGhzDQogICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2Vk
LCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0KICAgdGltZS4gIEl0IGlz
IGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2UNCiAgIG1h
dGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiIN
Cg0KICAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1EcmFmdHMgY2FuIGJlIGFjY2Vzc2Vk
IGF0DQogICBodHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0cy50eHQuDQoNCiAg
IFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJlY3RvcmllcyBjYW4gYmUgYWNj
ZXNzZWQgYXQNCiAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwuDQoNCiAgIFRoaXMg
SW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUgb24gQXVndXN0IDI3LCAyMDA4Lg0KDQpDb3B5cmln
aHQgTm90aWNlDQoNCiAgIENvcHlyaWdodCAoQykgVGhlIElFVEYgVHJ1c3QgKDIwMDgpLg0KDQpB
YnN0cmFjdA0KDQogICBTSURSIGFyY2hpdGVjdHVyZSBkZXNjcmliZXMgYW4gYXJjaGl0ZWN0dXJl
IGZvciBhbiBpbmZyYXN0cnVjdHVyZSB0byANCiAgIHN1cHBvcnQgc2VjdXJlIEludGVybmV0IHJv
dXRpbmcuIFRoZSBmb3VuZGF0aW9uIG9mIHRoZSBhcmNoaXRlY3R1cmUgDQogICBpcyBhIHB1Ymxp
YyBrZXkgaW5mcmFzdHJ1Y3R1cmUgKFBLSSkgdGhhdCByZXByZXNlbnRzIHRoZSBhbGxvY2F0aW9u
IA0KICAgaGllcmFyY2h5IG9mIElQIGFkZHJlc3Mgc3BhY2UgYW5kIEF1dG9ub21vdXMgU3lzdGVt
IE51bWJlcnM7IA0KICAgY2VydGlmaWNhdGVzIGZyb20gdGhpcyBQS0kgYXJlIHVzZWQgdG8gdmVy
aWZ5IHNpZ25lZCBvYmplY3RzIHRoYXQgDQogICBhdXRob3JpemUgYXV0b25vbW91cyBzeXN0ZW1z
IHRvIG9yaWdpbmF0ZSByb3V0ZXMgZm9yIHNwZWNpZmllZCBJUCAgDQoNCg0KDQpNYW5yYWwgICAg
ICAgICAgICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMDggICAgICAgICAgICAgICAg
IFtQYWdlIDFdDQogDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgU2VjdXJpdHkgbGltaXRhdGlv
bnMgb2YgU0lEUiAgICAgICAgICAgRmVicnVhcnkgMjAwOA0KDQoNCiAgIGFkZHJlc3MgcHJlZml4
ZXMuIFRoZSBkYXRhIG9iamVjdHMgdGhhdCBjb21wcmlzZSB0aGUgUEtJLCBhcyB3ZWxsIGFzIA0K
ICAgb3RoZXIgc2lnbmVkIG9iamVjdHMgbmVjZXNzYXJ5IGZvciBzZWN1cmUgcm91dGluZywgYXJl
IHN0b3JlZCBhbmQgDQogICBkaXNzZW1pbmF0ZWQgdGhyb3VnaCBhIGRpc3RyaWJ1dGVkIHJlcG9z
aXRvcnkgc3lzdGVtLiBUaGlzIGRvY3VtZW50IA0KICAgZGVzY3JpYmVzIGxpbWl0YXRpb25zIGFu
ZCBvdGhlciBsaW1pdGF0aW9ucyB0byB0aGUgdXNlIG9mIHRoZSBTSURSIA0KICAgaW5mcmFzdHJ1
Y3R1cmUuDQoNCg0KUmVxdWlyZW1lbnRzIExhbmd1YWdlDQoNCiAgIFRoZSBrZXkgd29yZHMgIk1V
U1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwNCiAgICJT
SE9VTEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFM
IiBpbiB0aGlzDQogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVk
IGluIFJGQyAyMTE5IFtSRkMyMTE5XS4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Ck1hbnJhbCAgICAgICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAwOCAgICAg
ICAgICAgICAgICAgW1BhZ2UgMl0NCiANCkludGVybmV0LURyYWZ0ICAgICAgICAgICBTZWN1cml0
eSBsaW1pdGF0aW9ucyBvZiBTSURSICAgICAgICAgICBGZWJydWFyeSAyMDA4DQoNCg0KICAxLiAg
SW50cm9kdWN0aW9uDQogICAgIA0KICAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0aGUgbGltaXRh
dGlvbnMgb2YgdGhlIFNJRFIgaW5mcmFzdHJ1Y3R1cmUgYW5kIHRoZWlyDQogICAgdXNlIHdpdGgg
c28tQkdQIGFuZCBvdGhlciBzdWNoIHJlbGF0ZWQgc2VjdXJpdHkgbWVjaGFuaXNtcy4NCg0KICAy
LiBMaW1pdGF0aW9ucw0KDQogICAgMi4xLiBQcm9ibGVtIHdpdGgganVzdCB2ZXJpZnlpbmcgb3Jp
Z2luDQogICAgICAgICAgICAgICAgDQogICAgICAgIFNJRFIgYXJjaGl0ZWN0dXJlIGFsbG93cyBh
IG1lY2hhbmlzbSB0byB2ZXJpZnkgYW4gQXV0b25vbW91UyBTeXN0ZW0gKEFTKQ0KICAgICAgICBo
YXMgcmlnaHRzIHRvIG9yaWdpbmF0ZSBhIHBhcnRpY3VsYXIgcHJlZml4Lg0KDQogICAgICAgIEJH
UCBiZXN0IHJvdXRlIHNlbGVjdGlvbiBhbGdvcml0aG0gaG93ZXZlciBkb2VzIG5vdCBvbmx5IHVz
ZSB0aGUgb3JpZ2luYWluZyANCiAgICAgICAgQVMsIGFuZCBOTFJJIHByZWZpeC4gSXQgdXNlcyBh
IGxvdCBvZiBvdGhlciBhdHRyaWJ1dGVzIGFzc29jaWF0ZWQgd2l0aCB0aGUgDQogICAgICAgIHJv
dXRlIHRvIGNhbGN1bGF0ZSB0aGUgYmVzdCByb3V0ZSBhbmQgcHJvcGFnYXRlIGl0IGFjcm9zcy4g
SWYgdGhlIG1hbGljaW91cw0KICAgICAgICByb3V0ZXIgZG9lcyBub3QgY2hhbmdlIHRoZSBvcmln
aW4gQVMgZm9yIGFuIE5MUkkgcHJlZml4IGJ1dCBjaGFuZ2VzIG90aGVyIA0KICAgICAgICBhdHRy
aWJ1dGVzIHJlcXVpcmVkIGZvciBiZXN0IHBhdGggc2VsZWN0aW9uLiBJdCBjYW4gc3RpbGwgbWFr
ZSBhIGxvdCBvZiANCiAgICAgICAgcm91dGVzIGJlIHJvdXRlZCB0aHJvdWdoIGl0LiANCg0KICAg
ICAgICBUaGUgbWFsaWNpb3VzIGRldmljZSBjYW4gdGhlbiBkbyB3aGF0ZXZlciBpdCB3YW50cyB3
aXRoIHN1Y2hjIHRyYWZmaWMgDQogICAgICAgIGluY2x1ZGluZyBibGFja2hvbGluZyBpdC4NCg0K
ICAgIDIuMiBDUFUgdXRpbGl6YXRpb24NCiAgDQogICAgICAgIEFzIHZlcmlmeWluZyBjZXJ0aWZp
Y2F0ZXMgY29zdHMgYSBsb3Qgb2YgQ1BVIGN5Y2xlcywgdGhpcyBjYW4gbGVhZCB0byBEb1MgDQog
ICAgICAgIGF0dGFja3Mgb24gdGhlIHJvdXRlci4NCg0KICAgICAgICBVc2luZyByYXRlIGxpbWl0
aW5nIGNhbiByZXN1bHQgaW4gZGVsYXlzIGluIEJHUCBjb252ZXJnZW5jZS4NCg0KICAzLiAgU2Vj
dXJpdHkgQ29uc2lkZXJhdGlvbnMNCg0KICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIHRoZSBzZWN1
cnR5IGxpbWl0YXRpb25zIG9mIHRoZSBTSURSIFBLSSBpbmZyYXN0cnVjdHVyZSB3aGVuDQogICB1
c2VkIHdpdGggQkdQLiAgDQoNCiAgNC4gIElBTkEgQ29uc2lkZXJhdGlvbnMNCg0KICAgVGhpcyBk
b2N1bWVudCBoYXMgbm8gYWN0aW9ucyBmb3IgSUFOQSBbSUFOQV0uDQoNCg0KICA1LiAgQWNrbm93
bGVkZ2VtZW50cw0KDQogICBBIGxvdCBvZiB0aGUgdGV4dCBpbiB0aGlzIGRvY3VtZW50IGlzIGJv
cnJvd2VkIGZyb20gW1NJRFItQVJDSF0uIFRoZQ0KICAgYXV0aG9ycyBvZiB0aGUgZG9jdW1lbnQg
YXJlIGFja25vd2xlZGdlZC4gDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCk1hbnJhbCAgICAgICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAy
NywgMjAwOCAgICAgICAgICAgICAgICAgW1BhZ2UgN10NCiANCkludGVybmV0LURyYWZ0ICAgICAg
ICAgICBTZWN1cml0eSBsaW1pdGF0aW9ucyBvZiBTSURSICAgICAgICAgICBGZWJydWFyeSAyMDA4
DQoNCg0KDQo4LiAgUmVmZXJlbmNlcw0KDQo4LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcw0KDQog
ICBbSUFOQV0gICAgICAgIE5hcnRlbiwgVC4gYW5kIEguIEFsdmVzdHJhbmQsICJHdWlkZWxpbmVz
IGZvciBXcml0aW5nDQogICAgICAgICAgICAgICAgIGFuIElBTkEgQ29uc2lkZXJhdGlvbnMgU2Vj
dGlvbiBpbiBSRkNzIiwgQkNQIDI2LCBSRkMNCiAgICAgICAgICAgICAgICAgMjQzNCwgT2N0b2Jl
ciAxOTk4Lg0KDQogICBbU0lEUi1BUkNIXSAgIFNJRFIgYXJjaGl0ZWN0dXJlIGRvY3VtZW50DQoN
CjguMi4gIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMNCg0KDQoNCg0KDQpNYW5yYWwgICAgICAgICAg
ICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjcsIDIwMDggICAgICAgICAgICAgICAgIFtQYWdl
IDhdDQogDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgU2VjdXJpdHkgbGltaXRhdGlvbnMgb2Yg
U0lEUiAgICAgICAgICAgRmVicnVhcnkgMjAwOA0KDQoNCkF1dGhvcnMnIEFkZHJlc3Nlcw0KDQog
ICBWaXNod2FzIE1hbnJhbA0KICAgSVAgSW5mdXNpb24gSW5jLiwNCiAgIEJhbWFua2hvbGEsIA0K
ICAgQmFuc2dhbGksDQogICBBbG1vcmEsDQogICBVdHRhcmFraGFuZCAtIDI2MzYwMQ0KICAgSW5k
aWENCiAgIEVtYWlsOiB2aXNod2FzQGlwaW5mdXNpb24uY29tICANCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCk1hbnJhbCAgICAgICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyNywgMjAwOCAg
ICAgICAgICAgICAgICBbUGFnZSA5XQ0KIA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgIFNlY3Vy
aXR5IGxpbWl0YXRpb25zIG9mIFNJRFIgICAgICAgICAgIEZlYnJ1YXJ5IDIwMDgNCg0KDQpGdWxs
IENvcHlyaWdodCBTdGF0ZW1lbnQNCg0KICAgQ29weXJpZ2h0IChDKSBUaGUgSUVURiBUcnVzdCAo
MjAwOCkuDQoNCiAgIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byB0aGUgcmlnaHRzLCBsaWNl
bnNlcyBhbmQgcmVzdHJpY3Rpb25zDQogICBjb250YWluZWQgaW4gQkNQIDc4LCBhbmQgZXhjZXB0
IGFzIHNldCBmb3J0aCB0aGVyZWluLCB0aGUgYXV0aG9ycw0KICAgcmV0YWluIGFsbCB0aGVpciBy
aWdodHMuDQoNCiAgIFRoaXMgZG9jdW1lbnQgYW5kIHRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQg
aGVyZWluIGFyZSBwcm92aWRlZCBvbiBhbg0KICAgIkFTIElTIiBiYXNpcyBhbmQgVEhFIENPTlRS
SUJVVE9SLCBUSEUgT1JHQU5JWkFUSU9OIEhFL1NIRSBSRVBSRVNFTlRTDQogICBPUiBJUyBTUE9O
U09SRUQgQlkgKElGIEFOWSksIFRIRSBJTlRFUk5FVCBTT0NJRVRZLCBUSEUgSUVURiBUUlVTVCBB
TkQNCiAgIFRIRSBJTlRFUk5FVCBFTkdJTkVFUklORyBUQVNLIEZPUkNFIERJU0NMQUlNIEFMTCBX
QVJSQU5USUVTLCBFWFBSRVNTDQogICBPUiBJTVBMSUVELCBJTkNMVURJTkcgQlVUIE5PVCBMSU1J
VEVEIFRPIEFOWSBXQVJSQU5UWSBUSEFUIFRIRSBVU0UgT0YNCiAgIFRIRSBJTkZPUk1BVElPTiBI
RVJFSU4gV0lMTCBOT1QgSU5GUklOR0UgQU5ZIFJJR0hUUyBPUiBBTlkgSU1QTElFRA0KICAgV0FS
UkFOVElFUyBPRiBNRVJDSEFOVEFCSUxJVFkgT1IgRklUTkVTUyBGT1IgQSBQQVJUSUNVTEFSIFBV
UlBPU0UuDQoNCg0KSW50ZWxsZWN0dWFsIFByb3BlcnR5DQoNCiAgIFRoZSBJRVRGIHRha2VzIG5v
IHBvc2l0aW9uIHJlZ2FyZGluZyB0aGUgdmFsaWRpdHkgb3Igc2NvcGUgb2YgYW55DQogICBJbnRl
bGxlY3R1YWwgUHJvcGVydHkgUmlnaHRzIG9yIG90aGVyIHJpZ2h0cyB0aGF0IG1pZ2h0IGJlIGNs
YWltZWQgdG8NCiAgIHBlcnRhaW4gdG8gdGhlIGltcGxlbWVudGF0aW9uIG9yIHVzZSBvZiB0aGUg
dGVjaG5vbG9neSBkZXNjcmliZWQgaW4NCiAgIHRoaXMgZG9jdW1lbnQgb3IgdGhlIGV4dGVudCB0
byB3aGljaCBhbnkgbGljZW5zZSB1bmRlciBzdWNoIHJpZ2h0cw0KICAgbWlnaHQgb3IgbWlnaHQg
bm90IGJlIGF2YWlsYWJsZTsgbm9yIGRvZXMgaXQgcmVwcmVzZW50IHRoYXQgaXQgaGFzDQogICBt
YWRlIGFueSBpbmRlcGVuZGVudCBlZmZvcnQgdG8gaWRlbnRpZnkgYW55IHN1Y2ggcmlnaHRzLiAg
SW5mb3JtYXRpb24NCiAgIG9uIHRoZSBwcm9jZWR1cmVzIHdpdGggcmVzcGVjdCB0byByaWdodHMg
aW4gUkZDIGRvY3VtZW50cyBjYW4gYmUNCiAgIGZvdW5kIGluIEJDUCA3OCBhbmQgQkNQIDc5Lg0K
DQogICBDb3BpZXMgb2YgSVBSIGRpc2Nsb3N1cmVzIG1hZGUgdG8gdGhlIElFVEYgU2VjcmV0YXJp
YXQgYW5kIGFueQ0KICAgYXNzdXJhbmNlcyBvZiBsaWNlbnNlcyB0byBiZSBtYWRlIGF2YWlsYWJs
ZSwgb3IgdGhlIHJlc3VsdCBvZiBhbg0KICAgYXR0ZW1wdCBtYWRlIHRvIG9idGFpbiBhIGdlbmVy
YWwgbGljZW5zZSBvciBwZXJtaXNzaW9uIGZvciB0aGUgdXNlIG9mDQogICBzdWNoIHByb3ByaWV0
YXJ5IHJpZ2h0cyBieSBpbXBsZW1lbnRlcnMgb3IgdXNlcnMgb2YgdGhpcw0KICAgc3BlY2lmaWNh
dGlvbiBjYW4gYmUgb2J0YWluZWQgZnJvbSB0aGUgSUVURiBvbi1saW5lIElQUiByZXBvc2l0b3J5
IGF0DQogICBodHRwOi8vd3d3LmlldGYub3JnL2lwci4NCg0KICAgVGhlIElFVEYgaW52aXRlcyBh
bnkgaW50ZXJlc3RlZCBwYXJ0eSB0byBicmluZyB0byBpdHMgYXR0ZW50aW9uIGFueQ0KICAgY29w
eXJpZ2h0cywgcGF0ZW50cyBvciBwYXRlbnQgYXBwbGljYXRpb25zLCBvciBvdGhlciBwcm9wcmll
dGFyeQ0KICAgcmlnaHRzIHRoYXQgbWF5IGNvdmVyIHRlY2hub2xvZ3kgdGhhdCBtYXkgYmUgcmVx
dWlyZWQgdG8gaW1wbGVtZW50DQogICB0aGlzIHN0YW5kYXJkLiAgUGxlYXNlIGFkZHJlc3MgdGhl
IGluZm9ybWF0aW9uIHRvIHRoZSBJRVRGIGF0DQogICBpZXRmLWlwckBpZXRmLm9yZy4NCg0KDQpB
Y2tub3dsZWRnbWVudA0KDQogICBGdW5kaW5nIGZvciB0aGUgUkZDIEVkaXRvciBmdW5jdGlvbiBp
cyBwcm92aWRlZCBieSB0aGUgSUVURg0KICAgQWRtaW5pc3RyYXRpdmUgU3VwcG9ydCBBY3Rpdml0
eSAoSUFTQSkuDQoNCg0KDQoNCg0KTWFucmFsICAgICAgICAgICAgICAgICAgICAgIEV4cGlyZXMg
QXVndXN0IDI3LCAyMDA4ICAgICAgICAgICAgICAgIFtQYWdlIDEwXQ0KIA0KDQo=
------=_Part_31239_5771214.1204171455873
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

------=_Part_31239_5771214.1204171455873--


