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

Slides:



Advertisements
Similar presentations
SIP Simplified August 2010 By Dale Anderson. SIP Simplified Session Initiation Protocol Core of SIP specifications is documented in IETF RFC 3261 Many.
Advertisements

Deployment of the Light Weight IPv6 protocols In the Internet of Things(IoT) draft-fu-lwig-iot-usecase-00 Qiao Fu China Mobile
© 2009 Leffingwell, LLC Agile Enterprise Release Planning.
Living Well On-Line.  Digital media: electronic devices and media platforms such as computers, cell phones, video, the Internet, and video games that.
Doc.: IEEE /1542r0 Submission Vertical Applications Technical Advisory Group Smart Grid Task Group Liaison Report Date: Slide.
E-Tailing Electronic Retailing or E-Tailing - is the sale of goods or services through the internet. This can include: business-to-business sales (B2B)
IPv6 RADIUS attributes for IPv6 access networks draft-lourdelet-radext-ipv6-access-01 Glen Zorn, Benoit Lourdelet Wojciech Dec, Behcet Sarikaya Radext/dhc.
1 RSVP-TE Extensions for Associated Bidirectional LSPs draft-ietf-ccamp-mpls-tp-rsvpte-ext-associated-lsp-06 Author list: Fei Zhang, ZTE
Draft-ietf-intarea-nat-reveal-analysis – IETF84 Analysis of Solution Candidates to Reveal a Host Identifier (HOST_ID) in Shared Address Deployments draft-ietf-intarea-nat-reveal-analysis-02.
BEHAVE BOF (Behavior Engineering for Hindrance AVoidancE) Cullen Jennings Jiri Kuthan.
Unrestricted Connection Manager MIF WG IETF 79, Beijing Gaétan Feige - Cisco Pierrick Seïté, France Telecom - Orange
Russ Housley IETF Chair Internet2 Spring Member Meeting 28 April 2009 Successful Protocol Development.
IETF69 - NEMO WG1 NEMO: Deployments and Requirements From a Consumer Electronics Perspective draft-ng-nemo-ce-req-00.txt Chan-Wah Ng
Multi6 interim meeting agenda Chairs: Brian Carpenter, Kurt Lindqvist 1.IPR reminder, logistics, agenda bashing 2.Charter review 3.draft-lear-multi6-things-to-think-about-03.txt.
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.
Guidance for Running Multiple IPv6 Prefixes (draft-liu-v6ops-running-multiple-prefixes-02) Bing Liu, Sheng Jiang (Speaker), Yang Bo IETF91
CAPWAP Arch-Draft Issues IETF 59, Seoul 4 March 2004.
HOMEGATE IPv6 Issues IETF76 November Overview Lack of widespread availability of IPv6-capable home gateways impacts IPv6 service enablement Specifications.
Dissuasion, Working Group Scope and Deliverables Lou Berger Pat Thaler
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.
RTP Splicing Status Update draft-ietf-avtext-splicing-for-rtp-11 Jinwei Xia.
IETF #84 - NETCONF WG session 1 NETCONF WG IETF 84, Vancouver, Canada MONDAY, July 30, Bert Wijnen Mehmet Ersue.
Submission doc.: IEEE r PAR Review SC November 2015 Date: November 2015 Jon Rosdahl, CSR-QualcommSlide 1 Authors:
Balanced Security for IPv6 CPE draft-ietf-v6ops-balanced-ipv6-security-01 IETF89 London M. Gysi, G. Leclanche, E. Vyncke, R. Anfinsen.
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.
/ Jonne Soininen v6ops-3GPP Design Team IETF#55, v6ops wg Atlanta, USA Jonne Soininen / Juha Wiljakka
Draft-melia-mipshop-mobility-services-ps-01.txt. From IETF #66 Discuss MIH PS (as expressed by the WG chair) Need a single PS at WG level (several drafts.
SPFBIS IETF 83 Paris, France SPFBIS -- IETF 831. Agenda 1.Administivia 2.RFC 4408 issues 3.SPF RRTYPE (issue 9) 4.DNS amplification attacks (issue 24)
1 1 Cullen Jennings IETF 90 V5. 2 WebRTC has “flows” of Audio, Video, and Data between browsers JavaScript applications running in the browser have an.
ITEC 370 Lecture 18 Testing. Review Questions? Design document due W –System can be implemented just by following it Implementation –Methods (prototype,
DIR-826L Wireless N600 Gigabit Cloud Router Sales Guide WRPD Jan 25 th, 2012 D-LINK HQ.
General to Specific One Type of HookOne Type of Hook.
What you need to know.  Each TDI vessel is equipped with satellite communications that supplies a LOW BANDWIDTH internet connection. Even though the.
GEONET Brainstorming Document. Content Purpose of the document Brainstorming process / plan Proposed charter Assumptions Use cases Problem description.
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.
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.
Powerpoint Templates Page 1 iPhone combines smart phone capabilities with graphical interface iPhone Application Development.
GGF - © Birds of a Feather - Policy Architecture Working Group.
Real-time aspects June 19, 2016
Module 1: Understanding Local Area Networks
CLUE WG Interim Meeting San Jose, CA Sept , 2012
IPv6 – THE WAY TO THE SECURE INTERNET
IETF 55 IPv6 Working Group IPv6 Node Requirements
Requirements for IPv6 prefix delegation for IETF-55th at Atlanta, Nov.2002 Shin Miyakawa NTT Communications.
draft-corujo-ps-common-interfaces-lmm-00
Dumps4download.us Cisco Exam Dumps Exam Dumps Questions
Internet of Things
IETF ACL YANG Enhancements
What is most important in your life
Requirements for IPv6 Routers draft-ietf-v6ops-ipv6rtr-reqs
Carles Gomez, S. M. Darroudi
SPRING IETF-98 Tuesday, March 28.
VoIP voice over Internet Protocol
Privacy Recommendation PAR Proposal
IEEE March 2014 Nominee Statement
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Chapter 11: Network Address Translation for IPv4
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
IOT Acronym as “Internet Of Things”
IEEE MEDIA INDEPENDENT HANDOVER DCN:
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
IEEE MEDIA INDEPENDENT HANDOVER DCN:
General to Specific One Type of Hook.
draft-ietf-pim-ipv4-prefix-over-ipv6-nh
Requirements for IPv6 Routers draft-ietf-v6ops-ipv6rtr-reqs-00
Requirements for IPv6 Routers draft-ali-ipv6rtr-reqs-02
Solutions to Fix Epson Printer Error Code W-61 This error is commonly known as a communication error while users are working on the Epson printer. Our.
Presentation transcript:

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

Changes between -02 and -04 Many nits and wording problems fixed Modified section around ICMP requirements Modified device model to fit better with existing YANG documents Modified section around ICMP

Scoping Statements This draft is not designed to apply to consumer devices, such as smart devices (refrigerators, light bulbs, garage door openers, etc.), Internet of Things (IoT) devices, cell phones primarily used as an end user device (such as checking email, social media, games, and use as a voice device), and other devices of this class. It is up to each provider or equipment purchaser to determine how best to apply this document to their environment. The intended use of this document is for operators to be able to point to a common set of functionality which should be available across all IPv6 implementations. Several members of the community have argued there is no common set of IPv6 features; rather each deployment of IPv6 calls for different feature sets. However, the authors of this draft believe outlining a common set of features expected of every IPv6 forwarding device is useful.

Scoping Statements Also modified all upper case MAY/SHOULD/MUST to lower case Would like to know if the lower cases should be pushed back to upper cases with the new scoping statements in place This would strengthen the document somewhat

Next Steps Answer the question over upper/lower case Some folks have argued parts of the document are too theoretical/don’t belong in a requirements list These sections would not fit in any other IETF document, however And many others have found them useful If we can resolve these two issues, it seems this document is ready to move forward in the process One more look from the WG Move to WG last call