IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information
RFC 4769

Note: This ballot was opened for revision 05 and is now closed.

(Jon Peterson) Yes

(Jari Arkko) No Objection

(Brian Carpenter) (was Discuss) No Objection

Comment (2006-06-22)
No email
send info
From Gen-ART review by David Black:

-- IANA-related nits

a) The registrations in Section 4 need to be self-contained, as
they will be extracted into an IANA registry:

http://www.iana.org/assignments/enum-services

So, the "(for author contact detail see Authors' Addresses section)"
text will not work in the registry.  A reference to the to-be-
published RFC with instructions to the RFC-Editor to put in the
actual number and supply that number to IANA for registration
purposes should work.

b) Why does the IANA Considerations section include a reference
to Section 3?  The registrations that IANA needs to process
appear to be entirely contained within Section 4.

From id-nits:

  - Unused Reference: '9' is defined on line 449, but not referenced
  - Unused Reference: '12' is defined on line 460, but not referenced
  - Unused Reference: '16' is defined on line 472, but not referenced

(Lisa Dusseault) No Objection

(Lars Eggert) No Objection

Comment (2006-06-21 for -)
No email
send info
Section 11.1, paragraph 0:

 11.1 Normative References

        Nit: idnits says:
        Unused Reference: [9] is defined on line 449, but not referenced
        Unused Reference: [12] is defined on line 460, but not referenced
        Unused Reference: [16] is defined on line 472, but not referenced

(Bill Fenner) No Objection

Comment (2006-06-22 for -)
No email
send info
Note: the reference to rfc3401 is a downref.

(Ted Hardie) No Objection

(Sam Hartman) (was Discuss) No Objection

(Russ Housley) No Objection

(Cullen Jennings) No Objection

Comment (2006-06-21 for -)
No email
send info
I think the examples numbers used in this draft need a pass to check that none of them could ever be numbers assigned to a real phone.

(David Kessens) No Objection

(Dan Romascanu) No Objection

Comment (2006-06-21 for -)
No email
send info
RFC 3761 which includes the IANA registration process upon which the content of this work is based is mentioned several times in the text without the appropriate reference number [1].

(Mark Townsley) No Objection

Magnus Westerlund No Objection