TSVWG%20IETF-73%20(Minneapolis) - PowerPoint PPT Presentation

About This Presentation
Title:

TSVWG%20IETF-73%20(Minneapolis)

Description:

Any submission to the IETF intended by the Contributor for publication as all or ... Michael - A framework for RSVP Security using dynamic group-keying ... – PowerPoint PPT presentation

Number of Views:15
Avg rating:3.0/5.0
Slides: 12
Provided by: ietf
Learn more at: https://www.ietf.org
Category:

less

Transcript and Presenter's Notes

Title: TSVWG%20IETF-73%20(Minneapolis)


1
TSVWGIETF-73 (Minneapolis)
  • James Polk
  • Lars Eggert
  • Magnus Westerlund

2
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
    within the context of an IETF activity is
    considered an "IETF Contribution". Such
    statements include oral statements in IETF
    sessions, as well as written and electronic
    communications made at any time or place, which
    are addressed to
  • the IETF plenary session,
  • any IETF working group or portion thereof,
  • the IESG or any member thereof on behalf of the
    IESG,
  • the IAB or any member thereof on behalf of the
    IAB,
  • any IETF mailing list, including the IETF list
    itself, any working group or design team list, or
    any other list functioning under IETF auspices,
  • the RFC Editor or the Internet-Drafts function
  • All IETF Contributions are subject to the rules
    of RFC 3978 (updated by RFC 4748) and RFC 3979
    (updated by RFC 4879).
  • Statements made outside of an IETF session,
    mailing list or other function, that are clearly
    not intended to be input to an IETF activity,
    group or function, are not IETF Contributions in
    the context of this notice.
  • Please consult RFC 3978 (and RFC 4748) for
    details.
  • A participant in any IETF activity is deemed to
    accept all IETF rules of process, as documented
    in Best Current Practices RFCs and IESG
    Statements.
  • A participant in any IETF activity acknowledges
    that written, audio and video records of meetings
    may be made and may be available to the public.

3
Other Notes
  • Need another Note Taker
  • Need a scribe for Jabber session
  • Wireless Make sure your computer is not in
    adhoc mode
  • Future TSVWG Authors
  • PLEASE add -tsvwg- to any ID submitted

4
TSVWG Agenda
  • Chairs Agenda Bashing
  • NOTE WELL
  • Document Status and Accomplishments
  • Milestones Review
  • Documents to have only Chair Comments on
  • draft-ietf-tsvwg-admitted-voice-dscp-03.txt
  • draft-ietf-tsvwg-udp-guidelines-08.txt
  • Fernandos - Port Randomization
  • (10 min) draft-ietf-port-randomization-02.txt
  • Bruce's - RSVP-over-L3VPNs
  • (10 min) draft-ietf-tsvwg-rsvp-l3vpn-00.txt

5
TSVWG Agenda (contd)
  • Michael - A framework for RSVP Security using
    dynamic group-keying
  • (10 min) draft-behringer-tsvwg-rsvp-security-gr
    oupkeying-01.txt
  • Joe - IANA Allocation Guidelines for TCP and
    UDP Port Numbers
  • (15 min) draft-ietf-tsvwg-iana-ports-00.txt
  • Randy - DTLS for SCTP
  • (5 min) draft-tuexen-tsvwg-dtls-for-sctp-00.txt
  • Bob's - Layered Encapsulation of Congestion
    Notification
  • (10 min) draft-ietf-tsvwg-ecn-tunnel-01.txt
  • Bob's - Byte and Packet Congestion
    Notification
  • (10 min) draft-ietf-tsvwg-byte-pkt-congest-00.t
    xt
  • Matt - Rethinking the TCP-Friendly Paradigm
  • (10 min) http//staff.psc.edu/mathis/unfriendly
    /

6
TSVWG Agenda (contd)
  • Preethi - HTTP over SCTP
  • (10 min) draft-natarajan-httpbis-sctp-00.txt

7
TSVWG Accomplishments and Status
  • 0 RFCs published since IETF 72
  • (oops!)
  • 1 IDs in RFC Editor Queue
  • UDP Guidelines

8
TSVWG Accomplishments and Status
  • 4 ID in IESG review
  • RSVP Extensions for Emergency Services
  • RSVP Proxy Approaches
  • RSVP Proxy Protocol
  • An EF DSCP for Capacity-Admitted Traffic
  • 0 IDs past WGLC
  • 0 ID in IETF last call
  • 0 ID almost ready for publication request

9
TSVWG Accomplishments and Status
  • 1 ID appears to be about done
  • L3 VPNs

10
TSVWG (current) Milestones
  • Done  Submit 'User-Defined Errors for RSVP' to
    IESG for consideration as Proposed Standard
  • Mar 2008  Submit 'DSCPs for Capacity-Admitted
    Traffic' to IESG for consideration as Proposed
    Standard
  • Done  Submit 'RSVP Extensions for Emergency
    Services' to IESG for consideration as Proposed
    Standard
  • Done  Submit 'RSVP Proxy Approaches' to IESG for
    consideration as Informational
  • Done  Submit 'RSVP Extensions for Path-Triggered
    RSVP Receiver Proxy' to IESG for consideration
    as Proposed Standard
  • Done  Submit 'UDP Usage Guidelines for
    Application Designers' to IESG for consideration
    as Best Current Practice
  • Jul 2008  Submit 'Sockets API Extensions for
    SCTP' to IESG for consideration as Informational
  • Oct 2008  Submit 'Port Randomization for
    Transport Protocols' to the IESG for
    consideration as a Best Current Practice
  • Dec 2008  Submit 'Applicability of Keying Methods
    for RSVP Security' to IESG for consideration as
    Informational

11
TSVWG Open Issues
  • Milestones need confirmation (that are WG items
    now)
Write a Comment
User Comments (0)
About PowerShow.com