OK, there are some fun discussion points here.
CHAIRS: Note well, we have moved well beyond the original points in my RTG-DIR review In line and trying to focus. [Linda2] Yes, need IANA registry. Reflected in -7 [AF3] OK. I see the registry. I think you still have work to do on it related to the 'C' bit. You don't have to do that now, but you will need to do it. [Linda3] Will chat with you during IETF119 on this subject. Well, since I won't be in Brisbane, please don't look for me in the corridor, too hard. I'm going to try to remember to be in the various chat spaces. My main point is . And you'll have to give IANA a clue about selecting from the range 128-255 to make sure the C-bit is set. [snip] --- > 4.6 and 4.7 > > Obviously, you are going to have to specify these TLVs in a future > version. For the include case, you are going to have to say whether this > is an ordered list, whether the inclusion is mandatory, and whether the > list is strict or loose. Multiple Include-Transit Sub-TLVs can be included in one GENEVE header to represent multiple nodes or regions to be included when the packet is steered through the Cloud Backbone. I-bit: When set to 0: it indicates it needs best effort to steer through the transit node ID. When set to 1, it indicates that the Transit Node ID must be included through the Cloud Backbone. If the Transit Node ID cannot be traversed, an alert or alarm must be generated to the enterprise via an out-of-band channel. It is out of the scope of this document to specify those alerts or alarms. [AF2] That is making progress. Thanks. I think you are still missing: * Is this an ordered list or just a set? [Linda3] Meant to say it is Not Ordered list. Sorry for the confusion. OK, take a look at what RSVP-TE did for inclusion (RFC 3209) and exclusion (RFC 4874). While it is fine for exclusion to be an unordered list, making inclusion unordered can lead to some interesting trombone/hairpin paths. Do you *really* want to force transit through GW1, GW2, and GW3 if the packet has already arrived at GW2 and can see a simple, short path to the destination? [AF2] * How is the string encoded? [Linda2] strictly between the enterprise <-> Cloud Provider. [AF3] So, is it a byte string or a character string? Is it printable? Is internationalization supported? How does an implementation at the enterprise manage to interwork with an implementation at the cloud provider? [Linda3] it is character string, like a region name, provided by the Cloud Provider. I suggest you go and talk with an expert in internationalization (that is not me!) to make sure you have enough detail in this section. Cheers, Adrian
_______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www.ietf.org/mailman/listinfo/rtgwg
