grow: draft-ietf-grow-anycast

[Joe Abley]

I made some small changes to draft-ietf-grow-anycast-01 in response to Pekka's most recent suggestions (see expurgated diff below). If there are no other comments on -01, I'll submit this as -02. The revised draft will be a candidate for a WGLC.

Joe

@@ -790,9 +790,11 @@
    that address might be signalled using a (32-bit) host route.
    For IPv6-numbered services, Anycast Addresses are not scoped

-   presented for IPv4 with respect to address suitability follow for
-   IPv6.

+   for IPv4 with respect to address suitability follow for IPv6.  Note

+   IPv6 have been removed from the IPv6 addressing specification in
+   [I-D.ietf-ipv6-addr-arch-v4].
4.6  Data Synchronisation
@@ -1237,6 +1237,11 @@
10.1  Normative References
+   [I-D.ietf-ipv6-addr-arch-v4]
+              Hinden, R. and S. Deering, "IP Version 6 Addressing
+              Architecture", draft-ietf-ipv6-addr-arch-v4-04 (work in
+              progress), May 2005.
+
    [RFC0793]  Postel, J., "Transmission Control Protocol", STD 7,
               RFC 793, September 1981.
@@ -1257,9 +1262,6 @@

               Address Spoofing", BCP 38, RFC 2827, May 2000.
-   [RFC3513]  Hinden, R. and S. Deering, "Internet Protocol Version 6
-              (IPv6) Addressing Architecture", RFC 3513, April 2003.
-

               Networks", BCP 84, RFC 3704, March 2004.
@@ -1413,11 +1413,15 @@
       some structural reorganisation; general wordsmithing.  Document
       discussed at IETF 62.
-   draft-ietd-grow-anycast-01:  This appendix added; acknowledgements
-      section added; commentary on [RFC3513] prohibition of anycast on
+   draft-ietf-grow-anycast-01:  This appendix added; acknowledgements
+      section added; commentary on RFC3513 prohibition of anycast on
       hosts removed; minor sentence re-casting and related jiggery-
       pokery.  This revision published for discussion at IETF 63.
+   draft-ietf-grow-anycast-02:  Normative reference to [I-D.ietf-ipv6-
+      addr-arch-v4] added (in the RFC editor's queue at the time of
+      writing; reference should be updated to an RFC number when
+      available).

- differently from unicast addresses [RFC3513]. As such the guidelines + differently from unicast addresses. As such the guidelines presented + that historical prohibitions on anycast distribution of services over Defeating Denial of Service Attacks which employ IP Source [RFC3704] Baker, F. and P. Savola, "Ingress Filtering for Multihomed

PGP.sig
Description: This is a digitally signed message part