Notes on SIPPING Session 2 at IETF 64 

reported by Steve S.

SIPPING 

SIPPING Minutes  IETF 64,  


Chairs:  HYPERLINK "mailto:Gonzalo.Camarillo@ericsson.com" Gonzalo Camarillo,  HYPERLINK "mailto:rohan@ekabal.com" Rohan Mahy, and  HYPERLINK "mailto:dean.willis@softarmor.com" Dean Willis

MONDAY, November 7, 2005, 1510-1710, Salon D/E

Status and Agenda Bash

Chairs 15 minutes 1510 - 1525  

New charter is up. 

RAI – Realtime Applications & Infrastructure


Config Framework and Data Sets

Dan Petrie

20 minutes 1525 - 1545 draft-ietf-sipping-config-framework-07.txt

draft-petrie-sipping-profile-datasets-03.txt

draft-petrie-sipping-sip-dataset-01.txt 



Properties required to deploy SIP.  Discussion, what exists is too complicated to be used. 

Very complex policies.  

Session Policies

Volker Hilt

20 minutes 1545 - 1605 draft-hilt-sipping-session-policy-framework-00.txt

draft-ietf-sipping-media-policy-dataset-00.txt

draft-hilt-sipping-policy-package-00.txt


Consent Framework

Gonzalo Camarillo

15 minutes 1605 - 1620 draft-ietf-sipping-consent-framework-03.txt




Conf Bridge Transcoding Model

Gonzalo Camarillo

10 minutes 1620 - 1630 draft-ietf-sipping-transc-conf-00.txt


IPv6 Transition

Vijay K. Gurbani

10 minutes 1630 - 1640 draft-ietf-sipping-v6-transition-01.txt

draft-gurbani-sipping-ipv6-sip-01.txt

7 torture test cases?    More needed.  

SIP-unfriendly Functions in Current Architectures

Jani Hautakorpi

10 minutes 1640 - 1650 draft-camarillo-sipping-sbc-funcs-02.txt

Session Border Controllers don’t play well with SIP.  

Max Forwards Issues

Robert Sparks

10 minutes 1650 - 1700 draft-lawrence-maxforward-problems-00.txt

Makes it easy to attack network.  One solution is loop detection on proxies that fork.

This seems to be a reasonable option.   

Multi transcoding

Tae -Gyu Kang

10 minutes 1700 - 1710 draft-kang-sipping-transc-scenario-00.txt


WEDNESDAY, November 9, 2005, 1300-1500, Salon D/E

Agenda Bash

5 minutes Discussion Leader 1300 - 1305

Retargetting Issues

Replaced by other work,  voice mail truck?  

Extending the SIP Reason Header with Warning Codes

10 minutes Paul Kyzivat

1335 - 1345 draft-hautakorpi-reason-header-for-warnings-00.txt

What’s the motivation?

Question (Gonzalo) about warning codes?   Why?    Jonathan – We have Response Codes so don’t need WC. Extension RC takes care of shortage of RCs.  G wants us to solve this.  J – no shortage of space.  

How much space left? Robert Sparks will find out.  


GRUU Reg Event Package

10 minutes Paul Kviyat

1325 - 1335 draft-ietf-sipping-gruu-reg-event-00.txt

Converted to WG draft.   Proposal to WGLC.  Approved.


SIP Identity Usage within Enterprise Scenarios

10 minutes Steffen Fries 

draft-fries-sipping-identity-enterprise-scenario-01.txt

Cullen has a major problem.  European privacy laws.  

Discussion on certificates???  Device Certificates?   

How do you establish trust in a corporate net and bind a device to a user id.?

Calling Party Category

Rocky Wang   draft-rocky-sipping-calling-party-category-01.txt 10 minutes Henning Schulzrinne

Supplementary Services meet VoIP.  

Jonathan:  Major problem.  Fundamentally won’t work.  Needs SAML??

Martin: Need labels:  prison, motel,...  Original Line Identification.  (CPC – Calling Party Category from ISUP)   

Steve ?   Do we want to go down this road?  

Janet Gunn:  Drop CPC coding but must do functions.  Invent a new way.

Forced Hospitality:  need something.  

Jonathan:  Role Assertion is necessary.  We need to do this. 

Hannes was volunteered (while out of room) to do a new doc. 

In my opinion: enough interest and different viewpoints that a requirements document is required and will speed up reaching a usable spec.


PRACK

Rohan:  Not much progess.  Hard.  State machine is too complex. 

What to do:  

Jonathan:  two reasons:   need additional messages, has to be backwards compatible with 2543.  Caution. Need to reevaluate assumptions.  Prack not worth enough to implement. 

Robert Sparks:  Full Prack not being implemented.


Requirements and Possible Mechanisms for File Transfer Services Within the Context of SIP Based Communication 


draft-isomaki-sipping-file-transfer-00.txt



Payment for Services in SIP

draft-jennings-sipping-pay-03.txt 

Postage Stamps for SPIT. 

Joel Halpern:  bad to be dependent on a micro-payment structure.  Hard task.  Needs SIP extensions.  Needs payment infrastructure.  We don’t want to work on that.  Very hard, many scenarios.

Cullen:  ditto Joel.  

Rohan: ditto,   SPIT prevention not practical.  Junk mail cost too expensive for poor countries.  Forget SPIT.  Just do micro-payment. 

?   wants micropayment. 

Hannes:  

Dean:  now overtime.  

URN for Services

10 minutes Henning Schulzrinne 

draft-schulzrinne-sipping-service-01.txt

Cullen:  doesn’t like separate code path

Jonathan:  likes separate code path. 

Much support.

James: SOS needs to be coordinated with Ecrit.