IETF 59

It's the 59th IETF, and we are still a working group.

A year ago we managed to finish off the work leading to the documents 
that passed the IESG in May and June.  Since then the document waited 
for the start of an XML registry at IANA.  The documents are still 
waiting for publication - which is why we still are a WG.

--

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

History repeats, therefore my life is a rerun.

Re: IETF 59

any ETA on when the refrences will be complete. It seems silly to keep
this document from moving forward for more than 6 months because of an XML
registry creation factor at IANA.

Are we at the mercy of this beauracy?

Doesn't one any recognize that keeping these docs from being published
prevents the clock from starting on new gTLD (epp based) registries from
having to implement the adopted wg documents.

yes, ICANN wrote those agreements so that if the IETf ever came up with a
standard registries have 135 days to implement it.

is there any way to remove these [administrative] blocking factors?

-rick

On Mon, 1 Mar 2004, Edward Lewis wrote:

> It's the 59th IETF, and we are still a working group.
>
> A year ago we managed to finish off the work leading to the documents
> that passed the IESG in May and June.  Since then the document waited
> for the start of an XML registry at IANA.  The documents are still
> waiting for publication - which is why we still are a WG.
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Edward Lewis                                            +1-703-227-9854

RE: IETF 59

> any ETA on when the refrences will be complete. It seems silly to keep
> this document from moving forward for more than 6 months 
> because of an XML
> registry creation factor at IANA.

The documents are now in RFC-EDITOR status, which means that the RFC Editor
is doing their final review before passing them to me for my 48-hour author
review.  The documents should be done within the next few weeks.

-Scott-

Re: IETF 59

At 0:14 -0800 3/1/04, Rick Wesson wrote:
>is there any way to remove these [administrative] blocking factors?

I'd say no, well, at least nothing (constructive) I can think of as a 
co-chair.  I.e., nothing has been blocking on the WG, the editor, or 
anything else internal to the IETF.
--

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

History repeats, therefore my life is a rerun.

Re: IETF 59

> ... or anything else internal to the IETF.

Well ... ICANN is meeting in Rome this week. It is litigation season.
Maybe they can scare up something _external_ to the IETF.

Idle hands, etc.

Re: Incoming Fax

RFC 3730 on Extensible Provisioning Protocol (EPP)

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

        RFC 3730

        Title:      Extensible Provisioning Protocol (EPP)
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      69
        Characters: 134337
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3730.txt

This document describes an application layer client-server protocol
for the provisioning and management of objects stored in a shared
central repository.  Specified in XML, the protocol defines generic
object management operations and an extensible framework that maps
protocol operations to objects.  This document includes a protocol
specification, an object mapping template, and an XML media type
registration.

This document is a product of the Provisioning Registry Protocol
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

RFC 3731 on Extensible Provisioning Protocol (EPP) Domain Name Mapping

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

        RFC 3731

        Title:      Extensible Provisioning Protocol (EPP) Domain Name
                    Mapping
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      45
        Characters: 92527
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-domain-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3731.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of Internet domain names
stored in a shared central repository.  Specified in XML, the mapping
defines EPP command syntax and semantics as applied to domain names.

This document is a product of the Provisioning Registry Protocol
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

RFC 3732 on Extensible Provisioning Protocol (EPP) Host Mapping

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

        RFC 3732

        Title:      Extensible Provisioning Protocol (EPP) Host
                    Mapping
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      28
        Characters: 57082
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-host-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3732.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of Internet host names
stored in a shared central repository.  Specified in XML, the mapping
defines EPP command syntax and semantics as applied to host names.

This document is a product of the Provisioning Registry Protocol
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

RFC 3733 on Extensible Provisioning Protocol (EPP) Contact Mapping

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

        RFC 3733

        Title:      Extensible Provisioning Protocol (EPP) Contact
                    Mapping
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    shollenbeck <at> verisign.com
        Pages:      41
        Characters: 83091
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-contact-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3733.txt

This document describes an Extensible Provisioning Protocol (EPP)
mapping for the provisioning and management of individual or
organizational social information identifiers (known as "contacts")
stored in a shared central repository.  Specified in Extensible Markup
Language (XML), the mapping defines EPP command syntax and semantics
as applied to contacts.

This document is a product of the Provisioning Registry Protocol
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.