RFC Errata
Found 3 records.
Status: Held for Document Update (2)
RFC 5012, "Requirements for Emergency Context Resolution with Internet Technologies", January 2008
Source of RFC: ecrit (rai)
Errata ID: 1259
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-13
Held for Document Update by: Robert Sparks
Section 8, pg.19 says:
Ma14. Resilience to mapping server failure: The mapping protocol MUST support a mechanism that enables the client to fail over to different (replica) mapping server.
It should say:
Ma14. Resilience to mapping server failure: The mapping protocol | MUST support a mechanism that enables the client to fail over to a different (replica) mapping server.
Notes:
insert missing "a"
Errata ID: 1263
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-13
Held for Document Update by: Robert Sparks
Section 8 (p.19) says:
Ma15. Traceable resolution: The mapping protocol SHOULD support the | ability of the mapping client to be able to determine the entity or entities that provided the emergency address resolution information.
It should say:
Ma15. Traceable resolution: The mapping protocol SHOULD support the | ability of the mapping client to determine the entity or entities that provided the emergency address resolution information.
Notes:
"double replication": ability to <-> to be able to :-)
Note:
The previous entry of this same Errata Entry has been truncated
inadvertently -- please remove it.
Status: Rejected (1)
RFC 5012, "Requirements for Emergency Context Resolution with Internet Technologies", January 2008
Source of RFC: ecrit (rai)Errata ID: 1260
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-13
Rejected by: Robert Sparks
Date Rejected: 2010-12-06
Report Text:
double replication : ability to <-> to be able to :-) --VERIFIER NOTES-- Partial report repeated in errata 1263