Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt

[Stephen Kent <[e-mail]>]

Doug,

I'm puzzled by your interpretation of RFC 7607. Specifically, Section 2 
of 7607 says:


    2. Behavior



    A BGP speaker MUST NOT originate or propagate a route with an AS
    number of zero in the AS_PATH, AS4_PATH, AGGREGATOR, or
    AS4_AGGREGATOR attributes.

    An UPDATE message that contains the AS number of zero in the AS_PATH
    or AGGREGATOR attribute MUST be considered as malformed and be
    handled by the procedures specified in [RFC7606].

    An UPDATE message that contains the AS number of zero in the AS4_PATH
    or AS4_AGGREGATOR attribute MUST be considered as malformed and be
    handled by the procedures specified in [RFC6793].

    If a BGP speaker receives zero as the peer AS in an OPEN message, it
    MUST abort the connection and send a NOTIFICATION with Error Code
    "OPEN Message Error" and subcode "Bad Peer AS" (seeSection 6 of [RFC4271]).  A router MUST NOT initiate a connection claiming to be
    AS 0.

This seems pretty definitive, and normative, not just a "usage convention" for AS 0,
as you suggest.

Steve

> Thanks Steve,
>
> You are right that the RFCs below should be referenced also.  Having reviewed them again, nothing I said previously seems to have changed.   AS 0 is at best a suggested usage convention.
>
> The thing I like about the 6483 text is that it makes explicit that ROAs can and will be created beneath an AS 0 ROA (one usage scenario is forcing your customers to issue ROAs before announcing their routes) and that all of this is "by convention".   So while not normative, I though 6483 painted the best picture of the issues we were discussing.
>
> dougm