IETF Logo Mail Archive

Re: [Speermint] Updated Draft: SPEERMINT Peering Architecture

Otmar Lendl <lendl@nic.at> Tue, 23 May 2006 20:59 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FidyL-0003x2-VI; Tue, 23 May 2006 16:59:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FidyK-0003wg-JS for speermint@ietf.org; Tue, 23 May 2006 16:59:20 -0400
Received: from arachne.bofh.priv.at ([193.154.150.108] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FidyJ-0003S5-A8 for speermint@ietf.org; Tue, 23 May 2006 16:59:20 -0400
Received: by mail.bofh.priv.at (Postfix, from userid 1000) id AEAE51A39F; Tue, 23 May 2006 22:59:10 +0200 (CEST)
Date: Tue, 23 May 2006 22:59:10 +0200
From: Otmar Lendl <lendl@nic.at>
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Speermint] Updated Draft: SPEERMINT Peering Architecture
Message-ID: <20060523205910.GB1811@nic.at>
Mail-Followup-To: Otmar Lendl <lendl@nic.at>, "Michael Hammer (mhammer)" <mhammer@cisco.com>, Brian Rosen <br@brianrosen.net>, "Francois D. Menard" <fmenard@xittelecom.com>, "Khan, Sohel Q [CTO]" <Sohel.Q.Khan@sprint.com>, David Meyer <dmm@1-4-5.net>, speermint@ietf.org
References: <072C5B76F7CEAB488172C6F64B30B5E3017E63F0@xmb-rtp-20b.amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E3017E63F0@xmb-rtp-20b.amer.cisco.com>
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: speermint@ietf.org, "Khan, Sohel Q [CTO]" <Sohel.Q.Khan@sprint.com>
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
Errors-To: speermint-bounces@ietf.org

On 2006/05/23 22:05, "Michael Hammer (mhammer)" <mhammer@cisco.com> wrote:
> 
> I think the the interworking of SIP to PSTN is out of scope here.  The
> issue is whether two peers, once they have discovered each other, can
> know what subset of SIP they need to support.  
[...]
> While coloring within those lines, the next question is whether there is
> a single subset that can be defined or whether there will be many.  I am
> betting on many, probably a different set for each federation or even
> bilateral pairing that might exist.  That could be another rabbit hole.
> I would be happy if two peers could point to the same subset and agree
> to use it, no matter how many subsets might exist.

Well, I've got a draft to sell to you.

>From the example section of draft-lendl-domain-policy-ddds-00.txt:

   o  If the carrier example.com only accepts SIP calls (in addition to
      PSTN interconnect) if the PSTN emulation is good, he might publish
      a policy like this:

      $ORIGIN example.com.
      ;      order pref flags service regexp replacement
       IN NAPTR 10 10   "U" "D2P+SIP:std" "!^.*$!urn:ietf:rfc:3578!" .
       IN NAPTR 10 11   "U" "D2P+SIP:std" "!^.*$!urn:ietf:rfc:3666!" .
       IN NAPTR 10 12   "U" "D2P+SIP:std" "!^.*$!urn:ietf:rfc:3960!" .

/ol
-- 
< Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer >

_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint

v2.23.0 | Report a Bug | By Email