Re: Last Call: draft-gould-rfc4310bis (Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol

Bernie Hoeneisen <[email protected]>
Newsgroups gmane.ietf.general,gmane.ietf.provreg
Message-ID <[email protected]>
I am a bit puzzeled that according to

   https://datatracker.ietf.org/idtracker/draft-gould-rfc4310bis/

draft-gould-rfc4310bis has already been placed on the IESG Telechat 
agenda, before the IETF Last Call has even ended.

Did this happen intentionally or by mistake?


Please be informed that on the provreg mailing list

   http://www.cafax.se/ietf-provreg/maillist/2010-01/maillist.html

there is a heavy discussion going on about the shortcomings of the current 
proposal. At least two issues have been identified so far:

1) XML namespace (interoperability issues as with the current proposal
    the feature negotiation does not work anymore as defined by the EPP
    core spec)

2) need for active / inactive flag (e.g. to mark a DS to be used for
    emergency key rollover)

Before these (and other) issues have been resolved, IMHO it does not make 
sense to discuss the I-D on the IESG Telechat.

The current proposal is still premature.


Furthermore due to lack of a Working Group (and lack of an _official_ IETF 
mailing list for EPP), many stakeholders are not even aware of EPP 
proposals going through standardization, which is somewhat in 
contradiction to the IETF transparency goals.

Have a nice weekend!

cheers,
  Bernie

-- 

http://ucom.ch/
Tech Consulting for Internet Standardization




Original Message:
> [...]
> Please send substantive comments to the
> [email protected] mailing lists by 2010-02-16. Exceptionally,
> comments may be sent to [email protected] instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
> [...]
> IESG discussion can be tracked via
> [...]
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=19451&rfc_flag=0
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.