IETF Logo Mail Archive

Re: [sipcore] RFC 6442 on Location Conveyance for the Session Initiation Protocol

"Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com> Sun, 04 December 2011 18:50 UTC

Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7882B21F86F6 for <sipcore@ietfa.amsl.com>; Sun, 4 Dec 2011 10:50:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level:
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFpgxeCVKv-Y for <sipcore@ietfa.amsl.com>; Sun, 4 Dec 2011 10:50:10 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 4D13821F86D0 for <sipcore@ietf.org>; Sun, 4 Dec 2011 10:50:09 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id pB4Io4E5010518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Dec 2011 19:50:04 +0100
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id pB4Io2TC003564; Sun, 4 Dec 2011 19:50:04 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Sun, 4 Dec 2011 19:50:00 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Sun, 04 Dec 2011 20:49:58 +0200
Message-ID: <999913AB42CC9341B05A99BBF358718DD7C885@FIESEXC035.nsn-intra.net>
In-Reply-To: <5A55A45AE77F5941B18E5457ECAC8188012119F93EAE@SISPE7MB1.commscope.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] RFC 6442 on Location Conveyance for the Session Initiation Protocol
Thread-Index: AcyxX5ln9mMgMQXqTKqK3GqxnY9A/wAGZDe5ABhtFkA=
References: <5A55A45AE77F5941B18E5457ECAC8188012119F93EAE@SISPE7MB1.commscope.com>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Winterbottom, James" <James.Winterbottom@commscope.com>, martin.thomson@gmail.com, jmpolk@cisco.com
X-OriginalArrivalTime: 04 Dec 2011 18:50:00.0242 (UTC) FILETIME=[86826920:01CCB2B5]
Cc: sipcore@ietf.org
Subject: Re: [sipcore] RFC 6442 on Location Conveyance for the Session Initiation Protocol
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Dec 2011 18:50:11 -0000

I thought I would never see this day. 

Congratulations!

> -----Original Message-----
> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On
> Behalf Of ext Winterbottom, James
> Sent: Saturday, December 03, 2011 7:05 AM
> To: 'martin.thomson@gmail.com'; 'jmpolk@cisco.com'
> Cc: 'sipcore@ietf.org'
> Subject: Re: [sipcore] RFC 6442 on Location Conveyance for the Session
> Initiation Protocol
> 
> +1
> 
> ----- Original Message -----
> From: sipcore-bounces@ietf.org <sipcore-bounces@ietf.org>
> To: James M. Polk <jmpolk@cisco.com>
> Cc: sipcore@ietf.org <sipcore@ietf.org>
> Sent: Sat Dec 03 10:02:15 2011
> Subject: Re: [sipcore] RFC 6442 on Location Conveyance for the Session
> Initiation Protocol
> 
> Congratulations.
> 
> On 3 December 2011 12:28, James M. Polk <jmpolk@cisco.com> wrote:
> > yyyeeeeeeee..... aaaaahhhhhhhhh
> >
> > clank...
> >
> > .....   creeeeek  .......
> >
> > <<<thud>>>
> >
> > (dust settles)
> >
> > wow... so that's been the weight dragging on me all this time....
> >
> > I feel better
> >
> > ;-)
> >
> > James
> >
> >
> > At 06:21 PM 12/2/2011, rfc-editor@rfc-editor.org wrote:
> >
> >> A new Request for Comments is now available in online RFC libraries.
> >>
> >>
> >>        RFC 6442
> >>
> >>        Title:      Location Conveyance for the Session
> >>                    Initiation Protocol
> >>        Author:     J. Polk, B. Rosen,
> >>                    J. Peterson
> >>        Status:     Standards Track
> >>        Stream:     IETF
> >>        Date:       December 2011
> >>        Mailbox:    jmpolk@cisco.com,
> >>                    br@brianrosen.net,
> >>                    jon.peterson@neustar.biz
> >>        Pages:      35
> >>        Characters: 80795
> >>        Updates/Obsoletes/SeeAlso:   None
> >>
> >>        I-D Tag:    draft-ietf-sipcore-location-conveyance-09.txt
> >>
> >>        URL:        http://www.rfc-editor.org/rfc/rfc6442.txt
> >>
> >> This document defines an extension to the Session Initiation
> >> Protocol (SIP) to convey geographic location information from one
> >> SIP entity to another SIP entity.  The SIP extension covers
> >> end-to-end conveyance as well as location-based routing, where SIP
> >> intermediaries make routing decisions based upon the location of the
> >> Location Target.  [STANDARDS-TRACK]
> >>
> >> This document is a product of the Session Initiation Protocol Core
> Working
> >> Group of the IETF.
> >>
> >> This is now a Proposed Standard Protocol.
> >>
> >> STANDARDS TRACK: This document specifies an Internet standards track
> >> protocol for the Internet community,and requests discussion and
> >> suggestions
> >> for improvements.  Please refer to the current edition of the
> Internet
> >> Official Protocol Standards (STD 1) for the standardization state
> and
> >> status of this protocol.  Distribution of this memo is unlimited.
> >>
> >> This announcement is sent to the IETF-Announce and rfc-dist lists.
> >> To subscribe or unsubscribe, see
> >>  http://www.ietf.org/mailman/listinfo/ietf-announce
> >>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> >>
> >> For searching the RFC series, see
> >> http://www.rfc-editor.org/rfcsearch.html.
> >> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
> >>
> >> Requests for special distribution should be addressed to either the
> >> author of the RFC in question, or to rfc-editor@rfc-
> editor.org.  Unless
> >> specifically noted otherwise on the RFC itself, all RFCs are for
> >> unlimited distribution.
> >>
> >>
> >> The RFC Editor Team
> >> Association Management Solutions, LLC
> >>
> >>
> >> _______________________________________________
> >> IETF-Announce mailing list
> >> IETF-Announce@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf-announce
> >
> >
> > _______________________________________________
> > sipcore mailing list
> > sipcore@ietf.org
> > https://www.ietf.org/mailman/listinfo/sipcore
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email