Requirements for IPv6 Routers draft-ietf-v6ops-ipv6rtr-reqs

Slides:



Advertisements
Similar presentations
Jan Žorž Story about RIPE-501 and RIPE-554 1
Advertisements

IETF 60 draft-ooms-v6ops-bgp-tunnel-03.txt Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE) J. De Clerq, Alcatel D. Ooms S.
IPv6 CPE Router Bis draft-wbeebee-v6ops-ipv6-cpe-router-bis Hemant Singh Wes Beebee
UML Unified Markup Language Ziya Karakaya Atılım University, Computer Engineering
IPv6 RADIUS attributes for IPv6 access networks draft-lourdelet-radext-ipv6-access-01 Glen Zorn, Benoit Lourdelet Wojciech Dec, Behcet Sarikaya Radext/dhc.
1 464XLAT Combination of Stateful and Stateless Translation draft-ietf-v6ops-464xlat-01 IETF 83 v6ops WG Japan Internet Exchange Co.,Ltd.
BEHAVE BOF (Behavior Engineering for Hindrance AVoidancE) Cullen Jennings Jiri Kuthan.
1 Behcet Sarikaya Frank Xia Ted Lemon July 2011 DHCPv6 Prefix Delegation as IPv6 Migration Tool in Mobile Networks IETF 81
BFD Working Group Document Status – IETF 78 Jeffrey Haas, Dave Ward,
1 Virtual Router Redundancy Protocol (VRRP) San Francisco IETF VRRP Working Group March 2003 San Francisco IETF Mukesh Gupta / Nokia Chair.
V6OPS WG – IETF #85 IPv6 for 3GPP Cellular Hosts draft-korhonen-v6ops-rfc3316bis-00 Jouni Korhonen, Jari Arkko, Teemu Savolainen, Suresh Krishnan.
1 ipv6-node-02.PPT/ 18 November 2002 / John Loughney IETF 55 IPv6 Working Group IPv6 Node Requirements draft-ietf-ipv6-node-requirements-02.txt John Loughney.
1 ipv6-node-02.PPT/ 18 November 2002 / John Loughney IETF 55 IPv6 Working Group IPv6 Node Requirements draft-ietf-ipv6-node-requirements-02.txt John Loughney.
1 IETF-70 draft-akhter-bmwg-mpls-meth MPLS Benchmarking Methodology draft-akhter-bmwg-mpls-meth-03 IETF 70 Aamer Akhter / Rajiv Asati /
Draft-chown-v6ops-vlan-usage-01 Tim Chown v6ops WG, IETF 60, San Diego, August 2, 2004.
Trust Anchor Update Requirements for DNSSEC Russ Mundy for the editors Steve Crocker, Howard Eland, Russ Mundy.
YANG Data Model for IPv4-in-IPv6 Softwire draft-sun-softwire-yang November 2014 Q. Sun, H. Wang, Y. Cui, I. Farrer (presenter), M. Boucadair.
IPng WORKING GROUP November 1999 Washington DC IETF Bob Hinden / Nokia Steve Deering / Cisco Systems Co-Chairs.
Using BGP to Bind MPLS Labels to Address Prefixes draft-rosen-idr-rfc3107bis-00 Eric Rosen (presented by Ross Callon) IETF 95 MPLS WGdraft-rosen-idr-rfc3107bis-001.
KIREETI KOMPELLA, LOA ANDERSSON ADRIAN FARREL SPECIAL PURPOSE LABELS.
AP CSP: Sending Binary Messages
IP Flow Information eXport (IPFIX)
Requirements for LER Forwarding of IPv4 Option Packets
Essay writing 1: Writing introductions
Booting up on the Home Link
Syam Madanapalli Basavaraj Patil Erik Nordmark JinHyeock Choi
IETF 55 IPv6 Working Group IPv6 Node Requirements
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
Vocabulary Prototype: A preliminary sketch of an idea or model for something new. It’s the original drawing from which something real might be built or.
RIPE IPv6-wg and Renumbering
Current Issues with DNS Configuration Options for SLAAC
76th IETF meeting, November 8-13, 2009
DHCPv6-Shield: Protecting Against Rogue DHCPv6 Servers
IPv6 Router Alert Option for MPLS OAM
SACM Virtual Interim Meeting
ND-Shield: Protecting against Neighbor Discovery Attacks
Designing the Architecture for Grid File System (GFS)
Chapter 2: Static Routing
By Jennifer Forsthoefel Courtesy of The Writing Studio
Implementing IP Addressing Services
Writing the *Complete* Sentence
Writing the Document Based Question (DBQ) Essay
Digital Citizenship and You.
Multicast Service Models draft-acg-mboned-multicast-models-00
American History 1 1/24 Please take the following off the white table:
NMDA Q & A draft-dsdt-nmda-guidelines &
Implementing IP Addressing Services
Introduction Communication Breakdown
Common Operations and Management on network Slices (coms) BoF
1 What do you think working conditions were like at the turn of the century?
Working in Groups.
IEEE P Wireless RANs Date:
Journal Section 1. What social media apps do you use?
Frame Request-Report Enhancements
Experimental Internet Resource Allocations
Fundamentals of Literary Concepts
Elizabeth Liner Lab of Things.
EAP Method Requirements for Emergency Services
An MPLS-Based Forwarding Plane for Service Function Chaining
Requirements for IPv6 Routers draft-ietf-v6ops-ipv6rtr-reqs
RFC 4601 Revision Prague, March 2011 Rishabh Parekh (Cisco)
draft-ietf-pim-ipv4-prefix-over-ipv6-nh
Requirements for IPv6 Routers draft-ietf-v6ops-ipv6rtr-reqs-00
Wireless Architectural Thoughts
IETF103 IS-IS V6/MT Deployment Considerations draft-chunduri-lsr-isis-preferred-path-routing-01 Uma Chunduri [Huawei USA] Jeff Tantsura [Apstra] LSR WG,
IETF105 IS-IS V6/MT Deployment Considerations draft-chunduri-lsr-isis-mt-deployment-cons-02 Uma Chunduri [Futurewei] Jeff Tantsura [Apstra] Shraddha Hegde.
M. Boucadair, J. Touch, P. Levis and R. Penno
Requirements for IPv6 Routers draft-ali-ipv6rtr-reqs-02
Henning Schulzrinne Columbia University
CSCI 360: Software Architecture & Design
Presentation transcript:

Requirements for IPv6 Routers draft-ietf-v6ops-ipv6rtr-reqs Russ White

Purpose Take advantage of the v4/v6 transition to think through changes in the ‘net architecture Provide a set of suggestions from providers to implementers A common set of IPv6 features in routers Even though these features might not be needed in every deployment Drive the implementor to explain why a particular feature is not implemented A solid base from which to think rationally about what should be common, and what is an exception

Changes Modified DHCP/SLAAC language Modified language around ICMP More changes are in the list of things to come for this one Many other changes Removed all RFC2119 language Second part of document is written as a set of suggested common elements

Current State “This needs to be scoped” “Okay, send me a scoping statement” “This should say enterprise devices” – but this does not work “This should say xxx” – but this does not work Silence “This is useless, it should not be an RFC draft” Accompanied by a train of exceptions

Current State There appears to be no consensus in the WG Options: No amount of “may” and reduction in what the document is saying seems to make anyone happy Options: Simply withdraw the document, as the WG is not going to reach consensus Try to find a way to move something useful forward Thoughts?