Re: [RAM] First cut at routing & addressing problem statement

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 03 August 2007 20:51 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IH475-0004J4-Vi; Fri, 03 Aug 2007 16:51:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IH474-0004Iy-T6 for ram@iab.org; Fri, 03 Aug 2007 16:51:10 -0400
Received: from fk-out-0910.google.com ([209.85.128.190]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IH474-00022U-F0 for ram@iab.org; Fri, 03 Aug 2007 16:51:10 -0400
Received: by fk-out-0910.google.com with SMTP id 19so1434698fkr for <ram@iab.org>; Fri, 03 Aug 2007 13:51:09 -0700 (PDT)
Received: by 10.82.112.16 with SMTP id k16mr3809419buc.1186143942768; Fri, 03 Aug 2007 05:25:42 -0700 (PDT)
Received: from ?10.10.50.8? ( [213.3.13.1]) by mx.google.com with ESMTPS id k10sm3096968nfh.2007.08.03.05.25.40 (version=SSLv3 cipher=RC4-MD5); Fri, 03 Aug 2007 05:25:40 -0700 (PDT)
Message-ID: <46B31EC7.7040904@gmail.com>
Date: Fri, 03 Aug 2007 14:25:43 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: [RAM] First cut at routing & addressing problem statement
References: <200707270020.l6R0KbZs014836@cichlid.raleigh.ibm.com>
In-Reply-To: <200707270020.l6R0KbZs014836@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ram@iab.org
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

> We would welcome comments on the document. In particular:
> 
>  - Do folk agree with the problem statement as written, or are we
>    missing something fairly fundamental?

Yes. I think it's correct to keep it down to the bare bones.

>  - Are there other pressures on the routing system that we have not
>    listed or described completely?

Not that I noticed.

>  - We intentionally did not include improving mobility as a core
>    "problem", as explained in the document. (That doesn't mean we
>    don't recognize that some of the solutions under discussion may
>    also be applicable to mobility scenarios. Rather, we tend to see
>    improved mobility as a possible benefit of certain classes of
>    solutions.)

I think this is correct. In many ways mobility is an overlay
on a routing system assumed to be stable and scaleable.

>  - Are there other views of what folk perceive the core routing and
>    addressing problem to be?

Not here.

     Brian

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram