Re: RFC 6117 on IANA Registration of Enumservices: Guide, Template, and IANA Considerations The Experts ..

"Livingood, Jason" <[email protected]> Mon, 14 Mar 2011 13:20:45 +0000
Newsgroups gmane.ietf.enum
Message-ID <C9A38D8D.1E028%[email protected]>
--===============0560855234==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_C9A38D8D1E028jasonlivingoodcablecomcastcom_"

--_000_C9A38D8D1E028jasonlivingoodcablecomcastcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

FINALLY!! (The =9600 was published in February 2006 and we had 22 revisions=
.)

:-)

Jason

On 3/12/11 5:02 PM, "Richard Shockey" <[email protected]<mailto:richard@sh=
ockey.us>> wrote:

Well its seems it's about time to declare victory...

The last thing we need to do is recommend to the IESG the List of Expert
Reviewers.

Any volunteers?

Gonzalo .. I'll volunteer.

-----Original Message-----
From: [email protected]<mailto:[email protected]>=
 [mailto:[email protected]]
On Behalf Of [email protected]<mailto:[email protected]>
Sent: Friday, March 11, 2011 9:12 PM
To: [email protected]<mailto:[email protected]>; rfc-dist@rfc-edi=
tor.org<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:r=
[email protected]>
Subject: RFC 6117 on IANA Registration of Enumservices: Guide, Template, an=
d
IANA Considerations


A new Request for Comments is now available in online RFC libraries.


        RFC 6117

        Title:      IANA Registration of Enumservices: Guide,
                    Template, and IANA Considerations
        Author:     B. Hoeneisen, A. Mayrhofer,
                    J. Livingood
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2011
        Mailbox:    [email protected]<mailto:[email protected]=
h>,
                    [email protected]<mailto:alexander.mayrhofer@=
enum.at>,
                    [email protected]<mailto:jason_livingoo=
[email protected]>
        Pages:      40
        Characters: 83838
        Obsoletes:  RFC3761

        I-D Tag:    draft-ietf-enum-enumservices-guide-22.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6117.txt

This document specifies a revision of the IANA Registration
Guidelines for Enumservices, describes corresponding registration
procedures, and provides a guideline for creating Enumservice
Specifications.  [STANDARDS-TRACK]

This document is a product of the Telephone Number Mapping Working Group of
the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]<mailto:rfc-e=
[email protected]>.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
IETF-Announce mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
enum mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/enum


--_000_C9A38D8D1E028jasonlivingoodcablecomcastcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <[email protected]>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>FINALLY!! (The =9600 was published in February 2006 and we had 22 revi=
sions.)</div>
</div>
<div><br>
</div>
<div>:-)</div>
<div><br>
</div>
<div>Jason</div>
<div><br>
</div>
<div>On 3/12/11 5:02 PM, &quot;Richard Shockey&quot; &lt;<a href=3D"mailto:=
[email protected]">[email protected]</a>&gt; wrote:</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>Well its seems it's about time to declare victory...</div>
<div><br>
</div>
<div>The last thing we need to do is recommend to the IESG the List of Expe=
rt</div>
<div>Reviewers.</div>
<div><br>
</div>
<div>Any volunteers? </div>
<div><br>
</div>
<div>Gonzalo .. I'll volunteer. </div>
<div><br>
</div>
<div>-----Original Message-----</div>
<div>From: <a href=3D"mailto:[email protected]">ietf-announce-=
[email protected]</a> [<a href=3D"mailto:[email protected]">mai=
lto:[email protected]</a>]</div>
<div>On Behalf Of <a href=3D"mailto:[email protected]">rfc-editor@r=
fc-editor.org</a></div>
<div>Sent: Friday, March 11, 2011 9:12 PM</div>
<div>To: <a href=3D"mailto:[email protected]">[email protected]</=
a>; <a href=3D"mailto:[email protected]">
[email protected]</a></div>
<div>Cc: <a href=3D"mailto:[email protected]">[email protected]</a>; <a href=3D"mai=
lto:[email protected]">
[email protected]</a></div>
<div>Subject: RFC 6117 on IANA Registration of Enumservices: Guide, Templat=
e, and</div>
<div>IANA Considerations</div>
<div><br>
</div>
<div><br>
</div>
<div>A new Request for Comments is now available in online RFC libraries.</=
div>
<div><br>
</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RFC 6117</div>
<div><br>
</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title:&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;IANA Registration of Enumservices: Guide, </div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Template, and IANA Consid=
erations </div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Author:&nbsp;&nbsp;&nb=
sp;&nbsp; B. Hoeneisen, A. Mayrhofer,</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;J. Livingood</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Status:&nbsp;&nbsp;&nb=
sp;&nbsp; Standards Track</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Stream:&nbsp;&nbsp;&nb=
sp;&nbsp; IETF</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Date:&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; March 2011</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Mailbox:&nbsp;&nbsp;&n=
bsp;&nbsp;<a href=3D"mailto:[email protected]">[email protected]=
.ch</a>,
</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"mailto:alexand=
[email protected]">[email protected]</a>,
</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"mailto:jason_l=
[email protected]">[email protected]</a></div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pages:&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;40</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Characters: 83838</div=
>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Obsoletes:&nbsp;&nbsp;=
RFC3761</div>
<div><br>
</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I-D Tag:&nbsp;&nbsp;&n=
bsp;&nbsp;draft-ietf-enum-enumservices-guide-22.txt</div>
<div><br>
</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;URL:&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://www.rfc-editor.org/rfc/rfc6=
117.txt">http://www.rfc-editor.org/rfc/rfc6117.txt</a></div>
<div><br>
</div>
<div>This document specifies a revision of the IANA Registration</div>
<div>Guidelines for Enumservices, describes corresponding registration</div=
>
<div>procedures, and provides a guideline for creating Enumservice</div>
<div>Specifications.&nbsp;&nbsp;[STANDARDS-TRACK]</div>
<div><br>
</div>
<div>This document is a product of the Telephone Number Mapping Working Gro=
up of</div>
<div>the IETF.</div>
<div><br>
</div>
<div>This is now a Proposed Standard Protocol.</div>
<div><br>
</div>
<div>STANDARDS TRACK: This document specifies an Internet standards track</=
div>
<div>protocol for the Internet community,and requests discussion and sugges=
tions</div>
<div>for improvements.&nbsp;&nbsp;Please refer to the current edition of th=
e Internet</div>
<div>Official Protocol Standards (STD 1) for the standardization state and<=
/div>
<div>status of this protocol.&nbsp;&nbsp;Distribution of this memo is unlim=
ited.</div>
<div><br>
</div>
<div>This announcement is sent to the IETF-Announce and rfc-dist lists.</di=
v>
<div>To subscribe or unsubscribe, see</div>
<div>&nbsp;&nbsp;<a href=3D"http://www.ietf.org/mailman/listinfo/ietf-annou=
nce">http://www.ietf.org/mailman/listinfo/ietf-announce</a></div>
<div>&nbsp;&nbsp;<a href=3D"http://mailman.rfc-editor.org/mailman/listinfo/=
rfc-dist">http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a></div>
<div><br>
</div>
<div>For searching the RFC series, see <a href=3D"http://www.rfc-editor.org=
/rfcsearch.html">
http://www.rfc-editor.org/rfcsearch.html</a>.</div>
<div>For downloading RFCs, see <a href=3D"http://www.rfc-editor.org/rfc.htm=
l">http://www.rfc-editor.org/rfc.html</a>.</div>
<div><br>
</div>
<div>Requests for special distribution should be addressed to either the</d=
iv>
<div>author of the RFC in question, or to <a href=3D"mailto:rfc-editor@rfc-=
editor.org">
[email protected]</a>.&nbsp;&nbsp;Unless</div>
<div>specifically noted otherwise on the RFC itself, all RFCs are for</div>
<div>unlimited distribution.</div>
<div><br>
</div>
<div><br>
</div>
<div>The RFC Editor Team</div>
<div>Association Management Solutions, LLC</div>
<div><br>
</div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>IETF-Announce mailing list</div>
<div><a href=3D"mailto:[email protected]">[email protected]</a></=
div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/ietf-announce">https:=
//www.ietf.org/mailman/listinfo/ietf-announce</a></div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>enum mailing list</div>
<div><a href=3D"mailto:[email protected]">[email protected]</a></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/enum">https://www.iet=
f.org/mailman/listinfo/enum</a></div>
<div><br>
</div>
</blockquote>
</body>
</html>

--_000_C9A38D8D1E028jasonlivingoodcablecomcastcom_--

--===============0560855234==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
enum mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/enum

--===============0560855234==--