Re: [Dime] draft-korhonen-dime-nai-routing-00.txt
"Korhonen, Jouni /TeliaSonera Finland Oyj" <jouni.korhonen@teliasonera.com> Fri, 04 July 2008 21:30 UTC
Return-Path: <dime-bounces@ietf.org>
X-Original-To: dime-archive@megatron.ietf.org
Delivered-To: ietfarch-dime-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D41D73A6BCF; Fri, 4 Jul 2008 14:30:34 -0700 (PDT)
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CC583A6BCF for <dime@core3.amsl.com>; Fri, 4 Jul 2008 14:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.216
X-Spam-Level:
X-Spam-Status: No, score=-5.216 tagged_above=-999 required=5 tests=[AWL=-1.033, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
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 sLzZU080O1kv for <dime@core3.amsl.com>; Fri, 4 Jul 2008 14:30:32 -0700 (PDT)
Received: from sehan002bb.han.telia.se (sehan002bb.han.telia.se [131.115.18.153]) by core3.amsl.com (Postfix) with ESMTP id 177B23A6BCE for <dime@ietf.org>; Fri, 4 Jul 2008 14:30:31 -0700 (PDT)
Received: from SEHAN021MB.tcad.telia.se ([131.115.18.160]) by sehan002bb.han.telia.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Jul 2008 23:30:37 +0200
Received: from 131.115.14.48 ([131.115.14.48]) by SEHAN021MB.tcad.telia.se ([131.115.18.162]) with Microsoft Exchange Server HTTP-DAV ; Fri, 4 Jul 2008 21:30:36 +0000
From: "Korhonen, Jouni /TeliaSonera Finland Oyj" <jouni.korhonen@teliasonera.com>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, dime@ietf.org
thread-topic: [Dime] draft-korhonen-dime-nai-routing-00.txt
thread-index: AcjeHTKCKUrl4HsvRJix2LpKPm+9kQ==
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Sat, 05 Jul 2008 00:30:28 +0300
Message-ID: <2e6601c8de1d$3282dbca$300e7383@tcad.telia.se>
X-Mailer: EAS Version 1.00
MIME-Version: 1.0
Content-Language: i-default
X-OriginalArrivalTime: 04 Jul 2008 21:30:37.0686 (UTC) FILETIME=[3357A960:01C8DE1D]
Subject: Re: [Dime] draft-korhonen-dime-nai-routing-00.txt
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: dime-bounces@ietf.org
Errors-To: dime-bounces@ietf.org
Hi Hannes,
Our impression after previous discussion was rather clear that routing issues would not be part of rfc3588bis and splitting the concepts of draft-tsou into smaller issues was encouraged. At least i was told so. I would be happy, if we could have the content described in this draft as a part of the rfc3588bis.
Backwards compatibility issues are imho clear.. With existing apps and rfc3588 you just don't have quarantees. So you better only apply enhanced routing to newly defined applications that can be explicit on the routing behavior.
And what is wrong with short drafts? Here we just have one issue that we want to be explicit about.
Cheers,
Jouni
--- alkuperäinen viesti ---
Lähettäjä: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
Aihe: [Dime] draft-korhonen-dime-nai-routing-00.txt
Päivämäärä: 4. heinäkuuta 2008
Aika: 21:55:16
I am a bit surprised about this document given the discussions we had in
the context of
http://tools.ietf.org/html/draft-tsou-dime-base-routing-ext-03. My
impression was that we need to provide the text relevant to this aspect
within RFC 3588bis. In fact, I naively thought that this has already
been done...
Without going into the details of the NAI decoration itself, which is
discussed already in RFC 4282 and RFC 5113, the real content is quite
short.
The backwards compatibility considerations make me a bit nervous
Ciao
Hannes
_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime
_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime
- [Dime] draft-korhonen-dime-nai-routing-00.txt Hannes Tschofenig
- Re: [Dime] draft-korhonen-dime-nai-routing-00.txt Korhonen, Jouni /TeliaSonera Finland Oyj
- Re: [Dime] draft-korhonen-dime-nai-routing-00.txt Hannes Tschofenig