Hi all,

seeing that there appear to be no further comments, and that I want RIS
to support 4-byte ASes in the short future, the following will be
implemented as MRT format for the RIS raw data dumps.

(I copied some parts of previous posts, to make sure it is completely
clear what I'm referring to, after all these (useful!) ideas.)



- A new BGP4MP subtype: BGP4MP_STATE_CHANGE_32BIT_AS, assigned subtype 5
  Exactly the same as BGP4MP_STATE_CHANGE, except for a 32bit AS number,
  instead of 16.



- A new MRT routing information type: TABLE_DUMP_V2, assigned MRT type
  13.

TABLE_DUMP_V2 will be implemented as:

  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                         Sequence number                       |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                         Originated Time                       |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                    Peer IP address (variable)                 |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                        Peer AS (variable)                     |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 | Prefix Length |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                        Prefix (variable)                      |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |      Attribute Length         |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                    BGP Attributes... (variable)
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

If the NLRI type is IPv4-Unicast, the Prefix
Length and Prefix fields are included.  If the NLRI type
is multi-protocol, the Prefix Length and Prefix fields are
omitted and the NLRI information is contained in the
MP_REACH_NLRI attribute.

The subtype field for a TABLE_DUMP_V2 will use the following bitfields:
0 - unset for IPv4, set for IPv6
1 - unset when AS field is 16 bits, set when it's 32 bits
2 - unset for IPv4 unicast, set for multi-protocol

(So IPv6/asn16/unicast would make the subtype value 1, ipv6/asn32 would
be 3.)


cheers,
-- 
Erik Romijn                 RIPE NCC jr. software engineer
http://www.ripe.net/        Information Services dept.

Attachment: pgpfdZNBcDLsK.pgp
Description: PGP signature

_______________________________________________
GROW mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/grow

Reply via email to