[Idr] IDR WG minutes

Yakov Rekhter <yakov@juniper.net> Wed, 09 November 2005 00:03 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZdQl-0002Qn-QO; Tue, 08 Nov 2005 19:03:11 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZdQk-0002Qg-OS for idr@megatron.ietf.org; Tue, 08 Nov 2005 19:03:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16806 for <idr@ietf.org>; Tue, 8 Nov 2005 19:02:44 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZdgd-0005u8-Pc for idr@ietf.org; Tue, 08 Nov 2005 19:19:37 -0500
Received: from merlot.juniper.net (merlot.juniper.net []) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id jA902wBm049379 for <idr@ietf.org>; Tue, 8 Nov 2005 16:02:58 -0800 (PST) (envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net []) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id jA902wG40936 for <idr@ietf.org>; Tue, 8 Nov 2005 16:02:58 -0800 (PST) (envelope-from yakov@juniper.net)
Message-Id: <200511090002.jA902wG40936@merlot.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <16842.1131494577.1@juniper.net>
Date: Tue, 08 Nov 2005 16:02:58 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Subject: [Idr] IDR WG minutes
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


Please review and comment for correctness. The deadline for
comments is Nov 21, 2005.

------- Forwarded Message

Date:    Tue, 08 Nov 2005 17:16:35 -0600
From:    David Ward <dward@cisco.com>
To:      <yakov@juniper.net>, <skh@nexthop.com>, David Ward <dward@cisco.com>
Subject: Notes from IDR IETF 64

Not much discussion this time ...


- -------------
0. Doc Status

a. new draft to be reissued for 4-octet AS
b. AS Confeds - implementation report submitted and spec will go as PS
c. GR - post AD comments to PS
d. RR - have IESG comments, revised draft sub. and back to editor
e. 1863 went to historic
f. ton of stuff on editor queue (all to be pub'ed as package vs individual
g. MPBGP, Cease notify at editor
h. a lot no progress (see slides) due to lack of implementation report

Pekka Savola: what is status of BGP MIB v2
YR: no implemenation report ... no progress

- -------------
1. as 4 octet commmunity - Rehkter
no slides 

Ext comm needs to be able to support 4 byte ASN ext comm

Existing doc removed language

New doc published for support (to not get in way of ext comm doc)

New doc produced via cut and paste protocol

It is currently individual submission

Could be WG doc but, it will sit until any implementations

Geoff Huston: It should be a WG draft

Take it to the list ... to be WG doc

1A. YR request from Tony Li to make AS hop count a WG document
sent to list and only got few replies asked room ... no concensus ... not WG
doc yet

- -------------
2. ORF groups - Hares

See slides  for structure of UPDATE

See slides for usage scenarios

Geoff Huston: You have small parts of a boolean language ... why not go all
the way?

Sue: We were told during the last two meetings that we should shrink back
the functionality

GH: Just add groups in groups and go for full boolean logic

We have had a lot of arguments/discussion on this topic and request more

GH: Can't determine beforehand how complex someone may want to get

Vach: What about other operands? E.g. "Not"

Need to see what you want or we are going full bore ...

Enke: If goal is to simplify config .. .but, ORF originally was not to
simplify config but, to improve performance. It is unclear how the config is

Sue: It is an effort to expand power of config

Kireeti: The language is not boolean complete

Rudiger: The language helps the pain w/ config

- -------------
3. Context AF - Ward

See slides

Yakov: Clarification if we need to have larger work in IETF

DWard: It is not dependent on that work and can work with existing

A document will be written that associates diffserv architecture to this

- -------------
4. Enke Chen - Extended Open Parameters

See slides
Problem ... we are running out of capability space

NAME? How does it work w/ ORF

Enke: It should work just fine. I don't understand.

- -------------
5. Chandra Appanna - Aggregate Withdraw

See slides

Ron Bonica: Does this have a mechanism to prevent WD another's routes

Chandra: That is implicit in the protocol

Ron: Can it be propagated?

Chandra: Not transitive

Yakov: Could be made transitive

Chandra: Yes but, we don't pass along WDs today and thus, the draft keeps

Yakov: Time to WD could be plugged in today w/o Aggregate WD

Chandra: This is much more convenient given the other positive attributes

Pekka; if using SBGP or soBGP would it require special processing?

Chandra: No but, haven't thought about it much

Yakov: Please make it transitive. If you use communities, it will be easily
transitive. Do we need the others?

- -------------
6. Gargi - Tunneling applications

see slides

Yakov: Connector attribute carries a shortand for the tunnel, not just the

Gargi: Yes

Yakov: It is even more than shortand but, a list of preferences for a set of

Gargi: Yes, there is nothing in the draft that prevents this from happening

Yakov: Most work going on in L3VPN but, IDR will oversee

- -------------
7. Gargi - Multicast signaling using BGP

see slides

No comments

Out of Time .......

------- End of Forwarded Message

Idr mailing list