Re: [v6ops] New Version Notification for draft-bp-v6ops-ipv6-ready-dns-dnssec-00.txt

Dear Jordi and Cameron,

I have read the draft and I agree with the solution (to provide also a 
AAAA record if the zone is DNSSEC signed) as a "recommendation".

However, I do not think that the timing described in Section 7 would be 
feasible. What do you mean under "MUST be suspended" in the following 
sentence?

	[...] If there is a failure at the
    deadline in complying with those requirements, the relevant NS, MUST
    be temporarily suspended until there is a subsequent successful
    verification.

Who would suspend what?

In my (admittedly incomplete) understanding  of the role of 
informational RFCs of the v6ops WG, they should provide guidance, and 
they may not command other bodies to do something.

Please correct me if I am mistaken.

Best regards,

Gábor

10/10/2018 8:32 PM keltezéssel, JORDI PALET MARTINEZ írta:
> Hi all,
>
> We have worked in an integrated version of two documents:
>
> draft-v6ops-byrne-dnssecaaaa
> draft-palet-sunset4-ipv6-ready-dns-00
>
> The new document is now:
>
> https://datatracker.ietf.org/doc/draft-bp-v6ops-ipv6-ready-dns-dnssec/?include_text=1
>
> Inputs welcome!
>
> Regards,
> Jordi
>   
>   
>
>
> -----Mensaje original-----
> De: <internet-drafts@ietf.org>
> Fecha: miércoles, 10 de octubre de 2018, 20:30
> Para: Jordi Palet <jordi.palet@theipv6company.com>, Jordi Palet Martinez <jordi.palet@theipv6company.com>, Cameron Byrne <cameron.byrne@t-mobile.com>, Cameron Byrne <Cameron.Byrne@T-Mobile.com>
> Asunto: New Version Notification for draft-bp-v6ops-ipv6-ready-dns-dnssec-00.txt
>
>      
>      A new version of I-D, draft-bp-v6ops-ipv6-ready-dns-dnssec-00.txt
>      has been successfully submitted by Jordi Palet Martinez and posted to the
>      IETF repository.
>      
>      Name:		draft-bp-v6ops-ipv6-ready-dns-dnssec
>      Revision:	00
>      Title:		IPv6-Ready DNS/DNSSSEC Infrastructure
>      Document date:	2018-10-10
>      Group:		Individual Submission
>      Pages:		6
>      URL:            https://www.ietf.org/internet-drafts/draft-bp-v6ops-ipv6-ready-dns-dnssec-00.txt
>      Status:         https://datatracker.ietf.org/doc/draft-bp-v6ops-ipv6-ready-dns-dnssec/
>      Htmlized:       https://tools.ietf.org/html/draft-bp-v6ops-ipv6-ready-dns-dnssec-00
>      Htmlized:       https://datatracker.ietf.org/doc/html/draft-bp-v6ops-ipv6-ready-dns-dnssec
>      
>      
>      Abstract:
>         This document defines the timing for implementing a worldwide
>         IPv6-Ready DNS and DNSSEC infrastructure, in order to facilitate the
>         global IPv6-only deployment.
>      
>         A key issue for this, is the need for a global support of DNSSEC and
>         DNS64, which in some scenarios do not work well together.  This
>         document states that any DNSSEC signed resources records should
>         include a native IPv6 resource record as the most complete and
>         expedient path to solve any deployment conflict with DNS64 and DNSSEC
>      
>                                                                                        
>      
>      
>      Please note that it may take a couple of minutes from the time of submission
>      until the htmlized version and diff are available at tools.ietf.org.
>      
>      The IETF Secretariat
>      
>      
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>