draft-ietf-v6ops-ipv6-discard-prefix-04.txt   draft-ietf-v6ops-ipv6-discard-prefix-05.txt 
v6ops Working Group N. Hilliard v6ops Working Group N. Hilliard
Internet-Draft INEX Internet-Draft INEX
Updates: 5156 (if approved) D. Freedman Intended status: Informational D. Freedman
Intended status: Informational Claranet Expires: December 11, 2012 Claranet
Expires: November 23, 2012 May 22, 2012 June 9, 2012
A Discard Prefix for IPv6 A Discard Prefix for IPv6
draft-ietf-v6ops-ipv6-discard-prefix-04 draft-ietf-v6ops-ipv6-discard-prefix-05
Abstract Abstract
Remote triggered black hole filtering describes a method of Remote triggered black hole filtering describes a method of
mitigating the effects of denial-of-service attacks by selectively mitigating the effects of denial-of-service attacks by selectively
discarding traffic based on source or destination address. Remote discarding traffic based on source or destination address. Remote
triggered black hole routing describes a method of selectively re- triggered black hole routing describes a method of selectively re-
routing traffic into a sinkhole router (for further analysis) based routing traffic into a sinkhole router (for further analysis) based
on destination address. This document updates RFC5156 by explaining on destination address. This document updates the IPv6 Special
why a unique IPv6 prefix should be formally assigned by IANA for the Purpose Address Registry by explaining why a unique IPv6 prefix
purpose of facilitating IPv6 remote triggered black hole filtering should be formally assigned by IANA for the purpose of facilitating
and routing. IPv6 remote triggered black hole filtering and routing.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 23, 2012. This Internet-Draft will expire on December 11, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 35 skipping to change at page 3, line 35
documentation in [RFC5737]. This approach is inadequate because RTBH documentation in [RFC5737]. This approach is inadequate because RTBH
configurations are not documentation, but rather operationally configurations are not documentation, but rather operationally
important features of many public-facing production networks. important features of many public-facing production networks.
Furthermore, [RFC3849] specifies that the IPv6 documentation prefix Furthermore, [RFC3849] specifies that the IPv6 documentation prefix
should be filtered in both local and public contexts. On this basis, should be filtered in both local and public contexts. On this basis,
it is suggested that both private network address blocks and the it is suggested that both private network address blocks and the
documentation prefixes described in [RFC5737] are inappropriate for documentation prefixes described in [RFC5737] are inappropriate for
RTBH configurations, and that a dedicated IPv6 prefix should be RTBH configurations, and that a dedicated IPv6 prefix should be
assigned instead. assigned instead.
This document updates [RFC5156]. This document updates the IPv6 Special Purpose Address Registry
[IANA-IPV6REG].
1.1. Notational Conventions 1.1. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. A Discard Prefix for IPv6 2. A Discard Prefix for IPv6
For the purposes of implementing an IPv6 remote triggered black hole For the purposes of implementing an IPv6 remote triggered black hole
skipping to change at page 4, line 41 skipping to change at page 4, line 42
On networks which implement IPv6 remote triggered black holes, some On networks which implement IPv6 remote triggered black holes, some
or all of this network block MAY be configured with a next-hop or all of this network block MAY be configured with a next-hop
destination of a discard or null interface on any or all IPv6 routers destination of a discard or null interface on any or all IPv6 routers
within the autonomous system. within the autonomous system.
4. IANA Considerations 4. IANA Considerations
This document directs IANA to record the allocation of the IPv6 This document directs IANA to record the allocation of the IPv6
address prefix xxxx/64 as a discard-only prefix in the IPv6 Address address prefix xxxx/64 as a discard-only prefix in the IPv6 Address
Space registry. No end party is to be assigned this prefix. The Space registry and to add the prefix to the IPv6 Special Purpose
prefix should be allocated from ::/3. Address Registry [IANA-IPV6REG]. No end party is to be assigned this
prefix. The prefix should be allocated from ::/3.
5. Security Considerations 5. Security Considerations
As the prefix specified in this document ought not normally be As the prefix specified in this document ought not normally be
transmitted or accepted over inter-domain BGP sessions for the transmitted or accepted over inter-domain BGP sessions for the
reasons described in Section 3, it is usually appropriate to include reasons described in Section 3, it is usually appropriate to include
this prefix in inter-domain BGP prefix filters [RFC3704] or otherwise this prefix in inter-domain BGP prefix filters [RFC3704] or otherwise
ensure the prefix is neither transmitted to or accepted from a third ensure the prefix is neither transmitted to or accepted from a third
party autonomous system. party autonomous system.
6. References 6. References
6.1. Normative References 6.1. Normative References
[IANA-IPV6REG]
Internet Assigned Numbers Authority, "IPv6 Special Purpose
Address Registry", 2012, <http://www.iana.org/assignments/
iana-ipv6-special-registry>.
[RFC3882] Turk, D., "Configuring BGP to Block Denial-of-Service [RFC3882] Turk, D., "Configuring BGP to Block Denial-of-Service
Attacks", RFC 3882, September 2004. Attacks", RFC 3882, September 2004.
[RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156,
April 2008.
[RFC5635] Kumari, W. and D. McPherson, "Remote Triggered Black Hole [RFC5635] Kumari, W. and D. McPherson, "Remote Triggered Black Hole
Filtering with Unicast Reverse Path Forwarding (uRPF)", Filtering with Unicast Reverse Path Forwarding (uRPF)",
RFC 5635, August 2009. RFC 5635, August 2009.
6.2. Informative References 6.2. Informative References
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets", E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996. BCP 5, RFC 1918, February 1996.
 End of changes. 8 change blocks. 
15 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/