Advancing the SIP Standards -Tracking- Robert Sparks Estacado - - PowerPoint PPT Presentation

advancing the sip standards tracking
SMART_READER_LITE
LIVE PREVIEW

Advancing the SIP Standards -Tracking- Robert Sparks Estacado - - PowerPoint PPT Presentation

Advancing the SIP Standards -Tracking- Robert Sparks Estacado Systems SIPit Twice a year - moves between continents 100s of implementations SIPit SIPit 16 statistics 2 major specification bugs A dozen specification


slide-1
SLIDE 1

Advancing the SIP Standards

  • Tracking-

Robert Sparks Estacado Systems

slide-2
SLIDE 2

SIPit

  • Twice a year - moves between continents
  • 100s of implementations
slide-3
SLIDE 3

SIPit

  • SIPit 16 statistics

– 2 major specification bugs – A dozen specification clarifications – Hundreds of implementation errors

slide-4
SLIDE 4

SIPit

  • Opportunity to observe

– What’s being implemented – What’s not being implemented – What folks are trying that’s not working – What’s being built without standardization

  • Opportunity to listen to

– What implementers find important – How the specs are interpreted

  • (when does MUST mean MUST, and why should we

ever implement a SHOULD?)

slide-5
SLIDE 5

What’s getting implemented?

slide-6
SLIDE 6

What should we track?

  • Send me email with what should be on

the SIPit 18 survey

– GRUU, outbound, connect-reuse – TLS, sips – Identity, sipping-certs – Non-trivial offer-answer – More details on use of PRACK

slide-7
SLIDE 7

Bug Tracking

  • Bugzilla - http://bugs.sipit.net
  • Heavily utilized during 3261 edits
  • Only draft editor can add/modify bugs
  • Two different use models

– Fixing bugs while editing drafts – Identifying bugs to fix in future spec updates

2 1 18 9 4 2 91 Open Bugs 3515 3420 3265 3264 3263 3262 3261

slide-8
SLIDE 8

Building interop reports

  • Huge task - only tractable in increments
  • From those docs in the hitchhiker’s guide:

NOT RECOMMENDED 37 REQUIRED 72 OPTIONAL 82 SHOULD NOT 222 RECOMMENDED 250 MUST NOT 500 MAY 1188 SHOULD 1386 MUST 2607

slide-9
SLIDE 9

Building interop reports

  • Two approaches

– Identify subset of each spec where it makes sense to pursue a report – Provide a place for the community to volunteer reports ad-hoc and watch for critical mass

slide-10
SLIDE 10

New Tools?

  • Different systems for spec issues vs.

bugs in drafts being developed

  • General wiki for tracking state of

implementation and interop statements