1 Use Cases & Requirements IETF#78, Maastricht, NL.

Slides:



Advertisements
Similar presentations
Authentication Authorization Accounting and Auditing
Advertisements

Internet Peer-to-Peer Application Infrastructure Darren New Invisible Worlds, Inc.
RPKI Standards Activity Geoff Huston APNIC February 2010.
Doc.: IEEE /1116r0 Submission July 2006 Harry Worstell, AT&T.Slide 1 TGp Closing Report Notice: This document has been prepared to assist IEEE.
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx Title: Proposal for adding a key hierarchy based approach in the security.
1 IETF 74, 30 Jul 2009draft-ietf-tsvwg-rsvp-security-groupkeying-05.txt Applicability of Keying Methods for RSVP security draft-ietf-tsvwg-rsvp-security-groupkeying-05.txt.
© 2006 NEC Corporation - Confidential age 1 November SPEERMINT Security Threats and Suggested Countermeasures draft-ietf-speermint-voipthreats-01.
2001_03_28 SG A contribution– 1 Dept of State ITAC-T Advisory Committee SG-A Ad Hoc Meeting on ENUM March 28th & 29th, 2001 ENUM CONTRIBUTION TITLE: ENUM.
SG-A Ad Hoc - ENUM Jordyn A. Buchanan Register.com February 12, 2001.
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Q & A for Discussion Date Submitted: Aug 17, 2010 Presented at IEEE a Teleconference.
ES-CS-Adhoc-Rep.ppt IEEE MEDIA INDEPENDENT HANDOVER DCN: ES-CS-Adhoc-Rep.ppt Title: ES/CS Ad-hoc Discussions.
External User Security Model (EUSM) for SNMPv3 draft-kaushik-snmp-external-usm-00.txt November, 2004.
SPPP Protocol Session Peering Provisioning Protocol draft-ietf-drinks-spprov-01.
ENUM? “ Telephone Number Mapping (ENUM or Enum, from TElephone NUmber Mapping) is a suite of protocols to unify the telephone numbering system E.164 with.
RIPE64 Enum Working Group DE-CIX NGN Services.
Microsoft Active Directory(AD) A presentation by Robert, Jasmine, Val and Scott IMT546 December 11, 2004.
ENUM Update for voipeer BOF Richard Shockey ENUM co-chair IETF 63 Paris.
12 January 2006 CDG Conference Call Integrating Existing Number Portability Solutions in Carrier-ENUM Douglas Ranalli, NetNumber, Inc.
Draft-khan-ip-serv-peer-arch-03.txt SPEERMINT Peering Architecture IETF-66, Montreal, Canada Sohel Khan, Ph.D. Technology Strategist.
DHCPv6 Redundancy Considerations Redundancy Proposals in RFC 6853.
SPEERMINT Terminology Draft th IETF - Chicago Editors: Daryl Malas David Meyer.
IETF #82 DRINKS WG Meeting Taipei, Taiwan Fri, Nov 18 th
1 Use Cases & Requirements IETF#77, Anaheim, CA..
ALTO BOF Charter Discussion. Charter Iterated (twice) on the list  Several comments on the first version Terminology, caching  No complains on current.
EAP Extensions for EAP Re- authentication Protocol (ERP) draft-wu-hokey-rfc5296bis-01 Yang Shi Qin Wu Zhen Cao
AAA and Mobile IPv6 Franck Le AAA WG - IETF55. Why Diameter support for Mobile IPv6? Mobile IPv6 is a routing protocol and does not deal with issues related.
IETF #81 DRINKS WG Meeting Québec City, QC, Canada Tue, July 26 th, 2011.
1 DRINKS Requirements Design Team Debrief IETF#73, Minneapolis, MN. (Sumanth Channabasappa, on behalf of the design team.)
Doc.: IEEE /0617r0 Submission May 2008 Tony Braskich, MotorolaSlide 1 Refining the Security Architecture Date: Authors:
National Computational Science National Center for Supercomputing Applications National Computational Science GSI Online Credential Retrieval Requirements.
SPPP Protocol Session Peering Provisioning Protocol draft-ietf-drinks-spprov-01.
Page 1 IETF Speermint Working Group Speermint Requirements/Guidelines for SIP session peering draft-ietf-speermint-requirements-02 IETF 69 - Monday July.
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx Title: IETF Liaison Report Date Submitted: November 16, 2006 Presented.
PCE 64 th IETF PCE Policy Architecture draft-berger-pce-policy-architecture-00.txt Lou Berger Igor Bryskin Dimitri Papadimitriou.
A Framework for Session Initiation Protocol User Agent Profile Delivery (draft-ietf-sipping-config-framework-11) SIPPING – IETF 68 Mar 19, 2007 Sumanth.
Doc.: IEEE Submission, Slide 1 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: November 14, 2013 Presented at IEEE session.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: September 16, 2010 Presented at IEEE session.
Doc.: IEEE /0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 1 Joiint TGU : Emergency Identifiers Notice: This document has been.
Draft-lendl-speermint- background-02 Thanks to Alex for presenting! IETF 73, November 2008Otmar Lendl.
IEEE MEDIA INDEPENDENT HANDOVER Title: An Architecture for Security Optimization During Handovers Date Submitted: September,
Page 1 IETF Speermint Working Group Speermint draft-ietf-speermint-requirements-04 IETF 71 - Wednesday March 12, 2008 Jean-François Mulé -
S. Ali, K. Cartwright, D. Guyton, A. Mayrhofer, J-F. Mulé Data for Reachability of Inter/tra-NetworK SIP (drinks) DRINKS WG draft-mule-drinks-proto-02.
Basics of the Domain Name System (DNS) By : AMMY- DRISS Mohamed Amine KADDARI Zakaria MAHMOUDI Soufiane Oujda Med I University National College of Applied.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: EAP Pre-authentication Problem Statement in IETF HOKEY WG Date Submitted: September,
Page 1 IETF DRINKS Working Group Data Model and Protocol Requirements for DRINKS IETF 72 - Thursday July Tom Creighton -
SPEERMINT Architecture - Reinaldo Penno Juniper Networks SPEERMINT, IETF 70 Vancouver, Canada 2 December 2007.
Location Routing Function Requirements Hadriel Kaplan
Draft-levin-simple-interdomain- reqs-03 (in 3 minutes or less) Edwin Aoki, America Online (representing the authors)
Doc.: IEEE /2179r0 Submission July 2007 Steve Emeott, MotorolaSlide 1 Summary of Updates to MSA Overview and MKD Functionality Text Date:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Open issues with PANA Protocol
Using NPAC as the ENUM Registry
ATIS/SIP Forum NNI Task Force – Routing Team
draft-dthakore-tls-authz
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP
A Scalable content-addressable network
A Unified Approach to IP Segment Routing
Summary of Unresolved General Comments for 2/14 TGs Telecon
IEEE MEDIA INDEPENDENT HANDOVER DCN:
R0KH-R1KH protocol requirements
Mesh Frame Formats Date: Authors: May 2007 March 2007
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: March 18, 2010 Presented at IEEE session.
IEEE MEDIA INDEPENDENT HANDOVER
Impact of KTP Non-definition
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: May 13, 2010 Presented at IEEE session.
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Mesh Frame Formats Date: Authors: May 2007 March 2007
Mesh Frame Formats Date: Authors: May 2007 March 2007
draft-gu-ppsp-peer-protocol-01
Presentation transcript:

1 Use Cases & Requirements IETF#78, Maastricht, NL.

2 Re-Recap Registry is the authoritative source for provisioned session establishment data (SED) and related information Local Data Repository is the data store component of an addressing server that provides resolution responses Registry is responsible for distributing SED and related information to the Local Data Repositories Registry Local Data Repository 1. Provision SED 2. Distribute SED Local Data Repository

3 Introduction The latest I-D revision can be found at: – There have been two revisions since Anaheim – The first revision (-02, May) incorporated comments and contributions just before the last IETF – The second revision (-03, May) was a result of the discussions at Anaheim and at the interim F2F meeting

4 Use Case Categories Provisioning Mechanisms Interconnect Schemes SED Exchange and Discovery Models SED Record Content Separation and Facilitation of Data Management Lookup Keys Number Portability Misc.

5 Snapshot of Use Cases (1/4) Provisioning – Real-Time – Non-Real-Time Bulk – Multi-request Interconnect Schemes – Inter-SSP SED – Direct v/s Indirect Peering – Intra-SSP SED – Selective Peering – Delegated Name Server

6 Snapshot of Use Cases (2/4) SED Exchange and Discovery Models – Unified LUF/LRF – Using LUF's Domain Name – Using LUFs Administrative Domain Identifier – Co-existent SED Exchange and Discovery Models SED Record Content – SED Record Content – Time-To-Live (TTL)

7 Snapshot of Use Cases (3/4) Separation and Facilitation of Data Management – Separation of Provisioning Responsibility – Destination Groups – Route Groups Lookup Keys – Additions and deletions – Carrier-of-Record vs Transit Lookup Key – Multiplicity of Identical Lookup Keys – Lookup Key Destination Group Modification – Lookup Key Carrier-Of-Record vs Transit Modification – Modification of authority

8 Snapshot of Use Cases (4/4) Number Portability Misc – Data Recipient Offer and Accept – Open numbering plans

Data Model 9 0..n n 1 1 1

10 Next Steps Incorporate any additional use cases (e.g., from our discussions today, as the protocol docs mature) – Any contributions? Discuss and incorporate comments – Otmar provided comments on the list on 7/21 – Any additional review volunteers? Progress to Last Call?