FW: SIP BCP-T

"Mark Watson" <mwatson@nortelnetworks.com> Tue, 02 November 1999 10:27 UTC

Message-ID: <61ABD11436FED21192440000F81F3E36012B706B@nwcwi1a.europe.nortel.com>
From: Mark Watson <mwatson@nortelnetworks.com>
To: "'sip@lists.research.bell-labs.com'" <sip@lists.research.bell-labs.com>
Subject: FW: SIP BCP-T
Date: Tue, 02 Nov 1999 10:22:21 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF251C.28E66CC8"
Sender: owner-sip@lists.research.bell-labs.com
Precedence: bulk

> All,
> 
> An enhanced definition for the ISUP MIME type is described in:
> 
> http://www.ietf.org/internet-drafts/draft-watson-sip-isup-mime-00.txt
> 
> This includes provision for identifying the base protocol version from
> which the encapsulated ISUP variant is derived. This will allow processing
> of the message at a node which supports the base protocol but not the
> variant.
> 
> Regards,
> 
> Mark Watson
> Nortel Networks
> 
> 
> ----------
> From: 	Aparna.Vemuri@Level3.com
> Sent: 	Monday, November 1, 1999 5:54 pm
> To: 	sip@lists.research.bell-labs.com
> Subject: 	SIP BCP-T
> 
> Hello,
> 
> A new version of the SIP BCP-T Internet draft is available at:
> 
> http://www.ietf.org/internet-drafts/draft-zimmerer-sip-bcp-t-00.txt
> 
> Also, the latest version of the ISUP MIME draft is available at:
> http://www.ietf.org/internet-drafts/draft-zimmerer-sip-isup-mime-00.txt.
> 
> 
> These two will (hopefully) be discussed at the SIP WG session at the IETF
> meet.
> 
> Comments are welcome.
> 
> 
> Thanks,
> Aparna
> 
> Aparna V.
> Level 3 Communications.
> 
> 
> 
>

FW: SIP BCP-T Mark Watson
SIP BCP-T Aparna.Vemuri