Re: [Idr] New version of draft-wang-idr-eag-distribution-00

"Jan Medved (jmedved)" <jmedved@cisco.com> Tue, 04 November 2014 02:00 UTC

Return-Path: <jmedved@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7537D1A1B11 for <idr@ietfa.amsl.com>; Mon, 3 Nov 2014 18:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.095
X-Spam-Level:
X-Spam-Status: No, score=-15.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsRI2d6Qfa8T for <idr@ietfa.amsl.com>; Mon, 3 Nov 2014 18:00:50 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAE071A1B7E for <idr@ietf.org>; Mon, 3 Nov 2014 18:00:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8642; q=dns/txt; s=iport; t=1415066449; x=1416276049; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=qoNUPYqCpQj11IKjlnswrmhoRaYbx91wzQjNANmF68k=; b=SMNY85vWLV4uCDqW58gVFc9c+E6ICIGai7jYpCmJGc5FoBk7CbHfDF4u X6Mcuf/9s5tZ6C9QnMIxYNRu6YL1qfl+6UYMuQU4mW9W3WMfhZSpDj6z/ 0zN4PSzxc4aNIMvVkijF/Psvq06G25mZiNZ6Pb/2wRAWNKsgkQG9PmmlQ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjkGALIyWFStJV2b/2dsb2JhbABcgw5UWASDAssxCodNAhyBBxYBAQEBAX2EAgEBAQQBAQEgEToLDAQCAQYCEQMBAQEBAgIjAwICAiULFAEICAIEAQ0FiEENmWucX5UDAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSBLY8wCBAbBwQCgnGBVAEEkhqET4cYgTGDTZFSg3hsgUiBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,311,1413244800"; d="scan'208";a="365892749"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-1.cisco.com with ESMTP; 04 Nov 2014 02:00:48 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id sA420mg0009229 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 4 Nov 2014 02:00:48 GMT
Received: from xmb-aln-x10.cisco.com ([169.254.5.151]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Mon, 3 Nov 2014 20:00:48 -0600
From: "Jan Medved (jmedved)" <jmedved@cisco.com>
To: "Osborne, Eric" <eric.osborne@level3.com>, Qin Wu <bill.wu@huawei.com>, "Bertrand Duvivier (bduvivie)" <bduvivie@cisco.com>, Hannes Gredler <hannes@juniper.net>, Jeff Tantsura <jeff.tantsura@ericsson.com>
Thread-Topic: [Idr] New version of draft-wang-idr-eag-distribution-00
Thread-Index: AQHP8tq71gzDGOJbXEecaEL53TvHU5xIlN8AgAA7YgCAACMZIIABQxcAgAVQSACAAAeSAA==
Date: Tue, 04 Nov 2014 02:00:48 +0000
Message-ID: <D07D6EDF.8E7F6%jmedved@cisco.com>
References: <D07528C7.771FD%jeff.tantsura@ericsson.com> <20141030073030.GE19169@hannes-mba.local> <D077CB41.8C7F1%jmedved@cisco.com> <5F1FD493E541C642ABBC18EDC327C82F1FF52148@xmb-aln-x11.cisco.com> <B8F9A780D330094D99AF023C5877DABA84625D35@nkgeml501-mbs.china.huawei.com> <63CB93BC589C1B4BAFDB41A0A19B7ACDFB32EA@USIDCWVEMBX08.corp.global.level3.com>
In-Reply-To: <63CB93BC589C1B4BAFDB41A0A19B7ACDFB32EA@USIDCWVEMBX08.corp.global.level3.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [10.27.7.170]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BD027D63728E1348B3388AE3B1B79C81@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/hmAvp3kIx5jec2Tc2hird7_6YdY
Cc: "idr@ietf.org" <idr@ietf.org>, Hares Susan <shares@ndzh.com>
Subject: Re: [Idr] New version of draft-wang-idr-eag-distribution-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 04 Nov 2014 02:00:52 -0000

Eric,

since BGP-LS has proven to be useful for distributing data other than link
state, we will keep finding new stuff that is “missing". So, as Hannes
pointed out, do we want to keep the document in a perpetual draft state,
or move it forward and define other types of stuff in different drafts?

In other words, is having EAG in the draft/RFC a necessary condition to
make the distribution of link-state function properly? Or is it a
necessary part of the NLRI/Attribute infrastructure proposed in the draft
to support distribution of LS (and other types of) data? If not, IMO it
merits its own draft.

Moreover, by adding EAG into the base BGP-LS draft we will make it a
mandatory requirement for all implementers to deal with it. At this point,
interoperability testing has been finished, and the draft and the
implementations have been aligned. We may have to restart the whole
process. There are plenty of examples of drafts/RFCs of similar scope that
augment some existing draft. I don’t see a reason why this should be a big
deal.



Thanks,
Jan


On 11/3/14, 8:33 AM, "Osborne, Eric" <eric.osborne@level3.com> wrote:

>-1, I guess, is my vote.  Not that we vote around here.
>
>I'm not sure I understand the practical benefit of closing it when we
>know there's stuff missing.  It's in WG LC, right?  Isn't the point to
>find things that need to be addressed *now*, rather than push it out the
>nest as quickly as possible when we already know we have a change to make?
>
>Adding EAG to bgp-ls isn't a big deal.  And it's not like people have
>never shipped product based on mature draft standards before.  Why not do
>it right while we still have the chance?
>
>
>
>
>eric
>
>> -----Original Message-----
>> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Qin Wu
>> Sent: Friday, October 31, 2014 4:25 AM
>> To: Bertrand Duvivier (bduvivie); Jan Medved (jmedved); Hannes Gredler;
>> Jeff Tantsura
>> Cc: idr@ietf.org; Hares Susan
>> Subject: Re: [Idr] New version of draft-wang-idr-eag-distribution-00
>> 
>> +1
>> Let's close the base spec for BGP-LS.
>> 
>> -Qin
>> -----邮件原件-----
>> 发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Bertrand Duvivier (bduvivie)
>> 发送时间: 2014年10月31日 2:19
>> 收件人: Jan Medved (jmedved); Hannes Gredler; Jeff Tantsura
>> 抄送: idr@ietf.org; Hares Susan
>> 主题: Re: [Idr] New version of draft-wang-idr-eag-distribution-00
>> 
>> Agree,
>> 
>> Best Regards Bertrand Duvivier
>> 
>> 
>> -----Original Message-----
>> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Jan Medved
>>(jmedved)
>> Sent: jeudi 30 octobre 2014 19:03
>> To: Hannes Gredler; Jeff Tantsura
>> Cc: idr@ietf.org; Hares Susan
>> Subject: Re: [Idr] New version of draft-wang-idr-eag-distribution-00
>> 
>> +1
>> 
>> bgp-ls is in the WG last call, let¹s not restart that clock.
>> 
>> 
>> Thanks,
>> Jan
>> 
>> 
>> On 10/30/14, 12:30 AM, "Hannes Gredler" <hannes@juniper.net> wrote:
>> 
>> >real question is:
>> >
>> >do we want to close BGP-LS base spec and submit it to IESG or leave it
>> >open as an eternal draft ? - IMO EAG is a useful thing hence vendors
>> >will be adding support for this, but can perfectly live as a standalone
>> >document,
>> >
>> >/hannes
>> >
>> >On Tue, Oct 28, 2014 at 06:12:28PM +0000, Jeff Tantsura wrote:
>> >|    Hi Eric,
>> >|    Agree, should be treated same way as AG and included in bgp-ls,
>> >|    Extended Administrative Group with TLV code point 1099
>> >|    Cheers,
>> >|    Jeff
>> >|    From: <Osborne>, Eric <[1]eric.osborne@level3.com>
>> >|    Date: Tuesday, October 28, 2014 at 6:48 AM
>> >|    To: wangzitao <[2]wangzitao@huawei.com>, "[3]idr@ietf.org"
>> >|    <[4]idr@ietf.org>
>> >|    Cc: Hares Susan <[5]shares@ndzh.com>
>> >|    Subject: Re: [Idr] New version of
>> >| draft-wang-idr-eag-distribution-00
>> >|
>> >|      I skimmed it and it  looks reasonable.  Given  that it really
>> >| just
>> > says
>> >|      ³use BGP-LS to send EAG just like we already send AG², why not
>> >just
>> >|      fold this content into bgp-ls?  The reason it¹s not in bgp-ls
>> >already
>> >|      is ­ I  suspect ­ just  a matter  of timing between  EAG and
>> >bgp-ls
>> >|      publication.
>> >|
>> >|
>> >|
>> >|
>> >|
>> >|
>> >|
>> >|
>> >|
>> >|      eric
>> >|
>> >|
>> >|
>> >|      From: Idr [[6]mailto:idr-bounces@ietf.org] On Behalf Of
>>wangzitao
>> >|      Sent: Monday, October 27, 2014 9:04 PM
>> >|      To: [7]idr@ietf.org
>> >|      Cc: Hares Susan
>> >|      Subject: [Idr] New version of draft-wang-idr-eag-distribution-00
>> >|
>> >|
>> >|
>> >|      Hi, folks:
>> >|
>> >|      We have  submitted  a new  short  draft  to discuss  BGP
>> >extension  for
>> >|      Extended admin Group
>> >|
>> >|
>> >| [8]https://tools.ietf.org/html/draft-wang-idr-eag-distribution-00
>> >|
>> >|      and requested a timeslot to present it at IETF91.
>> >|
>> >|      Please help review and comment on this short draft.
>> >|
>> >|      Thanks in advance.
>> >|
>> >|
>> >|
>> >|      Regards!
>> >|
>> >|      -Michael
>> >|
>> >| References
>> >|
>> >|    Visible links
>> >|    1. mailto:eric.osborne@level3.com
>> >|    2. mailto:wangzitao@huawei.com
>> >|    3. mailto:idr@ietf.org
>> >|    4. mailto:idr@ietf.org
>> >|    5. mailto:shares@ndzh.com
>> >|    6. mailto:idr-bounces@ietf.org
>> >|    7. mailto:idr@ietf.org
>> >|    8. https://tools.ietf.org/html/draft-wang-idr-eag-distribution-00
>> >
>> >| _______________________________________________
>> >| Idr mailing list
>> >| Idr@ietf.org
>> >| https://www.ietf.org/mailman/listinfo/idr
>> >
>> >_______________________________________________
>> >Idr mailing list
>> >Idr@ietf.org
>> >https://www.ietf.org/mailman/listinfo/idr
>> 
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>> 
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr