Re: (v6ops) WG Last Call: draft-ietf-v6ops-renumbering-procedure-00.txt (fwd)

[Brian E Carpenter <brc@zurich.ibm.com>]

I's suggest that at this point in the discussion you can drop
the cross-posting to multi6.

While you are tweaking, it might be worth adding a note that
the eventual multi6 solution(s) may add new issues to
the renumbering recipe, or alternatively may simplify it.

   Brian



Fred Baker wrote:
> At 07:29 AM 07/08/04 +0300, Pekka Savola wrote:
>
> > A possible compromise here could be putting RFC3704 in as a 
> > *normative* reference (btw, some of those other ones might be as well 
> > because they're required for understanding), implying that it's a MUST 
> > read.. which could be interpreted as not having to summarize or 
> > repeats its contents here.
>
>
> I'm perfectly willing to do that. Will that address the issues?
>
> Glancing through, I at the moment have all references as informational. 
> It occurs to me that this is probably not right. Would you suggest the 
> following, or would you also make others normative? There is probably an 
> argument for making all or almost all of the RFCs normative, but my 
> sense is not to take quite that expansive of a view.
>
>         <references title="Normative References">
>                         <?rfc include="reference.RFC.2072" ?>
>                         <?rfc include="reference.RFC.2460" ?>
>                         <?rfc include="reference.RFC.2461" ?>
>                         <?rfc include="reference.RFC.2462" ?>
>                         <?rfc include="reference.RFC.3315" ?>
>                         <?rfc include="reference.RFC.3704" ?>
>         </references>
>                 <references title="Informative References">
>                         <?rfc include="reference.RFC.1034" ?>
>                         <?rfc include="reference.RFC.1035" ?>
>                         <?rfc include="reference.RFC.1305" ?>
>                         <?rfc include="reference.RFC.1995" ?>
>                         <?rfc include="reference.RFC.1996" ?>
>                         <?rfc include="reference.RFC.2136" ?>
>                         <?rfc include="reference.RFC.2535" ?>
>                         <?rfc include="reference.RFC.2827" ?>
>                         <?rfc include="reference.RFC.2845" ?>
>                         <?rfc include="reference.RFC.2931" ?>
>                         <?rfc include="reference.RFC.3007" ?>
>                         <?rfc include="reference.RFC.3177" ?>
>                         <?rfc 
> include="reference.I-D.ietf-dhc-dhcpv6-opt-prefix-delegation"?>
>                         <?rfc 
> include="reference.I-D.ietf-dnsop-ipv6-dns-issues"?>
>
>
>    [Clausewitz]
>               von Clausewitz, C., Howard, M., Paret, P. and D. Brodie,
>               "On War, Chapter VII, 'Friction in War'", June 1989.
>
>    [I-D.ietf-dhc-dhcpv6-opt-prefix-delegation]
>               Troan, O. and R. Droms, "IPv6 Prefix Options for DHCPv6",
>               draft-ietf-dhc-dhcpv6-opt-prefix-delegation-05 (work in
>               progress), October 2003.
>
>    [I-D.ietf-dnsop-ipv6-dns-issues]
>               Durand, A., Ihren, J. and P. Savola, "Operational
>               Considerations and Issues with IPv6 DNS",
>               draft-ietf-dnsop-ipv6-dns-issues-07 (work in progress),
>               May 2004.
>
>    [RFC1034]  Mockapetris, P., "Domain names - concepts and facilities",
>               STD 13, RFC 1034, November 1987.
>
>    [RFC1035]  Mockapetris, P., "Domain names - implementation and
>               specification", STD 13, RFC 1035, November 1987.
>
>    [RFC1305]  Mills, D., "Network Time Protocol (Version 3)
>               Specification, Implementation", RFC 1305, March 1992.
>
>    [RFC1995]  Ohta, M., "Incremental Zone Transfer in DNS", RFC 1995,
>               August 1996.
>
>    [RFC1996]  Vixie, P., "A Mechanism for Prompt Notification of Zone
>               Changes (DNS NOTIFY)", RFC 1996, August 1996.
>
>    [RFC2072]  Berkowitz, H., "Router Renumbering Guide", RFC 2072,
>               January 1997.
>
>    [RFC2136]  Vixie, P., Thomson, S., Rekhter, Y. and J. Bound, "Dynamic
>               Updates in the Domain Name System (DNS UPDATE)", RFC 2136,
>               April 1997.
>
>    [RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
>               (IPv6) Specification", RFC 2460, December 1998.
>
>    [RFC2461]  Narten, T., Nordmark, E. and W. Simpson, "Neighbor
>               Discovery for IP Version 6 (IPv6)", RFC 2461, December
>               1998.
>
>    [RFC2462]  Thomson, S. and T. Narten, "IPv6 Stateless Address
>               Autoconfiguration", RFC 2462, December 1998.
>
>    [RFC2535]  Eastlake, D., "Domain Name System Security Extensions",
>               RFC 2535, March 1999.
>
>    [RFC2827]  Ferguson, P. and D. Senie, "Network Ingress Filtering:
>               Defeating Denial of Service Attacks which employ IP Source
>               Address Spoofing", BCP 38, RFC 2827, May 2000.
>
>    [RFC2845]  Vixie, P., Gudmundsson, O., Eastlake, D. and B.
>               Wellington, "Secret Key Transaction Authentication for DNS
>               (TSIG)", RFC 2845, May 2000.
>
>    [RFC2931]  Eastlake, D., "DNS Request and Transaction Signatures (
>               SIG(0)s)", RFC 2931, September 2000.
>
>    [RFC3007]  Wellington, B., "Secure Domain Name System (DNS) Dynamic
>               Update", RFC 3007, November 2000.
>
>    [RFC3177]  IAB and IESG, "IAB/IESG Recommendations on IPv6 Address
>               Allocations to Sites", RFC 3177, September 2001.
>
>    [RFC3315]  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C. and
>               M. Carney, "Dynamic Host Configuration Protocol for IPv6
>               (DHCPv6)", RFC 3315, July 2003.
>
>    [RFC3704]  Baker, F. and P. Savola, "Ingress Filtering for Multihomed
>               Networks", BCP 84, RFC 3704, March 2004.