Re: [Sidrops] 8210bis

[Randy Bush <[e-mail]>]

>> while we're doing the ASPA PDU hack, do any implementors of 6810/8210
>> have comments based on experience implementing 6810/8210?

your comments really appreciated

> The one thing that tripped me up when implementing RTR was that the
> content of the End-of-data PDU had changed between versions 0 and 1 and
> this isn’t properly mentioned in 8210 (there’s a vague note in section
> 1.2 that one can really only interpret correctly in hindsight). Since
> the old format isn’t mentioned but in practice you will have to
> implement version 0, you need to read and implement an obsoleted RFC
> which seems a bit wrong to me.
> 
> It would be good if 8210bis would at least stick a big warning at its
> equivalent to section 5.8 or, better yet, show the format for version
> 0 as well.

both done.

> The other thing that is a bit iffy when implementing is that for the
> Router Key PDU the flags field is moved from the payload into to the
> header repurposing part of what is the session ID when present.

yuchhh!  <blush>

> Maybe for the ASPA PDU you could keep it in the payload?

5.12.  ASPA PDU

   0          8          16         24        31
   .-------------------------------------------.
   | Protocol |   PDU    |                     |
   | Version  |   Type   |         zero        |
   |    2     |    11    |                     |
   +-------------------------------------------+
   |                                           |
   |                 Length                    |
   |                                           |
   +-------------------------------------------+
   |          |          |                     |
   |  Flags   |   zero   |  Provider AS Count  |
   |          |          |                     |
   +-------------------------------------------+
   |                                           |
   |    Customer Autonomous System Number      |
   |                                           |
   +-------------------------------------------+
   |                                           |
   |    Provider Autonomous System Number      |
   |                                           |
   ~-------------------------------------------~

   The ASPA PDU is to support [I-D.ietf-sidrops-aspa-profile].

   The lowest-order bit of the Flags field is 1 for an announcement and
   0 for a withdrawal.  Withdrawal of a non-existant or non-matching
   ASPA PDU is an error.

   The Provider AS Count is the number of 32-bit Provider Autonomous
   System Numbers in the PDU.  There may be none.

   The Customer Autonomous System Number is the 32-bit Autonomous System
   Number of the customer which signed the PDU.  There may be only one
   ASPA for a Customer Autonomous System Number active at any time.

   There are zero or more 32-bit Provider Autonomous System Number
   fields; see [I-D.ietf-sidrops-aspa-profile].