Subject: AW: [Sipping] Ad-hoc on TISPAN: Wednesday 0900-1000 in Bourdeaux

From: "Jesske, R" <[email-masked]>
Date: Tue, 2 Aug 2005 09:43:44 +0200

Dear all,
I would like to point also to draft:

http://www.ietf.org/internet-drafts/draft-garcia-sipping-etsi-ngn-p-headers-00.txt

>From Miguel Garcia that slipped through. It is planned that all possible P-header extensions for TISPAN should be described within one document.

Roland

> -----Ursprüngliche Nachricht-----
> Von: [email-masked] 
> [mailto:[email-masked]] Im Auftrag von Gonzalo Camarillo
> Gesendet: Dienstag, 2. August 2005 09:30
> An: sipping
> Cc: Rohan Mahy; Allison Mankin; Dean Willis
> Betreff: [Sipping] Ad-hoc on TISPAN: Wednesday 0900-1000 in Bourdeaux
> 
> 
> Folks,
> 
> the ad-hoc on TISPAN will finally be taking place on 
> Wednesday from 0900 
> to 1000 in Bordeaux. Right after the ad-hoc, we will have the SIPPING 
> session in the same room.
> 
> Unfortunatelly, this ad-hoc overlaps with an AVT session, but 
> there is 
> nothing we can do about it.
> 
> You may want to read the following drafts to prepare for this ad-hoc 
> meeting:
> 
> draft-jesske-sipping-tispan-requirements-01.txt
> draft-jesske-sipping-tispan-analysis-00.txt
> draft-jesske-sipping-etsi-ngn-reason-00.txt
> 
> The idea is to discuss requirements, technical solutions, alternative 
> approaches, etc... complaining about business plans is out of 
> the scope 
> of this meeting.
> 
> Let's try to get a common understanding on this area.
> 
> Cheers,
> 
> Gonzalo
> SIPPING co-chair
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [email-masked] for questions on current sip
> Use [email-masked] for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP