IETF Logo Mail Archive

Re: [Idr] Fwd: New Version Notification for draft-scudder-idr-open-registr y-00

Yakov Rekhter <yakov@juniper.net> Tue, 16 December 2008 21:15 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FF233A6ABA; Tue, 16 Dec 2008 13:15:19 -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 C41A83A6ABA for <idr@core3.amsl.com>; Tue, 16 Dec 2008 13:15:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.481
X-Spam-Level:
X-Spam-Status: No, score=-6.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gm2mfwisOVBX for <idr@core3.amsl.com>; Tue, 16 Dec 2008 13:15:18 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by core3.amsl.com (Postfix) with ESMTP id DB9223A69A9 for <idr@ietf.org>; Tue, 16 Dec 2008 13:15:17 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKSUgaXiZq/zUrD9FXt29qM8bjPvM3C2u9@postini.com; Tue, 16 Dec 2008 13:15:11 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.311.2; Tue, 16 Dec 2008 13:12:35 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Dec 2008 13:12:35 -0800
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Dec 2008 13:12:35 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 Dec 2008 13:12:35 -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 mBGLCYM14365; Tue, 16 Dec 2008 13:12:34 -0800 (PST) (envelope-from yakov@juniper.net)
Message-ID: <200812162112.mBGLCYM14365@magenta.juniper.net>
To: raszuk@juniper.net
In-Reply-To: <4948121A.2060108@juniper.net>
References: <200812161847.mBGIlxM42915@magenta.juniper.net> <4948031F.6080802@juniper.net> <200812161952.mBGJqfM76382@magenta.juniper.net> <4948121A.2060108@juniper.net>
X-MH-In-Reply-To: Robert Raszuk <raszuk@juniper.net> message dated "Tue, 16 Dec 2008 12:39:54 -0800."
MIME-Version: 1.0
Content-ID: <32844.1229461954.1@juniper.net>
Date: Tue, 16 Dec 2008 13:12:34 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 16 Dec 2008 21:12:35.0117 (UTC) FILETIME=[043D7DD0:01C95FC3]
Cc: idr@ietf.org
Subject: Re: [Idr] Fwd: New Version Notification for draft-scudder-idr-open-registr y-00
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

Robert,

> Yakov,
> 
> I think it would be indeed the best of both .. To have an explanation 
> msg in the IANA registry for those OPEN msg optional parameters type codes.
> 
> In fact John's text can already serve as such.

That would be fine with me too, as long as Routing ADs are ok with
this.

Yakov.

> 
> Thx,
> R.
> 
> > Robert,
> > 
> >> IMHO we should just fix IANA Considerations section of 4271 by issuing a 
> >> new version of it rather then having pointer in the IANA registry of 
> >> OPEN msg optional parameters to one paragraph spec redirecting to 
> >> incomplete RFC 4271.
> > 
> > We had a similar situation before, where BGP Communities (rfc1997)
> > defined Communities without specifying registry for such communities.
> > This was addressed *not* by issuing a new version of rfc1997, but
> > by a message from Routing AD (Dave Ward) to the IDR mailing list
> > that proposed the text for the registry. After discussion on the
> > mailing list and at the IDR WG meeting we reached a consensus on
> > this text, and subsequently IANA established such registry.
> > 
> > Yakov.
> > 
> >> Cheers,
> >> R.
> >>
> >>> Folks,
> >>>
> >>> Please comment on the attached. The deadline for comments is Dec 31, 2008
.
> > 
> 
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email