RE: FW: Protocol Action: 'Extensible ProvisioningProtocol (EPP) Transportover TCP' to Full Standard

"Hollenbeck, Scott" <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <046F43A8D79C794FA4733814869CDF0702C729BB@dul1wnexmb01.vcorp.ad.vrsn.com>
I just sent an updated report to the Secretariat for posting.

-Scott- 

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Patrick Mevzek
> Sent: Thursday, August 20, 2009 10:14 AM
> To: [email protected]
> Subject: Re: [ietf-provreg] FW: Protocol Action: 'Extensible 
> ProvisioningProtocol (EPP) Transportover TCP' to Full Standard
> 
> Hello Scott,
> 
> Hollenbeck, Scott <[email protected]> 2009-08-20 15:10
> > 4934bis has been approved by the IESG.  That's the last of the 
> > document updates for Full Standard.  An updated 
> implementation report 
> > can be found here:
> > 
> > http://www.ietf.org/iesg/implementation/report-rfc4930-4934.txt
> > 
> > Thanks to everyone who helped move this forward.
> 
> Thanks for your work.
> 
> If it is still possible (and if not that is no big deal), can 
> you make the following changes:
> - use the From: email address used here for me in the document
> 
> and for EPP TLDs:
> - update .FR as it is used in production now (since March) (I 
> do not know for .SI, I think they are in production too, same for .NO)
> - add: .NL (being developed)
> - add: .IT
> - add: .CO.CZ (status unknown)
> 
> 
> 
> --
> Patrick Mevzek
> Dot and Co <http://www.dotandco.com/> <http://www.dotandco.net/>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> -=-=-=-=-=-=-
> List run by majordomo software.  For (Un-)subscription and 
> similar details send "help" to [email protected]
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software.  For (Un-)subscription and similar details
send "help" to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.