SIPCORE

Stockholm, SwedenFRIDAY, July 31, 2009, 0900-1130,

Congresshall A

Reminder

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 5378 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 5378 and RFC 3979 for details.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 be made and may be available to the public.

Reminder

Administrative Tasks

• Blue Sheets• Note Taker• Emergency Backup Note Taker• Jabber Scribe

Reminder

AgendaTime Length Presenter Topic

0900 – 0915 15 Chairs Status and agenda bash (you are here)

0915 – 0945 30 Christer Holmberg Negotiation between adjacent nodes during initial request or dialog.

0945 – 1015 30 François Audet Delivering request-URI and parameters to UAS via proxy

1015 – 1045 30 Adam Roach Revising RFC 3265

1045 – 1130 45 Padding

Reminder

Chartered Work Item StatusJul 2009 Delivering request-URI and parameters to UAS via

proxyDiscussing Today

Jul 2009 INFO package framework WGLC just finished

Aug 2009 Termination of early dialog prior to final response WGLC done

Aug 2009 Location Conveyance with SIP In WGLC until Aug 7

Sep 2009 Essential corrections to RFC 3261 (1st batch) See Next Slide

Oct 2009 Example security flows Needs Review

Oct 2009 Extension for use in etags in conditional notification

IESG needs changes

Dec 2009 SIP Events throttling mechanism Light ML Discussion

Dec 2009 Mechanism for indicating support for keep-alives Discussing Today

Dec 2009 Error corrections and clarifications to RFC3265 Discussing Today

Jan 2010 Presence Scaling Requirements AD Evaluation

Essential Corrections:To Be or Not To Be

• Originally anticipated 3 to 4 essential corrections documents a year, published in annual bundles.

• Actual frequency of documents has been much, much lower.

• Current candidate documents are at radically different levels of maturity.

• Chairs called the question on the list of whether we should abandon EC process in favor of progressing drafts independently

• Preliminary messages indicate support for advancing independently, but not enough discussion to declare consensus

Reminder

Call for Dedicated Reviewers

• Show of hands: Who is willing to commit to review draft-ietf-sipcore-secflows?

• Please don’t make me figure out ways to make Powerpoint more annoying.