Transcript IETF Structure and Internet Standards Process

DISPATCH WG
IETF 92
Mary Barnes (WG co-chair)
Cullen Jennings (WG co-chair)
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.
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.
Agenda – Monday, March 23, 2015
13:00-13:20 Agenda bash, RAI Status, items of interest
(Chairs)
13:20-13:40 Routing Out of Dialog Request (Andrew Allen)
13:40-14:10 GeoJSON (Sean Gillies)
14:10-14:40 Calling Name Identity Trust (CNIT) (Richard
Shockey)
14:40-15:00 Video Relay Service (VRS) (Brian Rosen)
Status
• Other topics proposed within pre-IETF-92 timeline:
Cause URI Parameter for Service Number translation
http://datatracker.ietf.org/doc/draft-mohali-dispatch-cause-forservice-number/
•DISPATCHed as AD sponsored.
•Two week call for comments
Instance ID for OMA PoC:
http://datatracker.ietf.org/doc/draft-allen-dispatch-poc-instanceidusage/
•Proposed to be DISPATCHed as AD sponsored (pending)
draft-mohali-dispatch-cause-for-servicenumber-01
• Solution to tag a called service access number that
has been translated into a routable number by an
application towards an endpoint (eg. call center)
• Update of RFC4458 to add a new value for the cause
URI parameter so that it can be possible to tag a
service access number anywhere in the signaling
path.
• This draft also addresses an interworking need with
TDM networks from 3GPP.
=> Please review and comment on DISPATCH WG
mailing list
IETF 92 Dallas
Marianne
Mohali
IETF-93 Deadlines
• June 8, 2015. Cutoff date to notify the
chairs/DISPATCH WG of plans to submit a proposal.
(draft deadline – 4 weeks)
• June 15, 2015. Cutoff for charter proposals for
topics.(draft deadline – 3 weeks)
• June 22, 2015. Announcement of topics that have
been dispatched for IETF-93. (draft deadline – 2
weeks)
• July 6, 2015. Draft deadline.
A brief word from
your ADs
ClosedSucceeded since last update
cuss
dart
geopriv
salud
soc
drinks (almost)
ART!
RAI + APP + [TSV] = ART
●
●
●
Goal: More flexibility in managing application-ish WGs
ADs (as of Weds.): Ben, Alissa, Barry
Question: What about RFC 5727?
o
o
Update so that it makes sense with reorg?
Move to Historic and rely on charters?
Other activities of interest
SIPNOC 2015
• Technically-focused educational conference for service
providers and network operators on how to “Make SIP Work
Better in the Network”
• June 23-25, 2015 at Dulles Hilton Hotel, Herndon, VA
• Developed specifically for the technical and operational staff of
service providers, including network architects and engineers
• Focused on addressing key deployment and operational issues
involving SIP–based technology and services
• Soliciting speaking presentations *now*.
• SIP Training session (*New for 2015*)
• For more information: http://www.sipnoc.org
SIP Forum - SIP Connect 2.0
• Update the reference architecture that sets forth the common network elements
necessary for service provider to IP PBX peering (e.g. to include SBC’s).
• Specify the basic protocols (and protocol extensions) that must be supported by
each element of the reference architecture.
• Specify the exact RFCs or other existing standards associated with these
protocols that must or should be supported by each element of the reference
architecture.
• Update the security model based on existing standards to authenticate and
authorize utilization of the service provider’s resources by an IP PBX.
• Specify the consensus method for supporting IPV6 and IPV4/6 Dual Stack
components within the reference architecture.
• Specify the consensus method for supporting secure media (SRTP).
• Specify the consensus method for supporting Video enabled devices.
• Specify the consensus method for supporting emergency calling
(NG911/NG112) and the transport of location information.
• Editor’s draft:
https://drive.google.com/file/d/0B7haaZ1Rd1KYZGlJWXJScmJ2Vkk/view
• Discussion on SIP Forum Tech WG mailing list: www.sipforum.org
SIP Forum - IP-NNI Initiative
• In December 2013, the Alliance for Telecommunications
Industry Solutions (ATIS) and the SIP Forum launched a
joint task force to develop IP-NNI (Network-to-Network
Interface) voluntary, consensus-driven specifications for
North American Service Providers.
• Identify a baseline set of features that should be
common to all IP-NNI implementations for voice service.
• Two draft specifications for public review/feedback:
(1) IP Interconnection Profile ( what goes on the wire)
(2) IP Interconnection Routing Report (Number
Translation and the databases/non normative)
• A snapshot of the work in progress is available on both
ATIS and SIP Forum websites:
https://access.atis.org/apps/group_public/document.ph
p?document_id=18864&wg_abbrev=ipnni
http://www.sipforum.org/content/view/421/171/
IMTC WebRTC TG
• The IMTC WebRTC Activity Group will be at the
upcoming IMTC SuperOp perform WebRTC
interoperability testing in Porto, Portugal
May 16 – 22, 2015
• Will focus testing on interoperability of WebRTC
implementations to SIP with WebRTC media either
converted to a more traditional SIP (SDES or
unencrypted RTP) profile, or for additional scenarios a
WebRTC based profile (DTLS-SRTP and ICE).
• IMTC members interested in participation in WebRTC
testing should register directly at
http://www.imtc.org/event/superop_2015/
• Non-members, please contact Nathalie Mariano at
[email protected] to inquire about
participation
Welcome to our new AD – Ben Campbell
Thanks to Richard for his 2 years of service as AD
from the following WGs:
DISPATCH
XRBLOCK
BFCPBIS
INSIPID
DRINKS
STRAW
P2PSIP
SIPCORE
SIPREC
XMPP
Former Fellow RAI co-AD