IANA Registration of Enumservices for Voice and Video Messaging
draft-ietf-enum-vmsg-02

[Ballot comment]
This seems specifically targeted to SIP instant messaging, so I believe
it's misleading to describe it as a function for all messaging systems.
I typically associate the term "messaging system" with an email server
with storage and list expansion capabilities (e.g., IMAP & SMTP) and I
don't think that's the intention of this specification.

[Ballot discuss]
This is a discuss discuss which I may or may not clear after the IESG
call.

When performing a fail-over operation while traversing a list of
references, there is always a question about how this interacts with
with the regular A or AAAA lookups likely to be performed on domain
names within the URI.  Is a client expected to try all A and all AAAA
records for a domain in a given URI before failing over to a lower
priority URI list?  I didn't have time to chase all the references, so
I'd like to understand whether or not this is specified to an appropriate
level of detail so that this can interoperate.

[Ballot discuss]
Question: Why does the draft specify separate Enumservice subtypes for
"sip"/"sips" (and "http"/"https")? It seems a single Enumservice for
both "sip"/"sips" would be sufficient (this approach is used in
e.g. E2U+SIP) -- but if a good reason exists, it would be interesting
to know why it didn't apply to earlier specs.

IANA Last Call comments:

Upon approval of this document, the IANA will make the following
assignments in the "Enumservice Registrations" registry at
http://www.iana.org/assignments/enum-services

Enumservice Name: "voicemsg"
Enumservice Type: "voicemsg"
Enumservice Subtypes: "sip"
URI Schemes: 'sip:'
Functional Specification:
This Enumservice indicates that the remote resource identified can
be addressed by the associated URI scheme in order to initiate a
voice communication session to a voice messaging system.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "voicemsg"
Enumservice Type: "voicemsg"
Enumservice Subtypes: "sips"
URI Schemes: 'sips:'
Functional Specification:
This Enumservice indicates that the remote resource identified can
be addressed by the associated URI scheme in order to initiate a
voice communication session to a voice messaging system.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "voicemsg"
Enumservice Type: "voicemsg"
Enumservice Subtype: "tel"
URI Schemes: 'tel:'
Functional Specification:
This Enumservice indicates that the remote resource identified can
be addressed by the associated URI scheme in order to initiate a
voice communication session to a voice messaging system.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "voicemsg"
Enumservice Type: "voicemsg"
Enumservice Subtype: "http"
URI Schemes: 'http:'
Functional Specification:
This Enumservice indicates that the remote resource identified by
the associated URI scheme is capable of being a source of
information.

Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI provides a
document. This document can contain references that will trigger
the download of many different kinds of information, such as text,
audio, video, executable code, or even voice message files. Thus,
one cannot be more specific about the kind of information expected
when contacting the resource.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "voicemsg"
Enumservice Type: "voicemsg"
Enumservice Subtype: "https"
URI Schemes: 'https:'
Functional Specification:
This Enumservice indicates that the remote resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure Socket
Layer protocol.

Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI provides a
document. This document can contain references that will trigger
the download of many different kinds of information, such as text,
audio, video, executable code, or even voice message files. Thus,
one cannot be more specific about the kind of information expected
when contacting the resource.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "videomsg"
Enumservice Type: "videomsg"
Enumservice Subtypes: "sip"
URI Schemes: 'sip:'
Functional Specification:
This Enumservice indicates that the remote resource identified can
be addressed by the associated URI scheme in order to initiate a
video communication session to a video messaging system.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "videomsg"
Enumservice Type: "videomsg"
Enumservice Subtypes: "sips"
URI Schemes: 'sips:'
Functional Specification:
This Enumservice indicates that the remote resource identified can
be addressed by the associated URI scheme in order to initiate a
video communication session to a video messaging system.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "videomsg"
Enumservice Type: "videomsg"
Enumservice Subtype: "http"
URI Schemes: 'http:'
Functional Specification:
This Enumservice indicates that the remote resource identified by the associated URI scheme is capable of being a source of
information.

Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI provides a
document. This document can contain references that will trigger
the download of many different kinds of information, such as text,
audio, video, executable code, or even video message files. Thus,
one cannot be more specific about the kind of information expected
when contacting the resource.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "videomsg"
Enumservice Type: "videomsg"
Enumservice Subtype: "https"
URI Schemes: 'https:'
Functional Specification:
This Enumservice indicates that the remote resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure Socket
Layer protocol.

Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI provides a
document. This document can contain references that will trigger
the download of many different kinds of information, such as text,
audio, video, executable code, or even video message files. Thus,
one cannot be more specific about the kind of information expected
when contacting the resource.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "unifmsg"
Enumservice Type: "unifmsg"
Enumservice Subtypes: "sip"
URI Schemes: 'sip:'
Functional Specification:
This Enumservice indicates that the remote resource identified can
be addressed by the associated URI scheme in order to initiate a
unified communication session to a unified messaging system.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "unifmsg"
Enumservice Type: "unifmsg"
Enumservice Subtypes: "sips"
URI Schemes: 'sips:'
Functional Specification:
This Enumservice indicates that the remote resource identified can
be addressed by the associated URI scheme in order to initiate a
unified communication session to a unified messaging system.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "unifmsg"
Enumservice Type: "unifmsg"
Enumservice Subtype: "http"
URI Schemes: 'http:'
Functional Specification:
This Enumservice indicates that the remote resource identified by
the associated URI scheme is capable of being a source of
information.

Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI provides a
document. This document can contain references that will trigger
the download of many different kinds of information, such as text,
audio, video, executable code, or even video message files. Thus,
one cannot be more specific about the kind of information expected
when contacting the resource.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

Enumservice Name: "unifmsg"
Enumservice Type: "unifmsg"
Enumservice Subtype: "https"
URI Schemes: 'https:'
Functional Specification:
This Enumservice indicates that the remote resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure Socket
Layer protocol.

Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI provides a
document. This document can contain references that will trigger
the download of many different kinds of information, such as text,
audio, video, executable code, or even video message files. Thus,
one cannot be more specific about the kind of information expected
when contacting the resource.
Security Considerations: See Section 4 of [RFC-enum-vmsg-02]
Intended Usage: COMMON
Authors:
Jason Livingood (jason_livingood@cable.comcast.com)
Don Troshynski (dtroshynski@acmepacket.com)
Any other information the author deems interesting:
Implementers should review a non-exclusive list of examples below
in Section 8 of [RFC-enum-vmsg-02]

We understand the above to be the only IANA Action for this
document.