RE: [Speermint] Updated Draft: SPEERMINT Peering Architecture

"Henry Sinnreich" <henry@pulver.com> Tue, 30 May 2006 00:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FksAC-0006xC-5w; Mon, 29 May 2006 20:32:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fks84-0005wu-3W for speermint@ietf.org; Mon, 29 May 2006 20:30:36 -0400
Received: from mail.pulver.com ([192.246.69.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fkrux-0003UR-Nq for speermint@ietf.org; Mon, 29 May 2006 20:17:04 -0400
Received: (qmail 20397 invoked by uid 510); 29 May 2006 19:57:09 -0400
Received: from henry@pulver.com by mail.pulver.com by uid 508 with qmail-scanner-1.22-st-qms (clamdscan: 0.72. spamassassin: 2.63. Clear:RC:1(24.1.140.191):. Processed in 1.055711 secs); 29 May 2006 23:57:09 -0000
X-Antivirus-MYDOMAIN-Mail-From: henry@pulver.com via mail.pulver.com
X-Antivirus-MYDOMAIN: 1.22-st-qms (Clear:RC:1(24.1.140.191):. Processed in 1.055711 secs Process 20392)
Received: from c-24-1-140-191.hsd1.tx.comcast.net (HELO DSX400) (henry@pulver.com@24.1.140.191) by 192.246.69.184 with SMTP; Mon, 29 May 2006 23:57:08 +0000
From: Henry Sinnreich <henry@pulver.com>
To: richard@shockey.us, "'Michael Hammer (mhammer)'" <mhammer@cisco.com>, 'Otmar Lendl' <lendl@nic.at>
Subject: RE: [Speermint] Updated Draft: SPEERMINT Peering Architecture
Date: Mon, 29 May 2006 19:16:57 -0500
Organization: pulver.com
Message-ID: <016d01c6837e$5e948ef0$2800a8c0@DSX400>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
In-Reply-To: <00ec01c68281$efb534a0$24f0a544@cis.neustar.com>
Thread-Index: AcZ/J15wu/Ba/2sNTLCXUP/3hHYAhQAFEQbgAAESENAA0GL/UAA+jhpg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: "'Khan, Sohel Q [CTO]'" <Sohel.Q.Khan@sprint.com>, speermint@ietf.org
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: henry@pulver.com
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

> Queried or cached it makes no difference.

The authors of this paper represent those who think there is a big
difference. Reasons include DNS caching conflicts with changing IP
addresses, security, etc. 

http://www.cs.cornell.edu/people/egs/papers/codons-sigcomm.pdf 

Fee free to dismiss yours humbly, I don't mind, but addressing the arguments
in the paper would be more convincing. 

It would be interesting to learn why the 20 year old DNS 'as is' is
considered to be good enough for eternity and any successor technology does
not even merit a read, let alone reconsidering business evolution plans
based on 1986 technology. Reminds us of SS7 indeed...

So what are counter-arguments to those presented in the paper on the
Cooperative Domain Name System? 

Thanks, Henry


-----Original Message-----
From: Richard Shockey [mailto:richard@shockey.us] 
Sent: Sunday, May 28, 2006 1:10 PM
To: henry@pulver.com; 'Michael Hammer (mhammer)'; 'Otmar Lendl'
Cc: 'Khan, Sohel Q [CTO]'; speermint@ietf.org
Subject: RE: [Speermint] Updated Draft: SPEERMINT Peering Architecture


Yes Henry ..but whether we like or not the DNS or at least the technology of
DNS is becoming the defacto number translation database of choice and as
such heralds the end of SS7.

Queried or cached it makes no difference.

> -----Original Message-----
> From: Henry Sinnreich [mailto:henry@pulver.com]
> Sent: Wednesday, May 24, 2006 10:47 AM
> To: 'Michael Hammer (mhammer)'; 'Otmar Lendl'
> Cc: 'Khan, Sohel Q [CTO]'; speermint@ietf.org
> Subject: RE: [Speermint] Updated Draft: SPEERMINT Peering Architecture
> 
> I believe Mike is right on track. Overloading the DNS with application
> protocol information, such as detailed policies for SIP is not what the
> DNS
> was designed for.
> 
> Going further down this path would make the DNS a successor of the AIN!
> 
> Thanks, Henry




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