I would like to make some comments on draft-kreeger-nvo3-overlay-cp-03.
In section 2 "Terminology" it states:
VN Alias: A string name for a VN as used by administrators and
customers to name a specific VN. A VN Alias is a human-usable
string that can be listed in contracts, customer forms, email,
configuration files, etc. and that can be communicated easily
vocally (e.g., over the phone). A VN Name is independent of the
underlying technology used to implement a VN and will generally
not be carried in protocol fields of control protocols used in
virtual networks. Rather, a VN Alias will be mapped into a VN
Name where precision is required.
I think, it should state:
VN Alias: A string name for a VN as used by administrators and
customers to name a specific VN. A VN Alias is a human-usable
string that can be listed in contracts, customer forms, email,
configuration files, etc. and that can be communicated easily
vocally (e.g., over the phone). A VN Alias is independent of the
underlying technology used to implement a VN and will generally
not be carried in protocol fields of control protocols used in
virtual networks. Rather, a VN Alias will be mapped into a VN
Name where precision is required.
In section 2 it states further:
VN ID: A unique and compact identifier for a VN within the scope of
a specific NVO3 administrative domain. It will generally be more
efficient to carry VN IDs as fields in control protocols than VN
Aliases. There is a one-to-one mapping between a VN Name and a VN
ID within an NVO3 Administrative Domain. Depending on the
technology used to implement an overlay network, the VN ID could
be used as the VN Context in the data plane, or would need to be
mapped to a locally-significant context ID.
It think, it should state:
VN ID: A unique and compact identifier for a VN within the scope of
a specific NVO3 administrative domain. It will generally be more
efficient to carry VN IDs as fields in control protocols than VN
Names. There is a one-to-one mapping between a VN Name and a VN
ID within an NVO3 Administrative Domain. Depending on the
technology used to implement an overlay network, the VN ID could
be used as the VN Context in the data plane, or would need to be
mapped to a locally-significant context ID.
Thanks,
Florian
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
