Ali: The expected format for tunnel encapsulation text. The description should be filled out whether your implementations use the Extended Community form or the Path Attribute.
You may also indicate in your implementation report what usage is normal. Thanks for working on this draft and asking for comments. Sue ============================= Tunnel encapsulation specification requires the following things for every tunnel: 1) Name - Do: give a short name Do not: Please do not replicate a subTLV name (segment lists) 2) Code (TBD or assigned number) 3) Description - short function description or a link to a longr text 4) list of all SubTLV defined for TEA Do: Look at RFC9012 and any other TEA document you reference (draft-ietf-idr-sr-policy-safi) Gather a full list of subTLVs and put it in a table Tunnel-name SubTLV Supported SubTLVs not supported ------------ ------------------ ---------------------- 5) A validation procedures Do: Write up a validation procedure for each Tunnel. You can look at the validation procedures for [RFC9012], but you do not have validate using Tunnel-Egress Endpoint. Don't: Assume that one tunnel validation procedure matches another. 5) Security Considerations Please look draft-ietf-idr-sr-policy-safi for a good template. 6) Manageability section. How is the operator going to create the three new tunnels in configuration? What problems do you envision gluing It will be useful to have these in unique setions. ================================================= Sub-TLV write-ups: 1) Title: One Line Summary (e.g. RPF Sub-TLV) 2) Type: TBDxx (either value or TBDXX) (e.g. 124) 3) Encoding of value byte 3.1 diagram of byte layout (most people use 32 bit, but you can use 16 bit) 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | +---------------+---------------+ (on the RPF, I cannot tell if you have 1 byte or no bytes) 3.2 Description of each field with: a) title, definition (e.g. RPF Su b) size c) limits on the field (e.g. 3.3) Error handling
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
