RE: AD Review of draft-ietf-vpim-vpimdir and draft-ietf-vpim-rout ing
"Glenn Parsons" <[email protected]> Mon, 9 Aug 2004 11:35:11 -0400
| Newsgroups | gmane.ietf.vpim |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============0715849313== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C47E26.6789A0A7" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C47E26.6789A0A7 Content-Type: text/plain; charset="ISO-8859-1" FYI > ---------- > From: Hollenbeck, Scott > Sent: Monday, August 9, 2004 10:38 AM > To: '[email protected]'; Parsons, Glenn [CAR:1A11:EXCH] > Cc: '[email protected]' > Subject: AD Review of draft-ietf-vpim-vpimdir and > draft-ietf-vpim-routing > > Glenn, Greg: > > Please forward a copy of this to the VPIM WG mailing list. I'm having > some > trouble sending mail from my subscribed address, but I want this to appear > in the WG list archives. > > I've completed my review of draft-ietf-vpim-vpimdir and > draft-ietf-vpim-routing. Here are my comments, which I've added to the > I-D > tracker: > > draft-ietf-vpim-vpimdir: The IANA Considerations section notes that > private > OIDs are being used, and loosely suggests that "IANA will provide a > replacement value from the IANA standards branch". There should be a > specific registration request in this section. Is this the "IANA > standards > branch" being described?: > > http://www.iana.org/assignments/ldap-parameters > > RFC 2279 (UTF-8) has been obsoleted by RFC 3629. Which reference is > appropriate? > > draft-ietf-vpim-routing: The abstract in section 1 is missing. > > I'd like to have the ENUM working group review this document, too. I'll > ask > them to do so. > > RFC 2915 has been obsoleted by RFCs 3401, 3402, 3403, and 3404. Which > reference is appropriate? > > RFC 2916 has been obsoleted by RFC 3761. Which reference is appropriate? > > Depending on what you have to say about the comments and what the ENUM WG > has to say about the service registrations, document updates will probably > be needed before I will feel comfortable requesting a last call. > > -Scott- > > ------_=_NextPart_001_01C47E26.6789A0A7 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3DISO-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2656.31"> <TITLE>RE: AD Review of draft-ietf-vpim-vpimdir and = draft-ietf-vpim-routing</TITLE> </HEAD> <BODY> <P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">FYI</FONT> </P> <UL> <P><FONT SIZE=3D2 FACE=3D"Arial">----------</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:</FONT></B> <FONT = SIZE=3D2 FACE=3D"Arial">Hollenbeck, Scott</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:</FONT></B> <FONT = SIZE=3D2 FACE=3D"Arial">Monday, August 9, 2004 10:38 AM</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:</FONT></B> = <FONT SIZE=3D2 FACE=3D"Arial">'[email protected]'; Parsons, Glenn = [CAR:1A11:EXCH]</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:</FONT></B> = <FONT SIZE=3D2 FACE=3D"Arial">'[email protected]'</FONT> <BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:</FONT></B> = <FONT SIZE=3D2 FACE=3D"Arial">AD = Review of draft-ietf-vpim-vpimdir and draft-ietf-vpim-routing</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">Glenn, Greg:</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">Please forward a copy of this to the = VPIM WG mailing list. I'm having some</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">trouble sending mail from my = subscribed address, but I want this to appear</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">in the WG list archives.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">I've completed my review of = draft-ietf-vpim-vpimdir and</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">draft-ietf-vpim-routing. Here = are my comments, which I've added to the I-D</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">tracker:</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">draft-ietf-vpim-vpimdir: The IANA = Considerations section notes that private</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">OIDs are being used, and loosely = suggests that "IANA will provide a</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">replacement value from the IANA = standards branch". There should be a</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">specific registration request in = this section. Is this the "IANA standards</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">branch" being = described?:</FONT> </P> <P><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Monaco"><A = HREF=3D"http://www.iana.org/assignments/ldap-parameters" = TARGET=3D"_blank">http://www.iana.org/assignments/ldap-parameters</A></F= ONT></U> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">RFC 2279 (UTF-8) has been obsoleted = by RFC 3629. Which reference is</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">appropriate?</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">draft-ietf-vpim-routing: The abstract = in section 1 is missing.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">I'd like to have the ENUM working = group review this document, too. I'll ask</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">them to do so.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">RFC 2915 has been obsoleted by RFCs = 3401, 3402, 3403, and 3404. Which</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">reference is appropriate?</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">RFC 2916 has been obsoleted by RFC = 3761. Which reference is appropriate?</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">Depending on what you have to say = about the comments and what the ENUM WG</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">has to say about the service = registrations, document updates will probably</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">be needed before I will feel = comfortable requesting a last call.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">-Scott-</FONT> </P> <BR> </UL> </BODY> </HTML> ------_=_NextPart_001_01C47E26.6789A0A7-- --===============0715849313== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ VPIM mailing list [email protected] https://www1.ietf.org/mailman/listinfo/vpim --===============0715849313==--