iptel working group ietf 52. agenda agenda bash [rosenberg] 2m cpl/trip updates [rosenberg] 5m trip...

5
iptel Working Group IETF 52

Upload: aaliyah-maher

Post on 27-Mar-2015

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Iptel Working Group IETF 52. Agenda Agenda Bash [Rosenberg] 2m CPL/TRIP Updates [Rosenberg] 5m TRIP MIB [Walker] 10m Gateway Registration Scenarios: Internet2

iptel Working Group

IETF 52

Page 2: Iptel Working Group IETF 52. Agenda Agenda Bash [Rosenberg] 2m CPL/TRIP Updates [Rosenberg] 5m TRIP MIB [Walker] 10m Gateway Registration Scenarios: Internet2

Agenda

Agenda Bash [Rosenberg] 2mCPL/TRIP Updates [Rosenberg] 5mTRIP MIB [Walker] 10m

Gateway Registration Scenarios: Internet2 [Schulzrinne] 5m Scenarios: Carrier [Peterson] 5m

Requirements [Rosenberg] 20m

Attributes [Bangalore] 10m

Page 3: Iptel Working Group IETF 52. Agenda Agenda Bash [Rosenberg] 2m CPL/TRIP Updates [Rosenberg] 5m TRIP MIB [Walker] 10m Gateway Registration Scenarios: Internet2

TRIP and CPL

• TRIP– -09 Approved as RFC

on 9/13/01

– Getting close to top of editors queue, maybe 3-4 weeks

• CPL– -05 just issued

– FINALLY reconciles iCal integration

• We are fully compliant

• Offline expansion solves many problems

– Added language-switch

– Many other minor fixes

– New WGLC ends 12/21/01

Page 4: Iptel Working Group IETF 52. Agenda Agenda Bash [Rosenberg] 2m CPL/TRIP Updates [Rosenberg] 5m TRIP MIB [Walker] 10m Gateway Registration Scenarios: Internet2

High Level Requirements

1. Fast call setups

2. Conveys failures of gateways rapidly

3. Conveys re-starts of gateways rapidly

4. Proxy has some way to know available capacity

5. Security: mutual authentication, integrity. Privacy less critical.

6. Convey routing preferences

7. Timeliness of attribute information

8. Extensible attributes9. Efficient10. Centralization of policy11. Proxies in ITAD make

independent policy decisions

12. Discovery?

Page 5: Iptel Working Group IETF 52. Agenda Agenda Bash [Rosenberg] 2m CPL/TRIP Updates [Rosenberg] 5m TRIP MIB [Walker] 10m Gateway Registration Scenarios: Internet2

Functional Requirements

• Have notion of connection between LS & GW

• Allow establishment of connection in either direction

• Allow for GW to propagate attributes to LS– Per gateway– Per trunk group– Per route

• Static and dynamic attributes• Extensible attribute set

• Allow rapid keepalives in both directions– Efficient

• Allow negotiation of keepalive interval

• Support partial updates• Allow LS to impose filters

on GW– Only specific attributes– Rate limitation– Thresholds