Re: [Idr] Implementation call for draft-ietf-idr-bgp-extended-messages (1/24/2017 to 1/31/2017)

Oliver: 

Thank you for checking the updates.  Draft-ietf-idr-bgp-extended-messages has been sent to the IESG for publication. 

Sue 

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Borchert, Oliver (Fed)
Sent: Thursday, February 16, 2017 8:40 AM
To: Dongjie (Jimmy); Susan Hares; 'John Scudder'
Cc: idr-chairs@ietf.org; idr@ietf.org
Subject: Re: [Idr] Implementation call for draft-ietf-idr-bgp-extended-messages (1/24/2017 to 1/31/2017)

Looks good to me,
Oliver

On 2/16/17, 1:36 AM, "Dongjie (Jimmy)" <jie.dong@huawei.com> wrote:

    Hi Oliver, 

    Thanks for the updates of the implementation report. I've updated the wiki page accordingly, including some editorial changes:

    https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-extended-implementations

    Please review and let me know if you have any comments.

    Best regards,
    Jie

    > -----Original Message-----
    > From: Borchert, Oliver (Fed) [mailto:oliver.borchert@nist.gov]
    > Sent: Thursday, February 16, 2017 8:41 AM
    > To: Susan Hares <shares@ndzh.com>; 'John Scudder' <jgs@juniper.net>
    > Cc: idr-chairs@ietf.org; idr@ietf.org
    > Subject: Re: Implementation call for draft-ietf-idr-bgp-extended-messages
    > (1/24/2017 to 1/31/2017)
    > 
    > Sue,
    > We updated our implementations and below find the updated implementation
    > reports for QuaggaSRx and BGPSEC-IO:
    > 
    > Current Wiki summary:
    > https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-extended-implementations
    > 
    > 1	Announce via BGP Capability advertisement (RFC5492) as BGP Extended
    > Capability	Yes	Yes
    > 2	If Extended Message Capability supported, Implementation MUST be able
    > to:	-	-
    > 2a	RECEIVE OPEN message larger than 4096 bytes (section 4, paragraph 2)	Yes
    > 	Yes
    > 2b	RECEIVE A UPDATE message larger tan 4096 bytes	Yes	Yes
    > 3	Applications putting data into BGP Extended messages MUST limit size of
    > payload to handle max message sizes on pathway	Yes	Yes
    > 4	Supports EXTENDED MESSAGE, but peer has not advertised BGP Extended
    > Capability	-	-
    > 4a	SHOULD NOT accept message	yes	yes
    > 4b	MAY Accept EXTENDED MESSAGE (config/implementation knob)	Yes	Yes
    > 5	Does not support EXTENDED Message (no support in code)
    > 5a	Does not send Extended Message capability
    > 5b	If receives Extended Message, follows RFC4221 handling and sends Bad
    > message length Notification
    > 
    > 
    > Updated Summary:
    > 
    > QuaggaSRx
    > ==========
    > 1) yes
    > 2a) – Draft was updated – N/A
    > 2b) yes
    > 3) yes
    > 4a) yes
    > 4b) yes
    > 5a) yes, can be configured
    > 5b) yes, if configured to not support
    > 
    > BGPSEC-IO
    > =========
    > 1) yes
    > 2a) – Draft was updated – N/A
    > 2b) yes
    > 3) yes
    > 4a) yes
    > 4b) yes
    > 5a) yes, can be configured
    > 5b) yes, if configured to not support
    > 
    > Oliver
    > -------------------------------------------------------------
    > Oliver Borchert, Computer Scientist
    > National Institute of Standards and Technology
    > (Phone) 301.975.4856 , (Fax) 301.975.6238
    > 

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