FW: [Enum] Fwd: Last Call: 'Voice Messaging Directory Service' to Proposed Standard
"Scott Hollenbeck" <[email protected]> Mon, 7 Feb 2005 09:13:06 -0500
| Newsgroups | gmane.ietf.vpim |
|---|---|
| Message-ID | <046F43A8D79C794FA4733814869CDF07057633@dul1wnexmb01.vcorp.ad.vrsn.com> |
Some comments on the last call for draft-ietf-vpim-routing-08.txt. -Scott- -----Original Message----- From: Stastny Richard [mailto:[email protected]]=20 Sent: Monday, February 07, 2005 9:06 AM To: Hollenbeck, Scott; [email protected] Subject: Re: [Enum] Fwd: [vpim] Last Call: 'Voice Messaging Directory Service' to Proposed Standard=20 So once again and officially: =20 I suggest or request the following change to http://www.ietf.org/internet-drafts/draft-ietf-vpim-routing-08.txt =20 to use instead of enumservice voice:dir=20 either=20 enumservice vpim:ldap (best choice) or enumservice vpim:dir =20 Rationale: 'voice' (as an Enumservice type) has already been "booked" in the VOVI drafts. Vovi-02 has only just expired, and we haven't yet shipped Vovi-3 only to refresh it as we're awaiting clarification on what the heck happened with Vovi's last call - this was to have taken place once we updated the draft to reflect concerns with Vovi-1, which we did, since which time... As the Enumservice type 'voice' is the 'top' of the IANA tree, we can't have two totally different Enumservices with the same type string, even if they have different subtypes. =20 =20 regards Richard PS: could anyone please crosspost to the vpim list ________________________________ Von: [email protected] im Auftrag von Hollenbeck, Scott Gesendet: Mo 07.02.2005 13:30 An: '[email protected]' Betreff: RE: [Enum] Fwd: [vpim] Last Call: 'Voice Messaging Directory Service' to Proposed Standard=20 > well you had better get your comments in now ... personally I > dont see a > problem with Greg's definitions. Even better than comments would be specific suggestions or requested changes. These two documents have been sitting around for quite a = while. I want to get them finished so I can close the VPIM working group. -Scott- _______________________________________________ enum mailing list [email protected] https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ VPIM mailing list [email protected] https://www1.ietf.org/mailman/listinfo/vpim