From bernard_aboba@hotmail.com Sun Oct 10 11:50:17 2010 Return-Path: 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 DB6653A6827 for ; Sun, 10 Oct 2010 11:50:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.825 X-Spam-Level: X-Spam-Status: No, score=-101.825 tagged_above=-999 required=5 tests=[AWL=0.773, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 ETumjd9sHqqj for ; Sun, 10 Oct 2010 11:50:01 -0700 (PDT) Received: from blu0-omc2-s14.blu0.hotmail.com (blu0-omc2-s14.blu0.hotmail.com [65.55.111.89]) by core3.amsl.com (Postfix) with ESMTP id E05243A6830 for ; Sun, 10 Oct 2010 11:50:00 -0700 (PDT) Received: from BLU137-DS8 ([65.55.111.71]) by blu0-omc2-s14.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 10 Oct 2010 11:51:10 -0700 X-Originating-IP: [24.19.29.20] X-Originating-Email: [bernard_aboba@hotmail.com] Message-ID: From: Bernard Aboba To: Date: Sun, 10 Oct 2010 11:51:12 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0157_01CB6871.6FCBC710" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcrrvaKxbDWoul6pSgqETCs+ydNLPx86tnHQ Content-Language: en-us X-OriginalArrivalTime: 10 Oct 2010 18:51:10.0643 (UTC) FILETIME=[1AF9C030:01CB68AC] Subject: [martini] Draft PROTO writeup for MARTINI GIN Document X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Oct 2010 18:50:17 -0000 ------=_NextPart_000_0157_01CB6871.6FCBC710 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit PROTO Writeup for draft-ietf-martini-gin ================================================= http://tools.ietf.org/html/draft-ietf-martini-gin (1.a) Who is the Document Shepherd for this document? Has the Document Shepherd personally reviewed this version of the document and, in particular, does he or she believe this version is ready for forwarding to the IESG for publication? Bernard Aboba is the document shepherd. I have personally reviewed the document, and believe it is ready for publication as an Informational RFC. (1.b) Has the document had adequate review both from key members of the interested community and others? Does the Document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? The document has been extensively discussed on the MARTINI WG mailing list. The discussion has included representatives from both the PBX and service-provider communities as well as participants in SIP Forum. As a result, the reviews appear to have been reasonably thorough and representative. (1.c) Does the Document Shepherd have concerns that the document needs more review from a particular or broader perspective, e.g., security, operational complexity, someone familiar with AAA, internationalization or XML? No concerns. (1.d) Does the Document Shepherd have any specific concerns or issues with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the interested community has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here. No concerns. (1.e) How solid is the consensus of the interested community behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the interested community as a whole understand and agree with it? There appears to be strong consensus behind the document, which has been evaluated against the solution requirements (and appears to meet all of them). (1.f) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise the areas of conflict in separate email messages to the Responsible Area Director. (It should be in a separate email because this questionnaire is entered into the ID Tracker.) No. (1.g) Has the Document Shepherd personally verified that the document satisfies all ID nits? (See http://www.ietf.org/ID-Checklist.html and http://tools.ietf.org/tools/idnits/). Boilerplate checks are not enough; this check needs to be thorough. Has the document met all formal review criteria it needs to, such as the MIB Doctor, media type and URI type reviews? IDNits are clean: idnits 2.12.05 tmp/draft-ietf-martini-gin-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see http://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to http://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document date (September 28, 2010) is 12 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 warnings (==), 1 comment (--). ---------------------------------------------------------------------------- ---- (1.h) Has the document split its references into normative and informative? Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the strategy for their completion? Are there normative references that are downward references, as described in [RFC3967]? If so, list these downward references to support the Area Director in the Last Call procedure for them [RFC3967]. The references in the document have been split into normative and informative. Normative references are all stable documents published as RFCs. (1.i) Has the Document Shepherd verified that the document IANA consideration section exists and is consistent with the body of the document? If the document specifies protocol extensions, are reservations requested in appropriate IANA registries? Are the IANA registries clearly identified? If the document creates a new registry, does it define the proposed initial contents of the registry and an allocation procedure for future registrations? Does it suggested a reasonable name for the new registry? See [I-D.narten-iana-considerations-rfc2434bis]. If the document describes an Expert Review process has Shepherd conferred with the Responsible Area Director so that the IESG can appoint the needed Expert during the IESG Evaluation? The IANA Considerations section exists (section 9). The document does not create a new registry or describe an Expert Review process. (1.j) Has the Document Shepherd verified that sections of the document that are written in a formal language, such as XML code, BNF rules, MIB definitions, etc., validate correctly in an automated checker? Not applicable. (1.k) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Writeup? Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: Technical Summary This document defines a mechanism by which a SIP server acting as a traditional Private Branch Exchange (SIP-PBX) can register with a SIP Service Provider (SSP) to receive phone calls for UAs designated by phone numbers. The mechanism requires that the multiple AoRs being registered are each globally unique, which is the case for fully qualified AoRs representing E.164 numbers. Working Group Summary Since this document relates to the registration of multiple AoRs in a single exchange, much of the discussion centered around the implications and limitations of the scheme. In particular, there was extensive discussion on potential requirements for globally reachable contact URIs, as well as the circumstances under which the multiple AoRs being registered would each be globally unique. Although the globally unique AoR requirement can be met for email-style URIs as well as URIs representing E.164 numbers, this document chooses to focus on URIs representing E.164 numbers only. Document Quality The document has been reviewed by participants within the IETF MARTINI WG, including SIP service providers as well as representatives from the PBX vendor community. It has gone through MARTINI WG last call. Personnel Bernard Aboba is the document shepherd for this document. Gonzalo Camarillo is the responsible AD. ------=_NextPart_000_0157_01CB6871.6FCBC710 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

PROTO Writeup for draft-ietf-martini-gin

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

 

http://tools.ietf.org/html/draft-ietf-martini-gin<= /o:p>

 

   (1.a)  Who is the Document = Shepherd for this document?  Has the

      Document Shepherd = personally reviewed this version of the document

      and, in particular, = does he or she believe this version is ready

      for forwarding to = the IESG for publication?

 

Bernard Aboba is the document shepherd.  I = have personally reviewed

the document, and believe it is ready for = publication as an Informational RFC.

 

   (1.b)  Has the document had = adequate review both from key members of

      the interested = community and others?  Does the Document Shepherd

      have any concerns = about the depth or breadth of the reviews that

      have been = performed?

 

The document has been extensively discussed on the = MARTINI WG mailing list.  The discussion has

included representatives from both the PBX and service-provider communities as well as

participants in SIP = Forum.  As a result, the reviews appear to have been

reasonably thorough and representative. =

 

   (1.c)  Does the Document Shepherd = have concerns that the document

      needs more review = from a particular or broader perspective, e.g.,

      security, = operational complexity, someone familiar with AAA,

      internationalization = or XML?

 

No concerns.

 

   (1.d)  Does the Document Shepherd = have any specific concerns or

      issues with this = document that the Responsible Area Director

      and/or the IESG = should be aware of?  For example, perhaps he or

      she is uncomfortable = with certain parts of the document, or has

      concerns whether = there really is a need for it.  In any event, if

      the interested = community has discussed those issues and has

      indicated that it = still wishes to advance the document, detail

      those concerns = here.

 

No concerns.

 

   (1.e)  How solid is the consensus = of the interested community behind

      this document?  = Does it represent the strong concurrence of a few

      individuals, with = others being silent, or does the interested

      community as a whole understand and agree with it?

 

There appears = to be strong consensus behind the = document, which

has been evaluated = against the solution requirements (and appears

to meet all of them). =

 

 

   (1.f)  Has anyone threatened an = appeal or otherwise indicated extreme

      discontent?  If = so, please summarise the areas of conflict in

      separate email = messages to the Responsible Area Director.  (It

      should be in a = separate email because this questionnaire is

      entered into the ID = Tracker.)

 

No.

 

   (1.g)  Has the Document Shepherd personally verified that the

      document satisfies = all ID nits?  (See

      http://www.ietf.org/ID-Checklist.html and

      http://tools.ietf.org/tools/idnits/).  Boilerplate checks are = not

      enough; this check = needs to be thorough.  Has the document met all

      formal review = criteria it needs to, such as the MIB Doctor, media

      type and URI type = reviews?

 

IDNits are clean:

 

idnits 2.12.05

 

tmp/draft-ietf-martini-gin-09.txt:

 

  Checking boilerplate required by RFC 5378 and the IETF Trust = (see

  http://trustee.ietf.org/license-info):

  -------------------------------------------------------------------------= ---

 

     No issues found here.

 

  Checking nits according to = http://www.ietf.org/id-info/1id-guidelines.txt:

  -------------------------------------------------------------------------= ---

 

     No issues found here.

 

  Checking nits according to http://www.ietf.org/id-info/checklist = :

  -------------------------------------------------------------------------= ---

 

     No issues found here.

 

  Miscellaneous warnings:

  -------------------------------------------------------------------------= ---

 

  -- The document date (September 28, 2010) is 12 days in the past.  = Is this

     intentional?

 

 

  Checking references for intended status: Proposed = Standard

  -------------------------------------------------------------------------= ---

 

     (See RFCs 3967 and 4897 for information about using normative = references

     to lower-maturity documents in RFCs)

 

     No issues found here.

 

     Summary: 0 errors (**), 0 warnings (=3D=3D), 1 comment = (--).

-------------------------------------------------------------------= -------------

 

   (1.h)  Has the document split its references into normative and

      informative?  = Are there normative references to documents that are

      not ready for = advancement or are otherwise in an unclear state?

      If such normative = references exist, what is the strategy for their

      completion?  = Are there normative references that are downward

      references, as = described in [RFC3967]?  If so, list these downward

      references to = support the Area Director in the Last Call procedure

      for them = [RFC3967].

 

The references in the document have been split into normative and informative.

 

Normative references are all stable documents = published as RFCs.

 

   (1.i)  Has the Document Shepherd = verified that the document IANA

      consideration = section exists and is consistent with the body of

      the document?  = If the document specifies protocol extensions, are

      reservations = requested in appropriate IANA registries?  Are the

      IANA registries = clearly identified?  If the document creates a new

      registry, does it = define the proposed initial contents of the

      registry and an = allocation procedure for future registrations?

      Does it suggested a reasonable name for the new registry?  See

      [I-D.narten-iana-considerations-rfc2434bis].  If the = document

      describes an Expert = Review process has Shepherd conferred with the

     Responsible Area = Director so that the IESG can appoint the needed

      Expert during the = IESG Evaluation?

 

The IANA Considerations = section exists (section 9).   The document

does not create a new = registry or describe an Expert Review process.

 

   (1.j)  Has the Document Shepherd = verified that sections of the

      document that are = written in a formal language, such as XML code,

      BNF rules, MIB = definitions, etc., validate correctly in an

      automated = checker?

 

Not applicable.

 

   (1.k)  The IESG approval = announcement includes a Document

      Announcement = Write-Up.  Please provide such a Document

      Announcement = Writeup?  Recent examples can be found in the

      "Action" announcements for approved documents.  The approval

      announcement = contains the following sections:

 

      Technical = Summary

 

This document defines a mechanism by which a SIP server acting as =
a
traditional Private Branch Exchange (SIP-PBX) can =
register with a SIP
Service Provider (SSP) to =
receive phone calls for UAs designated by
phone =
numbers.  The mechanism requires that the multiple AoRs being =

registered are each globally unique, which is the =
case for fully qualified
AoRs representing E.164 =
numbers.

 

      Working Group = Summary

 

Since this document relates to the registration of multiple AoRs =
in
a single exchange, much of the discussion =
centered around the 
implications and limitations =
of the scheme.  In particular, there
was =
extensive discussion on potential requirements for =
globally
reachable contact URIs, as well as the =
circumstances under
which the multiple AoRs being =
registered would each be globally
unique.  =
Although the globally unique AoR requirement can =
be
met for email-style URIs as well as URIs =
representing E.164
numbers, this document chooses =
to focus on URIs representing
E.164 numbers only. =

 

      Document = Quality

 

The document has been reviewed by participants = within the IETF MARTINI WG, including SIP

service providers as well as representatives from = the PBX vendor community.  It has gone

through MARTINI WG last call.

 

      = Personnel

 

Bernard Aboba is the document shepherd for this = document.

Gonzalo Camarillo is the responsible = AD.

------=_NextPart_000_0157_01CB6871.6FCBC710-- From adam@nostrum.com Sun Oct 10 14:39:07 2010 Return-Path: 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 D6A7C3A67E6 for ; Sun, 10 Oct 2010 14:39:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.306 X-Spam-Level: X-Spam-Status: No, score=-101.306 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100] 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 R05-ZU8jEg-F for ; Sun, 10 Oct 2010 14:39:03 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 2F0373A67AB for ; Sun, 10 Oct 2010 14:39:01 -0700 (PDT) Received: from hydra-3.local (ppp-70-242-117-72.dsl.rcsntx.swbell.net [70.242.117.72]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o9ALe8S2087364 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 10 Oct 2010 16:40:08 -0500 (CDT) (envelope-from adam@nostrum.com) Message-ID: <4CB232B8.2060501@nostrum.com> Date: Sun, 10 Oct 2010 16:40:08 -0500 From: Adam Roach User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------070604090102080800060802" Cc: Bernard Aboba , "martini@ietf.org" Subject: Re: [martini] Draft PROTO writeup for MARTINI GIN Document X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Oct 2010 21:39:08 -0000 This is a multi-part message in MIME format. --------------070604090102080800060802 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Bernard: Before you send this off to Gonzalo, I think we still have an open issue in section 7.1.1: Open Issue: This section needs to call out the level of support required of GIN systems with regards to public GRUUs. This issue is being resolved on the MARTINI mailing list. I didn't see a formal announcement of consensus on this topic on the mailing list, although there was a lot of traffic around September 28th and 29th. I think the two contenders are basically: (1) "The SSP SHOULD support the public GRUU mechanism described in this section", or (2) "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs." There were some fringe opinions that don't fit into either of these buckets, but (from what I can see on the mailing list), none of these opinions were held by more than one person. I personally think option (2) is preferable, for the reasons I've explained earlier on the list. /a On 10/10/10 13:51, Oct 10, Bernard Aboba wrote: > > PROTO Writeup for draft-ietf-martini-gin > > ================================================= > > http://tools.ietf.org/html/draft-ietf-martini-gin > > (1.a) Who is the Document Shepherd for this document? Has the > > Document Shepherd personally reviewed this version of the document > > and, in particular, does he or she believe this version is ready > > for forwarding to the IESG for publication? > > Bernard Aboba is the document shepherd. I have personally reviewed > > the document, and believe it is ready for publication as an > Informational RFC. > > (1.b) Has the document had adequate review both from key members of > > the interested community and others? Does the Document Shepherd > > have any concerns about the depth or breadth of the reviews that > > have been performed? > > The document has been extensively discussed on the MARTINI WG mailing > list. The discussion has > > included representatives from both the PBX and service-provider > communities as well as > > participants in SIP Forum. As a result, the reviews appear to have been > > reasonably thorough and representative. > > (1.c) Does the Document Shepherd have concerns that the document > > needs more review from a particular or broader perspective, e.g., > > security, operational complexity, someone familiar with AAA, > > internationalization or XML? > > No concerns. > > (1.d) Does the Document Shepherd have any specific concerns or > > issues with this document that the Responsible Area Director > > and/or the IESG should be aware of? For example, perhaps he or > > she is uncomfortable with certain parts of the document, or has > > concerns whether there really is a need for it. In any event, if > > the interested community has discussed those issues and has > > indicated that it still wishes to advance the document, detail > > those concerns here. > > No concerns. > > (1.e) How solid is the consensus of the interested community behind > > this document? Does it represent the strong concurrence of a few > > individuals, with others being silent, or does the interested > > community as a whole understand and agree with it? > > There appears to be strong consensus behind the document, which > > has been evaluated against the solution requirements (and appears > > to meet all of them). > > (1.f) Has anyone threatened an appeal or otherwise indicated extreme > > discontent? If so, please summarise the areas of conflict in > > separate email messages to the Responsible Area Director. (It > > should be in a separate email because this questionnaire is > > entered into the ID Tracker.) > > No. > > (1.g) Has the Document Shepherd personally verified that the > > document satisfies all ID nits? (See > > http://www.ietf.org/ID-Checklist.html and > > http://tools.ietf.org/tools/idnits/). Boilerplate checks are not > > enough; this check needs to be thorough. Has the document met all > > formal review criteria it needs to, such as the MIB Doctor, media > > type and URI type reviews? > > IDNits are clean: > > idnits 2.12.05 > > tmp/draft-ietf-martini-gin-09.txt: > > Checking boilerplate required by RFC 5378 and the IETF Trust (see > > http://trustee.ietf.org/license-info): > > > ---------------------------------------------------------------------------- > > No issues found here. > > Checking nits according to > http://www.ietf.org/id-info/1id-guidelines.txt: > > > ---------------------------------------------------------------------------- > > No issues found here. > > Checking nits according to http://www.ietf.org/id-info/checklist : > > > ---------------------------------------------------------------------------- > > No issues found here. > > Miscellaneous warnings: > > > ---------------------------------------------------------------------------- > > -- The document date (September 28, 2010) is 12 days in the past. > Is this > > intentional? > > Checking references for intended status: Proposed Standard > > > ---------------------------------------------------------------------------- > > (See RFCs 3967 and 4897 for information about using normative > references > > to lower-maturity documents in RFCs) > > No issues found here. > > Summary: 0 errors (**), 0 warnings (==), 1 comment (--). > > -------------------------------------------------------------------------------- > > (1.h) Has the document split its references into normative and > > informative? Are there normative references to documents that are > > not ready for advancement or are otherwise in an unclear state? > > If such normative references exist, what is the strategy for their > > completion? Are there normative references that are downward > > references, as described in [RFC3967]? If so, list these downward > > references to support the Area Director in the Last Call procedure > > for them [RFC3967]. > > The references in the document have been split into normative and > informative. > > Normative references are all stable documents published as RFCs. > > (1.i) Has the Document Shepherd verified that the document IANA > > consideration section exists and is consistent with the body of > > the document? If the document specifies protocol extensions, are > > reservations requested in appropriate IANA registries? Are the > > IANA registries clearly identified? If the document creates a new > > registry, does it define the proposed initial contents of the > > registry and an allocation procedure for future registrations? > > Does it suggested a reasonable name for the new registry? See > > [I-D.narten-iana-considerations-rfc2434bis]. If the document > > describes an Expert Review process has Shepherd conferred with the > > Responsible Area Director so that the IESG can appoint the needed > > Expert during the IESG Evaluation? > > The IANA Considerations section exists (section 9). The document > > does not create a new registry or describe an Expert Review process. > > (1.j) Has the Document Shepherd verified that sections of the > > document that are written in a formal language, such as XML code, > > BNF rules, MIB definitions, etc., validate correctly in an > > automated checker? > > Not applicable. > > (1.k) The IESG approval announcement includes a Document > > Announcement Write-Up. Please provide such a Document > > Announcement Writeup? Recent examples can be found in the > > "Action" announcements for approved documents. The approval > > announcement contains the following sections: > > Technical Summary > > This document defines a mechanism by which a SIP server acting as a > traditional Private Branch Exchange (SIP-PBX) can register with a SIP > Service Provider (SSP) to receive phone calls for UAs designated by > phone numbers. The mechanism requires that the multiple AoRs being > registered are each globally unique, which is the case for fully qualified > AoRs representing E.164 numbers. > > Working Group Summary > > Since this document relates to the registration of multiple AoRs in > a single exchange, much of the discussion centered around the > implications and limitations of the scheme. In particular, there > was extensive discussion on potential requirements for globally > reachable contact URIs, as well as the circumstances under > which the multiple AoRs being registered would each be globally > unique. Although the globally unique AoR requirement can be > met for email-style URIs as well as URIs representing E.164 > numbers, this document chooses to focus on URIs representing > E.164 numbers only. > > Document Quality > > The document has been reviewed by participants within the IETF MARTINI > WG, including SIP > > service providers as well as representatives from the PBX vendor > community. It has gone > > through MARTINI WG last call. > > Personnel > > Bernard Aboba is the document shepherd for this document. > > Gonzalo Camarillo is the responsible AD. > > > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini --------------070604090102080800060802 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Bernard:

Before you send this off to Gonzalo, I think we still have an open issue in section 7.1.1:

 Open Issue: This section needs to call out the level of support
   required of GIN systems with regards to public GRUUs.  This issue is
   being resolved on the MARTINI mailing list.

I didn't see a formal announcement of consensus on this topic on the mailing list, although there was a lot of traffic around September 28th and 29th. I think the two contenders are basically: (1) "The SSP SHOULD support the public GRUU mechanism described in this section", or (2)  "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."

There were some fringe opinions that don't fit into either of these buckets, but (from what I can see on the mailing list), none of these opinions were held by more than one person.

I personally think option (2) is preferable, for the reasons I've explained earlier on the list.

/a


On 10/10/10 13:51, Oct 10, Bernard Aboba wrote:

PROTO Writeup for draft-ietf-martini-gin

=================================================

 

http://tools.ietf.org/html/draft-ietf-martini-gin

 

   (1.a)  Who is the Document Shepherd for this document?  Has the

      Document Shepherd personally reviewed this version of the document

      and, in particular, does he or she believe this version is ready

      for forwarding to the IESG for publication?

 

Bernard Aboba is the document shepherd.  I have personally reviewed

the document, and believe it is ready for publication as an Informational RFC.

 

   (1.b)  Has the document had adequate review both from key members of

      the interested community and others?  Does the Document Shepherd

      have any concerns about the depth or breadth of the reviews that

      have been performed?

 

The document has been extensively discussed on the MARTINI WG mailing list.  The discussion has

included representatives from both the PBX and service-provider communities as well as

participants in SIP Forum.  As a result, the reviews appear to have been

reasonably thorough and representative.

 

   (1.c)  Does the Document Shepherd have concerns that the document

      needs more review from a particular or broader perspective, e.g.,

      security, operational complexity, someone familiar with AAA,

      internationalization or XML?

 

No concerns.

 

   (1.d)  Does the Document Shepherd have any specific concerns or

      issues with this document that the Responsible Area Director

      and/or the IESG should be aware of?  For example, perhaps he or

      she is uncomfortable with certain parts of the document, or has

      concerns whether there really is a need for it.  In any event, if

      the interested community has discussed those issues and has

      indicated that it still wishes to advance the document, detail

      those concerns here.

 

No concerns.

 

   (1.e)  How solid is the consensus of the interested community behind

      this document?  Does it represent the strong concurrence of a few

      individuals, with others being silent, or does the interested

      community as a whole understand and agree with it?

 

There appears to be strong consensus behind the document, which

has been evaluated against the solution requirements (and appears

to meet all of them).

 

 

   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme

      discontent?  If so, please summarise the areas of conflict in

      separate email messages to the Responsible Area Director.  (It

      should be in a separate email because this questionnaire is

      entered into the ID Tracker.)

 

No.

 

   (1.g)  Has the Document Shepherd personally verified that the

      document satisfies all ID nits?  (See

      http://www.ietf.org/ID-Checklist.html and

      http://tools.ietf.org/tools/idnits/).  Boilerplate checks are not

      enough; this check needs to be thorough.  Has the document met all

      formal review criteria it needs to, such as the MIB Doctor, media

      type and URI type reviews?

 

IDNits are clean:

 

idnits 2.12.05

 

tmp/draft-ietf-martini-gin-09.txt:

 

  Checking boilerplate required by RFC 5378 and the IETF Trust (see

  http://trustee.ietf.org/license-info):

  ----------------------------------------------------------------------------

 

     No issues found here.

 

  Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt:

  ----------------------------------------------------------------------------

 

     No issues found here.

 

  Checking nits according to http://www.ietf.org/id-info/checklist :

  ----------------------------------------------------------------------------

 

     No issues found here.

 

  Miscellaneous warnings:

  ----------------------------------------------------------------------------

 

  -- The document date (September 28, 2010) is 12 days in the past.  Is this

     intentional?

 

 

  Checking references for intended status: Proposed Standard

  ----------------------------------------------------------------------------

 

     (See RFCs 3967 and 4897 for information about using normative references

     to lower-maturity documents in RFCs)

 

     No issues found here.

 

     Summary: 0 errors (**), 0 warnings (==), 1 comment (--).

--------------------------------------------------------------------------------

 

   (1.h)  Has the document split its references into normative and

      informative?  Are there normative references to documents that are

      not ready for advancement or are otherwise in an unclear state?

      If such normative references exist, what is the strategy for their

      completion?  Are there normative references that are downward

      references, as described in [RFC3967]?  If so, list these downward

      references to support the Area Director in the Last Call procedure

      for them [RFC3967].

 

The references in the document have been split into normative and informative.

 

Normative references are all stable documents published as RFCs.

 

   (1.i)  Has the Document Shepherd verified that the document IANA

      consideration section exists and is consistent with the body of

      the document?  If the document specifies protocol extensions, are

      reservations requested in appropriate IANA registries?  Are the

      IANA registries clearly identified?  If the document creates a new

      registry, does it define the proposed initial contents of the

      registry and an allocation procedure for future registrations?

      Does it suggested a reasonable name for the new registry?  See

      [I-D.narten-iana-considerations-rfc2434bis].  If the document

      describes an Expert Review process has Shepherd conferred with the

     Responsible Area Director so that the IESG can appoint the needed

      Expert during the IESG Evaluation?

 

The IANA Considerations section exists (section 9).   The document

does not create a new registry or describe an Expert Review process.

 

   (1.j)  Has the Document Shepherd verified that sections of the

      document that are written in a formal language, such as XML code,

      BNF rules, MIB definitions, etc., validate correctly in an

      automated checker?

 

Not applicable.

 

   (1.k)  The IESG approval announcement includes a Document

      Announcement Write-Up.  Please provide such a Document

      Announcement Writeup?  Recent examples can be found in the

      "Action" announcements for approved documents.  The approval

      announcement contains the following sections:

 

      Technical Summary

 

This document defines a mechanism by which a SIP server acting as a
traditional Private Branch Exchange (SIP-PBX) can register with a SIP
Service Provider (SSP) to receive phone calls for UAs designated by
phone numbers.  The mechanism requires that the multiple AoRs being 
registered are each globally unique, which is the case for fully qualified
AoRs representing E.164 numbers.

 

      Working Group Summary

 

Since this document relates to the registration of multiple AoRs in
a single exchange, much of the discussion centered around the 
implications and limitations of the scheme.  In particular, there
was extensive discussion on potential requirements for globally
reachable contact URIs, as well as the circumstances under
which the multiple AoRs being registered would each be globally
unique.  Although the globally unique AoR requirement can be
met for email-style URIs as well as URIs representing E.164
numbers, this document chooses to focus on URIs representing
E.164 numbers only.

 

      Document Quality

 

The document has been reviewed by participants within the IETF MARTINI WG, including SIP

service providers as well as representatives from the PBX vendor community.  It has gone

through MARTINI WG last call.

 

      Personnel

 

Bernard Aboba is the document shepherd for this document.

Gonzalo Camarillo is the responsible AD.


_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini

--------------070604090102080800060802-- From bernard_aboba@hotmail.com Sun Oct 10 18:09:43 2010 Return-Path: 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 0880A3A6874 for ; Sun, 10 Oct 2010 18:09:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.83 X-Spam-Level: X-Spam-Status: No, score=-101.83 tagged_above=-999 required=5 tests=[AWL=0.768, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 VtzH30n7i81o for ; Sun, 10 Oct 2010 18:09:40 -0700 (PDT) Received: from blu0-omc2-s19.blu0.hotmail.com (blu0-omc2-s19.blu0.hotmail.com [65.55.111.94]) by core3.amsl.com (Postfix) with ESMTP id 6FCFA3A672E for ; Sun, 10 Oct 2010 18:09:33 -0700 (PDT) Received: from BLU137-W37 ([65.55.111.73]) by blu0-omc2-s19.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 10 Oct 2010 18:10:44 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_18bd43a0-ddbb-4bc0-94c0-d80f1c43847c_" X-Originating-IP: [24.19.90.172] From: Bernard Aboba To: Date: Sun, 10 Oct 2010 18:10:44 -0700 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 11 Oct 2010 01:10:44.0338 (UTC) FILETIME=[2127D520:01CB68E1] Subject: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 01:09:44 -0000 --_18bd43a0-ddbb-4bc0-94c0-d80f1c43847c_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable There is one outstanding issue on the GIN document=2C which relates to SSP = support for public GRUUs. We would now like to have a consensus call of th= e WG on this point.=20 The consensus call will last until October 17=2C 2010. Please respond to t= his email indicating whether you wish to change the current text in the doc= ument=2C and if so=2C how. Choices include:=20 (1) No change (public GRUU support remains optional).=20 (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism described in this section=2C unless the SSP has other means of providing globally routable contact URIs." = --_18bd43a0-ddbb-4bc0-94c0-d80f1c43847c_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable There is one outstanding issue on the GIN document=2C which relates to SSP = support for public GRUUs. =3B We would now like to have a consensus cal= l of the WG on this point.

The consensus call will last until Octob= er 17=2C 2010. =3B Please respond to this email indicating whether you = wish to change the current text in the document=2C and if so=2C how. = =3B Choices include:

(1) =3B No change (public GRUU support rem= ains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section."

(3) =3B Change the MAY to: =3B "The SSP MUST s= upport the public GRUU mechanism described in this section=2C unless the SSP has other means of providing globally routable contact URIs."


= --_18bd43a0-ddbb-4bc0-94c0-d80f1c43847c_-- From aallen@rim.com Sun Oct 10 23:58:38 2010 Return-Path: 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 106FA3A68F8 for ; Sun, 10 Oct 2010 23:58:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.057 X-Spam-Level: X-Spam-Status: No, score=-6.057 tagged_above=-999 required=5 tests=[AWL=-0.855, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4] 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 RRrRisWOmROC for ; Sun, 10 Oct 2010 23:58:37 -0700 (PDT) Received: from mhs04ykf.rim.net (mhs04ykf.rim.net [216.9.243.82]) by core3.amsl.com (Postfix) with ESMTP id BA3F73A68C3 for ; Sun, 10 Oct 2010 23:58:36 -0700 (PDT) X-AuditID: 0a666446-b7b19ae0000019a1-1b-4cb2b5e31f03 Received: from XCH139CNC.rim.net ( [10.65.10.235]) by mhs04ykf.rim.net (RIM Mail) with SMTP id 43.B8.06561.3E5B2BC4; Mon, 11 Oct 2010 02:59:47 -0400 (EDT) Received: from XCH02DFW.rim.net ([10.150.100.31]) by XCH139CNC.rim.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Oct 2010 02:59:47 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB6911.E34257E7" X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 11 Oct 2010 01:59:45 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: Acto4St09uu1/WVrRgulpwRsp1ygGgAMJlwAAAAFtlA= From: "Andrew Allen" To: X-OriginalArrivalTime: 11 Oct 2010 06:59:47.0869 (UTC) FILETIME=[E4790CD0:01CB6911] X-Brightmail-Tracker: AAAAAQAAAZE= Subject: [martini] FW: Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 06:58:38 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CB6911.E34257E7 Content-Type: text/plain; charset="us-ascii" content-transfer-encoding: quoted-printable (3) From: Andrew Allen Sent: Monday, October 11, 2010 1:59 AM To: 'Bernard Aboba' Subject: RE: [martini] Consensus call on Public GRUU language (3) From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of Bernard Aboba Sent: Sunday, October 10, 2010 8:11 PM To: martini@ietf.org Subject: [martini] Consensus call on Public GRUU language There is one outstanding issue on the GIN document, which relates to SSP support for public GRUUs. We would now like to have a consensus call of the WG on this point. The consensus call will last until October 17, 2010. Please respond to this email indicating whether you wish to change the current text in the document, and if so, how. Choices include: (1) No change (public GRUU support remains optional). (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs." ---------------------------------------------------------------------=0A= This transmission (including any attachments) may contain confidential infor= mation, privileged material (including material protected by the solicitor-c= lient or other applicable privileges), or constitute non-public information.= Any use of this information by anyone other than the intended recipient is= prohibited. If you have received this transmission in error, please immedia= tely reply to the sender and delete this information from your system. Use,= dissemination, distribution, or reproduction of this transmission by uninte= nded recipients is not authorized and may be unlawful. ------_=_NextPart_001_01CB6911.E34257E7 Content-Type: text/html; charset="us-ascii" content-transfer-encoding: quoted-printable

(3)

 

From: Andrew Allen <= br> Sent: Monday, October 11, 2010 1:59 AM
To: 'Bernard Aboba'
Subject: RE: [martini] Consensus call on Public GRUU language

 

(3)

 

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of <= /b>Bernard Aboba
Sent: Sunday, October 10, 2010 8:11 PM
To: martini@ietf.org
Subject: [martini] Consensus call on Public GRUU language<= /span>

 

There is one outstanding issue on the GIN document, which relates to SSP support for public GRUUs.  We would now like to have a consensus call of the WG on this point.

The consensus call will last until October 17, 2010.  Please respond to this email indicating whether you wish to change the current text in the document, and if so, how.  Choices include:

(1)  No change (public GRUU support remains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanis= m described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public GRU= U mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."

---------------------------------------------------------------------
= =0A= This transmission (including any attachments) may contain confidential infor= mation, privileged material (including material protected by the solicitor-c= lient or other applicable privileges), or constitute non-public information.= Any use of this information by anyone other than the intended recipient is= prohibited. If you have received this transmission in error, please immedia= tely reply to the sender and delete this information from your system. Use,= dissemination, distribution, or reproduction of this transmission by uninte= nded recipients is not authorized and may be unlawful. ------_=_NextPart_001_01CB6911.E34257E7-- From keith.drage@alcatel-lucent.com Mon Oct 11 07:00:44 2010 Return-Path: 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 085283A6A2C for ; Mon, 11 Oct 2010 07:00:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.139 X-Spam-Level: X-Spam-Status: No, score=-103.139 tagged_above=-999 required=5 tests=[AWL=-0.891, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 xnzYMNEjdxmJ for ; Mon, 11 Oct 2010 07:00:43 -0700 (PDT) Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 030813A6A29 for ; Mon, 11 Oct 2010 07:00:42 -0700 (PDT) Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o9BE1n5B027363 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 11 Oct 2010 16:01:52 +0200 Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.44]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 11 Oct 2010 16:01:37 +0200 From: "DRAGE, Keith (Keith)" To: Bernard Aboba , "martini@ietf.org" Date: Mon, 11 Oct 2010 16:01:36 +0200 Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: Acto4SrgVpfZi2qVQdmdwrH9AVt72AAadbKQ Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE21748F979FRMRSSXCHMBSC3d_" MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84 Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 14:00:44 -0000 --_000_EDC0A1AE77C57744B664A310A0B23AE21748F979FRMRSSXCHMBSC3d_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable (3) Keith ________________________________ From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf = Of Bernard Aboba Sent: Monday, October 11, 2010 2:11 AM To: martini@ietf.org Subject: [martini] Consensus call on Public GRUU language There is one outstanding issue on the GIN document, which relates to SSP su= pport for public GRUUs. We would now like to have a consensus call of the = WG on this point. The consensus call will last until October 17, 2010. Please respond to thi= s email indicating whether you wish to change the current text in the docum= ent, and if so, how. Choices include: (1) No change (public GRUU support remains optional). (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism de= scribed in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism de= scribed in this section, unless the SSP has other means of providing global= ly routable contact URIs." --_000_EDC0A1AE77C57744B664A310A0B23AE21748F979FRMRSSXCHMBSC3d_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
(3)
 
Keith

From: martini-bounces@ietf.org=20 [mailto:martini-bounces@ietf.org] On Behalf Of Bernard=20 Aboba
Sent: Monday, October 11, 2010 2:11 AM
To:=20 martini@ietf.org
Subject: [martini] Consensus call on Public GR= UU=20 language

There is one outstanding issue on the GIN document, which rela= tes=20 to SSP support for public GRUUs.  We would now like to have a consen= sus=20 call of the WG on this point.

The consensus call will last until= =20 October 17, 2010.  Please respond to this email indicating whether y= ou=20 wish to change the current text in the document, and if so, how.  Ch= oices=20 include:

(1)  No change (public GRUU support remains optiona= l).=20

(2) Change the MAY to: "The SSP SHOULD support the public GRUU=20 mechanism described in this section."

(3)  Change the MAY=20 to:  "The SSP MUST support the public GRUU mechanism described in th= is=20 section, unless the SSP has other means of providing globally routable co= ntact=20 URIs."


--_000_EDC0A1AE77C57744B664A310A0B23AE21748F979FRMRSSXCHMBSC3d_-- From richard@shockey.us Mon Oct 11 07:11:30 2010 Return-Path: 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 828AA3A6A85 for ; Mon, 11 Oct 2010 07:11:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.242 X-Spam-Level: X-Spam-Status: No, score=-102.242 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] 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 n72fLf652cgZ for ; Mon, 11 Oct 2010 07:11:29 -0700 (PDT) Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by core3.amsl.com (Postfix) with SMTP id CB39E3A6A83 for ; Mon, 11 Oct 2010 07:11:28 -0700 (PDT) Received: (qmail 5223 invoked by uid 0); 11 Oct 2010 14:12:40 -0000 Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy3.bluehost.com with SMTP; 11 Oct 2010 14:12:40 -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=o+cW8wYxifHHPpNYimNAYIBJA3hPFIBkULL/nL0tVUCheM+HZRKm+rs7PGwic76Njeknu0wLYRKvPomgs15c2IKr6IJNMPyp3l1ZC5+TlMfINgx8w4ucDtBdqbAN1kpm; Received: from pool-173-79-200-247.washdc.fios.verizon.net ([173.79.200.247] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1P5J7I-0002HO-26; Mon, 11 Oct 2010 08:12:40 -0600 From: "Richard Shockey" To: "'Bernard Aboba'" , References: In-Reply-To: Date: Mon, 11 Oct 2010 10:12:39 -0400 Message-ID: <00d101cb694e$5d432c40$17c984c0$@us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D2_01CB692C.D6318C40" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acto4SgbeOTwg58rQSe6m8VyCWIupwAbQOyg Content-Language: en-us X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.79.200.247 authed with richard@shockey.us} Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 14:11:30 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_00D2_01CB692C.D6318C40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit (1) Preferred (2) would work as well. I do not support MUST in any language. From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of Bernard Aboba Sent: Sunday, October 10, 2010 9:11 PM To: martini@ietf.org Subject: [martini] Consensus call on Public GRUU language There is one outstanding issue on the GIN document, which relates to SSP support for public GRUUs. We would now like to have a consensus call of the WG on this point. The consensus call will last until October 17, 2010. Please respond to this email indicating whether you wish to change the current text in the document, and if so, how. Choices include: (1) No change (public GRUU support remains optional). (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs." ------=_NextPart_000_00D2_01CB692C.D6318C40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

(1)    Preferred  (2) would work as well.  I do not = support MUST in any language.

 

From:= = martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of Bernard Aboba
Sent: Sunday, October 10, 2010 9:11 PM
To: martini@ietf.org
Subject: [martini] Consensus call on Public GRUU = language

 

There is one outstanding issue on the = GIN document, which relates to SSP support for public GRUUs.  We would = now like to have a consensus call of the WG on this point.

The consensus call will last until October 17, 2010.  Please = respond to this email indicating whether you wish to change the current text in the document, and if so, how.  Choices include:

(1)  No change (public GRUU support remains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU = mechanism described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public = GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."

------=_NextPart_000_00D2_01CB692C.D6318C40-- From HKaplan@acmepacket.com Mon Oct 11 07:32:39 2010 Return-Path: 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 560BB3A6AA9 for ; Mon, 11 Oct 2010 07:32:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.471 X-Spam-Level: X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.127, 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 ybO+5V3tc8e6 for ; Mon, 11 Oct 2010 07:32:38 -0700 (PDT) Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 05A423A6A8A for ; Mon, 11 Oct 2010 07:32:38 -0700 (PDT) Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 11 Oct 2010 10:33:50 -0400 Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Mon, 11 Oct 2010 10:33:28 -0400 From: Hadriel Kaplan To: Bernard Aboba Date: Mon, 11 Oct 2010 10:33:27 -0400 Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: ActpUUS+VcOqWU6YSsS53zvsTXyC2g== Message-ID: <0ED05B9A-58B9-46BA-9F20-B569F42E511E@acmepacket.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_0ED05B9A58B946BA9F20B569F42E511Eacmepacketcom_" MIME-Version: 1.0 Cc: "martini@ietf.org" Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 14:32:39 -0000 --_000_0ED05B9A58B946BA9F20B569F42E511Eacmepacketcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable (1) or (2). On Oct 10, 2010, at 9:10 PM, Bernard Aboba wrote: There is one outstanding issue on the GIN document, which relates to SSP su= pport for public GRUUs. We would now like to have a consensus call of the = WG on this point. The consensus call will last until October 17, 2010. Please respond to thi= s email indicating whether you wish to change the current text in the docum= ent, and if so, how. Choices include: (1) No change (public GRUU support remains optional). (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism de= scribed in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism de= scribed in this section, unless the SSP has other means of providing global= ly routable contact URIs." --_000_0ED05B9A58B946BA9F20B569F42E511Eacmepacketcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
There is one outstanding issue on the GIN document, w= hich relates to SSP support for public GRUUs.  We would now like to ha= ve a consensus call of the WG on this point. 

The consensus call will last until October 17, = 2010.  Please respond to this email indicating whether you wish to cha= nge the current text in the document, and if so, how.  Choices include= : 

(1)  No ch= ange (public GRUU support remains optional). 

(2) Change the MAY to: "The SSP SHOULD support = the public GRUU mechanism described in this section."

(3)  Chan= ge the MAY to:  "The SSP MUST support the public GRUU mechanism descri= bed in this section, unless the SSP has other means of providing globally r= outable contact URIs."


<ATT00001..c>

= --_000_0ED05B9A58B946BA9F20B569F42E511Eacmepacketcom_-- From md3135@att.com Mon Oct 11 07:35:47 2010 Return-Path: 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 D4BF73A6A8A for ; Mon, 11 Oct 2010 07:35:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.543 X-Spam-Level: X-Spam-Status: No, score=-106.543 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] 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 wS8D21dVLyw0 for ; Mon, 11 Oct 2010 07:35:46 -0700 (PDT) Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id 0CD6A3A6A85 for ; Mon, 11 Oct 2010 07:35:45 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: md3135@att.com X-Msg-Ref: server-13.tower-121.messagelabs.com!1286807816!47466489!1 X-StarScan-Version: 6.2.4; banners=-,-,- X-Originating-IP: [144.160.20.146] Received: (qmail 2027 invoked from network); 11 Oct 2010 14:36:56 -0000 Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-13.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Oct 2010 14:36:56 -0000 Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o9BEaKig024537; Mon, 11 Oct 2010 10:36:20 -0400 Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o9BEaF1g024407; Mon, 11 Oct 2010 10:36:15 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB6951.BDA5574A" Date: Mon, 11 Oct 2010 10:36:47 -0400 Message-ID: <14C85D6CCBE92743AF33663BF5D24EBA07F30626@gaalpa1msgusr7e.ugd.att.com> In-Reply-To: <0ED05B9A-58B9-46BA-9F20-B569F42E511E@acmepacket.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: ActpUUS+VcOqWU6YSsS53zvsTXyC2gAAGzfw References: <0ED05B9A-58B9-46BA-9F20-B569F42E511E@acmepacket.com> From: "DOLLY, MARTIN C (ATTLABS)" To: "Hadriel Kaplan" , "Bernard Aboba" Cc: martini@ietf.org Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 14:35:48 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CB6951.BDA5574A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Agreed, 1 or 2 =20 From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of Hadriel Kaplan Sent: Monday, October 11, 2010 10:33 AM To: Bernard Aboba Cc: martini@ietf.org Subject: Re: [martini] Consensus call on Public GRUU language =20 =20 (1) or (2). =20 =20 On Oct 10, 2010, at 9:10 PM, Bernard Aboba wrote: There is one outstanding issue on the GIN document, which relates to SSP support for public GRUUs. We would now like to have a consensus call of the WG on this point.=20 The consensus call will last until October 17, 2010. Please respond to this email indicating whether you wish to change the current text in the document, and if so, how. Choices include:=20 (1) No change (public GRUU support remains optional).=20 (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs." =20 ------_=_NextPart_001_01CB6951.BDA5574A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Agreed, 1 or 2

 

From:= martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf = Of Hadriel Kaplan
Sent: Monday, October 11, 2010 10:33 AM
To: Bernard Aboba
Cc: martini@ietf.org
Subject: Re: [martini] Consensus call on Public GRUU = language

 

 

(1) or (2).

 

 

On Oct 10, 2010, at 9:10 PM, Bernard Aboba = wrote:



There is one outstanding issue on the GIN document, which relates to SSP = support for public GRUUs.  We would now like to have a consensus call of the WG = on this point. 

The consensus call will last until October 17, 2010.  Please = respond to this email indicating whether you wish to change the current text in the document, and if so, how.  Choices include: 

(1)  No change (public GRUU support remains optional). 

(2) Change the MAY to: "The SSP SHOULD support the public GRUU = mechanism described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public = GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."


<ATT00001..c>

 

------_=_NextPart_001_01CB6951.BDA5574A-- From pkyzivat@cisco.com Mon Oct 11 07:54:54 2010 Return-Path: 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 D71983A6B03 for ; Mon, 11 Oct 2010 07:54:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.495 X-Spam-Level: X-Spam-Status: No, score=-110.495 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] 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 wm7wobegrpdU for ; Mon, 11 Oct 2010 07:54:53 -0700 (PDT) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 756C93A6B02 for ; Mon, 11 Oct 2010 07:54:53 -0700 (PDT) Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhcFAJvCskxAZnwN/2dsb2JhbACUEY18caRSnDaFSASKQYMD X-IronPort-AV: E=Sophos;i="4.57,314,1283731200"; d="scan'208";a="169373953" Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 11 Oct 2010 14:56:05 +0000 Received: from [161.44.174.118] (dhcp-161-44-174-118.cisco.com [161.44.174.118]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9BEu46d017264 for ; Mon, 11 Oct 2010 14:56:04 GMT Message-ID: <4CB32584.7020302@cisco.com> Date: Mon, 11 Oct 2010 10:56:04 -0400 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: martini@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 14:54:55 -0000 (2) or (3). Thanks, Paul On 10/10/2010 9:10 PM, Bernard Aboba wrote: > There is one outstanding issue on the GIN document, which relates to SSP > support for public GRUUs. We would now like to have a consensus call of > the WG on this point. > > The consensus call will last until October 17, 2010. Please respond to > this email indicating whether you wish to change the current text in the > document, and if so, how. Choices include: > > (1) No change (public GRUU support remains optional). > > (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism > described in this section." > > (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism > described in this section, unless the SSP has other means of providing > globally routable contact URIs." > > > > > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini From adam@nostrum.com Mon Oct 11 08:40:38 2010 Return-Path: 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 47F803A68D5 for ; Mon, 11 Oct 2010 08:40:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.665 X-Spam-Level: X-Spam-Status: No, score=-102.665 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 8tNFEwK4DW4J for ; Mon, 11 Oct 2010 08:40:36 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 4322E3A68DB for ; Mon, 11 Oct 2010 08:40:36 -0700 (PDT) Received: from dn3-228.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o9BFf6ZF073487 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 11 Oct 2010 10:41:06 -0500 (CDT) (envelope-from adam@nostrum.com) Message-ID: <4CB33012.2050004@nostrum.com> Date: Mon, 11 Oct 2010 10:41:06 -0500 From: Adam Roach User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Paul Kyzivat References: <4CB32584.7020302@cisco.com> In-Reply-To: <4CB32584.7020302@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: martini@ietf.org Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 15:40:38 -0000 To clarify my earlier comment: I prefer (3), but could go along with (2) also. /a On 10/11/10 9:56 AM, Paul Kyzivat wrote: > (2) or (3). > > Thanks, > Paul > > On 10/10/2010 9:10 PM, Bernard Aboba wrote: >> There is one outstanding issue on the GIN document, which relates to SSP >> support for public GRUUs. We would now like to have a consensus call of >> the WG on this point. >> >> The consensus call will last until October 17, 2010. Please respond to >> this email indicating whether you wish to change the current text in the >> document, and if so, how. Choices include: >> >> (1) No change (public GRUU support remains optional). >> >> (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism >> described in this section." >> >> (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism >> described in this section, unless the SSP has other means of providing >> globally routable contact URIs." >> >> >> >> >> _______________________________________________ >> martini mailing list >> martini@ietf.org >> https://www.ietf.org/mailman/listinfo/martini > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini From john.elwell@siemens-enterprise.com Mon Oct 11 08:47:33 2010 Return-Path: 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 272D23A6A9E for ; Mon, 11 Oct 2010 08:47:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.627 X-Spam-Level: X-Spam-Status: No, score=-102.627 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 7eTxdgE0F4Nt for ; Mon, 11 Oct 2010 08:47:32 -0700 (PDT) Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id DA6FB3A68FF for ; Mon, 11 Oct 2010 08:47:31 -0700 (PDT) Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1869180; Mon, 11 Oct 2010 17:48:43 +0200 Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 0D1721EB82B0; Mon, 11 Oct 2010 17:48:43 +0200 (CEST) Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 11 Oct 2010 17:48:42 +0200 From: "Elwell, John" To: Bernard Aboba , "martini@ietf.org" Date: Mon, 11 Oct 2010 17:48:41 +0200 Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: Acto4SlvtJ9+gLvZRFGop/ln+glsTQAemdAQ Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 15:47:33 -0000 I can accept (1), (2) or (3). John=20 > -----Original Message----- > From: martini-bounces@ietf.org=20 > [mailto:martini-bounces@ietf.org] On Behalf Of Bernard Aboba > Sent: 11 October 2010 02:11 > To: martini@ietf.org > Subject: [martini] Consensus call on Public GRUU language >=20 > There is one outstanding issue on the GIN document, which=20 > relates to SSP support for public GRUUs. We would now like=20 > to have a consensus call of the WG on this point.=20 >=20 > The consensus call will last until October 17, 2010. Please=20 > respond to this email indicating whether you wish to change=20 > the current text in the document, and if so, how. Choices include:=20 >=20 > (1) No change (public GRUU support remains optional).=20 >=20 > (2) Change the MAY to: "The SSP SHOULD support the public=20 > GRUU mechanism described in this section." >=20 > (3) Change the MAY to: "The SSP MUST support the public=20 > GRUU mechanism described in this section, unless the SSP has=20 > other means of providing globally routable contact URIs." >=20 >=20 >=20 > = From D.Hancock@CableLabs.com Mon Oct 11 10:15:37 2010 Return-Path: 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 A28623A6B4A for ; Mon, 11 Oct 2010 10:15:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.463 X-Spam-Level: X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] 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 gPtOl9yUkgTn for ; Mon, 11 Oct 2010 10:15:35 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id D97CC3A6B01 for ; Mon, 11 Oct 2010 10:15:27 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o9BHGcxG024426; Mon, 11 Oct 2010 11:16:38 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Mon, 11 Oct 2010 11:16:39 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Mon, 11 Oct 2010 11:16:38 -0600 From: David Hancock To: Bernard Aboba , "martini@ietf.org" Date: Mon, 11 Oct 2010 11:16:38 -0600 Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: Acto4Sm0/xIiGG/VQsq1Uts5k0JXLwAhP/64 Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D1FF510F4@srvxchg> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 17:15:37 -0000 (1) preferred, (2) OK. David ________________________________________ From: martini-bounces@ietf.org [martini-bounces@ietf.org] On Behalf Of Bern= ard Aboba [bernard_aboba@hotmail.com] Sent: Sunday, October 10, 2010 7:10 PM To: martini@ietf.org Subject: [martini] Consensus call on Public GRUU language There is one outstanding issue on the GIN document, which relates to SSP su= pport for public GRUUs. We would now like to have a consensus call of the = WG on this point. The consensus call will last until October 17, 2010. Please respond to thi= s email indicating whether you wish to change the current text in the docum= ent, and if so, how. Choices include: (1) No change (public GRUU support remains optional). (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism de= scribed in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism de= scribed in this section, unless the SSP has other means of providing global= ly routable contact URIs." From JSBURTON@cablevision.com Mon Oct 11 10:54:01 2010 Return-Path: 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 75FED3A6B48 for ; Mon, 11 Oct 2010 10:54:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.838 X-Spam-Level: X-Spam-Status: No, score=0.838 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 cKb49yqfmnJC for ; Mon, 11 Oct 2010 10:54:00 -0700 (PDT) Received: from cscpsmout01.cablevision.com (cscpsmout01.cablevision.com [167.206.119.144]) by core3.amsl.com (Postfix) with ESMTP id EFA643A6B36 for ; Mon, 11 Oct 2010 10:53:59 -0700 (PDT) Received: from c3gwiaoutvs.cablevision.com (c3gwiaoutvs.cablevision.com [10.128.36.189]) by cscpsmout01.cablevision.com (Sentrion-MTA-4.0.2/Sentrion-MTA-4.0.2) with ESMTP id o9BHt96d001202 for ; Mon, 11 Oct 2010 13:55:10 -0400 X-DKIM: Sendmail DKIM Filter v2.5.6 cscpsmout01.cablevision.com o9BHt96d001202 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cablevision.com; s=cscprod; t=1286819710; bh=EnikzaRaw/GYRjbDkbBmnL2CiUSW+oCHmIpJjOU /qg0=; h=Message-Id:Date:From:To:Subject:References:In-Reply-To: Mime-Version:Content-Type; b=zhZj6r+ZpTW2/LUWMTHUKNl1o8MxA87EtZg5Z lgFjinmot4XUc0vPdQLilRaWaz0TaisBRcCKLcNhjMz2Nb9Ch56eib+0rbb9T/0vr6W 5csF9Z+u4fUmzdhDNQWQ33vFjOyL0CEN8RJ7MYZctWntiY0jcN1UMFaPIZAKHLmYUbg = Received: from C3GWIAOUTDOM-MTA by c3gwiaoutvs.cablevision.com with Novell_GroupWise; Mon, 11 Oct 2010 13:55:09 -0400 Message-Id: <4CB3173D.38CD.00CB.1@cablevision.com> X-Mailer: Novell GroupWise Internet Agent 8.0.2 Date: Mon, 11 Oct 2010 13:55:07 -0400 From: "Jack Burton" To: References: In-Reply-To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__PartB39E416B.0__=" X-Auth-Type: Internal IP Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 17:54:01 -0000 --=__PartB39E416B.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit (1) Jack >>> Bernard Aboba 10/10/2010 21:10 >>> There is one outstanding issue on the GIN document, which relates to SSP support for public GRUUs. We would now like to have a consensus call of the WG on this point. The consensus call will last until October 17, 2010. Please respond to this email indicating whether you wish to change the current text in the document, and if so, how. Choices include: (1) No change (public GRUU support remains optional). (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs." -------------------------------------------------------- The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful. If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof. -------------------------------------------------------- --=__PartB39E416B.0__= Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Description: HTML
(1)
Jack


>>> Bernard Aboba <bernard_aboba@hotmail.com> 10/10/2010 21:10 >>>
There is one outstanding issue on the GIN document, which relates to SSP support for public GRUUs.  We would now like to have a consensus call of the WG on this point.

The consensus call will last until October 17, 2010.  Please respond to this email indicating whether you wish to change the current text in the document, and if so, how.  Choices include:

(1)  No change (public GRUU support remains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."



--------------------------------------------------------
The information transmitted in this email and any of its attachments is intended only for the person or entity to which it is addressed and may contain information concerning Cablevision and/or its affiliates and subsidiaries that is proprietary, privileged, confidential and/or subject to copyright. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited and may be unlawful. If you received this in error, please contact the sender immediately and delete and destroy the communication and all of the attachments you have received and all copies thereof.
-------------------------------------------------------- --=__PartB39E416B.0__=-- From bernard_aboba@hotmail.com Mon Oct 11 13:36:21 2010 Return-Path: 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 8F1343A6B3B for ; Mon, 11 Oct 2010 13:36:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.836 X-Spam-Level: X-Spam-Status: No, score=-101.836 tagged_above=-999 required=5 tests=[AWL=0.762, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 K5NdSu0sxR7b for ; Mon, 11 Oct 2010 13:36:20 -0700 (PDT) Received: from blu0-omc2-s27.blu0.hotmail.com (blu0-omc2-s27.blu0.hotmail.com [65.55.111.102]) by core3.amsl.com (Postfix) with ESMTP id B69603A6B22 for ; Mon, 11 Oct 2010 13:36:19 -0700 (PDT) Received: from BLU137-W25 ([65.55.111.73]) by blu0-omc2-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 11 Oct 2010 13:37:32 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_b10c098c-b4f4-426f-91ab-f8039a689ab2_" X-Originating-IP: [72.11.66.126] From: Bernard Aboba To: Date: Mon, 11 Oct 2010 13:37:32 -0700 Importance: Normal In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7D1FF510F4@srvxchg> References: , <76AC5FEF83F1E64491446437EA81A61F7D1FF510F4@srvxchg> MIME-Version: 1.0 X-OriginalArrivalTime: 11 Oct 2010 20:37:32.0660 (UTC) FILETIME=[215E0340:01CB6984] Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 20:36:21 -0000 --_b10c098c-b4f4-426f-91ab-f8039a689ab2_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Speaking as an individual: (1) preferred=2C (2) OK.=20 =20 > From: D.Hancock@CableLabs.com > To: bernard_aboba@hotmail.com=3B martini@ietf.org > Date: Mon=2C 11 Oct 2010 11:16:38 -0600 > Subject: RE: [martini] Consensus call on Public GRUU language >=20 > (1) preferred=2C (2) OK. >=20 > David > ________________________________________ > From: martini-bounces@ietf.org [martini-bounces@ietf.org] On Behalf Of Be= rnard Aboba [bernard_aboba@hotmail.com] > Sent: Sunday=2C October 10=2C 2010 7:10 PM > To: martini@ietf.org > Subject: [martini] Consensus call on Public GRUU language >=20 > There is one outstanding issue on the GIN document=2C which relates to SS= P support for public GRUUs. We would now like to have a consensus call of t= he WG on this point. >=20 > The consensus call will last until October 17=2C 2010. Please respond to = this email indicating whether you wish to change the current text in the do= cument=2C and if so=2C how. Choices include: >=20 > (1) No change (public GRUU support remains optional). >=20 > (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism = described in this section." >=20 > (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism de= scribed in this section=2C unless the SSP has other means of providing glob= ally routable contact URIs." >=20 >=20 = --_b10c098c-b4f4-426f-91ab-f8039a689ab2_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Speaking as an individual: (1) preferred=2C (2) OK.
 =3B
>=3B From: D.Hancock@CableLabs.com
>=3B To: bernard_aboba@hotmail.co= m=3B martini@ietf.org
>=3B Date: Mon=2C 11 Oct 2010 11:16:38 -0600
= >=3B Subject: RE: [martini] Consensus call on Public GRUU language
>= =3B
>=3B (1) preferred=2C (2) OK.
>=3B
>=3B David
>= =3B ________________________________________
>=3B From: martini-bounce= s@ietf.org [martini-bounces@ietf.org] On Behalf Of Bernard Aboba [bernard_a= boba@hotmail.com]
>=3B Sent: Sunday=2C October 10=2C 2010 7:10 PM
&= gt=3B To: martini@ietf.org
>=3B Subject: [martini] Consensus call on P= ublic GRUU language
>=3B
>=3B There is one outstanding issue on = the GIN document=2C which relates to SSP support for public GRUUs. We would= now like to have a consensus call of the WG on this point.
>=3B
&= gt=3B The consensus call will last until October 17=2C 2010. Please respond= to this email indicating whether you wish to change the current text in th= e document=2C and if so=2C how. Choices include:
>=3B
>=3B (1) N= o change (public GRUU support remains optional).
>=3B
>=3B (2) C= hange the MAY to: "The SSP SHOULD support the public GRUU mechanism describ= ed in this section."
>=3B
>=3B (3) Change the MAY to: "The SSP M= UST support the public GRUU mechanism described in this section=2C unless t= he SSP has other means of providing globally routable contact URIs."
>= =3B
>=3B
= --_b10c098c-b4f4-426f-91ab-f8039a689ab2_-- From shida@ntt-at.com Tue Oct 12 07:07:54 2010 Return-Path: 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 CB0FD3A696E for ; Tue, 12 Oct 2010 07:07:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.283 X-Spam-Level: X-Spam-Status: No, score=-102.283 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] 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 OKkmO2s-lh3C for ; Tue, 12 Oct 2010 07:07:54 -0700 (PDT) Received: from gateway02.websitewelcome.com (gateway02.websitewelcome.com [67.18.62.20]) by core3.amsl.com (Postfix) with SMTP id 869E03A696B for ; Tue, 12 Oct 2010 07:07:52 -0700 (PDT) Received: (qmail 15602 invoked from network); 12 Oct 2010 14:09:06 -0000 Received: from gator465.hostgator.com (69.56.174.130) by gateway02.websitewelcome.com with SMTP; 12 Oct 2010 14:09:06 -0000 Received: from [60.236.84.106] (port=62057 helo=[192.168.1.2]) by gator465.hostgator.com with esmtpa (Exim 4.69) (envelope-from ) id 1P5fXM-0008Nn-DG; Tue, 12 Oct 2010 09:09:10 -0500 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: multipart/alternative; boundary=Apple-Mail-7--652306579 From: Shida Schubert In-Reply-To: Date: Tue, 12 Oct 2010 23:08:58 +0900 Message-Id: <26FD0F38-FCAF-4A82-8AA4-A611428C1E07@ntt-at.com> References: To: Bernard Aboba X-Mailer: Apple Mail (2.1081) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator465.hostgator.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ntt-at.com Cc: martini@ietf.org Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2010 14:07:54 -0000 --Apple-Mail-7--652306579 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Can live with (2), prefer (1) Shida On Oct 11, 2010, at 10:10 AM, Bernard Aboba wrote: > There is one outstanding issue on the GIN document, which relates to = SSP support for public GRUUs. We would now like to have a consensus = call of the WG on this point.=20 >=20 > The consensus call will last until October 17, 2010. Please respond = to this email indicating whether you wish to change the current text in = the document, and if so, how. Choices include:=20 >=20 > (1) No change (public GRUU support remains optional).=20 >=20 > (2) Change the MAY to: "The SSP SHOULD support the public GRUU = mechanism described in this section." >=20 > (3) Change the MAY to: "The SSP MUST support the public GRUU = mechanism described in this section, unless the SSP has other means of = providing globally routable contact URIs." >=20 >=20 > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini --Apple-Mail-7--652306579 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

Can live with (2), prefer = (1)

 Shida

On Oct 11, = 2010, at 10:10 AM, Bernard Aboba wrote:

 

The consensus call = will last until October 17, 2010.  Please respond to this email = indicating whether you wish to change the current text in the document, = and if so, how.  Choices include: 

(1)  No change = (public GRUU support remains optional). 

(2) Change the MAY = to: "The SSP SHOULD support the public GRUU mechanism described in this = section."

(3)  Change the MAY to:  "The SSP MUST = support the public GRUU mechanism described in this section, unless the = SSP has other means of providing globally routable contact = URIs."


_______________________________________________
marti= ni mailing list
martini@ietf.org
https://www.ietf.or= g/mailman/listinfo/martini

= --Apple-Mail-7--652306579-- From SBharrat@sonusnet.com Tue Oct 12 12:03:10 2010 Return-Path: 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 D7BD33A6A4B for ; Tue, 12 Oct 2010 12:03:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.948 X-Spam-Level: X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.651, 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 NuJ2o8Nzejsj for ; Tue, 12 Oct 2010 12:03:09 -0700 (PDT) Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by core3.amsl.com (Postfix) with ESMTP id 97F793A6A3E for ; Tue, 12 Oct 2010 12:03:09 -0700 (PDT) Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id o9CJ4OxS026915 for ; Tue, 12 Oct 2010 15:04:24 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 12 Oct 2010 15:03:48 -0400 Message-ID: <637C77B6763BB54ABF989B6B21D5323504041473@sonusmail05.sonusnet.com> In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7D1FF510F4@srvxchg> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: Acto4Sm0/xIiGG/VQsq1Uts5k0JXLwAhP/64ADZ7YPA= From: "Bharrat, Shaun" To: Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2010 19:03:10 -0000 (1) preferred, (2) OK Shaun =20 > -----Original Message----- > From: martini-bounces@ietf.org=20 > [mailto:martini-bounces@ietf.org] On Behalf Of David Hancock > Sent: Monday, October 11, 2010 1:17 PM > To: Bernard Aboba; martini@ietf.org > Subject: Re: [martini] Consensus call on Public GRUU language >=20 > (1) preferred, (2) OK. >=20 > David > ________________________________________ > From: martini-bounces@ietf.org [martini-bounces@ietf.org] On=20 > Behalf Of Bernard Aboba [bernard_aboba@hotmail.com] > Sent: Sunday, October 10, 2010 7:10 PM > To: martini@ietf.org > Subject: [martini] Consensus call on Public GRUU language >=20 > There is one outstanding issue on the GIN document, which=20 > relates to SSP support for public GRUUs. We would now like=20 > to have a consensus call of the WG on this point. >=20 > The consensus call will last until October 17, 2010. Please=20 > respond to this email indicating whether you wish to change=20 > the current text in the document, and if so, how. Choices include: >=20 > (1) No change (public GRUU support remains optional). >=20 > (2) Change the MAY to: "The SSP SHOULD support the public=20 > GRUU mechanism described in this section." >=20 > (3) Change the MAY to: "The SSP MUST support the public=20 > GRUU mechanism described in this section, unless the SSP has=20 > other means of providing globally routable contact URIs." >=20 >=20 > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini >=20 From dwsauder@dsauder.com Wed Oct 13 06:52:01 2010 Return-Path: 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 DC26D3A6AFF for ; Wed, 13 Oct 2010 06:52:01 -0700 (PDT) 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 hp971miy4oow for ; Wed, 13 Oct 2010 06:51:59 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id CFA583A6951 for ; Wed, 13 Oct 2010 06:51:43 -0700 (PDT) Received: from [10.16.5.31] ([206.132.246.2]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MaJHc-1PPt1z0rUm-00Ka8B; Wed, 13 Oct 2010 09:52:57 -0400 Message-ID: <4CB5B9B5.6040501@dsauder.com> Date: Wed, 13 Oct 2010 08:52:53 -0500 From: Doug Sauder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: martini@ietf.org References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------010008000705020002060009" X-Provags-ID: V02:K0:E6qvzcRFrz8TWnkMq+/WwjB9dEY2n1A3Tl5HpksE5kR xwFgQKuJIngDUxM2P9tTOwy9X+Xd2nR8d2GAzfXQ3AdLuMJm1x ThTpUrjHP4fgAaMrDaitt3fZBe3CvMTN9cbbv8tkQioLZEyJv9 GVfnzCyGZ61ZnoE0M48sanG+TIIysavmG2nuvCb3U4Gf6ikKou qOcZqJ6IwfLN9NOPLeobDxB/ZDGdigHxHwHeHi/Yh0= Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2010 13:52:02 -0000 This is a multi-part message in MIME format. --------------010008000705020002060009 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit (1) preferred, or (2) On 2010-10-10 20:10, Bernard Aboba wrote: > There is one outstanding issue on the GIN document, which relates to > SSP support for public GRUUs. We would now like to have a consensus > call of the WG on this point. > > The consensus call will last until October 17, 2010. Please respond > to this email indicating whether you wish to change the current text > in the document, and if so, how. Choices include: > > (1) No change (public GRUU support remains optional). > > (2) Change the MAY to: "The SSP SHOULD support the public GRUU > mechanism described in this section." > > (3) Change the MAY to: "The SSP MUST support the public GRUU > mechanism described in this section, unless the SSP has other means of > providing globally routable contact URIs." > > > > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini --------------010008000705020002060009 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit (1) preferred, or (2)

On 2010-10-10 20:10, Bernard Aboba wrote:
There is one outstanding issue on the GIN document, which relates to SSP support for public GRUUs.  We would now like to have a consensus call of the WG on this point.

The consensus call will last until October 17, 2010.  Please respond to this email indicating whether you wish to change the current text in the document, and if so, how.  Choices include:

(1)  No change (public GRUU support remains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."



_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini
--------------010008000705020002060009-- From alan.b.johnston@gmail.com Wed Oct 13 07:40:32 2010 Return-Path: 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 883E33A6B29 for ; Wed, 13 Oct 2010 07:40:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[AWL=-0.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100] 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 O+yIfSc+U82f for ; Wed, 13 Oct 2010 07:40:31 -0700 (PDT) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 53B9C3A6AFC for ; Wed, 13 Oct 2010 07:39:55 -0700 (PDT) Received: by yxk30 with SMTP id 30so55513yxk.31 for ; Wed, 13 Oct 2010 07:41:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding :x-mailer:from:subject:date:to; bh=IEce9Oi+7WNFz6BxWD7DkZvkkJn2/6WJ2p/9ILc8+ao=; b=TzTWmYPiuo91EmFnFzAX7qX1kqTlP8/xhb2de6B7OppXfT9I79qB9INkbe3PDTBEkS YhKBygCmx3k5tjKe+2vYpUtTgeSPW0qnI2wtHrVhcoTBlcamBthqSqiU0uBKdF5l32cr T/iDsNghzUlNynkDU0oPaV9eDudEJS7Vkem8Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:x-mailer:from:subject:date:to; b=KPDRdbDlHexb80cEDZVG5quy/eg8Ku9NxXiInNr1xYVNsVn21PD65ORa7MirVP6ngP GeebncvlCj5sCWkp1u+O42/f8yCsGtfMXM9wigy3nHdlRcdSl+hG3OZyefSTgHddHC/i AsmG1CAhHiTNtOOCtfaOFvCF8rjV+8vf/XE9A= Received: by 10.151.112.3 with SMTP id p3mr1246416ybm.147.1286980871258; Wed, 13 Oct 2010 07:41:11 -0700 (PDT) Received: from [10.128.112.89] (mobile-166-137-136-251.mycingular.net [166.137.136.251]) by mx.google.com with ESMTPS id q34sm8116920yba.22.2010.10.13.07.41.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 13 Oct 2010 07:41:10 -0700 (PDT) References: <4CB5B9B5.6040501@dsauder.com> In-Reply-To: <4CB5B9B5.6040501@dsauder.com> Mime-Version: 1.0 (iPhone Mail 8B117) Content-Type: multipart/alternative; boundary=Apple-Mail-1--563978002 Message-Id: <3C056D0C-1017-4D83-876B-E158AC900622@gmail.com> Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (8B117) From: Alan Johnston Date: Wed, 13 Oct 2010 09:40:53 -0500 To: "martini@ietf.org" Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2010 14:40:32 -0000 --Apple-Mail-1--563978002 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I support no change to the document on this issue (I.e. Option 1).=20 - Alan - >=20 > On 2010-10-10 20:10, Bernard Aboba wrote: >>=20 >> There is one outstanding issue on the GIN document, which relates to SSP s= upport for public GRUUs. We would now like to have a consensus call of the W= G on this point.=20 >>=20 >> The consensus call will last until October 17, 2010. Please respond to t= his email indicating whether you wish to change the current text in the docu= ment, and if so, how. Choices include:=20 >>=20 >> (1) No change (public GRUU support remains optional).=20 >>=20 >> (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism d= escribed in this section." >>=20 >> (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism d= escribed in this section, unless the SSP has other means of providing global= ly routable contact URIs." >>=20 >>=20 >>=20 >> _______________________________________________ >> martini mailing list >> martini@ietf.org >> https://www.ietf.org/mailman/listinfo/martini >=20 > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini --Apple-Mail-1--563978002 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=utf-8
I support no change to the document on this issue (I.e. Option 1). 

- Alan -


On 2010-10-10 20:10, Bernard Aboba wrote:
There is one outstanding issue on the GIN document, which relates to SSP support for public GRUUs.  We would now like to have a consensus call of the WG on this point.

The consensus call will last until October 17, 2010.  Please respond to this email indicating whether you wish to change the current text in the document, and if so, how.  Choices include:

(1)  No change (public GRUU support remains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."



_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini
_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini
--Apple-Mail-1--563978002-- From brian.lindsay@genband.com Thu Oct 14 20:28:52 2010 Return-Path: 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 0676F3A6A79 for ; Thu, 14 Oct 2010 20:28:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.481 X-Spam-Level: X-Spam-Status: No, score=-6.481 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 L8F77BcvIt1X for ; Thu, 14 Oct 2010 20:28:51 -0700 (PDT) Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by core3.amsl.com (Postfix) with ESMTP id 863743A6A11 for ; Thu, 14 Oct 2010 20:28:50 -0700 (PDT) Received: from source ([63.149.188.88]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKTLfKwpUKJaQMIJ14xihEXZlTbZN3v9fl@postini.com; Thu, 14 Oct 2010 20:30:11 PDT Received: from owa.genband.com ([172.16.21.97]) by mail.genband.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 14 Oct 2010 22:28:47 -0500 Received: from GBPLMAIL02.genband.com ([fe80::9455:4039:582f:aee8]) by GBEX01.genband.com ([fe80::5918:c932:6f1f:2053%14]) with mapi id 14.01.0218.012; Thu, 14 Oct 2010 22:28:47 -0500 From: Brian Lindsay To: Bernard Aboba , "martini@ietf.org" Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: AQHLaOEpHT+mo6ju3U6UJaRdVW54IJNBX58g Date: Fri, 15 Oct 2010 03:28:47 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [1.220.1.186] Content-Type: multipart/alternative; boundary="_000_F1A0ED6425368141998E077AC43334E4276DE4CDgbplmail02genba_" MIME-Version: 1.0 X-OriginalArrivalTime: 15 Oct 2010 03:28:47.0749 (UTC) FILETIME=[141B0B50:01CB6C19] X-TM-AS-Product-Ver: SMEX-8.0.0.4160-6.500.1024-17704.004 X-TM-AS-Result: No--32.122200-5.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2010 03:28:52 -0000 --_000_F1A0ED6425368141998E077AC43334E4276DE4CDgbplmail02genba_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, My preference is (1). Thanks Brian ---------------------------------- Brian Lindsay Sr. Architect, System Architecture GENBAND +1.613.763.3459 From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf = Of Bernard Aboba Sent: Sunday, October 10, 2010 9:11 PM To: martini@ietf.org Subject: [martini] Consensus call on Public GRUU language There is one outstanding issue on the GIN document, which relates to SSP su= pport for public GRUUs. We would now like to have a consensus call of the = WG on this point. The consensus call will last until October 17, 2010. Please respond to thi= s email indicating whether you wish to change the current text in the docum= ent, and if so, how. Choices include: (1) No change (public GRUU support remains optional). (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism de= scribed in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism de= scribed in this section, unless the SSP has other means of providing global= ly routable contact URIs." --_000_F1A0ED6425368141998E077AC43334E4276DE4CDgbplmail02genba_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

    My preference is (1).

 

    Thanks

      Brian

 

----------------------------------

Brian Lindsay

Sr. Architect, System Architecture

GENBAND

+1.613.763.3459

 

From: martini-= bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of Bernard Aboba
Sent: Sunday, October 10, 2010 9:11 PM
To: martini@ietf.org
Subject: [martini] Consensus call on Public GRUU language=

 

There is one outstan= ding issue on the GIN document, which relates to SSP support for public GRU= Us.  We would now like to have a consensus call of the WG on this point.

The consensus call will last until October 17, 2010.  Please respond t= o this email indicating whether you wish to change the current text in the = document, and if so, how.  Choices include:

(1)  No change (public GRUU support remains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU mechani= sm described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public GR= UU mechanism described in this section, unless the SSP has other means of p= roviding globally routable contact URIs."

--_000_F1A0ED6425368141998E077AC43334E4276DE4CDgbplmail02genba_-- From martien.huysmans@ericsson.com Fri Oct 15 05:45:45 2010 Return-Path: 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 89F453A6974 for ; Fri, 15 Oct 2010 05:45:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.213 X-Spam-Level: X-Spam-Status: No, score=-5.213 tagged_above=-999 required=5 tests=[AWL=1.385, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 CeEjpGGDFmZo for ; Fri, 15 Oct 2010 05:45:44 -0700 (PDT) Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 157E63A68E9 for ; Fri, 15 Oct 2010 05:45:43 -0700 (PDT) X-AuditID: c1b4fb39-b7bbbae000007e67-47-4cb84d48f4c5 Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id EC.70.32359.84D48BC4; Fri, 15 Oct 2010 14:47:04 +0200 (CEST) Received: from ESESSCMS0365.eemea.ericsson.se ([169.254.1.32]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Fri, 15 Oct 2010 14:47:04 +0200 From: Martien Huysmans To: "martini@ietf.org" Date: Fri, 15 Oct 2010 14:47:03 +0200 Thread-Topic: [martini] Consensus call on Public GRUU language Thread-Index: Acto4SoHpTotrZRjQdaFVEePfREqHgDhbqMw Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_B1771F0F1F97A8478E2F449EA19CC7C5DA45BDFDESESSCMS0365eem_" MIME-Version: 1.0 X-Brightmail-Tracker: AAAAAA== Subject: Re: [martini] Consensus call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2010 12:45:45 -0000 --_000_B1771F0F1F97A8478E2F449EA19CC7C5DA45BDFDESESSCMS0365eem_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable My preference is (1). Regards Martien ________________________________ From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf = Of Bernard Aboba Sent: Monday, October 11, 2010 3:11 AM To: martini@ietf.org Subject: [martini] Consensus call on Public GRUU language There is one outstanding issue on the GIN document, which relates to SSP su= pport for public GRUUs. We would now like to have a consensus call of the = WG on this point. The consensus call will last until October 17, 2010. Please respond to thi= s email indicating whether you wish to change the current text in the docum= ent, and if so, how. Choices include: (1) No change (public GRUU support remains optional). (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism de= scribed in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism de= scribed in this section, unless the SSP has other means of providing global= ly routable contact URIs." --_000_B1771F0F1F97A8478E2F449EA19CC7C5DA45BDFDESESSCMS0365eem_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

My preference = is (1).

 

Regards Martie= n

 

From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf Of Bernard Aboba
Sent: Monday, October 11, 20= 10 3:11 AM
To: martini@ietf.org
Subject: [martini] Consensus= call on Public GRUU language

 

There is one outstanding issu= e on the GIN document, which relates to SSP support for public GRUUs.  We w= ould now like to have a consensus call of the WG on this point.

The consensus call will last until October 17, 2010.  Please respond t= o this email indicating whether you wish to change the current text in the document, and if so, how.  Choices include:

(1)  No change (public GRUU support remains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU mechani= sm described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public GR= UU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."

--_000_B1771F0F1F97A8478E2F449EA19CC7C5DA45BDFDESESSCMS0365eem_-- From bernard_aboba@hotmail.com Mon Oct 18 17:20:17 2010 Return-Path: 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 AE8913A6AC4 for ; Mon, 18 Oct 2010 17:20:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.921 X-Spam-Level: X-Spam-Status: No, score=-100.921 tagged_above=-999 required=5 tests=[AWL=-0.182, BAYES_20=-0.74, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 ki97wgpugw4Z for ; Mon, 18 Oct 2010 17:20:16 -0700 (PDT) Received: from blu0-omc2-s28.blu0.hotmail.com (blu0-omc2-s28.blu0.hotmail.com [65.55.111.103]) by core3.amsl.com (Postfix) with ESMTP id 3743F3A6857 for ; Mon, 18 Oct 2010 17:20:16 -0700 (PDT) Received: from BLU104-W29 ([65.55.111.71]) by blu0-omc2-s28.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 18 Oct 2010 17:21:45 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_867743da-1994-4f45-b684-6d72333f7ce0_" X-Originating-IP: [131.107.0.87] From: Bernard Aboba To: Date: Mon, 18 Oct 2010 17:21:44 -0700 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 19 Oct 2010 00:21:45.0802 (UTC) FILETIME=[9CF4D2A0:01CB6F23] Subject: [martini] Summary of Consensus Call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 00:20:17 -0000 --_867743da-1994-4f45-b684-6d72333f7ce0_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The MARTINI WG Consensus Call on Public GRUU language has now concluded: http://www.ietf.org/mail-archive/web/martini/current/msg02017.html =20 Three options were presented to the WG: =20 (1) No change (public GRUU support remains optional).=20 (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism de= scribed in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism de= scribed in this section=2C unless the SSP has other means of providing glob= ally routable contact URIs." Seventeen individuals responded to the consensus call. Of these=2C 13 indi= cated a preference for Option 1.=20 =20 Four individuals indicated a preference for Option 2=3B seven individuals i= ndicated Option 2 as a second choice or "OK" option.=20 =20 Five individuals indicated Option 3 as their preferred option.=20 =20 Given that the most popular choice was for public GRUU support to remain op= tional (the original language prior to IETF 78)=2C=20 it does not appear that there is WG consensus to change the text.=20 =20 =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =20 Individual Option 1 Option 2 Option 3 URL Andrew Allen 1 http://www.ietf.org/mail-archive/web/martini/current/msg02018.html Keith Drage 1 http://www.ietf.org/mail-archive/web/martini/current/msg02019.html Richard Shockey 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02020.html Hadriel Kaplan 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02021.html Martin Dolly 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02022.html Paul Kyzivat 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02023.html Adam Roach 2 1 http://www.ietf.org/mail-archive/web/martini/current/msg02024.html John Elwell 1 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02025.html David Hancock 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02026.html Jack Burton 1 http://www.ietf.org/mail-archive/web/martini/current/msg02027.html Bernard Aboba 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02028.html Shida Schubert 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02029.html Shaun Barrat 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02030.html Doug Sauder 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02031.html Alan Johnston 1 http://www.ietf.org/mail-archive/web/martini/current/msg02032.html Brian Lindsay 1 http://www.ietf.org/mail-archive/web/martini/current/msg02033.html Martien Huysmans 1 http://www.ietf.org/mail-archive/web/martini/current/msg02034.html Total Preferred 13 4 5 Total Second choice 7 = --_867743da-1994-4f45-b684-6d72333f7ce0_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The MARTINI WG Consensus Call on Public GRUU language has now concluded: http://www.ietf.org/mail-archive/web/martini/current/msg02017.html<= BR>  =3B
Three options were presented to the WG:
 =3B
(1) =3B No change (public GRUU support remains optional).

(2) C= hange the MAY to: "The SSP SHOULD support the public GRUU mechanism describ= ed in this section."

(3) =3B Change the MAY to: =3B "The SSP= MUST support the public GRUU mechanism described in this section=2C unless= the SSP has other means of providing globally routable contact URIs."
<= BR>Seventeen individuals responded to the consensus call. =3B Of these= =2C 13 indicated a preference for Option 1.
 =3B
Four individuals indicated a preference for Option 2=3B seven individuals i= ndicated Option 2 as a second choice or "OK" option.
 =3B
Five individuals indicated Option 3 as their preferred option.
 =3B
Given that the most popular choice was for public GRUU support to remain op= tional (the original language prior to IETF 78)=2C
it does not appear that there is WG consensus to change the text.
 =3B
 =3B
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 =3B
 =3B
Individual Option 1= Option 2= Option 3 URL
Andrew Allen 1 http://www.ietf.org/mail-archive/web/martini/current/msg02018.= html
Keith Drage 1 http://www.ietf.org/mail-archive/web/martini/current/msg02019.= html
Richard Shockey 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02020.= html
Hadriel Kaplan 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02021.= html
Martin Dolly 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02022.= html
Paul Kyzivat 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02023.= html
Adam Roach 2 1 http://www.ietf.org/mail-archive/web/martini/current/msg02024.= html
John Elwell 1 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02025.= html
David Hancock 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02026.= html
Jack Burton 1 http://www.ietf.org/mail-archive/web/martini/current/msg02027.= html
Bernard Aboba 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02028.= html
Shida Schubert 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02029.= html
Shaun Barrat 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02030.= html
Doug Sauder 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02031.= html
Alan Johnston 1 http://www.ietf.org/mail-archive/web/martini/current/msg02032.= html
Brian Lindsay 1 http://www.ietf.org/mail-archive/web/martini/current/msg02033.= html
Martien Huysmans 1 http://www.ietf.org/mail-archive/web/martini/current/msg02034.= html
Total Preferred 13 4 5 =
Total Second choice 7

= --_867743da-1994-4f45-b684-6d72333f7ce0_-- From adam@nostrum.com Mon Oct 18 18:23:09 2010 Return-Path: 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 51B003A6BF8 for ; Mon, 18 Oct 2010 18:23:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.383 X-Spam-Level: X-Spam-Status: No, score=-102.383 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 Oayjhy5tIP5E for ; Mon, 18 Oct 2010 18:23:08 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 3C9B23A6C08 for ; Mon, 18 Oct 2010 18:22:49 -0700 (PDT) Received: from hydra-3.local (ppp-70-242-117-72.dsl.rcsntx.swbell.net [70.242.117.72]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o9J1OFt1097101 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 18 Oct 2010 20:24:15 -0500 (CDT) (envelope-from adam@nostrum.com) Message-ID: <4CBCF33F.4040105@nostrum.com> Date: Mon, 18 Oct 2010 20:24:15 -0500 From: Adam Roach User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Bernard Aboba References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------080302090806010701020509" Received-SPF: pass (nostrum.com: 70.242.117.72 is authenticated by a trusted mechanism) Cc: martini@ietf.org Subject: Re: [martini] Summary of Consensus Call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 01:23:09 -0000 This is a multi-part message in MIME format. --------------080302090806010701020509 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit The new -10 version of the draft reflects the result of this consensus call. I believe that this version is ready to send to the IESG for publication. New version: http://www.ietf.org/id/draft-ietf-martini-gin-10.txt Diffs: http://tools.ietf.org/rfcdiff?url2=draft-ietf-martini-gin-10.txt /a On 10/18/10 19:21, Oct 18, Bernard Aboba wrote: > The MARTINI WG Consensus Call on Public GRUU language has now concluded: > http://www.ietf.org/mail-archive/web/martini/current/msg02017.html > > Three options were presented to the WG: > > (1) No change (public GRUU support remains optional). > > (2) Change the MAY to: "The SSP SHOULD support the public GRUU > mechanism described in this section." > > (3) Change the MAY to: "The SSP MUST support the public GRUU > mechanism described in this section, unless the SSP has other means of > providing globally routable contact URIs." > > Seventeen individuals responded to the consensus call. Of these, 13 > indicated a preference for Option 1. > > Four individuals indicated a preference for Option 2; seven > individuals indicated Option 2 as a second choice or "OK" option. > > Five individuals indicated Option 3 as their preferred option. > > Given that the most popular choice was for public GRUU support to > remain optional (the original language prior to IETF 78), > it does not appear that there is WG consensus to change the text. > > > =============================================== > > > *Individual* *Option 1* *Option 2* *Option 3* *URL* > Andrew Allen > > 1 http://www.ietf.org/mail-archive/web/martini/current/msg02018.html > Keith Drage > > 1 http://www.ietf.org/mail-archive/web/martini/current/msg02019.html > Richard Shockey 1 2 > http://www.ietf.org/mail-archive/web/martini/current/msg02020.html > Hadriel Kaplan 1 1 > http://www.ietf.org/mail-archive/web/martini/current/msg02021.html > Martin Dolly 1 1 > http://www.ietf.org/mail-archive/web/martini/current/msg02022.html > Paul Kyzivat > 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02023.html > Adam Roach > 2 1 http://www.ietf.org/mail-archive/web/martini/current/msg02024.html > John Elwell 1 1 1 > http://www.ietf.org/mail-archive/web/martini/current/msg02025.html > David Hancock 1 2 > http://www.ietf.org/mail-archive/web/martini/current/msg02026.html > Jack Burton 1 > > http://www.ietf.org/mail-archive/web/martini/current/msg02027.html > Bernard Aboba 1 2 > http://www.ietf.org/mail-archive/web/martini/current/msg02028.html > Shida Schubert 1 2 > http://www.ietf.org/mail-archive/web/martini/current/msg02029.html > Shaun Barrat 1 2 > http://www.ietf.org/mail-archive/web/martini/current/msg02030.html > Doug Sauder 1 2 > http://www.ietf.org/mail-archive/web/martini/current/msg02031.html > Alan Johnston 1 > > http://www.ietf.org/mail-archive/web/martini/current/msg02032.html > Brian Lindsay 1 > > http://www.ietf.org/mail-archive/web/martini/current/msg02033.html > Martien Huysmans 1 > > http://www.ietf.org/mail-archive/web/martini/current/msg02034.html > > > > > > Total Preferred *13* *4* *5* ** > Total Second choice *7* > > > > > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini --------------080302090806010701020509 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit The new -10 version of the draft reflects the result of this consensus call. I believe that this version is ready to send to the IESG for publication.

New version:
    http://www.ietf.org/id/draft-ietf-martini-gin-10.txt

Diffs:
    http://tools.ietf.org/rfcdiff?url2=draft-ietf-martini-gin-10.txt

/a

On 10/18/10 19:21, Oct 18, Bernard Aboba wrote:
The MARTINI WG Consensus Call on Public GRUU language has now concluded:
http://www.ietf.org/mail-archive/web/martini/current/msg02017.html
 
Three options were presented to the WG:
 
(1)  No change (public GRUU support remains optional).

(2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism described in this section."

(3)  Change the MAY to:  "The SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs."

Seventeen individuals responded to the consensus call.  Of these, 13 indicated a preference for Option 1.
 
Four individuals indicated a preference for Option 2; seven individuals indicated Option 2 as a second choice or "OK" option.
 
Five individuals indicated Option 3 as their preferred option.
 
Given that the most popular choice was for public GRUU support to remain optional (the original language prior to IETF 78),
it does not appear that there is WG consensus to change the text.
 
 
===============================================
 
 
Individual Option 1 Option 2 Option 3 URL
Andrew Allen

1 http://www.ietf.org/mail-archive/web/martini/current/msg02018.html
Keith Drage

1 http://www.ietf.org/mail-archive/web/martini/current/msg02019.html
Richard Shockey 1 2
http://www.ietf.org/mail-archive/web/martini/current/msg02020.html
Hadriel Kaplan 1 1
http://www.ietf.org/mail-archive/web/martini/current/msg02021.html
Martin Dolly 1 1
http://www.ietf.org/mail-archive/web/martini/current/msg02022.html
Paul Kyzivat
1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02023.html
Adam Roach
2 1 http://www.ietf.org/mail-archive/web/martini/current/msg02024.html
John Elwell 1 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02025.html
David Hancock 1 2
http://www.ietf.org/mail-archive/web/martini/current/msg02026.html
Jack Burton 1

http://www.ietf.org/mail-archive/web/martini/current/msg02027.html
Bernard Aboba 1 2
http://www.ietf.org/mail-archive/web/martini/current/msg02028.html
Shida Schubert 1 2
http://www.ietf.org/mail-archive/web/martini/current/msg02029.html
Shaun Barrat 1 2
http://www.ietf.org/mail-archive/web/martini/current/msg02030.html
Doug Sauder 1 2
http://www.ietf.org/mail-archive/web/martini/current/msg02031.html
Alan Johnston 1

http://www.ietf.org/mail-archive/web/martini/current/msg02032.html
Brian Lindsay 1

http://www.ietf.org/mail-archive/web/martini/current/msg02033.html
Martien Huysmans 1

http://www.ietf.org/mail-archive/web/martini/current/msg02034.html





Total Preferred 13 4 5
Total Second choice 7 



_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini

--------------080302090806010701020509-- From root@core3.amsl.com Mon Oct 18 18:30:16 2010 Return-Path: X-Original-To: martini@ietf.org Delivered-To: martini@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 174E23A6BE8; Mon, 18 Oct 2010 18:30:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20101019013010.174E23A6BE8@core3.amsl.com> Date: Mon, 18 Oct 2010 18:30:02 -0700 (PDT) Cc: martini@ietf.org Subject: [martini] I-D Action:draft-ietf-martini-gin-10.txt X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 01:30:17 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiple AoR reachabiliTy InformatioN Indication Working Group of the IETF. Title : Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP) Author(s) : A. Roach Filename : draft-ietf-martini-gin-10.txt Pages : 32 Date : 2010-10-18 This document defines a mechanism by which a SIP server acting as a traditional Private Branch Exchange (SIP-PBX) can register with a SIP Service Provider (SSP) to receive phone calls for UAs designated by phone numbers. In order to function properly, this mechanism relies on the fact that the phone numbers are fully qualified and globally unique. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-martini-gin-10.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-martini-gin-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-10-18181842.I-D@ietf.org> --NextPart-- From bernard_aboba@hotmail.com Mon Oct 18 18:32:27 2010 Return-Path: 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 9FB8E3A6A70 for ; Mon, 18 Oct 2010 18:32:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.85 X-Spam-Level: X-Spam-Status: No, score=-101.85 tagged_above=-999 required=5 tests=[AWL=0.748, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 MoLtqAJaR-k1 for ; Mon, 18 Oct 2010 18:32:12 -0700 (PDT) Received: from blu0-omc2-s5.blu0.hotmail.com (blu0-omc2-s5.blu0.hotmail.com [65.55.111.80]) by core3.amsl.com (Postfix) with ESMTP id B88D93A6BF8 for ; Mon, 18 Oct 2010 18:32:07 -0700 (PDT) Received: from BLU104-W10 ([65.55.111.73]) by blu0-omc2-s5.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 18 Oct 2010 18:33:37 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_46e13102-94d9-40f9-a07b-bbca076a2c04_" X-Originating-IP: [131.107.0.72] From: Bernard Aboba To: Date: Mon, 18 Oct 2010 18:33:35 -0700 Importance: Normal In-Reply-To: <4CBCF33F.4040105@nostrum.com> References: , <4CBCF33F.4040105@nostrum.com> MIME-Version: 1.0 X-OriginalArrivalTime: 19 Oct 2010 01:33:37.0317 (UTC) FILETIME=[A6D1CD50:01CB6F2D] Cc: martini@ietf.org Subject: Re: [martini] Summary of Consensus Call on Public GRUU language X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 01:32:27 -0000 --_46e13102-94d9-40f9-a07b-bbca076a2c04_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks. I will send a request to the IESG to consider publication of -10 a= s a Proposed Standard.=20 =20 Date: Mon=2C 18 Oct 2010 20:24:15 -0500 From: adam@nostrum.com To: bernard_aboba@hotmail.com CC: martini@ietf.org Subject: Re: [martini] Summary of Consensus Call on Public GRUU language The new -10 version of the draft reflects the result of this consensus call= . I believe that this version is ready to send to the IESG for publication. New version: http://www.ietf.org/id/draft-ietf-martini-gin-10.txt Diffs: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-martini-gin-10.txt /a On 10/18/10 19:21=2C Oct 18=2C Bernard Aboba wrote:=20 The MARTINI WG Consensus Call on Public GRUU language has now concluded: http://www.ietf.org/mail-archive/web/martini/current/msg02017.html =20 Three options were presented to the WG: =20 (1) No change (public GRUU support remains optional).=20 (2) Change the MAY to: "The SSP SHOULD support the public GRUU mechanism de= scribed in this section." (3) Change the MAY to: "The SSP MUST support the public GRUU mechanism de= scribed in this section=2C unless the SSP has other means of providing glob= ally routable contact URIs." Seventeen individuals responded to the consensus call. Of these=2C 13 indi= cated a preference for Option 1.=20 =20 Four individuals indicated a preference for Option 2=3B seven individuals i= ndicated Option 2 as a second choice or "OK" option.=20 =20 Five individuals indicated Option 3 as their preferred option.=20 =20 Given that the most popular choice was for public GRUU support to remain op= tional (the original language prior to IETF 78)=2C=20 it does not appear that there is WG consensus to change the text.=20 =20 =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =20 Individual Option 1 Option 2 Option 3 URL Andrew Allen 1 http://www.ietf.org/mail-archive/web/martini/current/msg02018.html Keith Drage 1 http://www.ietf.org/mail-archive/web/martini/current/msg02019.html Richard Shockey 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02020.html Hadriel Kaplan 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02021.html Martin Dolly 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02022.html Paul Kyzivat 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02023.html Adam Roach 2 1 http://www.ietf.org/mail-archive/web/martini/current/msg02024.html John Elwell 1 1 1 http://www.ietf.org/mail-archive/web/martini/current/msg02025.html David Hancock 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02026.html Jack Burton 1 http://www.ietf.org/mail-archive/web/martini/current/msg02027.html Bernard Aboba 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02028.html Shida Schubert 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02029.html Shaun Barrat 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02030.html Doug Sauder 1 2 http://www.ietf.org/mail-archive/web/martini/current/msg02031.html Alan Johnston 1 http://www.ietf.org/mail-archive/web/martini/current/msg02032.html Brian Lindsay 1 http://www.ietf.org/mail-archive/web/martini/current/msg02033.html Martien Huysmans 1 http://www.ietf.org/mail-archive/web/martini/current/msg02034.html Total Preferred 13 4 5 Total Second choice 7 _______________________________________________ martini mailing list martini@ietf.org https://www.ietf.org/mailman/listinfo/martini = --_46e13102-94d9-40f9-a07b-bbca076a2c04_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks. =3B I will send =3Ba request to the IESG to consider = =3Bpublication of -10 as a Proposed Standard.
 =3B
Date: Mon=2C 18 Oct 2010 20:24:15 -0500
From: adam@nostrum.com
To: be= rnard_aboba@hotmail.com
CC: martini@ietf.org
Subject: Re: [martini] S= ummary of Consensus Call on Public GRUU language

The new -10 version o= f the draft reflects the result of this consensus call. I believe that this= version is ready to send to the IESG for publication.

New version:<= BR> =3B =3B =3B http://w= ww.ietf.org/id/draft-ietf-martini-gin-10.txt

Diffs:
 =3B&= nbsp=3B =3B http:/= /tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-martini-gin-10.txt

/a<= BR>
On 10/18/10 19:21=2C Oct 18=2C Bernard Aboba wrote:=20
The MARTINI WG Consensus Call on Public GRUU language has now concluded:http://www.ietf.org/mail-archive/web/martini/current/m= sg02017.html
 =3B
Three options were presented to the WG:
=  =3B
(1) =3B No change (public GRUU support remains optional). <= BR>
(2) Change the MAY to: "The SSP SHOULD support the public GRUU mecha= nism described in this section."

(3) =3B Change the MAY to: = =3B "The SSP MUST support the public GRUU mechanism described in this secti= on=2C unless the SSP has other means of providing globally routable contact= URIs."

Seventeen individuals responded to the consensus call. = =3B Of these=2C 13 indicated a preference for Option 1.
 =3B
Fou= r individuals indicated a preference for Option 2=3B seven individuals indi= cated Option 2 as a second choice or "OK" option.
 =3B
Five indi= viduals indicated Option 3 as their preferred option.
 =3B
Given= that the most popular choice was for public GRUU support to remain optiona= l (the original language prior to IETF 78)=2C
it does not appear that t= here is WG consensus to change the text.
 =3B
 =3B
=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 =3B =3B
Indivi= dual Option 1 Option 2 Option 3 URL
Andrew Allen

1 http://www.ietf.org/mail-archi= ve/web/martini/current/msg02018.html
Keith Drage

1 http://www.ietf.org/mail-archi= ve/web/martini/current/msg02019.html
Richard Shockey 1 2
http://www.ietf.org/mail-archi= ve/web/martini/current/msg02020.html
Hadriel Kaplan 1 1
http://www.ietf.org/mail-archi= ve/web/martini/current/msg02021.html
Martin Dolly 1 1
http://www.ietf.org/mail-archi= ve/web/martini/current/msg02022.html
Paul Kyzivat
1 1 http://www.ietf.org/mail-archi= ve/web/martini/current/msg02023.html
Adam Roach
2 1 http://www.ietf.org/mail-archi= ve/web/martini/current/msg02024.html
John Elwell 1 1 1 http://www.ietf.org/mail-archi= ve/web/martini/current/msg02025.html
David Hancock 1 2
http://www.ietf.org/mail-archi= ve/web/martini/current/msg02026.html
Jack Burton 1

http://www.ietf.org/mail-archi= ve/web/martini/current/msg02027.html
Bernard Aboba 1 2
http://www.ietf.org/mail-archi= ve/web/martini/current/msg02028.html
Shida Schubert 1 2
http://www.ietf.org/mail-archi= ve/web/martini/current/msg02029.html
Shaun Barrat 1 2
http://www.ietf.org/mail-archi= ve/web/martini/current/msg02030.html
Doug Sauder 1 2
http://www.ietf.org/mail-archi= ve/web/martini/current/msg02031.html
Alan Johnston 1

http://www.ietf.org/mail-archi= ve/web/martini/current/msg02032.html
Brian Lindsay 1

http://www.ietf.org/mail-archi= ve/web/martini/current/msg02033.html
Martien Huysmans 1

http://www.ietf.org/mail-archi= ve/web/martini/current/msg02034.html


Total Preferred 13 4 5
Total Second choice 7

<= BR>

_______________________________________________
martini mailing list
mar=
tini@ietf.org
https://www.ietf.org/mailman/listinfo/marti=
ni

= --_46e13102-94d9-40f9-a07b-bbca076a2c04_-- From bernarda@microsoft.com Tue Oct 26 04:50:21 2010 Return-Path: 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 A73293A67DB for ; Tue, 26 Oct 2010 04:50:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.538 X-Spam-Level: X-Spam-Status: No, score=-10.538 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] 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 i-BYfCKvOL1y for ; Tue, 26 Oct 2010 04:50:20 -0700 (PDT) Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id A5ACE3A67D7 for ; Tue, 26 Oct 2010 04:50:20 -0700 (PDT) Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 26 Oct 2010 04:52:07 -0700 Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server (TLS) id 14.1.255.3; Tue, 26 Oct 2010 04:52:07 -0700 Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.233]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Tue, 26 Oct 2010 04:52:07 -0700 From: Bernard Aboba To: "'martini@ietf.org'" Thread-Topic: Call for Agenda Items for IETF 79 Thread-Index: Act1BD6iiQqJG+veRMig92RFA021Nw== Date: Tue, 26 Oct 2010 11:52:20 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_D9FB39B69BD6F846B37BE8645782A7E8062336TK5EX14MBXW653win_" MIME-Version: 1.0 Subject: [martini] Call for Agenda Items for IETF 79 X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2010 11:50:21 -0000 --_000_D9FB39B69BD6F846B37BE8645782A7E8062336TK5EX14MBXW653win_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The MARTINI WG has two sessions scheduled at IETF 79: * A one hour session from 1510 - 1610 on Monday, November 8, 2010 * A two and a half hour session from 0900 - 1130 on Thursday, Novem= ber 11, 2010 We would now like to solicit agenda items for these sessions. If you have an agenda item, please send it to myself or Spencer. --_000_D9FB39B69BD6F846B37BE8645782A7E8062336TK5EX14MBXW653win_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The MARTINI WG has two sessions scheduled at IETF 79:<= o:p>

 

·      =    A one hour session from 1510 - 1610 on Monda= y, November 8, 2010

·      =    A two and a half hour session from 0900 - 11= 30 on Thursday, November 11, 2010

 

We would now like to solicit agenda items for these sessions.

 

If you have an agenda item, please send it to myself o= r Spencer.

--_000_D9FB39B69BD6F846B37BE8645782A7E8062336TK5EX14MBXW653win_-- From bernard_aboba@hotmail.com Tue Oct 26 04:50:51 2010 Return-Path: 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 6329A3A6941 for ; Tue, 26 Oct 2010 04:50:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.876 X-Spam-Level: X-Spam-Status: No, score=-101.876 tagged_above=-999 required=5 tests=[AWL=0.722, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 tpTVSHkqXz-X for ; Tue, 26 Oct 2010 04:50:50 -0700 (PDT) Received: from blu0-omc2-s37.blu0.hotmail.com (blu0-omc2-s37.blu0.hotmail.com [65.55.111.112]) by core3.amsl.com (Postfix) with ESMTP id 6CD103A682E for ; Tue, 26 Oct 2010 04:50:50 -0700 (PDT) Received: from BLU104-DS16 ([65.55.111.72]) by blu0-omc2-s37.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 26 Oct 2010 04:52:37 -0700 X-Originating-IP: [24.19.29.20] X-Originating-Email: [bernard_aboba@hotmail.com] Message-ID: From: Bernard Aboba To: Date: Tue, 26 Oct 2010 04:52:50 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0200_01CB74C9.A4D1EA20" X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: Act1BD6iiQqJG+veRMig92RFA021NwAAAmVg X-OriginalArrivalTime: 26 Oct 2010 11:52:37.0221 (UTC) FILETIME=[48D1A950:01CB7504] Subject: [martini] Call for Agenda Items for IETF 79 X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2010 11:50:51 -0000 ------=_NextPart_000_0200_01CB74C9.A4D1EA20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit The MARTINI WG has two sessions scheduled at IETF 79: . A one hour session from 1510 - 1610 on Monday, November 8, 2010 . A two and a half hour session from 0900 - 1130 on Thursday, November 11, 2010 We would now like to solicit agenda items for these sessions. If you have an agenda item, please send it to myself or Spencer. ------=_NextPart_000_0200_01CB74C9.A4D1EA20 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The MARTINI WG has two sessions scheduled at IETF = 79:

 

·         A one hour session from 1510 - 1610 on = Monday, November 8, 2010

·         A two and a half hour session from 0900 - = 1130 on Thursday, November 11, 2010

 

We would now like to solicit agenda items for these sessions.

 

If you have an agenda item, please send it to = myself or Spencer.

------=_NextPart_000_0200_01CB74C9.A4D1EA20-- From HKaplan@acmepacket.com Tue Oct 26 06:44:49 2010 Return-Path: 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 507A23A68EC for ; Tue, 26 Oct 2010 06:44:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.472 X-Spam-Level: X-Spam-Status: No, score=-2.472 tagged_above=-999 required=5 tests=[AWL=0.126, 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 CPbcTP8XKJqw for ; Tue, 26 Oct 2010 06:44:47 -0700 (PDT) Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 723903A68E6 for ; Tue, 26 Oct 2010 06:44:46 -0700 (PDT) Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 26 Oct 2010 09:46:33 -0400 Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 26 Oct 2010 09:46:31 -0400 From: Hadriel Kaplan To: Bernard Aboba Date: Tue, 26 Oct 2010 09:46:25 -0400 Thread-Topic: [martini] Call for Agenda Items for IETF 79 Thread-Index: Act1FDIDdUETmsLjTZGi0UJXsymQjA== Message-ID: <730ECD00-6D22-45E4-B39A-F843A1634684@acmepacket.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_730ECD006D2245E4B39AF843A1634684acmepacketcom_" MIME-Version: 1.0 Cc: "martini@ietf.org" Subject: Re: [martini] Call for Agenda Items for IETF 79 X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2010 13:44:49 -0000 --_000_730ECD006D2245E4B39AF843A1634684acmepacketcom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I'd like to present updated versions of Olive and Vermouth. I submitted the updated drafts before the 5pm PDT deadline yesterday, but d= id not click on the confirmation email link before the deadline, and appare= ntly clicking on the email's confirmation also has to be done before the de= adline because the tool won't let me confirm them now. So I'm trying to find a public website to post them on. Any suggestions? -hadriel On Oct 26, 2010, at 7:52 AM, Bernard Aboba wrote: The MARTINI WG has two sessions scheduled at IETF 79: * A one hour session from 1510 - 1610 on Monday, November 8, 2010 * A two and a half hour session from 0900 - 1130 on Thursday, Novem= ber 11, 2010 We would now like to solicit agenda items for these sessions. If you have an agenda item, please send it to myself or Spencer. --_000_730ECD006D2245E4B39AF843A1634684acmepacketcom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The MARTINI WG has two sessions scheduled at I= ETF 79:
 
=B7      &nbs= p;  A one hour session from 1510 - 1610 on Monday, November 8, 2010
= =B7 A two and a half hour sessio= n from 0900 - 1130 on Thursday, November 11, 2010
 
We would now like to solicit agenda items for these sessions.
 
If you have an agenda item, please send it to mysel= f or Spencer.
<ATT00001..c><= /span>

= --_000_730ECD006D2245E4B39AF843A1634684acmepacketcom_-- From gonzalo.camarillo@ericsson.com Wed Oct 27 09:39:29 2010 Return-Path: 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 864543A6A60 for ; Wed, 27 Oct 2010 09:39:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.481 X-Spam-Level: X-Spam-Status: No, score=-106.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] 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 7lePmSShNmyI for ; Wed, 27 Oct 2010 09:38:54 -0700 (PDT) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id D7D083A6A38 for ; Wed, 27 Oct 2010 09:37:30 -0700 (PDT) X-AuditID: c1b4fb3d-b7b28ae00000135b-60-4cc8556bbbc5 Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 97.D8.04955.B6558CC4; Wed, 27 Oct 2010 18:38:04 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 27 Oct 2010 18:38:03 +0200 Received: from [131.160.126.178] ([131.160.126.178]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 27 Oct 2010 18:38:03 +0200 Message-ID: <4CC8556B.9030706@ericsson.com> Date: Wed, 27 Oct 2010 19:38:03 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: martini@ietf.org X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 27 Oct 2010 16:38:03.0501 (UTC) FILETIME=[534A59D0:01CB75F5] X-Brightmail-Tracker: AAAAAA== Subject: [martini] Comments on draft-ietf-martini-gin X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2010 16:39:30 -0000 Hi, I have received a publication request for the following draft. https://datatracker.ietf.org/doc/draft-ietf-martini-gin/ I have just requested its IETF LC to start. Note that this will be a three-week IETF LC (instead of the typical two-week IETF LC) because of the upcoming face-to-face meeting. I have a few minor comments on the draft. Please, treat them as IETF LC comments. Expand acronyms on their first use (e.g., UA in the Abstract and AOR in the Introduction) The document uses both "registrar" and "SSP registrar". Using a single term would be clearer. Foe example, the following two sentences are parallel but use different terms: Page 7: A registrar that receives a REGISTER request... Page 8: An SSP registrar that receives a REGISTER request... First sentence of Section 7.1.1 The text uses "optional". Do you want to use the RFC 2119 "OPTIONAL" instead? Second paragraph of page 25: s/"Proxy-Require" header/"Proxy-Require" header field/ Cheers, Gonzalo From trac@tools.ietf.org Wed Oct 27 10:55:12 2010 Return-Path: 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 A7F7C3A6828 for ; Wed, 27 Oct 2010 10:55:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.571 X-Spam-Level: X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] 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 Q-4hMnF9gUbK for ; Wed, 27 Oct 2010 10:55:11 -0700 (PDT) Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id C9BA83A6991 for ; Wed, 27 Oct 2010 10:55:11 -0700 (PDT) Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from ) id 1PBAFC-00027N-58; Wed, 27 Oct 2010 10:57:02 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "martini issue tracker" X-Trac-Version: 0.11.7 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.11.7, by Edgewall Software To: Gonzalo.Camarillo@ericsson.com X-Trac-Project: martini Date: Wed, 27 Oct 2010 17:57:02 -0000 X-URL: http://tools.ietf.org/martini/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/63 Message-ID: <072.8ca4ca124b0ddedc02770ecbf0c7c018@tools.ietf.org> X-Trac-Ticket-ID: 63 X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: Gonzalo.Camarillo@ericsson.com, martini@ietf.org X-SA-Exim-Mail-From: trac@tools.ietf.org X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false Cc: martini@ietf.org Subject: [martini] gin #63 (new): AD feedback X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2010 17:55:12 -0000 #63: AD feedback I have a few minor comments on the draft. Please, treat them as IETF LC comments. Expand acronyms on their first use (e.g., UA in the Abstract and AOR in the Introduction) The document uses both "registrar" and "SSP registrar". Using a single term would be clearer. Foe example, the following two sentences are parallel but use different terms: Page 7: A registrar that receives a REGISTER request... Page 8: An SSP registrar that receives a REGISTER request... First sentence of Section 7.1.1 The text uses "optional". Do you want to use the RFC 2119 "OPTIONAL" instead? Second paragraph of page 25: s/"Proxy-Require" header/"Proxy-Require" header field/ -- --------------------------------------------+------------------------------- Reporter: Gonzalo.Camarillo@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: gin | Version: 1.0 Severity: Submitted WG Document | Keywords: --------------------------------------------+------------------------------- Ticket URL: martini From bernard_aboba@hotmail.com Wed Oct 27 11:03:00 2010 Return-Path: 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 AF18B3A6910 for ; Wed, 27 Oct 2010 11:03:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.894 X-Spam-Level: X-Spam-Status: No, score=-101.894 tagged_above=-999 required=5 tests=[AWL=0.704, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 ajWKlm3u64yv for ; Wed, 27 Oct 2010 11:02:59 -0700 (PDT) Received: from blu0-omc2-s17.blu0.hotmail.com (blu0-omc2-s17.blu0.hotmail.com [65.55.111.92]) by core3.amsl.com (Postfix) with ESMTP id 873A33A6828 for ; Wed, 27 Oct 2010 11:02:59 -0700 (PDT) Received: from BLU104-W29 ([65.55.111.73]) by blu0-omc2-s17.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Oct 2010 11:04:48 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_4598ef23-2136-47fb-947d-21ee8f51347d_" X-Originating-IP: [24.19.29.20] From: Bernard Aboba To: Date: Wed, 27 Oct 2010 11:04:48 -0700 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 27 Oct 2010 18:04:48.0862 (UTC) FILETIME=[71ED67E0:01CB7601] Subject: [martini] IETF 79 MARTINI WG Agenda - Take One X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2010 18:03:00 -0000 --_4598ef23-2136-47fb-947d-21ee8f51347d_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MARTINI WG IETF 79 Agenda=20 Chairs: Bernard Aboba Spencer Dawkins Jabber room: martini at jabber.ietf.org (Please join) Monday=2C November 8=2C 2010 15:10 - 16:10 Pearl Room 15:10 - 15:15=2C Preliminaries Note Well Note Takers Jabber scribe Agenda bash Document Status Individual Submissions (50 minutes) =20 15:15 - 15:40=2C Other Logical Identifier Values (OLIVE)=2C Hadriel Kaplan = (25 minutes) http://tools.ietf.org/html/draft-kaplan-martini-with-olive 15:40 =96 16:05=2C MARTINI Event Package for Registration (VERMOUTH)=2C Had= riel Kaplan (25 minutes) http://tools.ietf.org/html/draft-kaplan-martini-vermouth Discussion and Wrap-up (5 minutes) 16:05 =96 16:10=2C Next Steps: WG Chairs & ADs (5 minutes) = --_4598ef23-2136-47fb-947d-21ee8f51347d_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MARTINI WG IETF 79 Agenda

Chairs:
Bernard Aboba <=3Bbernard_ab= oba at hotmail.com>=3B
Spencer Dawkins <=3Bspencer at wonderhamster.= org>=3B

Jabber room: =3B martini at jabber.ietf.org (Please jo= in)

Monday=2C November 8=2C 2010

15:10 - 16:10

Pearl R= oom

15:10 - 15:15=2C Preliminaries

 =3B =3B =3B&n= bsp=3B Note Well
 =3B =3B =3B =3B Note Takers
 = =3B =3B =3B =3B Jabber scribe
 =3B =3B =3B = =3B Agenda bash
 =3B =3B =3B =3B Document Status

= Individual Submissions (50 minutes)
 =3B
15:15 - 15:40=2C Other L= ogical Identifier Values (OLIVE)=2C Hadriel Kaplan (25 minutes)
http://t= ools.ietf.org/html/draft-kaplan-martini-with-olive

15:40 =96 16:05= =2C MARTINI Event Package for Registration (VERMOUTH)=2C Hadriel Kaplan (25= minutes)
http://tools.ietf.org/html/draft-kaplan-martini-vermouth
Discussion and Wrap-up (5 minutes)

16:05 =96 16:10=2C Next Steps:&= nbsp=3B WG Chairs &=3B ADs (5 minutes) = --_4598ef23-2136-47fb-947d-21ee8f51347d_-- From bernard_aboba@hotmail.com Fri Oct 29 10:49:39 2010 Return-Path: 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 217D13A67AD for ; Fri, 29 Oct 2010 10:49:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.695 X-Spam-Level: X-Spam-Status: No, score=-100.695 tagged_above=-999 required=5 tests=[AWL=-0.511, BAYES_40=-0.185, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 5+EzTTUIX9Yt for ; Fri, 29 Oct 2010 10:49:38 -0700 (PDT) Received: from blu0-omc2-s15.blu0.hotmail.com (blu0-omc2-s15.blu0.hotmail.com [65.55.111.90]) by core3.amsl.com (Postfix) with ESMTP id F24583A67FB for ; Fri, 29 Oct 2010 10:49:37 -0700 (PDT) Received: from BLU104-DS5 ([65.55.111.72]) by blu0-omc2-s15.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Oct 2010 10:51:32 -0700 X-Originating-IP: [24.19.29.20] X-Originating-Email: [bernard_aboba@hotmail.com] Message-ID: From: Bernard Aboba To: Date: Fri, 29 Oct 2010 10:52:03 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0119_01CB7757.523C1340" X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: Act3kf5PQOWFdmMFRbi1fUku8zQi2w== X-OriginalArrivalTime: 29 Oct 2010 17:51:32.0468 (UTC) FILETIME=[EC10D340:01CB7791] Subject: [martini] Updated OLIVE and VERMOUTH documents X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 17:49:39 -0000 ------=_NextPart_000_0119_01CB7757.523C1340 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit At IETF 79, Hadriel will be presenting the OLIVE and VERMOUTH documents. Through a quirk in the system, updated versions of the document were submitted on time but not confirmed, so that they are not currently on the archive. Instead, they can be obtained here: http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-martini-vermouth-01.txt http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-martini-with-olive-02.t xt ------=_NextPart_000_0119_01CB7757.523C1340 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

At IETF 79, Hadriel will be presenting the OLIVE = and VERMOUTH documents. 

 

Through a quirk in the system, updated versions of = the document were submitted on time but not confirmed, so that they are not currently on the archive.

 

Instead, they can be obtained here:

 

http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-ma= rtini-vermouth-01.txt

http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-ma= rtini-with-olive-02.txt

 

 

------=_NextPart_000_0119_01CB7757.523C1340-- From HKaplan@acmepacket.com Fri Oct 29 11:10:46 2010 Return-Path: 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 4287E3A69E3 for ; Fri, 29 Oct 2010 11:10:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.466 X-Spam-Level: X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.132, 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 YhMnakX0J8E6 for ; Fri, 29 Oct 2010 11:10:42 -0700 (PDT) Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id DD4E13A69DE for ; Fri, 29 Oct 2010 11:10:41 -0700 (PDT) Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 29 Oct 2010 14:12:36 -0400 Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 29 Oct 2010 14:12:36 -0400 From: Hadriel Kaplan To: Bernard Aboba Date: Fri, 29 Oct 2010 14:12:34 -0400 Thread-Topic: [martini] Updated OLIVE and VERMOUTH documents Thread-Index: Act3lNybLZHUJR+nRuOXoJIXkYHuUg== Message-ID: <859F4559-6609-4E3C-9786-B3FAE6BF428F@acmepacket.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_859F455966094E3C9786B3FAE6BF428Facmepacketcom_" MIME-Version: 1.0 Cc: "martini@ietf.org" Subject: Re: [martini] Updated OLIVE and VERMOUTH documents X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 18:10:46 -0000 --_000_859F455966094E3C9786B3FAE6BF428Facmepacketcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thanks for hosting these Bernard. With regards to Olive: The consensus from the last meeting in Maastricht was to split it out into = two separate drafts: one on local numbers and one on email-style AoRs. Oli= ve is now just the local numbers part, and a separate draft will be submitt= ed for email-style ones when the submission tool re-opens. (the draft is al= ready done but it makes no real changes from the previous Olive other than = just being only about email-style AoRs) With regards to Vermouth: The consensus form the last meeting in Maastricht was to define a new event= package instead of hacking reg-event, and the general feedback was for the= new event package to be for the list of provisioned numbers/names, without= registration status and such. Therefore, the updated Vermouth draft is a = straw-man towards that model. It is NOT a complete proposal, because I thi= nk this actually requires a small design team or at least serious discussio= n of exactly what needs to be in the XML doc and what its structure and sem= antics should be. I will send an email to start a new thread on that topic= . -hadriel On Oct 29, 2010, at 1:52 PM, Bernard Aboba wrote: At IETF 79, Hadriel will be presenting the OLIVE and VERMOUTH documents. Through a quirk in the system, updated versions of the document were submit= ted on time but not confirmed, so that they are not currently on the archiv= e. Instead, they can be obtained here: http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-martini-vermouth-01.tx= t http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-martini-with-olive-02.= txt --_000_859F455966094E3C9786B3FAE6BF428Facmepacketcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
At IETF 79, Hadrie= l will be presenting the OLIVE and VERMOUTH documents. 
 
Through a quirk in the system, updated versions of the doc= ument were submitted on time but not confirmed, so that they are not curren= tly on the archive.
 
Instead, they can be obt= ained here:
 
&nb= sp;
 
<ATT00001..c>

= --_000_859F455966094E3C9786B3FAE6BF428Facmepacketcom_-- From HKaplan@acmepacket.com Fri Oct 29 12:00:58 2010 Return-Path: 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 7D42B3A6A9E for ; Fri, 29 Oct 2010 12:00:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.467 X-Spam-Level: X-Spam-Status: No, score=-2.467 tagged_above=-999 required=5 tests=[AWL=0.132, 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 6Sfj1eqXf7-Y for ; Fri, 29 Oct 2010 12:00:57 -0700 (PDT) Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 8D4613A6A49 for ; Fri, 29 Oct 2010 12:00:56 -0700 (PDT) Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 29 Oct 2010 15:02:51 -0400 Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 29 Oct 2010 15:02:51 -0400 From: Hadriel Kaplan To: "martini@ietf.org" Date: Fri, 29 Oct 2010 15:02:49 -0400 Thread-Topic: An event-package for GIN Thread-Index: Act3m+IAailrJYQjRmWrKm3DTxgBxQ== Message-ID: <4496ABEB-9822-4B8F-8517-BA0D549C3947@acmepacket.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [martini] An event-package for GIN X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 19:00:58 -0000 Howdy, At the last Martini meeting in Maastricht, there was general consensus that= we need to provide a way for the IP-PBX (or any authorized SIP device) to = learn the AoRs/names the SSP has provisioned for expansion a la GIN - i.e.,= what the SSP will route to the IP-PBX. The initial proposal in Vermouth-0= 0 was to re-use the reg-event package for this purpose, with some hacks to = handle wildcard/range situations. In Maastricht, there was general agreeme= nt to not do that, and instead define a new event package specific to the p= roblem at hand, and unrelated to registration state - effectively just the = provisioning info. Vermouth-01 is a straw-man based on that idea, but it r= eally needs more careful thought, and it raises some bigger questions. Thi= s email is an attempt to start discussion of those. 1) In theory, an event-package for this doesn't have to be specific for a G= IN-model to begin with, nor any registration-based SIP trunk. It's really = just about learning basic AoR/name provisioning info in a registrar's datab= ase. So the first question is: is Martini the right WG for this work? 2) Does it need a list of requirements? My gut says it probably does, even= if it's only a small handful. -hadriel= From bernard_aboba@hotmail.com Fri Oct 29 12:25:27 2010 Return-Path: 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 36E293A6A7B for ; Fri, 29 Oct 2010 12:25:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.899 X-Spam-Level: X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[AWL=0.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 fceKUWWgYixj for ; Fri, 29 Oct 2010 12:25:24 -0700 (PDT) Received: from blu0-omc2-s16.blu0.hotmail.com (blu0-omc2-s16.blu0.hotmail.com [65.55.111.91]) by core3.amsl.com (Postfix) with ESMTP id 8EBA73A67D1 for ; Fri, 29 Oct 2010 12:25:24 -0700 (PDT) Received: from BLU104-DS3 ([65.55.111.71]) by blu0-omc2-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Oct 2010 12:27:18 -0700 X-Originating-IP: [24.19.29.20] X-Originating-Email: [bernard_aboba@hotmail.com] Message-ID: From: Bernard Aboba To: Date: Fri, 29 Oct 2010 12:27:50 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0156_01CB7764.B3B26900" X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Thread-Index: Act3n1/MRJtcag3xRDOba9PdNPSU7Q== X-OriginalArrivalTime: 29 Oct 2010 19:27:18.0817 (UTC) FILETIME=[4D281910:01CB779F] Subject: [martini] IETF 79 MARTINI WG Agenda - Take Two X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 19:25:27 -0000 ------=_NextPart_000_0156_01CB7764.B3B26900 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit MARTINI WG IETF 79 Agenda Chairs: Bernard Aboba Spencer Dawkins Jabber room: martini at jabber.ietf.org (Please join) Thursday, November 11, 2010 0900 - 1130 Pearl Room 09:00 - 09:15, Preliminaries Note Well Note Takers Jabber scribe Agenda bash Document Status WG Work Items 09:15 - 9:45, GIN, Adam Roach (30 minutes) http://tools.ietf.org/html/draft-ietf-martini-gin Individual Submissions (90 minutes) 09:45 - 10:30, Other Logical Identifier Values (OLIVE), Hadriel Kaplan (45 minutes) http://tools.ietf.org/html/draft-kaplan-martini-with-olive http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-martini-with-olive-02.t xt 10:30 - 11:15, MARTINI Event Package for Registration (VERMOUTH), Hadriel Kaplan (45 minutes) http://tools.ietf.org/html/draft-kaplan-martini-vermouth http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-martini-vermouth-01.txt Discussion and Wrap-up (15 minutes) 11:15 - 11:30, Discussion and Next Steps: WG Chairs & ADs (15 minutes) ------=_NextPart_000_0156_01CB7764.B3B26900 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

MARTINI WG IETF 79 Agenda

 

Chairs:

Bernard Aboba <bernard_aboba at = hotmail.com>

Spencer Dawkins <spencer at = wonderhamster.org>

 

Jabber room:  martini at jabber.ietf.org = (Please join)

 

Thursday, November 11, 2010

 

0900 - 1130

 

Pearl Room

 

09:00 - 09:15, Preliminaries

 

     Note Well

     Note Takers

     Jabber = scribe

     Agenda bash

     Document = Status

 

WG Work Items

 

09:15 - 9:45,  GIN, Adam Roach (30 = minutes)

http://tools.ietf.org/html/draft-ietf-martini-gin<= /o:p>

 

Individual Submissions (90 minutes)

 

09:45 - 10:30, Other Logical Identifier Values = (OLIVE), Hadriel Kaplan (45 minutes)

http://tools.ietf.org/html/draft-kaplan-martini-with-ol= ive

http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-ma= rtini-with-olive-02.txt

 

10:30 – 11:15, MARTINI Event Package for = Registration (VERMOUTH), Hadriel Kaplan (45 minutes)

http://tools.ietf.org/html/draft-kaplan-martini-vermout= h

http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-ma= rtini-vermouth-01.txt

 

Discussion and Wrap-up (15 minutes)

 

11:15 - 11:30, Discussion and Next Steps:  WG = Chairs & ADs (15 minutes)

------=_NextPart_000_0156_01CB7764.B3B26900-- From pkyzivat@cisco.com Fri Oct 29 14:21:57 2010 Return-Path: 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 905D73A6803 for ; Fri, 29 Oct 2010 14:21:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.476 X-Spam-Level: X-Spam-Status: No, score=-110.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] 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 6FzDJCMQvLZJ for ; Fri, 29 Oct 2010 14:21:56 -0700 (PDT) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 7E6E73A6827 for ; Fri, 29 Oct 2010 14:21:56 -0700 (PDT) Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiMFAE/YykxAZnwM/2dsb2JhbACTWI15caNmnBSFSASKU4MI X-IronPort-AV: E=Sophos;i="4.58,261,1286150400"; d="scan'208";a="176726973" Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 29 Oct 2010 21:23:51 +0000 Received: from [161.44.174.118] (dhcp-161-44-174-118.cisco.com [161.44.174.118]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9TLNp9o007907 for ; Fri, 29 Oct 2010 21:23:51 GMT Message-ID: <4CCB3B67.2020505@cisco.com> Date: Fri, 29 Oct 2010 17:23:51 -0400 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5 MIME-Version: 1.0 To: martini@ietf.org References: <4496ABEB-9822-4B8F-8517-BA0D549C3947@acmepacket.com> In-Reply-To: <4496ABEB-9822-4B8F-8517-BA0D549C3947@acmepacket.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [martini] An event-package for GIN X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 21:21:57 -0000 I support going through the requirements process. Hopefully it can be quick. If not, its probably because it isn't as straightforward as we think. Thanks, Paul On 10/29/2010 3:02 PM, Hadriel Kaplan wrote: > Howdy, > At the last Martini meeting in Maastricht, there was general consensus that we need to provide a way for the IP-PBX (or any authorized SIP device) to learn the AoRs/names the SSP has provisioned for expansion a la GIN - i.e., what the SSP will route to the IP-PBX. The initial proposal in Vermouth-00 was to re-use the reg-event package for this purpose, with some hacks to handle wildcard/range situations. In Maastricht, there was general agreement to not do that, and instead define a new event package specific to the problem at hand, and unrelated to registration state - effectively just the provisioning info. Vermouth-01 is a straw-man based on that idea, but it really needs more careful thought, and it raises some bigger questions. This email is an attempt to start discussion of those. > > 1) In theory, an event-package for this doesn't have to be specific for a GIN-model to begin with, nor any registration-based SIP trunk. It's really just about learning basic AoR/name provisioning info in a registrar's database. So the first question is: is Martini the right WG for this work? > > 2) Does it need a list of requirements? My gut says it probably does, even if it's only a small handful. > > -hadriel > _______________________________________________ > martini mailing list > martini@ietf.org > https://www.ietf.org/mailman/listinfo/martini > From bernard_aboba@hotmail.com Fri Oct 29 14:47:24 2010 Return-Path: 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 11C5B3A67D6 for ; Fri, 29 Oct 2010 14:47:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.903 X-Spam-Level: X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[AWL=0.695, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 yaEmjL5KUwiw for ; Fri, 29 Oct 2010 14:47:19 -0700 (PDT) Received: from blu0-omc2-s27.blu0.hotmail.com (blu0-omc2-s27.blu0.hotmail.com [65.55.111.102]) by core3.amsl.com (Postfix) with ESMTP id E64043A6AC4 for ; Fri, 29 Oct 2010 14:47:18 -0700 (PDT) Received: from BLU104-DS13 ([65.55.111.73]) by blu0-omc2-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Oct 2010 14:49:13 -0700 X-Originating-IP: [72.11.66.126] X-Originating-Email: [bernard_aboba@hotmail.com] Message-ID: From: Bernard Aboba To: Date: Fri, 29 Oct 2010 14:49:07 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0044_01CB7778.70EAFBA0" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Act3n1/MRJtcag3xRDOba9PdNPSU7QAEy1eQ Content-Language: en-us X-OriginalArrivalTime: 29 Oct 2010 21:49:13.0169 (UTC) FILETIME=[201B1C10:01CB77B3] Subject: [martini] IETF 79 MARTINI WG Agenda - Take Three X-BeenThere: martini@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of en-mass SIP PBX registration mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 21:47:24 -0000 ------=_NextPart_000_0044_01CB7778.70EAFBA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit MARTINI WG IETF 79 Agenda Chairs: Bernard Aboba Spencer Dawkins Jabber room: martini at jabber.ietf.org (Please join) Thursday, November 11, 2010 0900 - 1130 Pearl Room 09:00 - 09:15, Preliminaries Note Well Note Takers Jabber scribe Agenda bash Document Status WG Work Items 09:15 - 9:25, GIN, Adam Roach (10 minutes) http://tools.ietf.org/html/draft-ietf-martini-gin Individual Submissions (80 minutes) 09:25 - 10:05, Other Logical Identifier Values (OLIVE), Hadriel Kaplan (40 minutes) http://tools.ietf.org/html/draft-kaplan-martini-with-olive http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-martini-with-olive-02.t xt 10:05 - 10:45, MARTINI Event Package for Registration (VERMOUTH), Hadriel Kaplan (40 minutes) http://tools.ietf.org/html/draft-kaplan-martini-vermouth http://aboba.drizzlehosting.com/MARTINI/draft-kaplan-martini-vermouth-01.txt Discussion and Wrap-up (45 minutes) 10:45 - 11:00 Discussion (15 minutes) 11:00 - 11:15, MARTINI WG Re-Charter Discussion: WG Chairs & ADs (15 minutes) 11:15 - 11:30 Next Steps: WG Chairs & ADs (15 minutes) ------=_NextPart_000_0044_01CB7778.70EAFBA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

MARTINI WG IETF 79 = Agenda

 

Chairs:

Bernard Aboba = <bernard_aboba at hotmail.com>

Spencer Dawkins = <spencer at wonderhamster.org>

 

Jabber room:  = martini at jabber.ietf.org (Please join)

 

Thursday, November 11, = 2010

 

0900 - = 1130

 

Pearl = Room

 

09:00 - 09:15, = Preliminaries

 

     Note = Well

     Note Takers

     Jabber scribe

     Agenda bash

     Document Status

 

WG Work = Items

 

09:15 - 9:25,  = GIN, Adam Roach (10 minutes)

http://tools.ietf.org/html/draft-ietf-martini-gin

 

Individual Submissions = (80 minutes)

 

09:25 - 10:05, Other = Logical Identifier Values (OLIVE), Hadriel Kaplan (40 = minutes)

http://tools.ietf.org/html/draft-kaplan-martini-wit= h-olive

http://aboba.drizzlehosting.com/MARTINI/draft-kapla= n-martini-with-olive-02.txt

 

10:05 – 10:45, = MARTINI Event Package for Registration (VERMOUTH), Hadriel Kaplan (40 = minutes)

http://tools.ietf.org/html/draft-kaplan-martini-ver= mouth

http://aboba.drizzlehosting.com/MARTINI/draft-kapla= n-martini-vermouth-01.txt

 

Discussion and Wrap-up = (45 minutes)

 

10:45 – 11:00 = Discussion (15 minutes)

11:00 – 11:15, = MARTINI WG Re-Charter Discussion: WG Chairs & ADs (15 minutes)

11:15 - 11:30 =  Next Steps:  WG Chairs & ADs (15 minutes)

------=_NextPart_000_0044_01CB7778.70EAFBA0--