Document Details - IPNNI-2021-00022R003.docx


Document Details
Share |
Name IPNNI-2021-00022R003.docx (171K)
Revision 3
Description Below are some examples of origids that we have seen in production that are not compliant with the recommended format (RFC 4122 UUID):

"# smbios implementations newer than version 2.8 are not"
"1234"
"858"
"986279842-79894328-45254-42543525243"
"FFFFFFFF-FFFF-FFFF-FFFF-010100000000"
"ba4f451c-cca7-2526-e053-b29a10ac35fe"


R0 proposed changing the described origid format and purpose in ATIS-1000074 from being recommended (SHOULD) to being required (MUST).

Based on feedback from the group, R1:

1. Does NOT change the format and purpose from SHOULD to MUST (reverts the changed text in R0 back to the baseline).
2. Requires that the origid be a string (this is currently not required in any ATIS or IETF document).
3. Removes the word unique when describing the origid because there is no requirement that origids be unique and many implementations currently use non-unique origids.
4. Removes call analytics as a purpose of the origid (the traceback purpose remains).

R2 fixes a typo and changes MUST to SHALL for consistency with the rest of the document.

R3 contains edits from the IP-NNI TF meeting on March 11, 2021.
Document State Contribution ((e.g., text to progress Issues))
Group / Folder ATIS/SIP Forum IP-NNI Task Force / IPNNI / 2021
Submitter By Anna Karditzas on Thursday, 11 March 2021 01:09pm
Technical Contact None Selected
Public URL https://access.atis.org/apps/group_public/document.php?document_id=58390&wg_abbrev=ipnni

Document Revisions
Name # State Submitter Date Action
3
Contribution
Anna Karditzas
2021-03-11
This doc
2
Contribution
Alec Fenichel
2021-02-27
1
Contribution
Alec Fenichel
2021-02-25
0
Administrative
Alec Fenichel
2021-02-11