IAX: Inter-Asterisk eXchange Version 2
draft-guy-iax-05

[Ballot comment]
I agree with Chris that details required to implement the
security mechanisms are missing. The protocol also
does not provide features like cryptographic algorithm
agility that would be required if this was an IETF protocol.

[Ballot comment]
I don't believe the specification has enough information to implement the MD5 and RSA authentication mechanisms.

Have the authors considered a mechanism to activate DTLS (4347)?

[Note]: 'The IESG thinks that this work is related to IETF work done in SIP, MMUSIC, and AVT WGs, but this does not prevent publishing.' added by Cullen Jennings

[Ballot discuss]
The note should cover the other WGs that also are doing work in this space, i.e. AVT and MMUSIC, maybe also mediactrl.

I am also worried that this specification seems to have a very simplistic mechanism for indicating congestion. It is also unclear what type of congestion they are talking about, call arrival or traffic induced network congestion. I think we need a more explicit IESG note for this.

IANA Evaluation comments:

IANA sent the authors the following questions:

- Do you want a registry of Message Types (Section 6)?

- Do you want a registry of Frame Types (Section 8.1.1, 8.2)?

- Do you want a registry of Comfort Noise Frames (Section 8.2.10)?

- Do you want a registry of Control Frames (Section 8.2.11)?

- Do you want a registry of IAX Frames (Section 8.2.12)?

- Do you want a registry of HTML Command Subclasses (Section 8.3)?

- Do you want a registry of IAX Information Elements (Section 8.4)?

- Do you want a registry of Authentication Methods (Section 8.4.13)?

- Do you want a registry of Dial Plan Status Flags (Section 8.4.19)?

- Do you want a registry of calling presentation values (Section 8.4.29)?

- Do you want a registry of calling type of number values (Section 8.4.30)?

- Do you want a registry of Network ID Plan Values (Section 8.4.31)?

- Do you want a registry of Network Type Values (Section 8.4.31)?

- Do you want a registry of Cause Codes (Section 8.4.33)?

- Do you want a registry of Encryption Methods (Section 8.4.34)?

- Do you want a registry of Media Formats (Section 8.5)?

These are the actions requested in the IANA Considerations
section:

Action 1 (see Section 5.1):

Upon approval of this document, IANA will change the status of
the following assignment in the "Uniform Resource Identifer (URI)
Schemes" registry (http://www.iana.org/assignments/uri-schemes.html) from
“provisional” to “permanent”:

URI Scheme Description Reference
--------- ----------- ------------
iax Inter-Asterisk eXchange [RFC-guy-iax-04]


Action 2:

Upon approval of this document, IANA will assign a UDP port from
the Well Known range at
http://www.iana.org/assignments/port-numbers

The following registered port numbers will be returned to the pool
of unassigned values:

Keyword Decimal Description References
------- ------- ----------- ----------
iax 4569/tcp Inter-Asterisk eXchange
iax 4569/udp Inter-Asterisk eXchange

Thank you.

[Note]: 'The IESG thinks that this work is related to IETF work done in SIP WG, but this does not prevent publishing.' added by Cullen Jennings