Re: [Speermint] I-D Action:draft-ietf-speermint-srv-naptr-use-06.txt

Daryl Malas <d.malas@cablelabs.com> Tue, 15 September 2009 20:18 UTC

Return-Path: <D.Malas@cablelabs.com>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B510928C235 for <speermint@core3.amsl.com>; Tue, 15 Sep 2009 13:18:17 -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 osENV4p7V8IE for <speermint@core3.amsl.com>; Tue, 15 Sep 2009 13:18:16 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id BF43828C20D for <speermint@ietf.org>; Tue, 15 Sep 2009 13:18:16 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n8FKJ1Va018097; Tue, 15 Sep 2009 14:19:01 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Tue, 15 Sep 2009 14:19:01 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
Received: from 10.4.10.173 ([10.4.10.173]) by srvxchg3.cablelabs.com ([10.5.0.25]) with Microsoft Exchange Server HTTP-DAV ; Tue, 15 Sep 2009 20:19:01 +0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Tue, 15 Sep 2009 14:19:01 -0600
From: Daryl Malas <d.malas@cablelabs.com>
To: Daryl Malas <d.malas@cablelabs.com>, Richard Shockey <richard@shockey.us>, speermint@ietf.org, Jason Livingood <jason_livingood@cable.comcast.com>, Tom Creighton <Tom_Creighton@cable.comcast.com>
Message-ID: <C6D552D5.4C25%d.malas@cablelabs.com>
Thread-Topic: [Speermint] I-D Action:draft-ietf-speermint-srv-naptr-use-06.txt
Thread-Index: Aco1VrcrkUDZwYmxm0SloaiTXTQvMQADhv5gADb3x5MAAERAvQ==
In-Reply-To: <C6D5510B.4C22%d.malas@cablelabs.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Approved: ondar
Subject: Re: [Speermint] I-D Action:draft-ietf-speermint-srv-naptr-use-06.txt
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 20:18:17 -0000

For the benefit of those who may not want to read the draft, it proposes a
method for including trunk group information in a NAPTR response.  I think
this could be included in this speermint draft.  The alternative approach is
an individual draft target more for ENUM in general.  Richard, correct me if
I am wrong here.

--Daryl


On 9/15/09 2:11 PM, "Daryl Malas" <d.malas@cablelabs.com> wrote:

> Richard,
> 
> You are correct.  This was the approach I was taking, but then I started to
> think about how it relates to peering.  We have the draft currently, and I
> thought it might fit best in it.  I can still submit an individual draft.
> Are there other thoughts on this from anyone else?
> 
> Thanks,
> 
> Daryl
> 
> 
> On 9/14/09 12:00 PM, "Richard Shockey" <richard@shockey.us> wrote:
> 
>> Its entirely up to you how you want to proceed. I certainly have no problem
>> with this approach though how it fits in with the SPEERMINT charter is
>> probably a question and I'd poll Cullen to see what he thinks.  In general
>> he certainly understands the application and the need. I was working on the
>> assumption that you could submit it as a AD sponsored draft since ENUM is
>> being shut down.
>> 
>> I'll certainly support whatever you guys want to do.
>> 
>>>  -----Original Message-----
>>>  From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
>>>  On Behalf Of Daryl Malas
>>>  Sent: Monday, September 14, 2009 12:16 PM
>>>  To: speermint@ietf.org; Jason Livingood; Tom Creighton
>>>  Subject: [Speermint] Re: I-D Action:draft-ietf-speermint-srv-naptr-
>>>  use-06.txt
>>>  
>>>  Jason and Tom,
>>>  
>>>  The more I think about the draft Tom and I submitted to ENUM
>>>  (draft-malas-enum-trunk-sip-00), the more I think it could easily fit
>>>  into
>>>  this draft.  The concept is simple and just identifies how trunk
>>>  groups
>>>  should be identified in an ENUM NAPTR response.  I think this will
>>>  primarily
>>>  be used for peering.
>>>  
>>>  Thoughts?
>>>  
>>>  Regards,
>>>  
>>>  Daryl
>>>  
>>>  
>>>  On 9/11/09 11:45 AM, "Internet-Drafts@ietf.org" <Internet-
>>>  Drafts@ietf.org>
>>>  wrote:
>>>  
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>> directories.
>>>> This draft is a work item of the Session PEERing for Multimedia
>>>  INTerconnect
>>>> Working Group of the IETF.
>>>> 
>>>> 
>>>> Title           : Use of DNS SRV and NAPTR Records for SPEERMINT
>>>> Author(s)       : T. Creighton, J. Livingood
>>>> Filename        : draft-ietf-speermint-srv-naptr-use-06.txt
>>>> Pages           : 14
>>>> Date            : 2009-09-11
>>>> 
>>>> The objective of this document is to specify the Best Current
>>>> Practice (BCP) adopted by a SSP or other organization providing
>>>> multimedia communication services such as Voice over Internet
>>>> Protocol(VoIP) in order to locate another SSP to peer with in the
>>>> context of Session PEERing for Multimedia INTerconnect.  This
>>>> document attempts to fill the gaps in information from RFC 3261, RFC
>>>> 3263, and other documents, in order to more assist SSPs in more
>>>> easily performing SIP peering.
>>>> 
>>>> [EDITORIAL NOTE: XREF ERROR GENERATED IN ABSTRACT, XREFS REMOVED]
>>>> 
>>>> A URL for this Internet-Draft is:
>>>> http://www.ietf.org/internet-drafts/draft-ietf-speermint-srv-naptr-
>>>  use-06.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.
>>>> _______________________________________________
>>>> Speermint mailing list
>>>> Speermint@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/speermint
>>>  
>>>  
>>>  -----------------
>>>  Daryl Malas
>>>  CableLabs
>>>  (o) +1 303 661 3302
>>>  (f) +1 303 661 9199
>>>  mailto:d.malas@cablelabs.com
>>>  
>>>  
>>>  _______________________________________________
>>>  Speermint mailing list
>>>  Speermint@ietf.org
>>>  https://www.ietf.org/mailman/listinfo/speermint
>> 
> 
> 
> -----------------
> Daryl Malas
> CableLabs
> (o) +1 303 661 3302
> (f) +1 303 661 9199
> mailto:d.malas@cablelabs.com
> 
> 
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint


-----------------
Daryl Malas
CableLabs
(o) +1 303 661 3302
(f) +1 303 661 9199
mailto:d.malas@cablelabs.com