Re: [martini] REMINDER: Ongoing MARTINI WG last Call on "Registration for Multiple Phone Numbers in the SIP"

"Richard Shockey" <richard@shockey.us> Mon, 19 July 2010 15:39 UTC

Return-Path: <richard@shockey.us>
X-Original-To: martini@core3.amsl.com
Delivered-To: martini@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 817AA3A6912 for <martini@core3.amsl.com>; Mon, 19 Jul 2010 08:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.709
X-Spam-Level:
X-Spam-Status: No, score=-1.709 tagged_above=-999 required=5 tests=[AWL=0.555, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 BdLjDeFl7Jkm for <martini@core3.amsl.com>; Mon, 19 Jul 2010 08:39:31 -0700 (PDT)
Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by core3.amsl.com (Postfix) with SMTP id 759483A6901 for <martini@ietf.org>; Mon, 19 Jul 2010 08:39:31 -0700 (PDT)
Received: (qmail 19785 invoked by uid 0); 19 Jul 2010 15:39:45 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy3.bluehost.com with SMTP; 19 Jul 2010 15:39:45 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=Obxn2mMQVQpw57u/4sl4vq9lTpUynt0S1HF8Jx9KNdLC1mmJ/Wq61ZhyHuAcDHxsdeM0G4Logw9l7MQtycTv0xJeVWjwNpxKpoYLiiQvvfvCPE/zFLs+uSqbJ1uyhjpd;
Received: from pool-96-231-199-72.washdc.fios.verizon.net ([96.231.199.72] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1OasRV-0004Yg-1T; Mon, 19 Jul 2010 09:39:45 -0600
From: Richard Shockey <richard@shockey.us>
To: bruno.chatras@orange-ftgroup.com, bernard_aboba@hotmail.com, martini@ietf.org
References: <BLU137-W168F37C34E4BA034704B8893BB0@phx.gbl> <9ECCF01B52E7AB408A7EB8535264214101AEE888@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <9ECCF01B52E7AB408A7EB8535264214101AEE888@ftrdmel0.rd.francetelecom.fr>
Date: Mon, 19 Jul 2010 11:39:43 -0400
Message-ID: <000001cb2758$9c977cd0$d5c67670$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01CB2737.1585DCD0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcskRx7iGkoyBz7lTz2mZXYyzjco+AC+tGTgAAWCwqA=
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 96.231.199.72 authed with richard@shockey.us}
Subject: Re: [martini] REMINDER: Ongoing MARTINI WG last Call on "Registration for Multiple Phone Numbers in the SIP"
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of en-mass SIP PBX registration mechanisms <martini.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/martini>
List-Post: <mailto:martini@ietf.org>
List-Help: <mailto:martini-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2010 15:39:37 -0000

My memory of the conversation was quite clear.  The two approaches are
orthogonal. Gin is NOT dependant on FRIENDS or the other way around. Each
approach should have its own option tag. There is NOT a one size fits all
solution. 

 

The friends solution can certainly propose a option tag on its own in the
usual way IETG WG way but the two are NOT part of a single draft.

 

As far as I’m concerned the WGLC should proceed as normal.

 

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of bruno.chatras@orange-ftgroup.com
Sent: Monday, July 19, 2010 9:01 AM
To: bernard_aboba@hotmail.com; martini@ietf.org
Subject: Re: [martini] REMINDER: Ongoing MARTINI WG last Call on
"Registration for Multiple Phone Numbers in the SIP"

 

Looking to the minutes of the MARTINI Interim V virtual meeting, it seems
that the discussion about "draft-vanelburg-martini-friends-00" was
inconclusive as to whether a change was required to the "gin" draft. I don't
think the WGLC can be completed before we have clarified the interactions
between "gin" and "friends".

Bruno

 


  _____  


De : martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] De la part
de Bernard Aboba
Envoyé : jeudi 15 juillet 2010 19:57
À : martini@ietf.org
Objet : [martini] REMINDER: Ongoing MARTINI WG last Call on "Registration
for Multiple Phone Numbers in the SIP"

This is a reminder of an ongoing MARTINI WG last call on "Registration for
Multiple Phone Numbers in the SIP" prior to requesting that the IESG publish
the document as a Proposed Standard. 

The document is available for inspection here:
http://www.ietf.org/internet-drafts/draft-ietf-martini-gin-05.txt

MARTINI WG last call will conclude on Thursday, July 22, 2010. 

Please respond to this WG last call, whether you have comments or not. 

If you have no comments, please reply to this message and indicate in the
body of your message whether you

think the document is ready for consideration by the IESG or not. 

If you have comments, please provide them to the WG in one of the following
ways: 

1. If you have an account on the IETF Tools server, or can open one, please
login and enter your issue(s) in the 

MARTINI Issue tracking database (TRAC), which is available here:

http://trac.tools.ietf.org/wg/martini/trac/newticket

Note that if you submit an issue in TRAC, it will automatically also be
posted to the MARTINI WG mailing list. 

2. If you don't have an account on the IETF Tools server, please post your

Issue to the MARTINI WG mailing list (martini at ietf.org) in the following
format: 

To:  martini at ietf.org

Subject: Requirements-Issue: <title of your issue>

Priority: blocker, critical, major, minor or trivial

<Explanation of your issue, including a proposal for specific text changes
to resolve the issue>