INFORMATIONAL

Errata Exist

Independent Submission M. Wilhelm Request for Comments: 7511 1 April 2015 Category: Informational ISSN: 2070-1721 Scenic Routing for IPv6 Abstract This document specifies a new routing scheme for the current version of the Internet Protocol version 6 (IPv6) in the spirit of "Green IT", whereby packets will be routed to get as much fresh-air time as possible. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7511. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Wilhelm Informational [Page 1]

RFC 7511 Scenic Routing 1 April 2015 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Conventions and Terminology . . . . . . . . . . . . . . . 3 2. Scenic Routing . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Scenic Routing Option (SRO) . . . . . . . . . . . . . . . 3 3. Implications . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Routing Implications . . . . . . . . . . . . . . . . . . 5 3.2. Implications for Hosts . . . . . . . . . . . . . . . . . 5 3.3. Proxy Servers . . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. Related Work . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . 7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 1 . Introduction RFC 5841 [RFC5841] provided some thoughts about Packet Moods and began to represent them as a TCP option, this doesn't help the packets escape their torturous routine. This document defines another way to deal with Green IT for traffic and network engineers and will hopefully aid the wellbeing of a myriad of network packets around the world. It proposes Scenic Routing, which incorporates the green-ness of a network path into the routing decision. A routing engine implementing Scenic Routing should therefore choose paths based on Avian IP Carriers [RFC1149] and/or wireless technologies so the packets will get out of the miles/kilometers of dark fibers that are in the ground and get as much fresh-air time and sunlight as possible. As of the widely known acceptance of the current version of the Internet Protocol (IPv6), this document only focuses on version 6 and ignores communication still based on Vintage IP [RFC791]. Wilhelm Informational [Page 2]

RFC 7511 Scenic Routing 1 April 2015 1.1 . Conventions and Terminology RFC 2119 [RFC2119]. Additionally, the key words "MIGHT", "COULD", "MAY WISH TO", "WOULD PROBABLY", "SHOULD CONSIDER", and "MUST (BUT WE KNOW YOU WON'T)" in this document are to interpreted as described in RFC 6919 [RFC6919]. 2 . Scenic Routing 2.1 . Scenic Routing Option (SRO) RFC2460]. The SRO can be included in any IPv6 datagram, but multiple SROs MUST NOT be present in the same IPv6 datagram. The SRO has no alignment requirement. If the SRO is set for a packet, every node en route from the packet source to the packet's final destination MUST preserve the option. The following Hop-by-Hop Option is proposed according to the specification in Section 4.2 of RFC 2460 [RFC2460]. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Option Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SRO Param | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Scenic Routing Option Layout Option Type 8-bit identifier of the type of option. The option identifier 0x0A (On Air) is proposed for Scenic Routing. Wilhelm Informational [Page 3]

RFC 7511 Scenic Routing 1 April 2015 Wilhelm Informational [Page 4]

RFC 7511 Scenic Routing 1 April 2015 3.3 . Proxy Servers 4 . Security Considerations RFC 6214 [RFC6214] apply for links provided by Avian IP Carriers. General security considerations of wireless communication apply for links using wireless technologies. As the user is able to influence where flows and packets are being routed within the network, this MIGHT influence traffic-engineering considerations and network operators MAY WISH TO take this into account before enabling Scenic Routing on their devices. 5 . IANA Considerations Section 2.1. If this work is standardized, IANA is requested to assign a value from the "Destination Options and Hop-by-Hop Options" registry for the purpose of Scenic Routing. There are no IANA actions requested at this time. 6 . Related Work Wilhelm Informational [Page 6]

RFC 7511 Scenic Routing 1 April 2015 rfc2324.org Wilhelm Informational [Page 8]