/
INSIPID WG
INSIPID WG

INSIPID WG - PowerPoint Presentation

phoebe-click
phoebe-click . @phoebe-click
Follow
124 views | Public

INSIPID WG - Description

IETF 88 Vancouver November 4 2013 Keith Drage WG cochair Gonzalo Salgueiro WG cochair Note Well This summary is only meant to point you in the right direction and doesnt have all the nuances The IETFs IPR Policy is set forth in BCP 79 please read it carefully ID: 541000 Download Presentation

Tags :

draft ietf insipid session ietf draft session insipid bcp review status update compatibility milestone chairs polk published amp chair

Share:

Link:

Embed:

Please download the presentation from below link :


Download Presentation - The PPT/PDF document "INSIPID WG" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.

Presentation on theme: "INSIPID WG"— Presentation transcript

Slide1

INSIPID WG

IETF-

88

Vancouver, November 4,

2013

Keith

Drage

(WG co-chair)

Gonzalo Salgueiro (WG co-chair)Slide2

Note Well

This summary is only meant to point you in the right direction, and doesn't have all the nuances. The IETF's IPR Policy is set forth in BCP 79; please read it carefully.

The Brief

S

ummary:

By participating with the IETF, you agree to follow IETF processes.

If you are aware that a contribution of yours (something you write, say, or discuss in any IETF context) is covered by patents or patent applications, you need to disclose that fact.

You understand that meetings might be recorded, broadcast, and publicly archived.

For further information, talk to a chair, ask an Area Director, or review the following:

BCP 9 (on the Internet Standards Process)

BCP 25 (on the Working Group processes)

BCP 78 (on the IETF Trust)

BCP 79 (on Intellectual Property Rights in the IETF)Slide3

Agenda

17:40  

Administrative (Blue Sheets, Note Takes, (Chairs, 5)

Jabber Scribes, etc.)

 

17:45

INSIPID WG Status Update (Chairs,10)

                           

17:55 A Proposal for Backwards Compatibility (J. Polk, 60)

of the INSIPID Session-ID

draft-polk-insipid-bkwds-compatibility-proposal-03Slide4

Agenda (cont’d)

18:55  End-to-End Session Identification in (J. Polk, 25)

IP-Based Multimedia Communication Networks  

       

draft-ietf-insipid-session-id-02

19:20

 

Requirements for Marking SIP (

Christer

Holmberg, 10)

Messages to be Logged

                                       

draft-dawes-dispatch-logme-reqs-03

19:30  Wrap-up & Action Item Review         (Chairs, 10)

19:40 EndSlide5

The revised WG charter that includes the new logging work was approved by the IESG on 10/11/2013

M

ilestones updated (11/3/2013) : Two new milestones for logging work Updated the dates of the existing milestonesKaplan Draft: Will go to IETF LC again now that (old) IPR has been filedNew version forthcoming with IANA registration text clarified and some APPSDIR review comments addressed

Status UpdateSlide6

Milestone:

Session-ID Requirements & Use Cases   draft-ietf-insipid-session-id-reqtsCompleted IETF LC (Sept 24) & Gen-ART LC reviewAwaiting WG feedback on APPSDIR review comments (done)Ver -09 published today and will be put up for IESG reviewMilestone: Session-ID Solution draft-ietf-insipid-session-idNo new version published since BerlinAwaiting resolution of backwards compatibility issueDraft published to foment discussion on backwards compatibility

Status UpdateSlide7

Milestone:

Reqts for Marking SIP Sessions for Loggingdraft-dawes-dispatch-logme-reqs is the only submission so farPlan to call for WG adoption soonIf planning to submit a draft for this milestone, please do so soonDiscussion should continue on the listMilestone: Protocol for Marking SIP Sessions for LoggingNo drafts put forward yet for this milestonePlease consider submitting

Status Update