From gaurav.knangla@gmail.com  Mon Dec  7 00:41:45 2009
Return-Path: <gaurav.knangla@gmail.com>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8AA628C122 for <sipping@core3.amsl.com>; Mon,  7 Dec 2009 00:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZUrQI3WTUO4 for <sipping@core3.amsl.com>; Mon,  7 Dec 2009 00:41:45 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by core3.amsl.com (Postfix) with ESMTP id B5BF528C121 for <sipping@ietf.org>; Mon,  7 Dec 2009 00:41:44 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id 19so599715fgg.13 for <sipping@ietf.org>; Mon, 07 Dec 2009 00:41:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Exb3QCM6JW65JLgchmvVnKxPYw6ufp+Fx9UaYQ3jpMc=; b=DodT3TbXjEi7gJrT+EBT8lsRFWALaIPj/PVL6jYhkHkd0kCeaBI4iJ/yOngoE2ep6+ fSuzJG9ANuB4L5Q5LduGdxvrzzGb85u6h8DTfacMwUEGIdiF4OZzE9unr6tgT3P+N8im W5hDhsZ2HsVyXOZFrFongPlQoMiQvuavbvkzI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=qDpr6fqy8cc7FvnSC674hiqrJ5FjD4KXjZa/44Hyi3zavCOpSrKL3lZDIM/63+1avX FvacOf0oSieEVnPyvriAIJOK/TilMRw2bZD/5rNFIE678W2kkkn42pV60Kj5u1jyKDsh IG6tdsj3WaEOgI5vnaC2rQbrolTNMHAVMjrS0=
MIME-Version: 1.0
Received: by 10.102.235.20 with SMTP id i20mr2026585muh.38.1260175290546; Mon,  07 Dec 2009 00:41:30 -0800 (PST)
Date: Mon, 7 Dec 2009 14:11:30 +0530
Message-ID: <925de63b0912070041l3b29dd84tb21a2caa770974ca@mail.gmail.com>
From: Gaurav Nangla <gaurav.knangla@gmail.com>
To: sipping@ietf.org, sip-implementors@lists.cs.columbia.edu,  discussion@sipforum.org
Content-Type: multipart/alternative; boundary=001636416d898c3968047a1f6cbf
Subject: [Sipping] Collision free Ids: Call-ID, icid-value, Session-ID
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2009 08:41:45 -0000

--001636416d898c3968047a1f6cbf
Content-Type: text/plain; charset=ISO-8859-1

Hi there!

Is there an approppriate algorithm like the 'Session-ID generation algorithm'
proposed in http://tools.ietf.org/html/draft-kaplan-sip-session-id-02, for
the Call-ID header and icid-value (P-Charging-Vector) param.

If another developer attempts to generate an id (vis-a-vis the Call-ID
header and icid-value (P-Charging-Vector) param) using a different algorithm
than the one I've cooked up, I'll have collisions with their ids, i.e. they
will no longer be globally unique.

Is there an appendix with an algorithm in the specs for generating these ids
that I'm missing or is this a real problem?

-- 
Gaurav

--001636416d898c3968047a1f6cbf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi there!<br><br>Is there an approppriate algorithm <span><span>like the &#=
39;Session-ID generation </span></span>algorithm&#39; proposed in <a href=
=3D"http://tools.ietf.org/html/draft-kaplan-sip-session-id-02" target=3D"_b=
lank">http://tools.ietf.org/html/draft-kaplan-sip-session-id-02</a>,
for the Call-ID header and icid-value (P-Charging-Vector) param.<br><div id=
=3D":1xl" class=3D"ii gt"><br>If
another developer attempts to generate an id (vis-a-vis the Call-ID
header and icid-value (P-Charging-Vector) param) using a different
algorithm than the one I&#39;ve cooked up, I&#39;ll have collisions with
their ids, i.e. they will no longer be globally unique.<br clear=3D"all"><b=
r>Is there an appendix with an algorithm in the specs for generating these =
ids that I&#39;m missing or is this a real problem?<br><br>-- <br><font col=
or=3D"#888888">Gaurav</font></div>

--001636416d898c3968047a1f6cbf--

From wwwrun@core3.amsl.com  Tue Dec  8 13:44:44 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: sipping@ietf.org
Delivered-To: sipping@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id D5C643A68E1; Tue,  8 Dec 2009 13:44:44 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20091208214444.D5C643A68E1@core3.amsl.com>
Date: Tue,  8 Dec 2009 13:44:44 -0800 (PST)
Cc: sipping@ietf.org
Subject: [Sipping] Last Call: draft-ietf-sipping-config-framework (A Framework for Session Initiation Protocol User Agent Profile Delivery) to Proposed Standard
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2009 21:44:45 -0000

The IESG has received a request from the Session Initiation Proposal 
Investigation WG (sipping) to consider the following document:

- 'A Framework for Session Initiation Protocol User Agent Profile 
   Delivery '
   <draft-ietf-sipping-config-framework-16.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-12-22. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The IPR disclosure at 
https://datatracker.ietf.org/ipr/search/?option=document_search&id_document_tag=10128
was received after the working group requested publication. Please consider that
disclosure when preparing comments.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-framework-16.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=10128&rfc_flag=0


From spencer@wonderhamster.org  Tue Dec  8 14:25:52 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C11293A6942; Tue,  8 Dec 2009 14:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[AWL=0.719,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BPWkTG8wEdhw; Tue,  8 Dec 2009 14:25:52 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id E49973A68D4; Tue,  8 Dec 2009 14:25:51 -0800 (PST)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MV6gv-1Nb4Wa0drB-00YLLu; Tue, 08 Dec 2009 17:25:40 -0500
Message-ID: <2D674B58536A4E71975022512AF6A411@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "SIP IETF" <sip@ietf.org>, <sipping@ietf.org>
Date: Tue, 8 Dec 2009 16:25:29 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/HBMPvVK1k616cbou+x2MAfC7qCXYOiEOCvxN 1O+9vOUGbJm5n1C6o/vCPFQRFikPmvF0Am3lZnmE4pVc0cXjz1 LJ8WjfQ7PooRCgsL0Zc1jDbnJ6uzitRz7JNE2o802Y=
Cc: techwg@sipforum.org
Subject: [Sipping] Fw: [martini] New Mailing List announcement - MARTINI (was - DREGS)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2009 22:25:52 -0000

Just so everyone is on the same page, Cullen asked me to announce this 
mailing list on SIP, SIPPING, and the techwg mailing list...

See you on MARTINI!

Thanks,

Spencer

----- Original Message ----- 
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: <dispatch@ietf.org>; <rai@ietf.org>
Cc: <martini@ietf.org>
Sent: Tuesday, December 08, 2009 4:23 PM
Subject: [martini] New Mailing List announcement - MARTINI (was - DREGS)


> Cullen has asked me to announce a new mailing list, called MARTINI 
> (acronym
> for "Multiple AoR reachabiliTy InformatioN Indication"), to be used for
> discussion of what has variously been called "implicit registration",
> "domain registration", and probably some other terms as well.
>
> To be a little more precise, the MARTINI mailing list was created to 
> discuss
> means by which an entity that is authoritative for SIP URIs can 
> dynamically
> register reachability information for multiple Addresses of Record 
> ("AORs")
> with a service provider.
>
> The coordinates are in the place you'd expect:
>
> General Discussion: martini@ietf.org
> To Subscribe: martini-request@ietf.org
> In Body: subscribe
> Archive: http://www.ietf.org/mail-archive/web/martini/index.html
>
> Just to catch people up... DISPATCH recommended that this proposed work go
> forward in a mini-working group. The IESG approved a proposed charter to 
> be
> sent for a two-week review on last Thursday's telechat, so you should see
> that announcement popping out fairly quickly.
>
> That charter also proposes an interim meeting in January 2010, and we'll 
> be
> discussing logistics on the MARTINI mailing list in the near future, so
> please subscribe Real Soon Now if you are interested in the topic.
>
> Thanks!
>
> Spencer
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini 


From root@core3.amsl.com  Sun Dec 20 11:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: sipping@ietf.org
Delivered-To: sipping@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id D58E73A688B; Sun, 20 Dec 2009 11:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20091220193001.D58E73A688B@core3.amsl.com>
Date: Sun, 20 Dec 2009 11:30:01 -0800 (PST)
Cc: sipping@ietf.org
Subject: [Sipping] I-D Action:draft-ietf-sipping-cc-framework-12.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Dec 2009 19:30:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.


	Title           : A Call Control and Multi-party usage framework for the Session Initiation Protocol (SIP)
	Author(s)       : R. Mahy, et al.
	Filename        : draft-ietf-sipping-cc-framework-12.txt
	Pages           : 44
	Date            : 2009-12-20

This document defines a framework and requirements for call control
and multi-party usage of Session Initiation Protocol (SIP).  To
enable discussion of multi-party features and applications we define
an abstract call model for describing the media relationships
required by many of these.  The model and actions described here are
specifically chosen to be independent of the SIP signaling and/or
mixing approach chosen to actually setup the media relationships.  In
addition to its dialog manipulation aspect, this framework includes
requirements for communicating related information and events such as
conference and session state, and session history.  This framework
also describes other goals that embody the spirit of SIP applications
as used on the Internet such as: definition of primitives, not
services; invoker and participant oriented; signaling and mixing
model independence, and others.

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups.  Note that
other groups may also distribute working documents as Internet-
Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This Internet-Draft will expire on June 23, 2010.

Copyright Notice

Copyright (c) 2009 IETF Trust and the persons identified as the
document authors.  All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document.  Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.  Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.

This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008.  The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-framework-12.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-sipping-cc-framework-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-12-20111925.I-D@ietf.org>


--NextPart--