
From rrg-bounces@irtf.org  Sun Feb  1 01:24:07 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DEEF3A68DD; Sun,  1 Feb 2009 01:24:07 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CFB83A6820 for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 01:24:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.566
X-Spam-Level: 
X-Spam-Status: No, score=-1.566 tagged_above=-999 required=5 tests=[AWL=0.329,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
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 lrsalSGCkNpz for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 01:24:04 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 84A7A3A68DD for <rrg@irtf.org>; Sun,  1 Feb 2009 01:24:03 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 7F259175CAD; Sun,  1 Feb 2009 20:23:43 +1100 (EST)
Message-ID: <49856AA3.4060404@firstpr.com.au>
Date: Sun, 01 Feb 2009 20:25:55 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: rrg@irtf.org
References: <20090131202433.ECCC16BE58D@mercury.lcs.mit.edu>
In-Reply-To: <20090131202433.ECCC16BE58D@mercury.lcs.mit.edu>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:   APT and Ivip greatly reduce the number of
                 destinations to which a full stream of mapping
                 updates need to be pushed, compared to
                 LISP-NERD.  So the choice is not just between
                 full pull (APT, TRRP) and full push (NERD).

                 Is LISP-ALT a quickie "solution" - with a
                 better, incompatible, real long-term solution
                 in the future?


Hi Noel,

I responded to what you wrote about mobility in a separate
thread.  You wrote:

> On a more general note, I actually did some 'back of the envelope'
> calculations a year or two ago, trying to decide whether to use push or pull,
> and my recollection is that the update rate numbers (i.e. the control traffic
> at each and every ITR) for push got fairly significant (in terms of the
> number of updates per second) even with only moderate numbers of mapping
> entries, and a fairly low assumed per-entry update rate (e.g. for provider
> changes only).

Sure, that is presumably for LISP-NERD - the only current
proposal which involves every ITR getting the full feed of
mapping updates.  I think most people agree LISP-NERD does not
scale well enough to be considered as a lasting solution.

For APT and Ivip, the mapping is pushed to local full-database
query servers.  These are much less numerous (factor of 10 to
100 or whatever) than ITRs, which will be caching ITRs.

Also, with Ivip, the caching ITR function can be performed in a
sending host (not behind NAT unless the ITR function opens a
persistent tunnel to its local query server).   Ivip has an
optional intermediate layer (or multiple layers) of caching
query servers between the caching ITRs and the local full
database query servers.  This may further reduce the number of
full database query servers needed, without adding any
significant delay to the ITR getting the mapping it needs.

Compared to LISP-NERD, this greatly reduces the number of
devices which get the full feed of mapping updates.


> Certainly, a full-push system is going to be distributing lots of mappings to
> boxes that never use them - my guess was something in the 99% region, if not
> much higher. (Long digression on the optimal mapping distribution system
> omitted - the points you raise are certainly valid, but there are good points
> on both sides, and I don't think the answer is clear-cut - if it were,
> we probably wouldn't still be discussing it.)

Sure, but mapping data with Ivip is quite compact, since it only
involves a single ETR address for each micronet.  (12 bytes at
most per micronet, but this could be conveyed in a more compact
form, probably down to 8 bytes.)  LISP and APT involves multiple
ETR addresses for each EID prefix.  Ivip's fast-push mapping
system is intended to be streamlined and will carry multiple
mapping updates (a hundred - or 700 or 800 or so with
jumboframes) per packet.

The volume of mapping changes are just not that big compared to
what ordinary domestic end-users are doing with the Net today.
In a few years time, it will be commonplace for these users to
be getting multiple gigabytes of near-real-time video data,
often from across the world, for a few dollars.

It will be a long time (massive use of TTR mobility) before
LISP, APT, Ivip etc. have mapping update rates to rival the 4 to
8 Mbps video streams which will be sent to ordinary homes.

Updates will be for some mix of:

  Changes for multihoming service restoration.

  Inbound TE.

  A mobile node's micronet being mapped to a new TTR.

Let's say it was all IPv6, with about 32 bytes per mapping change:

   64 bits Micronet base address, in units of /64.

   64 bits (32 would usually do) Micronet length in the same
   units.

   128 bits ETR address.

Allowing for a 50% overhead, 1Mbps provides 2600 mapping updates
a second.  For arguments' sake, let's say half are mobile TTR
selections, this is 1,300 people a second, on average travelling
something like 1000km.   That, on average, is 4.6M an hour - far
more than will ever be needed on this planet using conventional
physics.

Do you have any BOTECs (Back of the Envelope Calculations . . .)
for far distant future mapping update rates?  Multiply them by
32 bytes for IPv6 Ivip and consider how bad, on average, that
will be  in the context of ISPs in that far distant future.
Peak rates would be higher of course.


> Also, I'm not sure that for those working on LISP, ALT is the 'preferred'
> long-range answer to the question of 'what does the mapping subsystem look
> like'. I think the focus is on ALT at the moment in large part because it's
> fairly easy to deploy, because it re-uses existing code. (Dino et al, please
> correct me to the degree I am confused here.)

I don't recall any other LISP people suggesting this - that ALT
as a first-cut system, to be replaced by something different and
better in the long term.

I think a LISP-ALT router can be created by correctly
configuring existing functions in any suitably flexible hardware
or software-based router.  The ITR and ETR functions require
some additional code to be written.

So it is not too hard to get LISP-ALT going.  For instance:

  http://www.lisp4.net/docs/lisp-ausnog02.ppt Aug 2008 slide 11:

    a very small amount of new code was written to support this


It wouldn't be surprising if a better architecture required more
thought and more code and complexity in some areas, such as a
fast-push mapping system and the full-database and caching query
servers.  Such an architecture would have greater benefits,
better scaling properties and less complexity and costs where it
really matters, such as in the ITR function.

For instance (not counting the PTMUD functions which are
reasonably complex for Ivip, LISP or any other system) Ivip ITRs
are a lot simpler than LISP ITRs or APT ITRs/DMs because they
don't need to test reachability to ETRs, or make any choices
between different ETRs.  Also, the mapping information they
cache is more compact than with LISP or APT.


> It might well make sense to transition to something else in the long run -

If this is true of LISP-ALT, then why bother with it?

What can be learnt by pushing ahead with it, compared to working
on a better architecture instead?  The problems with delays,
long-paths, robustness vs. a relatively flat, aggregated ALT
structure etc. have already been pointed out.


> but then of course one has the transition issue to deal with, and from what
> thinking I have put into that particular problem, it's more problematic that
> some of the other long-term transition issues (e.g. to a different inter-xTR
> packet format, etc). So that would argue to make replacement of that
> subsystem priority number one...

With a 15% per annum growth in the DFZ routing table, even if it
accelerates considerably due to finer slicing and dicing of IPv4
space, the sky is not going to fall in this year, the next or by
2015.

If getting the right design takes another few years compared to
adopting a quickie solution, then it will be well worth doing
this extra work.


 - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 03:49:30 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7984528C148; Sun,  1 Feb 2009 03:49:30 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FA6E28C0FC for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 03:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.57
X-Spam-Level: 
X-Spam-Status: No, score=-1.57 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
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 3nGFgDVoVXy4 for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 03:49:27 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id F139E28C148 for <rrg@irtf.org>; Sun,  1 Feb 2009 03:49:25 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id CD895175CAC; Sun,  1 Feb 2009 22:49:05 +1100 (EST)
Message-ID: <49858CB6.9020609@firstpr.com.au>
Date: Sun, 01 Feb 2009 22:51:18 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Subject: [rrg] RANGER-06
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:    I read the RANGER I-D and came away without
                  any substantial understanding of what RANGER
                  is supposed to achieve, in terms of scalable
                  routing and addressing, or what new capabilities
                  or requirements it has for hosts - different from
                  how the IPv4 and IPv6 Internets work today.

Hi Fred,

Here are my thoughts when reading and trying to understand:

  http://tools.ietf.org/html/draft-templin-ranger-06

In the absence of any Summary and Analysis on the RRG wiki, and
without actually reading the various related I-Ds, I am hoping to
understand enough of RANGER by reading the above I-D - to decide
whether I want to read the other documents.

I thought I had a half-way decent understanding of SEAL from early
2008, but I wouldn't want to be examined on it, and I haven't kept up
with your revisions since then.

I don't really understand VET or ISATAP - but I figure I shouldn't
have to read a bunch of other documents in order to develop a
reasonable overview of RANGER.


You gave a summary:

  RANGER BOF - call for participation
  http://www.irtf.org/pipermail/rrg/2009-January/000909.html

While I understand that RANGER is intended to be a solution to the
routing and addressing problems we are all trying to solve, I
couldn't figure out from the summary whether RANGER is:

  1 - A core-edge separation scheme (LISP, APT, Ivip, TRRP)

  2 - A core-edge elimination scheme - usually done with
      changes in hosts, such as with HIP.

  3 - Something else.

The first two classes are discussed in:

      Towards a Future Internet Architecture: Arguments for
      Separating Edges from Transit Core
      Dan Jen, Lixia Zhang, Lan Wang, Beichuan Zhang
      http://conferences.sigcomm.org/hotnets/2008/papers/18.pdf

I got the clear impression that RANGER is intended to work with both
IPv4 and IPv6 and enable a recursive application of the same "network
within a network" structure, with one of the goals being the re-use
of at least some parts of the address space as separate namespaces in
separate networks.  There are lots of encapsulating tunnels, with
SEAL somehow taking care of the PMTU problems these cause.  IPv4 can
travel in IPv6 tunnels and vice-versa.

At this point, I wanted to know:

  1 - Is this intended to be a complete scalable routing solution?

  2 - Assuming this is the case, to what extent are host stack, API
      and application changes required?

  3 - I knew "mapping" was somehow involved in RANGER, but the
      introduction does not mention it, and I want to know how this
      concept in RANGER compares with its use in LISP, APT, Ivip etc.

  4 - What sort of introduction plan you had in mind, including
      immediate benefits to those end-user networks and ISPs which
      adopt it - together with costs, risks, changes to networks,
      hosts etc.


I am up to page 12 and will summarise my questions so far.

Then I will read on and write further comments.

In the terminology section, or in some early section, I think you
really need to give the reader a good functional understanding of
some of the building blocks of RANGER.  These include:

   The mapping system.  There are frequent references to this, but
   by page 12, no description of its purpose, structure or
   functionality.

   VET.  From the "Terminology" section:

      Virtual Enterprise Traversal (VET) [I-D.templin-autoconf-dhcp];
      functional specifications and operational practices that
      provide a functional superset of 6over4 and ISATAP.  In
      addition to both unicast and multicast tunneling, VET also
      supports address/prefix autoconfiguration as well as additional
      encapsulations such as IPSec, SEAL, LISP, etc.

   This is very broad-brush, so I read the abstracts:

      http://tools.ietf.org/html/draft-templin-autoconf-dhcp-32

         Enterprise networks connect routers over various link types,
         and may also connect to provider networks and/or the global
         Internet.  Nodes in enterprise networks must have a way to
         automatically provision IP addresses/prefixes and other
         information, and must also support internetworking operation
         even in highly-dynamic networks.  This document specifies a
         Virtual Enterprise Traversal (VET) abstraction for
         autoconfiguration and operation of nodes in enterprise
         networks.

      http://tools.ietf.org/html/rfc2529  (6over4)

         This memo specifies the frame format for transmission of
         IPv6 packets and the method of forming IPv6 link-local
         addresses over IPv4 domains.  It also specifies the content
         of the Source/Target Link-layer Address option used in the
         Router Solicitation, Router Advertisement, Neighbor
         Solicitation, and Neighbor Advertisement and Redirect
         messages, when those messages are transmitted on an IPv4
         multicast network.

         The motivation for this method is to allow isolated IPv6
         hosts, located on a physical link which has no directly
         connected IPv6 router, to become fully functional IPv6 hosts
         by using an IPv4 domain that supports IPv4 multicast as
         their virtual local link. It uses IPv4 multicast as a
         "virtual Ethernet".

            (IPv4 multicast??  Who actually uses this in big
             networks?  It doesn't work in the DFZ.  I see later
             that there is some explanation of this in section 4.1
             of the RANGER I-D.)

      http://tools.ietf.org/html/rfc5214  (ISATAP)

        The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
        connects dual-stack (IPv6/IPv4) nodes over IPv4 networks.
        ISATAP views the IPv4 network as a link layer for IPv6 and
        supports an automatic tunneling abstraction similar to the
        Non-Broadcast Multiple Access (NBMA) model.

   Lacking detailed understanding of all the above, I have a vague,
   open, notion of VET being a means of connecting things via
   tunnels, though I have no idea what this means with multicast, or
   with "LISP encapsulation" .

Now to the I-D:

Page 6:

  What is meant by "next generation enterprise networks"?

  I think I get the notion of "enterprises within enterprises" -
  including with inner enterprise networks running their own BGP
  which is separate from that of the outer enterprise.

  I don't understand how this differs in a functional sense from what
  can be done today with conventional techniques.  Also, how many
  enterprises want to be connected to the rest of the world solely
  from within another?


Page 8:

  I understand VET can connect multiple sub-enterprises within one
  enterprise, with the sub-enterprises using the outer enterprise's
  addressing system, or having their own.

  I want to know how DNS works in the latter scenario.  I think of
  DNS as a global system returning (in addition to MX records,
  sub-domains and potentially other things) one or more IP addresses
  for a given FQDN.  While I have heard of plans to make DNS supply
  different answers for requests from different places (and while I
  know there are good purposes for this in the global Internet to
  cause sessions to go to servers which are generally physically
  close to the requesting host) I want to know how DNS can work if
  some enterprises are using some numeric range of what is to other
  enterprises "public" address space in a different, private,
  manner than the other enterprises.

  With IPv6, there's plenty of space - so why would any network
  want to reuse part of it which someone else is already using?

  With IPv4, there is not enough - but how could reusing part of
  the global public space be a good idea, since it would seem to
  require that local hosts not be able to access some parts of
  the public address space outside?


Page 9:

     "The prefixes could be either Provider-Independent (PI) prefixes
      owned by the BR or Provider-Aggregated (PA) prefixes delegated
      by the BG, but the prefixes are linked with mapping and routing
      over the virtual topology in both cases."

   I don't understand how prefixes could be "linked".   I still have
   no idea what "mapping" means in the context of RANGER.

     "Additionally, fault tolerance and multihoming is naturally
      afforded through configuration of multiple BGs per enterprise."

   I haven't seen a diagram depicting multihomed networks, only one
   network within another.  Searching ahead I find a section on
   Multihoming, on page 16 and am alarmed to discover that HIP may
   be required to do it!

      "At the enterprise edge, a true location/identity split
       approach such as HIP may be necessary for supporting true
       multihoming across multiple physical links with diverse
       properties."


Page 10, para 2:

   I understand that PA prefixes are handed downwards, from routers
   closer to the DFZ to routers in sub-networks, and then from
   those routers potentially to further sub-networks etc.

   I also understand that PI prefixes are announced (by some
   secure means, I assume) from the lower levels and the upper
   layer routers carry the announcement, advertisement whatever
   to make the prefix appear to the rest of the world.

   But I still have no idea what RANGER's "mapping system" is, so
   I can't understand the following at all:  Regarding PI prefix
   information propagating upwards, via "registration":

      "This registration results in updates to the mapping system,
       which can later be used to populate a BR's Forwarding
       Information Base (FIB)."


Page 11 para 3:

   Again, there is mention of mapping: "mapping database lookups"
   but I still have no idea what this means.

   I gather that VET can have more than two networks connected to
   it, as per Figure 3, and that the connections need not always
   be maintained.   So I wonder how it scales if the traffic does
   need to maintain them.  If there are 100 networks connecting
   via VET, are there 100 * 99 separate sets of two-way tunnel?


OK - now I am at page 13, with more questions than understanding.

What exactly are "legacy services" in this context.  I figure they
are the global behaviours of the entire IPv4 and IPv6 Internets as
perceived by any participating host today.

But this is page 13, and there has been no description of what is
different, from a host point of view, or in terms of DNS, about the
new RANGER architecture.

What is it you are trying to do which is different from today's
Internets?

A quick scan of page 13 turns up, in the last para, mention of NAT in
some intermediate network as part of providing "legacy services".
NAT is to be avoided if at all possible.

I still don't understand why enterprises want to be recursively
nested.  For multihoming, don't they want two or more physically
diverse connections to the DFZ, as short and fat as possible?

If multihoming with RANGER requires host changes, such as with HIP,
then isn't this a complete non-starter in terms of any routing
scaling solution, which has to be adopted enthusiastically and
voluntarily by the great majority of end-user networks?


Page 14:

     "IPv4 NAT capability however this approach requires multiple
      instances of stateful NAT devices on the path which can lead to
      an overall degree of brittleness and intolerance to routing
      changes."

   This makes me think RANGER is some kind of radical revision of
   both IPv4 and IPv6 in a way which makes current hosts, DNS etc.
   non-functional, or only partially functional - and therefore to
   be known as "legacy" and afforded special treatment.

   What are the unique advantages of changing much of the Net over
   to this RANGER model?   LISP, APT, Ivip and TRRP etc. provide
   multihoming without any host changes, but it seems RANGER can't
   provide it, except with the complete host changes of HIP.

I can't make head or tail of section 3.2.3.

In 3.3 I understand that SEAL will somehow enable the creation of
good tunnels, with proper management of PMTUD, in an environment
where ICMP messages, particularly RFC 1191 Packet Too Big (PTB)
messages may be either lost or spoofed.


Page 15:

  "mapping/routing"??


Page 16:

  I haven't tried to follow all the mobile stuff, but I have a
  question about the airliner with a PI prefix which it announces
  at one ground station, and then the next (say 1/3 the way around
  the planet).

  As long as this is a real, public, PI prefix, then in order to
  ensure optimal paths, potentially all routers in the DFZ will
  need to adapt to the change.  It doesn't matter how many
  layers of networks there are between the DFZ and those
  ground points, or whether the ground points are owned by the
  same network or not.  Moving PI space requires BGP changes -
  and this is an unscalable approach considering the number of
  aircraft travelling in this way.   A solution is the TTR
  approach, in which this specific problem is discussed:

    http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf

  I still don't have any clear idea of what RANGER is supposed to
  achieve or how it helps with mobility.

  The TTR approach avoids the need for the mobile node to ever
  renumber its public, numerically stable, physically globally
  mobile, address, no matter how many CoAs it has.  So there is
  no breaks in sessions, as long as connectivity is maintained
  via one CoA or another in any access network, including behind
  NAT.

Section 3.5 on multihoming:

  If an enterprise advertises a prefix to multiple upstream
  BGs, how do these advertise it upwards to the DFZ?  What if
  the link to one BG becomes unusable, but that BG is still
  advertising the prefix to the DFZ?

  Is HIP really needed for multihoming with RANGER?

  If so, this requires the hosts to get a separate address
  from each PA prefix from each upstream ISP/whatever.  But
  the first two sentences of this section involve the network
  advertising a PI prefix (or multiple PI prefixes) with
  every upstream BG.  This is like traditional BGP-based
  multihoming today - and not related at all to the PA based
  HIP approach.



Page 17:

       "4.4. The Locator Identifier Split Protocol (LISP)

        The Locator-Identifier Split Protocol (LISP)
        [I-D.farinacci-lisp] proposes a map-and-encaps architecture
        for scalable routing and addressing within the global
        Internet Default Free Zone (DFZ).  Several companion
        documents (e.g., LISP-ALT, LISP-CONS, LISP-EMACS,
        LISP-NERD) propose mapping function solutions.  A related
        mapping function solution proposal is found in
        [I-D.jen-apt]."

APT is not related to LISP, in my view.  It has some common
characteristics, such as non-real-time mapping and each ITR having to
do reachability testing to each ETR etc.

However, APT is more than a mapping distribution system.  It is
completely different from LISP-NERD on one hand and the other LISP
approaches on the other, in that it uses local query servers.

        "LISP, and a number of related proposals being discussed in
         the Routing Research Group, share common properties with the
         solution proposed here."

I have no idea what common properties these are.

       "They may therefore be architecturally consistent with
        the RANGER architecture."


I have spent a few hours trying to understand RANGER - its purpose,
its changes to host and DNS behavior, its support for multihoming,
its support for today's IPv4 and IPv6 Internet host and DNS behaviour
("legacy").  I still have no clear idea what RANGER is supposed to
achieve or how it works.

Does RANGER complement a global LISP, APT or Ivip system?

If so, then is it a solution to the scalable routing problem on its
own?  If so, then why would anyone want LISP, APT or Ivip?

If not, then why do we want to know about it here?  What does it add
to the scalable routing solution which is not already provided by
LISP, APT or Ivip?

The final section on Security again fails to connect with my mind in
a concrete enough fashion to form real understanding.

I need overall goals, purpose etc.  I need to know where this scheme
fits with other schemes - does it complement a core-edge separation
scheme, is it one in itself or is it something else?  I need to have
a rough understanding of the behaviour of the building blocks - SEAL
and VET - so I can envisage what RANGER builds them into.  I have
some understanding of SEAL, but none of VET.  I think the RANGER I-D
needs to be self-contained, so people who don't already know of your
specific building blocks can learn enough about them to understand
your description of how RANGER would work.

  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 09:26:57 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DC933A6AB9; Sun,  1 Feb 2009 09:26:57 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 781F83A689F; Thu, 29 Jan 2009 16:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ltVt1WF48aGQ; Thu, 29 Jan 2009 16:15:06 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 90DA53A6859; Thu, 29 Jan 2009 16:15:06 -0800 (PST)
Received: from [75.209.223.67] (67.sub-75-209-223.myvzw.com [75.209.223.67]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n0U0EW03004865; Thu, 29 Jan 2009 16:14:35 -0800 (PST)
Message-ID: <49824668.8010709@isi.edu>
Date: Thu, 29 Jan 2009 16:14:32 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Dino Farinacci <dino@cisco.com>
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au><6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>	<497EB510.8060100@firstpr.com.au>	<39C363776A4E8C4A94691D2BD9D1C9A1057DFFA6@XCH-NW-7V2.nw.nos.boeing.com> <440A01B3-E96C-461A-93EC-6FD8E74FC7D2@cisco.com>
In-Reply-To: <440A01B3-E96C-461A-93EC-6FD8E74FC7D2@cisco.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Sun, 01 Feb 2009 09:26:57 -0800
Cc: int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org, RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as	towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Dino Farinacci wrote:
>> The approach in the current LISP draft still relies on ICMPs
>> coming from anonymous network middleboxes (which Dino himself
>> has said that we cannot depend on), and provides insufficient
> 
> I did not say that. I said you cannot depend on ICMP Unreachables. But
> ICMP TooBig and Time-Exceeded message are sent and are more dependable.
> That is, they can get lost when they are transmitted since they are
> single transmitted datagrams. But at least they are sent.

Can you clarify? ICMP unreachables are required sent, just as TooBigs
and Time-Exceededs. They're all blocked by various systems, including
NATs and firewalls, so none can be relied upon.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmCRmgACgkQE5f5cImnZrvJMwCg5sXMLzPhykKChfhblr+JiJk6
2kwAn02MGjy1fmqwNvX+cLCzbsduDnaX
=9wnh
-----END PGP SIGNATURE-----
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 09:26:57 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC1453A6B8B; Sun,  1 Feb 2009 09:26:57 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8C173A6944 for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 21:18:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_MED=-4]
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 ZMFSQoDX+p57 for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 21:18:00 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 4B4BD3A6B02 for <rrg@irtf.org>; Sat, 31 Jan 2009 21:18:00 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,358,1231113600"; d="scan'208";a="240664569"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 01 Feb 2009 05:17:37 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n115HbYJ024767;  Sat, 31 Jan 2009 21:17:37 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n115Hbfv019871; Sun, 1 Feb 2009 05:17:37 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 31 Jan 2009 21:17:37 -0800
Received: from [10.21.120.250] ([10.21.120.250]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 31 Jan 2009 21:17:37 -0800
Message-ID: <49853070.1030808@cisco.com>
Date: Sat, 31 Jan 2009 21:17:36 -0800
From: Enke Chen <enkechen@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
X-OriginalArrivalTime: 01 Feb 2009 05:17:37.0142 (UTC) FILETIME=[65669960:01C9842C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7603; t=1233465457; x=1234329457; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=enkechen@cisco.com; z=From:=20Enke=20Chen=20<enkechen@cisco.com> |Subject:=20Re=3A=20[rrg]=20BGP=20scaling=20limit |Sender:=20; bh=IhMV9mF+V67CQjtrcrZ9yHLHs2h2yDLdzqrZsOm4QyU=; b=Zq5RypeFYJ3DpjEuRhzT8KAUTKzkJZRQo/kpsIBqZkQeD5AXTwKVCvcMdH /V77I8+8Qp/yzfR21vJY6/pwbET8RLdZzJygwqR2ab6P0dQbMcf2wmoXi43K jcRSuEV6kXHBa5ScPv2X+U8a05zBL4CVGpNWetkDLDACugoB3uTVc=;
Authentication-Results: sj-dkim-1; header.From=enkechen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
X-Mailman-Approved-At: Sun, 01 Feb 2009 09:26:57 -0800
Cc: rrg@irtf.org, Enke Chen <enkechen@cisco.com>
Subject: Re: [rrg] BGP scaling limit
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi, Danny:

Just saw this email as I am not on the IRTF mailing list:

Excerpt from the email:

------------------------------------------------------------------------------

I don't agree with this.  Offer me an alternative for 10 or
more interconnections between the largest networks today?
Offer me an alternative for how those paths and the current
inter-domain routing protocol amplify (not minimize) the number
of paths.
-----------------------------------------------------------

Here is what I (Enke) am thinking:

I do agree that the current operational model of doing shortest-exit
(and thus resulting in path multiplications) has scalability concerns,
especially with the increase in the number of peering locations between
providers.

So here is an alternative (operationally):

      accept MEDs from each other and perform longest-exit.

The MEDs could be set by the sender based on the location (community)
so that at most 2 or 3 peering locations would advertise the same
MED.

For example, for a particular prefix originated from New York:

        Peering Location         MED
        -----------------------------
         New York / DC           10

                  Chicago/ Denver                       20
                  SFO / LA                                 30
                  .....

The location/community based route-map should be uniform (i.e., 
identical) at the peering
locations.

This approach should reduce the number paths significantly, and yet 
maintain redundancy
and convergence properties in a network.

Any comments?

-- Enke
       

    * /From/: Danny McPherson <danny at arbor.net
      <mailto:danny@DOMAIN.HIDDEN>>
    * /To/: <tony.li at tony.li <mailto:tony.li@DOMAIN.HIDDEN>>
    * /Cc/: 'RRG' <rrg at irtf.org <mailto:rrg@DOMAIN.HIDDEN>>
    * /Date/: Mon, 12 Jan 2009 14:01:24 -0700

------------------------------------------------------------------------

On Jan 12, 2009, at 10:34 AM, Tony Li wrote:

      

    As you point out, this is more to do with the specific protocol than
    it is to do with the overall routing architecture. As such, this is
    why it's

    really much more of the domain of IDR than RRG.
      

Well, so long as the folks designing the next generation
understand the problem and mitigate the constraints.  I'm
not totally sure the former is the case, which has effects
on the latter.


    BTW, AFAIK, route reflection _reduces_ the number of paths as
    compared to

    full-mesh IBGP.  Am I missing something?
      

Depends on the number of RRs, where the best path
is, network architecture, etc..  The growth curves
I've seen (wFrom rrg-bounces at irtf.org  Mon Jan 12 13:01:51 2009



On Jan 12, 2009, at 10:34 AM, Tony Li wrote:

      

    As you point out, this is more to do with the specific protocol than
    it is to do with the overall routing architecture. As such, this is
    why it's

    really much more of the domain of IDR than RRG.
      

Well, so long as the folks designing the next generation
understand the problem and mitigate the constraints.  I'm
not totally sure the former is the case, which has effects
on the latter.


    BTW, AFAIK, route reflection _reduces_ the number of paths as
    compared to

    full-mesh IBGP.  Am I missing something?
      

Depends on the number of RRs, where the best path
is, network architecture, etc..  The growth curves
I've seen (which I hhich I hope to be able to share soon)
illustrate that the number of iBGP paths is growing
at anywhere from 6-14x the rate of the DFZ, and
the reason is because of external factors, protocol
design issues, and implementations.


    Paths that are introduced for the sake of traffic engineering are a
    well

    understood and self-inflicted problem.
      

Really?  So a multi-homed AS is TE?  So networks that interconnect
in 10 places result in 10 paths for each prefix and that's self-
inflicted?  What's the alternative to avoiding this self-inflicted
pain?


     If those folks that introduced the
    extra paths took equivalent interest in limiting their dispersion and
      

    cooperated in filtering unnecessary long prefixes, this could
    readily be

    addressed.
      

No, I'm not talking about just extraneous or covered prefixes,
that's only a tiny part of the problem I'm referring to.
Denseness of external interconnection, unique attributes,
BGP as defined today AND TE have effects on these, I'd say the
latter the least.


     In short, this is not an issue with the fundamental
      

    architecture, it's about how the architecture is being used. Thus,
    this is

    largely an operational issue.
      

I don't agree with this.  Offer me an alternative for 10 or
more interconnections between the largest networks today?
Offer me an alternative for how those paths and the current
inter-domain routing protocol amplify (not minimize) the number
of paths.


    Further, if we did something to fundamentally remove the capability to
      

    traffic engineer in the future, I strongly suspect that that would
    be an

    architectural issue, most likely fatal.
      

Again, TE is only a tiny part of the problem I'm referring
to here - fully dependent on ones definition of TE, of course.

-danny

_______________________________________________
rrg mailing list
rrg at irtf.org
http://www.irtf.org/mailman/listinfo/rrg


ope to be able to share soon)
illustrate that the number of iBGP paths is growing
at anywhere from 6-14x the rate of the DFZ, and
the reason is because of external factors, protocol
design issues, and implementations.


    Paths that are introduced for the sake of traffic engineering are a
    well

    understood and self-inflicted problem.
      

Really?  So a multi-homed AS is TE?  So networks that interconnect
in 10 places result in 10 paths for each prefix and that's self-
inflicted?  What's the alternative to avoiding this self-inflicted
pain?


     If those folks that introduced the
    extra paths took equivalent interest in limiting their dispersion and
      

    cooperated in filtering unnecessary long prefixes, this could
    readily be

    addressed.
      

No, I'm not talking about just extraneous or covered prefixes,
that's only a tiny part of the problem I'm referring to.
Denseness of external interconnection, unique attributes,
BGP as defined today AND TE have effects on these, I'd say the
latter the least.


     In short, this is not an issue with the fundamental
      

    architecture, it's about how the architecture is being used. Thus,
    this is

    largely an operational issue.
      

I don't agree with this.  Offer me an alternative for 10 or
more interconnections between the largest networks today?
Offer me an alternative for how those paths and the current
inter-domain routing protocol amplify (not minimize) the number
of paths.


    Further, if we did something to fundamentally remove the capability to
      

    traffic engineer in the future, I strongly suspect that that would
    be an

    architectural issue, most likely fatal.
      

Again, TE is only a tiny part of the problem I'm referring
to here - fully dependent on ones definition of TE, of course.

-danny

_______________________________________________
rrg mailing list
rrg at irtf.org
http://www.irtf.org/mailman/listinfo/rrg


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 09:26:57 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D47583A6B8F; Sun,  1 Feb 2009 09:26:57 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F5DA3A6944 for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 21:29:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.224
X-Spam-Level: 
X-Spam-Status: No, score=-6.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_MED=-4]
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 tQ+-RYpNI4vZ for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 21:29:47 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 47B343A68DF for <rrg@irtf.org>; Sat, 31 Jan 2009 21:29:47 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,358,1231113600"; d="scan'208";a="240667607"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 01 Feb 2009 05:29:28 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n115TSBQ005287;  Sat, 31 Jan 2009 21:29:28 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n115TSfk017330; Sun, 1 Feb 2009 05:29:28 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 31 Jan 2009 21:29:28 -0800
Received: from [10.21.120.250] ([10.21.120.250]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 31 Jan 2009 21:29:27 -0800
Message-ID: <49853337.2030205@cisco.com>
Date: Sat, 31 Jan 2009 21:29:27 -0800
From: Enke Chen <enkechen@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
References: <49853070.1030808@cisco.com>
In-Reply-To: <49853070.1030808@cisco.com>
X-OriginalArrivalTime: 01 Feb 2009 05:29:28.0053 (UTC) FILETIME=[0D230250:01C9842E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8260; t=1233466168; x=1234330168; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=enkechen@cisco.com; z=From:=20Enke=20Chen=20<enkechen@cisco.com> |Subject:=20Re=3A=20[rrg]=20BGP=20scaling=20limit |Sender:=20; bh=Orluu+B7F3LRlZGi1YT4ZK5PeUyESSKCujj5LXDuSbk=; b=FJFqJco8165Reszs54pZigz958v8gGb4o8Mfm0N1gs1Vdof7EKQbGfnRSM MAOBMwuy8UJVno8C8fRo2xJUIaW/qY/4wNO+4Q8/vfDzAsYdynAMM68qHGwy xWXxBQQ/7I;
Authentication-Results: sj-dkim-3; header.From=enkechen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
X-Mailman-Approved-At: Sun, 01 Feb 2009 09:26:57 -0800
Cc: rrg@irtf.org, Enke Chen <enkechen@cisco.com>
Subject: Re: [rrg] BGP scaling limit
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

BTW, the MED setting could also be based on the normalized metric.  For 
example:

           IGP metric                     MED
          --------------------------------
             0-20                               10
            21-40                              20
            41-100                            30
            ...

-- Enke

Enke Chen wrote:
> Hi, Danny:
>
> Just saw this email as I am not on the IRTF mailing list:
>
> Excerpt from the email:
>
> ------------------------------------------------------------------------------ 
>
>
> I don't agree with this.  Offer me an alternative for 10 or
> more interconnections between the largest networks today?
> Offer me an alternative for how those paths and the current
> inter-domain routing protocol amplify (not minimize) the number
> of paths.
> -----------------------------------------------------------
>
> Here is what I (Enke) am thinking:
>
> I do agree that the current operational model of doing shortest-exit
> (and thus resulting in path multiplications) has scalability concerns,
> especially with the increase in the number of peering locations between
> providers.
>
> So here is an alternative (operationally):
>
>      accept MEDs from each other and perform longest-exit.
>
> The MEDs could be set by the sender based on the location (community)
> so that at most 2 or 3 peering locations would advertise the same
> MED.
>
> For example, for a particular prefix originated from New York:
>
>        Peering Location         MED
>        -----------------------------
>         New York / DC           10
>
>                  Chicago/ Denver                       20
>                  SFO / LA                                 30
>                  .....
>
> The location/community based route-map should be uniform (i.e., 
> identical) at the peering
> locations.
>
> This approach should reduce the number paths significantly, and yet 
> maintain redundancy
> and convergence properties in a network.
>
> Any comments?
>
> -- Enke
>      
>    * /From/: Danny McPherson <danny at arbor.net
>      <mailto:danny@DOMAIN.HIDDEN>>
>    * /To/: <tony.li at tony.li <mailto:tony.li@DOMAIN.HIDDEN>>
>    * /Cc/: 'RRG' <rrg at irtf.org <mailto:rrg@DOMAIN.HIDDEN>>
>    * /Date/: Mon, 12 Jan 2009 14:01:24 -0700
>
> ------------------------------------------------------------------------
>
> On Jan 12, 2009, at 10:34 AM, Tony Li wrote:
>
>     
>    As you point out, this is more to do with the specific protocol than
>    it is to do with the overall routing architecture. As such, this is
>    why it's
>
>    really much more of the domain of IDR than RRG.
>     
> Well, so long as the folks designing the next generation
> understand the problem and mitigate the constraints.  I'm
> not totally sure the former is the case, which has effects
> on the latter.
>
>
>    BTW, AFAIK, route reflection _reduces_ the number of paths as
>    compared to
>
>    full-mesh IBGP.  Am I missing something?
>     
> Depends on the number of RRs, where the best path
> is, network architecture, etc..  The growth curves
> I've seen (wFrom rrg-bounces at irtf.org  Mon Jan 12 13:01:51 2009
>
>
>
> On Jan 12, 2009, at 10:34 AM, Tony Li wrote:
>
>     
>    As you point out, this is more to do with the specific protocol than
>    it is to do with the overall routing architecture. As such, this is
>    why it's
>
>    really much more of the domain of IDR than RRG.
>     
> Well, so long as the folks designing the next generation
> understand the problem and mitigate the constraints.  I'm
> not totally sure the former is the case, which has effects
> on the latter.
>
>
>    BTW, AFAIK, route reflection _reduces_ the number of paths as
>    compared to
>
>    full-mesh IBGP.  Am I missing something?
>     
> Depends on the number of RRs, where the best path
> is, network architecture, etc..  The growth curves
> I've seen (which I hhich I hope to be able to share soon)
> illustrate that the number of iBGP paths is growing
> at anywhere from 6-14x the rate of the DFZ, and
> the reason is because of external factors, protocol
> design issues, and implementations.
>
>
>    Paths that are introduced for the sake of traffic engineering are a
>    well
>
>    understood and self-inflicted problem.
>     
> Really?  So a multi-homed AS is TE?  So networks that interconnect
> in 10 places result in 10 paths for each prefix and that's self-
> inflicted?  What's the alternative to avoiding this self-inflicted
> pain?
>
>
>     If those folks that introduced the
>    extra paths took equivalent interest in limiting their dispersion and
>     
>    cooperated in filtering unnecessary long prefixes, this could
>    readily be
>
>    addressed.
>     
> No, I'm not talking about just extraneous or covered prefixes,
> that's only a tiny part of the problem I'm referring to.
> Denseness of external interconnection, unique attributes,
> BGP as defined today AND TE have effects on these, I'd say the
> latter the least.
>
>
>     In short, this is not an issue with the fundamental
>     
>    architecture, it's about how the architecture is being used. Thus,
>    this is
>
>    largely an operational issue.
>     
> I don't agree with this.  Offer me an alternative for 10 or
> more interconnections between the largest networks today?
> Offer me an alternative for how those paths and the current
> inter-domain routing protocol amplify (not minimize) the number
> of paths.
>
>
>    Further, if we did something to fundamentally remove the capability to
>     
>    traffic engineer in the future, I strongly suspect that that would
>    be an
>
>    architectural issue, most likely fatal.
>     
> Again, TE is only a tiny part of the problem I'm referring
> to here - fully dependent on ones definition of TE, of course.
>
> -danny
>
> _______________________________________________
> rrg mailing list
> rrg at irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>
>
> ope to be able to share soon)
> illustrate that the number of iBGP paths is growing
> at anywhere from 6-14x the rate of the DFZ, and
> the reason is because of external factors, protocol
> design issues, and implementations.
>
>
>    Paths that are introduced for the sake of traffic engineering are a
>    well
>
>    understood and self-inflicted problem.
>     
> Really?  So a multi-homed AS is TE?  So networks that interconnect
> in 10 places result in 10 paths for each prefix and that's self-
> inflicted?  What's the alternative to avoiding this self-inflicted
> pain?
>
>
>     If those folks that introduced the
>    extra paths took equivalent interest in limiting their dispersion and
>     
>    cooperated in filtering unnecessary long prefixes, this could
>    readily be
>
>    addressed.
>     
> No, I'm not talking about just extraneous or covered prefixes,
> that's only a tiny part of the problem I'm referring to.
> Denseness of external interconnection, unique attributes,
> BGP as defined today AND TE have effects on these, I'd say the
> latter the least.
>
>
>     In short, this is not an issue with the fundamental
>     
>    architecture, it's about how the architecture is being used. Thus,
>    this is
>
>    largely an operational issue.
>     
> I don't agree with this.  Offer me an alternative for 10 or
> more interconnections between the largest networks today?
> Offer me an alternative for how those paths and the current
> inter-domain routing protocol amplify (not minimize) the number
> of paths.
>
>
>    Further, if we did something to fundamentally remove the capability to
>     
>    traffic engineer in the future, I strongly suspect that that would
>    be an
>
>    architectural issue, most likely fatal.
>     
> Again, TE is only a tiny part of the problem I'm referring
> to here - fully dependent on ones definition of TE, of course.
>
> -danny
>
> _______________________________________________
> rrg mailing list
> rrg at irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>
>

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 09:26:58 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1793E3A6B95; Sun,  1 Feb 2009 09:26:58 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 461383A6949; Sun,  1 Feb 2009 01:31:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 VPL0E0fdODXL; Sun,  1 Feb 2009 01:31:26 -0800 (PST)
Received: from mta2.cl.cam.ac.uk (mta2.cl.cam.ac.uk [128.232.0.14]) by core3.amsl.com (Postfix) with ESMTP id 799BC3A68DD; Sun,  1 Feb 2009 01:31:25 -0800 (PST)
Received: from rhee.cl.cam.ac.uk ([128.232.1.202] helo=cl.cam.ac.uk) by mta2.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 1LTYfI-000315-00; Sun, 01 Feb 2009 09:30:56 +0000
To: Christian Vogt <christian.vogt@ericsson.com>
In-reply-to: <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com> 
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com> <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com>
Comments: In-reply-to Christian Vogt <christian.vogt@ericsson.com> message dated "Sat, 31 Jan 2009 11:49:46 -0800."
MIME-Version: 1.0
Content-ID: <5883.1233480655.1@cl.cam.ac.uk>
Date: Sun, 01 Feb 2009 09:30:55 +0000
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
Message-Id: <E1LTYfI-000315-00@mta2.cl.cam.ac.uk>
X-Mailman-Approved-At: Sun, 01 Feb 2009 09:26:57 -0800
Cc: int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org, rrg RG <rrg@irtf.org>, Jon.Crowcroft@cl.cam.ac.uk
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

you can push info multiply redundently
(or cross-post:)
and you get reliability with a silly overhead

or you can push an update which is wrong and disconnect the entire
world, e.g.
http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html

so aside from the basic academic type scaling, has anyone done
this sort of disaster-prone analysis for LISP/ALT?

(i.e. human stupidity resilience, rather than security-to-prevent evil)

one is reminded of simily errors with DNS root databases and with 
BGP adverts...one woudn't want to design a system with
one-click take-down again

In missive <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com>, Christian Vogt 
typed:

 >>
 >>On Jan 28, 2009, Dino Farinacci wrote:
 >>
 >>> You cannot push around 10^10 entries and store them everywhere. [...]
 >>
 >>
 >>
 >>Dino -
 >>
 >>I think we should experimentally compare ALT with other mapping systems
 >>before we decide whether pull-based or push-based mapping systems are
 >>better.  Dismissing push-based mapping systems without corroborating
 >>data would be a bit premature in my opinion.
 >>
 >>In the absence of experimentation results, I would actually argue in
 >>favor of push-based mapping systems based on some analytical reasoning:
 >>Pull-based mapping systems have two important disadvantages compared to
 >>push-based mapping systems:
 >>
 >>- Performance penalty, i.e., additional propagation latencies for some
 >>   packets, and higher loss probabilities for packets that take a sub-
 >>   optimal path
 >>
 >>- Robustness penalty due to a new online dependency on components off
 >>   the actual transmission path.  (FWIW: All pull-based mapping systems
 >>   have this penalty.  Mapping requests must be routed via overlay
 >>   infrastructure because the direct route is unknown at that time.)
 >>
 >>Furthermore, I do not share your concerns regarding push-based mapping
 >>systems:  BGP is pushing routing data already today, and this works
 >>fine.  Any routing-scalability-related issues with BGP are not due to
 >>BGP being push-based; they are due to frequent updates and a high load
 >>for core routers.  Both of these issues would go away in an address
 >>indirection architecture (be it LISP, Ivip, APT, or Six/One Router),
 >>independent of whether you use a pull- or push-based mapping system.
 >>
 >>In conclusion:  The overlay approach of ALT is certainly an interesting
 >>idea.  But I think it would be premature to conclude that it is the only
 >>viable solution before we have more evidence to back this claim.
 >>
 >>- Christian
 >>
 >>
 >>PS:  I admit that I have never been really good in avoiding cross-
 >>posting.  But this is obviously my all-time negative record...
 >>
 >>
 >>
 >>_______________________________________________
 >>routing-discussion mailing list
 >>routing-discussion@ietf.org
 >>https://www.ietf.org/mailman/listinfo/routing-discussion

 cheers

   jon

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 10:18:13 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7AAA3A6908; Sun,  1 Feb 2009 10:18:13 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82D7B28C101 for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 10:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level: 
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tAU-bMLXfL2S for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 10:18:11 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 6460528C0ED for <rrg@irtf.org>; Sun,  1 Feb 2009 10:18:11 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,360,1231113600"; d="scan'208";a="240862194"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 01 Feb 2009 18:17:52 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n11IHqB9024712;  Sun, 1 Feb 2009 10:17:52 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n11IHqiu016379; Sun, 1 Feb 2009 18:17:52 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 1 Feb 2009 10:17:52 -0800
Received: from [192.168.1.2] ([10.21.77.236]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 1 Feb 2009 10:17:52 -0800
Message-Id: <55757C03-B881-4D45-BDFC-4FFB8CAD156D@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Christian Vogt <christian.vogt@ericsson.com>
In-Reply-To: <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sun, 1 Feb 2009 10:17:53 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com> <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 01 Feb 2009 18:17:52.0260 (UTC) FILETIME=[6562B440:01C98499]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3266; t=1233512272; x=1234376272; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[lisp]=20Please=20respond=3A=20Question s=20from=20the=20IESG=20as=20to=20whether=20a=20WG=20forming =20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=SR2nu3S4BpwVSfkClB1WKhZAzoA2mzPTlETTGhKcJWs=; b=QetIvihuqmGeA51DN1GX5h3klGNYJ2VSvGv4tMWNqhR5N5fd6Z1BEUdb/K MAsTGru8whLP0XkNNX3VOUYCpsHyN2bd9KYd42lmNy3nY7skVwQXH94TjY6N 9VOvsKSn2TdmPWMeml6y5TqRF2RQQ03S+HAX6coF4P+R3rPIDyJsE=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> Dino -
>
> I think we should experimentally compare ALT with other mapping  
> systems
> before we decide whether pull-based or push-based mapping systems are
> better.  Dismissing push-based mapping systems without corroborating
> data would be a bit premature in my opinion.

Agree.

> In the absence of experimentation results, I would actually argue in
> favor of push-based mapping systems based on some analytical  
> reasoning:
> Pull-based mapping systems have two important disadvantages compared  
> to
> push-based mapping systems:
>
> - Performance penalty, i.e., additional propagation latencies for some
>  packets, and higher loss probabilities for packets that take a sub-
>  optimal path
>
> - Robustness penalty due to a new online dependency on components off
>  the actual transmission path.  (FWIW: All pull-based mapping systems
>  have this penalty.  Mapping requests must be routed via overlay
>  infrastructure because the direct route is unknown at that time.)

Make note that LISP-ALT is a hybrid. It pushes EID-prefix  
announcements via eBGP over an alternate topology of GRE tunnels. And  
then ITRs pull the mappings by sending Map-Requests on this topology  
so ETRs (who are authoritative for the mappings) can return Map-Replies.

> Furthermore, I do not share your concerns regarding push-based mapping
> systems:  BGP is pushing routing data already today, and this works
> fine.  Any routing-scalability-related issues with BGP are not due to

But the BGP RIB is order 10^5 and on average (there is lots of data on  
this) only 10% of that table is used in any given router.

> BGP being push-based; they are due to frequent updates and a high load
> for core routers.  Both of these issues would go away in an address

Other reason you want to push is if all the nodes in the "push domain"  
need to use the information. If they don't it is a waste of memory and  
resources. BGP is used as a transport for routing information but each  
node uses that information.

Make note that NERD has been called a "push" mechanism. But it  
actually is requesting to receive *all mappings*.

Also, another point I want to make where I'll use the iPhone 2.0  
release as an example. In 2.0, they said they had "push email". Well  
from a user point of view, that means when you open your mail app, the  
email is sitting there ready to be read. If in the background, there  
was a periodic process to pull the email, then it still looks like push.

The point here is begging a single question:

     1) Should all the mappings in the universe be in an ITR?

     2) Should only the mappings for sites the ITR is currently  
talking to be in the ITR?

This is the important matter. Decide on that then we can talk about  
how to get the mappings where they need to be.

> In conclusion:  The overlay approach of ALT is certainly an  
> interesting
> idea.  But I think it would be premature to conclude that it is the  
> only
> viable solution before we have more evidence to back this claim.

Why do you think a conclusion is being made. I haven't made any.

Anyways, this is a good discussion and glad we have moved passed the  
definition of an EID.

Dino

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 10:45:53 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F08828C13D; Sun,  1 Feb 2009 10:45:53 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4FC23A6A9F for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 10:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.864
X-Spam-Level: 
X-Spam-Status: No, score=-2.864 tagged_above=-999 required=5 tests=[AWL=-0.557, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
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 8pYec1UUwuYT for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 10:45:51 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 2E1EB3A693B for <rrg@irtf.org>; Sun,  1 Feb 2009 10:45:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id ADD674302E3; Sun,  1 Feb 2009 10:45:32 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-64.clppva.btas.verizon.net [71.161.51.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 021B54302E0; Sun,  1 Feb 2009 10:45:31 -0800 (PST)
Message-ID: <4985EDC6.9070608@joelhalpern.com>
Date: Sun, 01 Feb 2009 13:45:26 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au>	<6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>	<3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>	<83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com>	<4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com> <55757C03-B881-4D45-BDFC-4FFB8CAD156D@cisco.com>
In-Reply-To: <55757C03-B881-4D45-BDFC-4FFB8CAD156D@cisco.com>
Cc: rrg RG <rrg@irtf.org>, lisp@ietf.org
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I don't think those are the only two alternatives.  For example, 
something like the APT idea where the full mappings are shipped to a set 
of devices such that such a full set is near to and on the query path of 
any leaf is an alternative worth examining.

 From a design perspective therefore, I would tend to look for a system 
where a device can be sent unsolicited mappings, can choose to keep 
them, and can issue a query via an overlay to resolve mappings it does 
not have.
While one could argue that this complicates the protocol, it is an 
unneeded complication only if we are very sure we know what the right 
answer is for information distribution.  It is admittedly more complex 
than just using BGP to carry EIDs.  Are we sufficiently sure?

It then becomes an operational decision whether the mappings are in any 
given leaf, in some intermediate devices, or in just the originating 
leaves.  (While the decision on the alternatives can not be made wholly 
independently by all the branches of the overlay tree, there is room for 
flexibility.)


Yours,
Joel

Dino Farinacci wrote:
>> Dino -
...
> The point here is begging a single question:
> 
>     1) Should all the mappings in the universe be in an ITR?
> 
>     2) Should only the mappings for sites the ITR is currently talking 
> to be in the ITR?
> 
> This is the important matter. Decide on that then we can talk about how 
> to get the mappings where they need to be.
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 12:07:16 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2E063A67AC; Sun,  1 Feb 2009 12:07:16 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADA383A67AC for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 12:07:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level: 
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 dcRSfSYRrdPQ for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 12:07:14 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 967743A63CB for <rrg@irtf.org>; Sun,  1 Feb 2009 12:07:14 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,360,1231113600"; d="scan'208";a="240888315"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 01 Feb 2009 20:05:56 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n11K5uSf004537;  Sun, 1 Feb 2009 12:05:56 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n11K5uUo003655; Sun, 1 Feb 2009 20:05:56 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 1 Feb 2009 12:05:55 -0800
Received: from [192.168.1.2] ([10.21.77.236]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 1 Feb 2009 12:05:55 -0800
Message-Id: <6DE40C2A-7621-4D06-959B-E88C1E04C592@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <4985EDC6.9070608@joelhalpern.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sun, 1 Feb 2009 12:05:56 -0800
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au>	<6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>	<3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>	<83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com>	<4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com> <55757C03-B881-4D45-BDFC-4FFB8CAD156D@cisco.com> <4985EDC6.9070608@joelhalpern.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 01 Feb 2009 20:05:55.0471 (UTC) FILETIME=[7DAE31F0:01C984A8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2011; t=1233518756; x=1234382756; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[lisp]=20[rrg]=20Please=20respond=3A=20 Questions=20from=20the=20IESG=20as=20to=09whether=20a=20WG=2 0forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=VpX5qfo1B0hFDkaWsH0UpjW3W+j7Lb9PIiPH/61s+b4=; b=f1wOw8MV9/oiaI2rYmBhf310P9trTaDbziBQnq9RLU87rom05qLUeq/o6Y LKuTSiqtBDYnIxDFFB/8PCPDt4kOlNtGAjoc9IOOWTmKyoEOW4LALKh4ciW5 HxZlS5vJMS;
Authentication-Results: sj-dkim-4; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: rrg RG <rrg@irtf.org>, lisp@ietf.org
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> I don't think those are the only two alternatives.  For example,  
> something like the APT idea where the full mappings are shipped to a  
> set of devices such that such a full set is near to and on the query  
> path of any leaf is an alternative worth examining.

We have stated before that LISP-ALT routers could cache mappings. This  
can help with Map-Request latency. And if the mappings are cached do  
to seeing Map-Replies or because they are pushed with some other  
protocol, then so be it.

> From a design perspective therefore, I would tend to look for a  
> system where a device can be sent unsolicited mappings, can choose  
> to keep them, and can issue a query via an overlay to resolve  
> mappings it does not have.

They would have to be signed.

> While one could argue that this complicates the protocol, it is an  
> unneeded complication only if we are very sure we know what the  
> right answer is for information distribution.  It is admittedly more  
> complex than just using BGP to carry EIDs.  Are we sufficiently sure?

Agree.

> It then becomes an operational decision whether the mappings are in  
> any given leaf, in some intermediate devices, or in just the  
> originating leaves.  (While the decision on the alternatives can not  
> be made wholly independently by all the branches of the overlay  
> tree, there is room for flexibility.)

Right, but is a state/latency tradeoff.

Dino

>
>
>
> Yours,
> Joel
>
> Dino Farinacci wrote:
>>> Dino -
> ...
>> The point here is begging a single question:
>>    1) Should all the mappings in the universe be in an ITR?
>>    2) Should only the mappings for sites the ITR is currently  
>> talking to be in the ITR?
>> This is the important matter. Decide on that then we can talk about  
>> how to get the mappings where they need to be.
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 18:13:22 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5861A3A6873; Sun,  1 Feb 2009 18:13:22 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E34EA3A6873 for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 18:13:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.124
X-Spam-Level: 
X-Spam-Status: No, score=0.124 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_53=0.6, RDNS_NONE=0.1]
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 y2v5MB7jp+4I for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 18:13:20 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 178603A6866 for <rrg@irtf.org>; Sun,  1 Feb 2009 18:13:16 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KEF00I5M1WO2J@szxga03-in.huawei.com> for rrg@irtf.org; Mon, 02 Feb 2009 10:07:36 +0800 (CST)
Received: from x41208a ([10.111.12.103]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KEF00N2L1WO3Z@szxga03-in.huawei.com> for rrg@irtf.org; Mon, 02 Feb 2009 10:07:36 +0800 (CST)
Date: Mon, 02 Feb 2009 10:07:35 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <4985EDC6.9070608@joelhalpern.com>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>
Message-id: <000301c984db$044d5150$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: AcmEnUpq8AvT4ucpQemmoKY97shgCAANhq+g
Cc: 'rrg RG' <rrg@irtf.org>, lisp@ietf.org
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Joel,

> I don't think those are the only two alternatives.  For 
> example, something like the APT idea where the full mappings 
> are shipped to a set of devices such that such a full set is 
> near to and on the query path of any leaf is an alternative 
> worth examining.

That's just the basic idea of VA (Virtual Aggregation, see
http://tools.ietf.org/html/draft-francis-idr-intra-va-01, and
http://tools.ietf.org/html/draft-xu-idr-tunnel-00). And we are now doing
some updates to simplify VA mechanism and will submit new versions soon.

>  From a design perspective therefore, I would tend to look 
> for a system where a device can be sent unsolicited mappings, 
> can choose to keep them, and can issue a query via an overlay 
> to resolve mappings it does not have.

In VA, the mappings (EID prefixes associated with RLOCs)are advertised
through currrent BGP connections. The RLOC information can be carried by a
new BGP attribute, e.g. a special extended community. VA routers will
install the mappings selectively into their routing tables according to
whether or not they are the APRs(Aggregate Point Router) for those mappings.
In this way, the full mappings are distributed among a set of APRs. The
overlay composed of a set of APRs can not only be used for mapping
request/reponse, but also be used for transferring data packets when the ITR
has no mapping entry for these packets in its cache.

> While one could argue that this complicates the protocol, it 
> is an unneeded complication only if we are very sure we know 
> what the right answer is for information distribution.  It is 
> admittedly more complex than just using BGP to carry EIDs.  
> Are we sufficiently sure?

In VA, extended communities are used for conveying the RLOCs, and BGP
computation behavior remain unchanged. So this will not complicate the
protocol too much.
 
Xiaohu


> Dino Farinacci wrote:
> >> Dino -
> ...
> > The point here is begging a single question:
> > 
> >     1) Should all the mappings in the universe be in an ITR?
> > 
> >     2) Should only the mappings for sites the ITR is 
> currently talking 
> > to be in the ITR?
> > 
> > This is the important matter. Decide on that then we can talk about 
> > how to get the mappings where they need to be.
> > 
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 18:48:55 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9902F3A67BD; Sun,  1 Feb 2009 18:48:55 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37A8C3A67BD for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 18:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.177
X-Spam-Level: 
X-Spam-Status: No, score=-0.177 tagged_above=-999 required=5 tests=[AWL=0.318,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
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 fQNC65XTNq0P for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 18:48:53 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 6D0C63A66B4 for <rrg@irtf.org>; Sun,  1 Feb 2009 18:48:53 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KEF00G0C3SO6K@szxga04-in.huawei.com> for rrg@irtf.org; Mon, 02 Feb 2009 10:48:24 +0800 (CST)
Received: from x41208a ([10.111.12.103]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KEF00A313SNK0@szxga04-in.huawei.com> for rrg@irtf.org; Mon, 02 Feb 2009 10:48:24 +0800 (CST)
Date: Mon, 02 Feb 2009 10:48:23 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <6DE40C2A-7621-4D06-959B-E88C1E04C592@cisco.com>
To: 'Dino Farinacci' <dino@cisco.com>, "'Joel M. Halpern'" <jmh@joelhalpern.com>
Message-id: <000b01c984e0$b74e6a00$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: AcmEqKcfYpzBzvZKTLysi2rXsXI1lAANgjVg
Cc: 'rrg RG' <rrg@irtf.org>
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as	to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> 
> > I don't think those are the only two alternatives.  For example, 
> > something like the APT idea where the full mappings are 
> shipped to a 
> > set of devices such that such a full set is near to and on 
> the query 
> > path of any leaf is an alternative worth examining.
> 
> We have stated before that LISP-ALT routers could cache 
> mappings. This can help with Map-Request latency. And if the 
> mappings are cached do to seeing Map-Replies or because they 
> are pushed with some other protocol, then so be it.

Does that mean the mapping system ( ALT overlay ) would spread some outdated
mapping informations to the ITRs? Besides, will it make the ALT router
become another vulnerable place?

Xiaohu 

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Feb  1 22:53:30 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDAF03A68A5; Sun,  1 Feb 2009 22:53:30 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58C713A68A5 for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 22:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.39
X-Spam-Level: 
X-Spam-Status: No, score=-5.39 tagged_above=-999 required=5 tests=[AWL=-0.869,  BAYES_00=-2.599, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_MED=-4,  SUBJ_ALL_CAPS=2.077]
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 PHzNDNtwEXrg for <rrg@core3.amsl.com>; Sun,  1 Feb 2009 22:53:27 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 4814F3A63D2 for <rrg@irtf.org>; Sun,  1 Feb 2009 22:53:24 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n126qmlv001938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Feb 2009 22:52:53 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n126qmZl028191; Sun, 1 Feb 2009 22:52:48 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n126qmif028186; Sun, 1 Feb 2009 22:52:48 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 1 Feb 2009 22:52:47 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 1 Feb 2009 22:52:46 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10581F2E9@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <49858CB6.9020609@firstpr.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RANGER-06
Thread-Index: AcmEYxkwgHUCUbvsTTSBwEmREj8nwQALmMMg
References: <49858CB6.9020609@firstpr.com.au>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Robin Whittle" <rw@firstpr.com.au>, "RRG" <rrg@irtf.org>
X-OriginalArrivalTime: 02 Feb 2009 06:52:47.0781 (UTC) FILETIME=[DB9EB550:01C98502]
Subject: Re: [rrg] RANGER-06
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Robin,

Thank you for your consideration of RANGER. Please see
below for my responses: 

> -----Original Message-----
> From: Robin Whittle [mailto:rw@firstpr.com.au] 
> Sent: Sunday, February 01, 2009 3:51 AM
> To: RRG
> Cc: Templin, Fred L
> Subject: RANGER-06
> 
> Short version:    I read the RANGER I-D and came away without
>                   any substantial understanding of what RANGER
>                   is supposed to achieve, in terms of scalable
>                   routing and addressing,

Scalable routing and addressing in RANGER has exactly the
same considerations as LISP, APT, and the other map/encaps
variants. It uses IP-in-IP encapsulation, with the outer
IP addresses taken from prefixes already published in BGP
routing tables in the global DFZ, and with inner IP
addresses taken from prefixes taken from a mapping table
kept separate from the global routing table. You have
heard me say it before, but IMHO to get to true scalable
routing and addressing we will need to eventually transition
to using IPv6 as the inner IP protocol for the long term.
But, nothing in the RANGER architecture depends on this.

>From a top-level perspective, RANGER is in many respects
th  offspring of a map/encaps lineage that includes (from
latest to eldest) RFC5214, RFC4380, RFC4213, RFC2529,
RFC2003, RFC1955, and certainly others that I am missing.

>                   or what new capabilities
>                   or requirements it has for hosts - different from
>                   how the IPv4 and IPv6 Internets work today.

No new capabilities or requirements for hosts. RANGER is
about xTR interactions in the network with unmodified hosts
at the edges. The hosts may be able to benefit from deploying
complementary mechanisms themselves in the future, but this
would be a separate transition and completely independent
of the RANGER domain of application.
 
> Hi Fred,
> 
> Here are my thoughts when reading and trying to understand:
> 
>   http://tools.ietf.org/html/draft-templin-ranger-06
> 
> In the absence of any Summary and Analysis on the RRG wiki, and
> without actually reading the various related I-Ds, I am hoping to
> understand enough of RANGER by reading the above I-D - to decide
> whether I want to read the other documents.
> 
> I thought I had a half-way decent understanding of SEAL from early
> 2008, but I wouldn't want to be examined on it, and I haven't kept up
> with your revisions since then.

Both the SEAL spec and prototype code have been stable
for a long time now.
 
> I don't really understand VET or ISATAP - but I figure I shouldn't
> have to read a bunch of other documents in order to develop a
> reasonable overview of RANGER.

RANGER is an architectural overview, and VET and SEAL
are functional building blocks. RANGER's job is to lead
the way for the other documents.

> You gave a summary:
> 
>   RANGER BOF - call for participation
>   http://www.irtf.org/pipermail/rrg/2009-January/000909.html
> 
> While I understand that RANGER is intended to be a solution to the
> routing and addressing problems we are all trying to solve, I
> couldn't figure out from the summary whether RANGER is:
> 
>   1 - A core-edge separation scheme (LISP, APT, Ivip, TRRP)

This is in fact exactly what RANGER is about.

>   2 - A core-edge elimination scheme - usually done with
>       changes in hosts, such as with HIP.

As stated earlier, the RANGER domain of application
focuses on the same xTR problem space as for LISP and
the others, and as such any host changes would be out
of scope. There is a sole exception that RANGER allows
end hosts to configure tunnel endpoints in certain
enterprise use cases, but that would be pushing the
RANGER core/edge separation all the way to the end
host as opposed to introducing a core-edge elimination
scheme. Such end hosts would generally be better served
to attach themselves to a native link of the inner IP
protocol and allow xTRs in the network to do any
necessary map/encaps, but in some cases there is
no other option.

>   3 - Something else.
> 
> The first two classes are discussed in:
> 
>       Towards a Future Internet Architecture: Arguments for
>       Separating Edges from Transit Core
>       Dan Jen, Lixia Zhang, Lan Wang, Beichuan Zhang
>       http://conferences.sigcomm.org/hotnets/2008/papers/18.pdf
> 
> I got the clear impression that RANGER is intended to work with both
> IPv4 and IPv6 and enable a recursive application of the same "network
> within a network" structure, with one of the goals being the re-use
> of at least some parts of the address space as separate namespaces in
> separate networks.  There are lots of encapsulating tunnels, with
> SEAL somehow taking care of the PMTU problems these cause.  IPv4 can
> travel in IPv6 tunnels and vice-versa.
> 
> At this point, I wanted to know:
> 
>   1 - Is this intended to be a complete scalable routing solution?

Yes.

>   2 - Assuming this is the case, to what extent are host stack, API
>       and application changes required?

No host stack/API/app changes.

>   3 - I knew "mapping" was somehow involved in RANGER, but the
>       introduction does not mention it, and I want to know how this
>       concept in RANGER compares with its use in LISP, APT, Ivip etc.

RANGER supports mapping in two ways. First, ITRs that
have a packet to send but no matching FIB entry can
either discard or queue the packet while they lookup
the mapping in the mapping system. (VET uses DNS syntax
as the "front-end" for mapping lookups, but the back-end
could be any sort of distributed database that stores
the mapping tables.)

In the second method, the ITR forwards a packet to a
default mapper (i.e., just like APT) and gets an ICMP
redirect back. The packet gets stretched, but the ICMP
redirect provides route optimization for future packets. 

>   4 - What sort of introduction plan you had in mind, including
>       immediate benefits to those end-user networks and ISPs which
>       adopt it - together with costs, risks, changes to networks,
>       hosts etc.

I think this is exactly the same analysis that the
LISP and APT approaches need to look at. But, RANGER
is advocating a transition to IPv6 also.
 
> I am up to page 12 and will summarise my questions so far.
> 
> Then I will read on and write further comments.
> 
> In the terminology section, or in some early section, I think you
> really need to give the reader a good functional understanding of
> some of the building blocks of RANGER.  These include:
> 
>    The mapping system.  There are frequent references to this, but
>    by page 12, no description of its purpose, structure or
>    functionality.
> 
>    VET.  From the "Terminology" section:
> 
>       Virtual Enterprise Traversal (VET) [I-D.templin-autoconf-dhcp];
>       functional specifications and operational practices that
>       provide a functional superset of 6over4 and ISATAP.  In
>       addition to both unicast and multicast tunneling, VET also
>       supports address/prefix autoconfiguration as well as additional
>       encapsulations such as IPSec, SEAL, LISP, etc.
> 
>    This is very broad-brush, so I read the abstracts:
> 
>       http://tools.ietf.org/html/draft-templin-autoconf-dhcp-32
> 
>          Enterprise networks connect routers over various link types,
>          and may also connect to provider networks and/or the global
>          Internet.  Nodes in enterprise networks must have a way to
>          automatically provision IP addresses/prefixes and other
>          information, and must also support internetworking operation
>          even in highly-dynamic networks.  This document specifies a
>          Virtual Enterprise Traversal (VET) abstraction for
>          autoconfiguration and operation of nodes in enterprise
>          networks.
> 
>       http://tools.ietf.org/html/rfc2529  (6over4)
> 
>          This memo specifies the frame format for transmission of
>          IPv6 packets and the method of forming IPv6 link-local
>          addresses over IPv4 domains.  It also specifies the content
>          of the Source/Target Link-layer Address option used in the
>          Router Solicitation, Router Advertisement, Neighbor
>          Solicitation, and Neighbor Advertisement and Redirect
>          messages, when those messages are transmitted on an IPv4
>          multicast network.
> 
>          The motivation for this method is to allow isolated IPv6
>          hosts, located on a physical link which has no directly
>          connected IPv6 router, to become fully functional IPv6 hosts
>          by using an IPv4 domain that supports IPv4 multicast as
>          their virtual local link. It uses IPv4 multicast as a
>          "virtual Ethernet".
> 
>             (IPv4 multicast??  Who actually uses this in big
>              networks?  It doesn't work in the DFZ.  I see later
>              that there is some explanation of this in section 4.1
>              of the RANGER I-D.)
> 
>       http://tools.ietf.org/html/rfc5214  (ISATAP)
> 
>         The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
>         connects dual-stack (IPv6/IPv4) nodes over IPv4 networks.
>         ISATAP views the IPv4 network as a link layer for IPv6 and
>         supports an automatic tunneling abstraction similar to the
>         Non-Broadcast Multiple Access (NBMA) model.
> 
>    Lacking detailed understanding of all the above, I have a vague,
>    open, notion of VET being a means of connecting things via
>    tunnels, though I have no idea what this means with multicast, or
>    with "LISP encapsulation" .
>
> Now to the I-D:
> 
> Page 6:
> 
>   What is meant by "next generation enterprise networks"?

A next-generation enterprise network is one which
deploys xTRs at border routers. This can either be
through building a brand new enterprise network from
scratch or by simply placing xTR-equipped border
routers at the edges of existing enterprise networks.

>   I think I get the notion of "enterprises within enterprises" -
>   including with inner enterprise networks running their own BGP
>   which is separate from that of the outer enterprise.
> 
>   I don't understand how this differs in a functional sense from what
>   can be done today with conventional techniques.  Also, how many
>   enterprises want to be connected to the rest of the world solely
>   from within another?

Using VET, each enterprise network appears as a virtual
Non-Broadcast, Multiple Access (NBMA) link, and multiple
enterprises are joined by xTRs that connect the links
together.

> Page 8:
> 
>   I understand VET can connect multiple sub-enterprises within one
>   enterprise, with the sub-enterprises using the outer enterprise's
>   addressing system, or having their own.
> 
>   I want to know how DNS works in the latter scenario.  I think of
>   DNS as a global system returning (in addition to MX records,
>   sub-domains and potentially other things) one or more IP addresses
>   for a given FQDN.  While I have heard of plans to make DNS supply
>   different answers for requests from different places (and while I
>   know there are good purposes for this in the global Internet to
>   cause sessions to go to servers which are generally physically
>   close to the requesting host) I want to know how DNS can work if
>   some enterprises are using some numeric range of what is to other
>   enterprises "public" address space in a different, private,
>   manner than the other enterprises.
> 
>   With IPv6, there's plenty of space - so why would any network
>   want to reuse part of it which someone else is already using?
> 
>   With IPv4, there is not enough - but how could reusing part of
>   the global public space be a good idea, since it would seem to
>   require that local hosts not be able to access some parts of
>   the public address space outside?

No, there is no re-use of inner IP address space; there
is only re-use of outer IP address space. And, the DNS
arrangement in VET calls for each enterprise to have
an enterprise-specific domain name (e.g., "example.com")
and arrange the inner IP address mappings as strings of
nibbles within that domain name. For example, for the
IPv6 prefix 2001:db8::/56 the mapping would appear as:

0.0.0.0.d.b.8.0.1.0.0.2.ip6.isatap.example.com

But, you really need to look to VET to get to this level
of detail.

> 
> Page 9:
> 
>      "The prefixes could be either Provider-Independent (PI) prefixes
>       owned by the BR or Provider-Aggregated (PA) prefixes delegated
>       by the BG, but the prefixes are linked with mapping and routing
>       over the virtual topology in both cases."
> 
>    I don't understand how prefixes could be "linked".   I still have
>    no idea what "mapping" means in the context of RANGER.
> 
>      "Additionally, fault tolerance and multihoming is naturally
>       afforded through configuration of multiple BGs per enterprise."
> 
>    I haven't seen a diagram depicting multihomed networks, only one
>    network within another.
>
>    Searching ahead I find a section on
>    Multihoming, on page 16 and am alarmed to discover that HIP may
>    be required to do it!

Whoops - time out! I think it is important to stop at
this point and making a clear differentiation between
*site* multihoming and *end system* multihoming. RANGER
is meaning to talk *only* about the former, while HIP
and others deal with the latter.  

>       "At the enterprise edge, a true location/identity split
>        approach such as HIP may be necessary for supporting true
>        multihoming across multiple physical links with diverse
>        properties."
>
> Page 10, para 2:
> 
>    I understand that PA prefixes are handed downwards, from routers
>    closer to the DFZ to routers in sub-networks, and then from
>    those routers potentially to further sub-networks etc.
> 
>    I also understand that PI prefixes are announced (by some
>    secure means, I assume) from the lower levels and the upper
>    layer routers carry the announcement, advertisement whatever
>    to make the prefix appear to the rest of the world.
> 
>    But I still have no idea what RANGER's "mapping system" is, so
>    I can't understand the following at all:  Regarding PI prefix
>    information propagating upwards, via "registration":
> 
>       "This registration results in updates to the mapping system,
>        which can later be used to populate a BR's Forwarding
>        Information Base (FIB)."
>
> Page 11 para 3:
> 
>    Again, there is mention of mapping: "mapping database lookups"
>    but I still have no idea what this means.
> 
>    I gather that VET can have more than two networks connected to
>    it, as per Figure 3, and that the connections need not always
>    be maintained.   So I wonder how it scales if the traffic does
>    need to maintain them.  If there are 100 networks connecting
>    via VET, are there 100 * 99 separate sets of two-way tunnel?
> 
> 
> OK - now I am at page 13, with more questions than understanding.
> 
> What exactly are "legacy services" in this context.  I figure they
> are the global behaviours of the entire IPv4 and IPv6 Internets as
> perceived by any participating host today.

Legacy services are services that were in place before
any inner IP addresses and prefixes were introduced into
the routing and addressing architecture. For example, if
inner IP addresses were IPv6 and outer IP were IPv4, the
legacy services would be any IPv4 services.

> But this is page 13, and there has been no description of what is
> different, from a host point of view, or in terms of DNS, about the
> new RANGER architecture.

No differences for any hosts.
 
> What is it you are trying to do which is different from today's
> Internets?
> 
> A quick scan of page 13 turns up, in the last para, mention of NAT in
> some intermediate network as part of providing "legacy services".
> NAT is to be avoided if at all possible.
> 
> I still don't understand why enterprises want to be recursively
> nested.

Let's call the existing Internet a gigantic Enterprise
network - after all, it is an "enterprise" in which all
DFZ routers throughout the world have a mutual spirit
of cooperation but with the potential for competing
interests or even conflict. Let's say that each major
corporation or ISP attached to the DFZ (e.g., Boeing,
Comcast, etc.) was an enterprise unto itself which would
be organized at a lower level of recursion removed from
the global Internet DFZ. Then, within each such major
enterprise there may be distinct "sites" (e.g., europe,
asia, the americas, etc.) and within each of those
distinct sites there may be other sites, etc. etc.

Now, let's look at it the other way around and suppose
that some parallel Internets were to come into being
that were totally separate from the Internet of today.
Each of those distinct Internets would be a separate
enterprise, and each could be interconnected across
a commons at a higher layer of recursion. And it is
also possible to postulate still higher layers of
recursion above that etc. etc.  

> For multihoming, don't they want two or more physically
> diverse connections to the DFZ, as short and fat as possible?

Site multihoming is indeed possible and encouraged.

> If multihoming with RANGER requires host changes, such as with HIP,
> then isn't this a complete non-starter in terms of any routing
> scaling solution, which has to be adopted enthusiastically and
> voluntarily by the great majority of end-user networks?

As I have been saying, RANGER and HIP are completely
separate mechanisms, where RANGER supports site
multihoming and HIP supports end system multihoming.
RANGER without HIP is the first-order deployment
scenario. HIP at a later time is possible, but has
nothing whatsoever to do with the RANGER deployment.
 
> Page 14:
> 
>      "IPv4 NAT capability however this approach requires multiple
>       instances of stateful NAT devices on the path which can lead to
>       an overall degree of brittleness and intolerance to routing
>       changes."
> 
>    This makes me think RANGER is some kind of radical revision of
>    both IPv4 and IPv6 in a way which makes current hosts, DNS etc.
>    non-functional, or only partially functional - and therefore to
>    be known as "legacy" and afforded special treatment.
> 
>    What are the unique advantages of changing much of the Net over
>    to this RANGER model?   LISP, APT, Ivip and TRRP etc. provide
>    multihoming without any host changes, but it seems RANGER can't
>    provide it, except with the complete host changes of HIP.
> 
> I can't make head or tail of section 3.2.3.
> 
> In 3.3 I understand that SEAL will somehow enable the creation of
> good tunnels, with proper management of PMTUD, in an environment
> where ICMP messages, particularly RFC 1191 Packet Too Big (PTB)
> messages may be either lost or spoofed.
> 
> 
> Page 15:
> 
>   "mapping/routing"??
> 
> 
> Page 16:
> 
>   I haven't tried to follow all the mobile stuff, but I have a
>   question about the airliner with a PI prefix which it announces
>   at one ground station, and then the next (say 1/3 the way around
>   the planet).
> 
>   As long as this is a real, public, PI prefix, then in order to
>   ensure optimal paths, potentially all routers in the DFZ will
>   need to adapt to the change.  It doesn't matter how many
>   layers of networks there are between the DFZ and those
>   ground points, or whether the ground points are owned by the
>   same network or not.  Moving PI space requires BGP changes -
>   and this is an unscalable approach considering the number of
>   aircraft travelling in this way.   A solution is the TTR
>   approach, in which this specific problem is discussed:
> 
>     http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf
> 
>   I still don't have any clear idea of what RANGER is supposed to
>   achieve or how it helps with mobility.

There is no intention whatsover that a fast-moving site
announce and withdraw PI prefixes frequently in a slow-
converging mapping system like the BGP. Boeing has learned
some lessons about this, and RANGER is not in any way
linked to or modeled after those earlier efforts.

Just as for multi-homing, RANGER intends to address *site*
mobility and allow other mechanisms to address *end system*
mobility if necessary.

>   The TTR approach avoids the need for the mobile node to ever
>   renumber its public, numerically stable, physically globally
>   mobile, address, no matter how many CoAs it has.  So there is
>   no breaks in sessions, as long as connectivity is maintained
>   via one CoA or another in any access network, including behind
>   NAT.
> 
> Section 3.5 on multihoming:
> 
>   If an enterprise advertises a prefix to multiple upstream
>   BGs, how do these advertise it upwards to the DFZ?  What if
>   the link to one BG becomes unusable, but that BG is still
>   advertising the prefix to the DFZ?

The prefix times out and goes away. If the link comes
back, the prefix will eventually come back.

>   Is HIP really needed for multihoming with RANGER?

HIP end-system mobility and multihoming are distinct and
separate from RANGER site mobility and multihoming as
addressed several times above.

>   If so, this requires the hosts to get a separate address
>   from each PA prefix from each upstream ISP/whatever.  But
>   the first two sentences of this section involve the network
>   advertising a PI prefix (or multiple PI prefixes) with
>   every upstream BG.  This is like traditional BGP-based
>   multihoming today - and not related at all to the PA based
>   HIP approach.
> 
> 
> 
> Page 17:
> 
>        "4.4. The Locator Identifier Split Protocol (LISP)
> 
>         The Locator-Identifier Split Protocol (LISP)
>         [I-D.farinacci-lisp] proposes a map-and-encaps architecture
>         for scalable routing and addressing within the global
>         Internet Default Free Zone (DFZ).  Several companion
>         documents (e.g., LISP-ALT, LISP-CONS, LISP-EMACS,
>         LISP-NERD) propose mapping function solutions.  A related
>         mapping function solution proposal is found in
>         [I-D.jen-apt]."
> 
> APT is not related to LISP, in my view.  It has some common
> characteristics, such as non-real-time mapping and each ITR having to
> do reachability testing to each ETR etc.
> 
> However, APT is more than a mapping distribution system.  It is
> completely different from LISP-NERD on one hand and the other LISP
> approaches on the other, in that it uses local query servers.
> 
>         "LISP, and a number of related proposals being discussed in
>          the Routing Research Group, share common properties with the
>          solution proposed here."
> 
> I have no idea what common properties these are.
> 
>        "They may therefore be architecturally consistent with
>         the RANGER architecture."
> 
> 
> I have spent a few hours trying to understand RANGER - its purpose,
> its changes to host and DNS behavior, its support for multihoming,
> its support for today's IPv4 and IPv6 Internet host and DNS behaviour
> ("legacy").  I still have no clear idea what RANGER is supposed to
> achieve or how it works.

You should really look at VET and SEAL too.

> Does RANGER complement a global LISP, APT or Ivip system?
> 
> If so, then is it a solution to the scalable routing problem on its
> own?  If so, then why would anyone want LISP, APT or Ivip?

Beginning with the ISATAP model, the RANGER approach began
examining "small" enterprise networks (like a SOHO network,
a mobile ad-hoc network, etc.) but it soon became clear
that the enterprise-within-enterprise model could recurse
upwards into larger and still larger enterprises until
ultimately the core of the global Internet itself could
be viewed as an enterprise network in exactly the same
way. So yes, RANGER has popped up the stack into the
same solution space the other proposals are targeting.

> If not, then why do we want to know about it here?  What does it add
> to the scalable routing solution which is not already provided by
> LISP, APT or Ivip?
> 
> The final section on Security again fails to connect with my mind in
> a concrete enough fashion to form real understanding.
> 
> I need overall goals, purpose etc.  I need to know where this scheme
> fits with other schemes - does it complement a core-edge separation
> scheme, is it one in itself or is it something else?  I need to have
> a rough understanding of the behaviour of the building blocks - SEAL
> and VET - so I can envisage what RANGER builds them into.  I have
> some understanding of SEAL, but none of VET.  I think the RANGER I-D
> needs to be self-contained, so people who don't already know of your
> specific building blocks can learn enough about them to understand
> your description of how RANGER would work.

RANGER, VET and SEAL should really be read as multiple
chapters of the same book. I'm sorry if you don't feel
it should be this way, but I think you would find many
similar examples in the published literature (the IPsec
RFC series comes to mind).

Thanks - Fred
fred.l.templin@boeing.com

> 
>   - Robin
> 
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 08:38:07 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50C8328C154; Mon,  2 Feb 2009 08:38:07 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06A7728C154 for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 08:38:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.575
X-Spam-Level: 
X-Spam-Status: No, score=-1.575 tagged_above=-999 required=5 tests=[AWL=0.320,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
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 Olo9JagRAxHG for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 08:38:04 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 5D4A93A68EC for <rrg@irtf.org>; Mon,  2 Feb 2009 08:38:04 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 50B0E175D1F; Tue,  3 Feb 2009 03:37:44 +1100 (EST)
Message-ID: <49872103.7020602@firstpr.com.au>
Date: Tue, 03 Feb 2009 03:36:19 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <49858CB6.9020609@firstpr.com.au> <39C363776A4E8C4A94691D2BD9D1C9A10581F2E9@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10581F2E9@XCH-NW-7V2.nw.nos.boeing.com>
Subject: Re: [rrg] RANGER-06
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Fred,

Thanks for these clarifications.  I am surprised, based on what I
read in the I that RANGER I-D:

  http://tools.ietf.org/html/draft-templin-ranger-06

that RANGER resembles LISP, APT or Ivip in that it has xTRs (ITRs and
ETRs) and a mapping system.  There is no mention of xTRs in the I-D.

I hope you will explain this more clearly, on the RRG list and/or in
a revised I-D - including by giving detailed examples and
explanations of many things, such as:

 0 - The major architectural differences between RANGER and other
     comparable schemes, such as LISP-ALT - and what benefits and
     problems arise from RANGER compared to some alternatives.

 1 - How the mapping system works from the point of view of the
     ITR.  This includes what actual data is in the mapping for
     each EID or whatever it is which is a unit of address space
     ("inner" address space, I think, in your terminology) which
     has a common treatment at ITRs.

 2 - Who controls the mapping - from an administrative point of view
     - and in a technical sense: what are the query servers which
     respond to mapping queries.   I gather it is a global query
     server system as with LISP-ALT or TRRP and that ITRs are all
     caching ITRs.

     Are the mapping queries and the query servers which send back
     the reply all operating on the "outer" address space, the
     "inner" or both?

 3 - How ITRs do reachability testing to ETRs, and make decisions
     about which ETR to use.  Ivip doesn't do it this way, but LISP
     and APT do - so as far as I know, so does RANGER.

 4 - One or two concrete examples of site multihoming.

 5 - Likewise RANGER's "site mobility" and an explanation of how this
     differs in principle and practice from "end system mobility".

 6 - What "reuse of outer address space" means, with some examples.
     I gather that, for instance, IPv4 space would be "outer" in the
     way you are depicting RANGER - analogous to LISP's RLOC space.
     "Inner space" I think is analogous to LISP's EID space - and
     in your preferred example is IPv6 space.

 7 - I understand a "legacy" host, such as an IPv4 host would keep
     working normally, and wouldn't be able to access anything in the
     inner address space (IPv6).  But what about existing IPv6
     hosts in networks which don't implement RANGER?  Will they
     still be able to communicate with any IPv6 host in any of the
     RANGER equipped networks?

 8 - I understand, in your preferred example, that IPv4 acts like
     RLOC space and IPv6 like EID space.  I guess that means that
     each network somehow only needs to have a routing system which
     handles a subset of the IPv6 space, with the rest accessible
     via ITRs and the mapping system.

     If you could explain clearly how RANGER achieves a reduction in
     DFZ size, while providing multihoming, TE and portability, that
     would be great.  I guess this means the IPv4 DFZ, where
     all the VET tunnels occur.  Is there anything like an IPv6 DFZ
     in RANGER?


It is always difficult explaining something new to people you you
don't know, via a unidirectional link such as a written document.  It
is hard to avoid using terms which mean something detailed and
specific to the author, but mean little - or something different - to
the reader.

Your response has definitely helped me understand what you are trying
to achieve, but I probably won't be diving into VET or SEAL soon.  My
overall experience is that you describe things in such high-level
terms, quite a few of which I don't understand in the specific way
you do, and that I have a very hard time constructing a nuts and
bolts model in my head of what RANGER would be like.

It helps to know the goals of RANGER - as I think you have described
more clearly in this reply than I in the I-D.  However, in order for
me to I feel I understand something I need to imagine a number of
building blocks which I understand very clearly, and then imagine
them strung together and interacting.

Then I can start to consider whether I think the whole thing will work!

I probably won't have time to build such an understanding of RANGER
in the foreseeable future, but I am keen to read anything more you
can say about it on the list, and I am sure other people would be
interested too.

  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 09:05:10 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B385D3A6A4B; Mon,  2 Feb 2009 09:05:10 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 522B13A6BBD for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 09:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.538
X-Spam-Level: 
X-Spam-Status: No, score=-6.538 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 TzstOujdRDVX for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 09:05:09 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 82C703A6973 for <rrg@irtf.org>; Mon,  2 Feb 2009 09:05:08 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,366,1231113600"; d="scan'208";a="35618887"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 02 Feb 2009 17:04:34 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n12H4XmU012494;  Mon, 2 Feb 2009 12:04:33 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n12H4XC9005154; Mon, 2 Feb 2009 17:04:33 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 12:04:33 -0500
Received: from cisco.com ([10.86.245.246]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Feb 2009 12:04:32 -0500
Date: Mon, 2 Feb 2009 12:04:31 -0500
From: Scott Brim <swb@employees.org>
To: Christian Vogt <christian.vogt@ericsson.com>
Message-ID: <20090202170431.GB1164@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Christian Vogt <christian.vogt@ericsson.com>, Dino Farinacci <dino@cisco.com>, rrg RG <rrg@irtf.org>, int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com> <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 02 Feb 2009 17:04:32.0984 (UTC) FILETIME=[51A03580:01C98558]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: routing-discussion@ietf.org, rrg RG <rrg@irtf.org>, int-area@ietf.org, lisp@ietf.org
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Christian Vogt on Sat, Jan 31, 2009 11:49:46AM -0800:
> I think we should experimentally compare ALT with other mapping
> systems before we decide whether pull-based or push-based mapping
> systems are better.  Dismissing push-based mapping systems without
> corroborating data would be a bit premature in my opinion.

I don't believe push-based mapping systems have been dismissed.  They
are still a valid option, and one that could be pursued at any time.
Some of us made an initial evaluation that pull-based systems are
better, but with experience that might change, and it can.  

Push-based and pull-based systems can coexist as long as their
protocols aren't too constrained.  A push-based system can act as a
representative for the sites it serves and inject mapping information
for them into a pull-based system, and so on.  

APT default mappers are something like hybridization points between
push and pull, but there are control messages which bypass them, so
the parallel isn't really exact.

> In the absence of experimentation results, I would actually argue in
> favor of push-based mapping systems based on some analytical reasoning:
> Pull-based mapping systems have two important disadvantages compared to
> push-based mapping systems:
>
> - Performance penalty, i.e., additional propagation latencies for some
>   packets, and higher loss probabilities for packets that take a sub-
>   optimal path
>
> - Robustness penalty due to a new online dependency on components off
>   the actual transmission path.  (FWIW: All pull-based mapping systems
>   have this penalty.  Mapping requests must be routed via overlay
>   infrastructure because the direct route is unknown at that time.)

And a push-based system is either very "chatty" or its state is
decoupled from operational reality.  With a pull-based system you can
have the authoritative sources of information be directly coupled to
the operational liveness of the ETRs -- they can be the ETRs
themselves.  You can get this with a push-based system but only at the
cost of a lot of messages sent without actually knowing if the
information will be used.

A push-based system has extra equipment, and administration, as well.
They all do.

But this is all initial evaluation.  

Scott
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 09:07:35 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3578B3A6BC5; Mon,  2 Feb 2009 09:07:35 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C16628C24D for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 09:07:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 V1g9hTN8EVrC for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 09:07:33 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 488163A6BBD for <rrg@irtf.org>; Mon,  2 Feb 2009 09:07:33 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,366,1231113600"; d="scan'208";a="35658235"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 02 Feb 2009 17:06:13 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n12H6DBi013624;  Mon, 2 Feb 2009 12:06:13 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n12H6DoK005957; Mon, 2 Feb 2009 17:06:13 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 12:06:13 -0500
Received: from cisco.com ([10.86.245.246]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Feb 2009 12:06:12 -0500
Date: Mon, 2 Feb 2009 12:06:03 -0500
From: Scott Brim <swb@employees.org>
To: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
Message-ID: <20090202170603.GC1164@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, Christian Vogt <christian.vogt@ericsson.com>, int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org, rrg RG <rrg@irtf.org>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com> <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com> <E1LTYfI-000315-00@mta2.cl.cam.ac.uk>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <E1LTYfI-000315-00@mta2.cl.cam.ac.uk>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 02 Feb 2009 17:06:12.0825 (UTC) FILETIME=[8D22BC90:01C98558]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, Christian Vogt <christian.vogt@ericsson.com>, routing-discussion@ietf.org, lisp@ietf.org
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to whether a	WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Jon Crowcroft on Sun, Feb 01, 2009 09:30:55AM +0000:
> you can push info multiply redundently
> (or cross-post:)
> and you get reliability with a silly overhead
> 
> or you can push an update which is wrong and disconnect the entire
> world, e.g.
> http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html
> 
> so aside from the basic academic type scaling, has anyone done
> this sort of disaster-prone analysis for LISP/ALT?

There is a concern about misconfiguration.  Certainly you want at
least doublechecking, and possibly signatures.

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 09:40:05 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A4583A692A; Mon,  2 Feb 2009 09:40:05 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38F293A6B35 for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 09:40:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level: 
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 kikHXpvDDiJE for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 09:40:03 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 726CC3A67F4 for <rrg@irtf.org>; Mon,  2 Feb 2009 09:40:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,366,1231113600"; d="scan'208";a="35662708"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 02 Feb 2009 17:38:43 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n12Hchnm014364;  Mon, 2 Feb 2009 12:38:43 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n12HchOU019090; Mon, 2 Feb 2009 17:38:43 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 12:38:43 -0500
Received: from cisco.com ([10.86.245.246]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Feb 2009 12:38:42 -0500
Date: Mon, 2 Feb 2009 12:38:38 -0500
From: Scott Brim <swb@employees.org>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Message-ID: <20090202173838.GD1164@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, rrg@irtf.org, int-area@ietf.org
References: <B0585DFE-4A47-481C-BABB-881BF179F827@cisco.com> <39C363776A4E8C4A94691D2BD9D1C9A10581F02F@XCH-NW-7V2.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10581F02F@XCH-NW-7V2.nw.nos.boeing.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 02 Feb 2009 17:38:43.0066 (UTC) FILETIME=[1791E5A0:01C9855D]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: rrg@irtf.org, int-area@ietf.org
Subject: Re: [rrg] [Int-area] RANGER BOF - call for participation
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

If you hold it, I will come.
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 10:03:19 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B35903A6B4D; Mon,  2 Feb 2009 10:03:19 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD0403A690B for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 10:03:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.52
X-Spam-Level: 
X-Spam-Status: No, score=-6.52 tagged_above=-999 required=5 tests=[AWL=0.079,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 sGQoPeOUL45K for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 10:03:17 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 9A0E03A6BBB for <rrg@irtf.org>; Mon,  2 Feb 2009 10:03:16 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,366,1231113600"; d="scan'208";a="136635766"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-1.cisco.com with ESMTP; 02 Feb 2009 18:02:57 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n12I2vVl030150;  Mon, 2 Feb 2009 10:02:57 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n12I2vna005286; Mon, 2 Feb 2009 18:02:57 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 10:02:57 -0800
Received: from [192.168.5.39] ([10.21.72.103]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 10:02:57 -0800
Message-Id: <DB1368FD-77E4-4744-B299-413D5BDE86DC@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Xu Xiaohu <xuxh@huawei.com>
In-Reply-To: <000b01c984e0$b74e6a00$670c6f0a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 2 Feb 2009 10:02:58 -0800
References: <000b01c984e0$b74e6a00$670c6f0a@china.huawei.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 02 Feb 2009 18:02:57.0077 (UTC) FILETIME=[7A3A5E50:01C98560]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=894; t=1233597777; x=1234461777; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20[lisp]=20Please=20respond=3A=20 Questions=20from=20the=20IESG=20as=09to=09whether=20a=20WG=2 0forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=DhZdU8GywHBhRBa6wbh94Zqs+j2S3A4SYXvqDaEXzls=; b=elKQhf9tc13U6VXqQbeTBWRZ2TdSxxn4PsqXaArNBsaRHd2UPHQjnKaMEQ /UT6USrPhyZOHp7qCLvUeXuQjzqWGN+0Kpm1K6KH9Af0o88DQGv5Vx9n63Y/ afVujd0E+/5o1sxl/oCKA3tro+4H862zziDZipt+69xKgTR7/xP4o=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: 'rrg RG' <rrg@irtf.org>
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as	to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I said *could*. Don't take this for a design. There are lots of  
details lacking.

Dino

On Feb 1, 2009, at 6:48 PM, Xu Xiaohu wrote:

>>
>>> I don't think those are the only two alternatives.  For example,
>>> something like the APT idea where the full mappings are
>> shipped to a
>>> set of devices such that such a full set is near to and on
>> the query
>>> path of any leaf is an alternative worth examining.
>>
>> We have stated before that LISP-ALT routers could cache
>> mappings. This can help with Map-Request latency. And if the
>> mappings are cached do to seeing Map-Replies or because they
>> are pushed with some other protocol, then so be it.
>
> Does that mean the mapping system ( ALT overlay ) would spread some  
> outdated
> mapping informations to the ITRs? Besides, will it make the ALT router
> become another vulnerable place?
>
> Xiaohu
>

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 10:21:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A03C63A6BBB; Mon,  2 Feb 2009 10:21:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 906063A68CC for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 10:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599]
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 OVzf8stm-vkL for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 10:21:39 -0800 (PST)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by core3.amsl.com (Postfix) with ESMTP id D4CC43A6A09 for <rrg@irtf.org>; Mon,  2 Feb 2009 10:21:38 -0800 (PST)
Received: by yx-out-2324.google.com with SMTP id 8so590569yxg.37 for <rrg@irtf.org>; Mon, 02 Feb 2009 10:21:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=eLkE8TtCmmpmkBClsTC6cPY+6xAeVYSxvfoz8OS58VQ=; b=qgRKdhrdbQZufPN93bC4QIqxaap3tf0tTiuRHMXGE7iIszDMlSY5hJ0pPJFraOsyDJ qVQFWeKA9cOK2ZvQDheVYo72OzeT/ENMYfudu1S1iOfEG0BVna0Ux/WBhv8FfTx7NVU3 SQPZUwtVvNxEYDtEzL6mCKinSaL2Pj6UgG8FU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ZRXSiIDPLi1moEojHzu+u/lKQRKABB5r/YtLbUDzctVhYu6UJNVb+8491YmyczIwzl DjVZBt5WMxDW5H1RGQM4WTVn53lU7oiApbGVyCWBI2uObSMYilPFeZ6lliu14RFdTndC YfwCc999OVeSTdz/sav+DVXJfnySQ1lcEz9to=
MIME-Version: 1.0
Received: by 10.100.108.9 with SMTP id g9mr2929830anc.137.1233598879793; Mon,  02 Feb 2009 10:21:19 -0800 (PST)
In-Reply-To: <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>
Date: Mon, 2 Feb 2009 13:21:19 -0500
X-Google-Sender-Auth: 35f0d594bb93fbd4
Message-ID: <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Christian Vogt <christian.vogt@ericsson.com>
Cc: int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, rrg RG <rrg@irtf.org>, lisp@ietf.org
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Wed, Jan 28, 2009 at 6:18 PM, Christian Vogt
<christian.vogt@ericsson.com> wrote:
>
> On Jan 24, 2009, Dino Farinacci wrote:
>
>>> 4 - LISP-ALT's Aggregation implies provider dependence.
>>>    This is Christian Vogt's critique:
>>>    http://psg.com/lists/rrg/2008/msg00259.html
>>
>> Not true. Aggregation here is for the EID-prefix. Service providers do
>> not carry EID-prefixes in their cores so you don't depend on them. The
>> decoupling of the address creates this. The dependence is now on the
>> ALT. And if your site resides in a specific region of the world, you get
>> your EID-prefixes from that registry. So readdressing your domain would
>> only occur if you moved it from one region to another (let's leave
>> mobile ASes out of this for now).
>
>
> Dino -
>
> There is a tradeoff between EID portability and path stretch along the
> ALT topology, and I believe the tradeoff made in LISP/ALT has been
> revised a few times.
>
> Portability of EID prefixes requires that the ALT topology follows
> EID-addressing.  This leads to potentially longer-than-optimal paths
> along the ALT topology.  Vice versa, if path stretch is to be limited,
> then portability of EID prefixes must be restricted.
>
> According to your email to Robin, LISP/ALT currently makes the following
> tradeoff:  Portability of EID prefixes is limited geographically in
> order to curb path stretch along the ALT topology to the maximum that
> can happen within a geographical region.
>
> That's possible, of course.  The cost is that networks scattered over
> different parts of the world, such as those of enterprises with global
> presence, cannot use a continuous address space internally -- even if
> they all attach to the same provider.

cant they? I thought one of the nice things about the loc/id split was
I could number my internals out of whatever I wanted, spread over
creation and the attachment points were the only things that required
aggregation, no?

-Chris
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 10:44:29 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ACF33A6BD0; Mon,  2 Feb 2009 10:44:29 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE8353A6BD0 for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 10:44:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level: 
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 97xxqPJEqwsB for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 10:44:28 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 794453A6BCA for <rrg@irtf.org>; Mon,  2 Feb 2009 10:44:28 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,366,1231113600"; d="scan'208";a="35671663"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 02 Feb 2009 18:42:53 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n12IgrSa021687;  Mon, 2 Feb 2009 13:42:53 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n12IgruK012257; Mon, 2 Feb 2009 18:42:53 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 13:42:53 -0500
Received: from cisco.com ([10.86.245.246]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Feb 2009 13:42:52 -0500
Date: Mon, 2 Feb 2009 13:42:47 -0500
From: Scott Brim <swb@employees.org>
To: Christopher Morrow <morrowc.lists@gmail.com>
Message-ID: <20090202184247.GE1164@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Christopher Morrow <morrowc.lists@gmail.com>, Christian Vogt <christian.vogt@ericsson.com>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, rrg RG <rrg@irtf.org>, lisp@ietf.org
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 02 Feb 2009 18:42:53.0054 (UTC) FILETIME=[0E5771E0:01C98566]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org, Christian Vogt <christian.vogt@ericsson.com>, rrg RG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a	WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Christopher Morrow on Mon, Feb 02, 2009 01:21:19PM -0500:
> > According to your email to Robin, LISP/ALT currently makes the following
> > tradeoff:  Portability of EID prefixes is limited geographically in
> > order to curb path stretch along the ALT topology to the maximum that
> > can happen within a geographical region.
> >
> > That's possible, of course.  The cost is that networks scattered over
> > different parts of the world, such as those of enterprises with global
> > presence, cannot use a continuous address space internally -- even if
> > they all attach to the same provider.
> 
> cant they? I thought one of the nice things about the loc/id split was
> I could number my internals out of whatever I wanted, spread over
> creation and the attachment points were the only things that required
> aggregation, no?

Sure, but if one of your sites is in New Zealand, and has a prefix
where the physical ALT hierarchy is optimized for sites in Europe, a
source in New Zealand trying to contact your site would see more delay
during the Map-Request/Reply exchange, even though it they are in the
same town.  However, Map-Request/Reply exchanges don't happen very
often, and the delay will be low (round trip across the Internet).
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 10:57:03 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 258D13A6AC8; Mon,  2 Feb 2009 10:57:03 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA2CA3A69DD for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 10:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Level: 
X-Spam-Status: No, score=-6.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bGf6krsfQ6Vv for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 10:57:01 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 8BAFA3A6965 for <rrg@irtf.org>; Mon,  2 Feb 2009 10:57:01 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,366,1231113600"; d="scan'208";a="29131541"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 02 Feb 2009 18:55:42 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n12ItgcF027525;  Mon, 2 Feb 2009 10:55:42 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n12Itgl1010372; Mon, 2 Feb 2009 18:55:42 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 10:55:42 -0800
Received: from [192.168.5.39] ([10.21.72.103]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 10:55:42 -0800
Message-Id: <EF626220-08E0-48F3-AEB9-F2B2B9296458@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 2 Feb 2009 10:55:43 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 02 Feb 2009 18:55:42.0131 (UTC) FILETIME=[D8BF4830:01C98567]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=260; t=1233600942; x=1234464942; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20Please=20respond=3A=20Questions =20from=20the=20IESG=20as=20to=20whether=20a=20WG=20=20formi ng=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=LhcXUKaGnCWfZvjYhftMR5t4pbld6/Xgml14Zm+dP2g=; b=fhe04fqsVlBrD3CIFUklny6BISU4j9CsgPN6GzRFZFO/zeh3G8GaEs2QiP d/8ZyxP+60ldebxEWcU9erdC9LcA1q1LvaysXtzyjbMCHBev5RQD08HRwY7N 6A7l0f2CYkNYB54ikS7YhgES3rAPi5OfvPRZm6c8AJdo649TcBkvo=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org, Christian Vogt <christian.vogt@ericsson.com>, rrg RG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> cant they? I thought one of the nice things about the loc/id split was
> I could number my internals out of whatever I wanted, spread over
> creation and the attachment points were the only things that required
> aggregation, no?

Yes you can.

Dino

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 11:00:44 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3F8228C249; Mon,  2 Feb 2009 11:00:44 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8404928C249 for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 11:00:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.417
X-Spam-Level: 
X-Spam-Status: No, score=-6.417 tagged_above=-999 required=5 tests=[AWL=0.182,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 3j5KMCWaplYT for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 11:00:41 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 7AB0B28C245 for <rrg@irtf.org>; Mon,  2 Feb 2009 11:00:41 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n12J08u8000835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 2 Feb 2009 13:00:12 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n12J08GF028303; Mon, 2 Feb 2009 13:00:08 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n12J01bo027797; Mon, 2 Feb 2009 13:00:08 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 2 Feb 2009 11:00:04 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 2 Feb 2009 11:00:02 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10581F627@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <49872103.7020602@firstpr.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] RANGER-06
Thread-Index: AcmFVLBJj5jMQYF5Tt6HRcKrs/8j6AABl+6Q
References: <49858CB6.9020609@firstpr.com.au> <39C363776A4E8C4A94691D2BD9D1C9A10581F2E9@XCH-NW-7V2.nw.nos.boeing.com> <49872103.7020602@firstpr.com.au>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Robin Whittle" <rw@firstpr.com.au>, "RRG" <rrg@irtf.org>
X-OriginalArrivalTime: 02 Feb 2009 19:00:04.0377 (UTC) FILETIME=[750ED890:01C98568]
Subject: Re: [rrg] RANGER-06
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Robin,

Please see below for some follow-up: 

> -----Original Message-----
> From: Robin Whittle [mailto:rw@firstpr.com.au] 
> Sent: Monday, February 02, 2009 8:36 AM
> To: RRG
> Cc: Templin, Fred L
> Subject: Re: [rrg] RANGER-06
> 
> Hi Fred,
> 
> Thanks for these clarifications.  I am surprised, based on what I
> read in the I that RANGER I-D:
> 
>   http://tools.ietf.org/html/draft-templin-ranger-06
> 
> that RANGER resembles LISP, APT or Ivip in that it has xTRs (ITRs and
> ETRs) and a mapping system.  There is no mention of xTRs in the I-D.

Using the LISP terminology, the RANGER "Border Router (BR)"
in fact performs the xTR function. But, have we settled on
a common terminology for RRG (and perhaps other domains
also) such that all map/encaps proposals have to use that
terminology?  

> I hope you will explain this more clearly, on the RRG list and/or in
> a revised I-D - including by giving detailed examples and
> explanations of many things, such as:
> 
>  0 - The major architectural differences between RANGER and other
>      comparable schemes, such as LISP-ALT - and what benefits and
>      problems arise from RANGER compared to some alternatives.

RANGER treats each enterprise as a link and views all
BRs (i.e., all xTRs) as neighbors on the link. That
means that ordinary link-scoped neighbor discovery
mechanisms (RS/RA/NS/NA/Redirect) can be used between
BRs as if they were on-link neighbors.

RANGER is also about discovery of BRs that can be used
as exit gateways for forwarding packets to destinations
outside of the enterprise. A special subset of these
BRs are known as "Border Gateways (BGs)" and provide
a "default" routing capability. In APT, these are
known as "default mappers". In ISATAP and VET, they
are known as "Potential Router List (PRL)" routers.  

>  1 - How the mapping system works from the point of view of the
>      ITR.  This includes what actual data is in the mapping for
>      each EID or whatever it is which is a unit of address space
>      ("inner" address space, I think, in your terminology) which
>      has a common treatment at ITRs.

How the mapping system works and the actual data in the
mapping system  is covered in detail in (VET, section 5.3.3).

About EID, again this comes down to a terminology question.
I still think the LISP EID terminology is misleading in that
the thing EID refers to is an IP address that gets assigned
to an interface just like any other IP address. I'm not going
to beat on this further, but at the same time I don't want to
propagate the use of the term in RANGER if I don't have to.

>  2 - Who controls the mapping - from an administrative point of view
>      - and in a technical sense: what are the query servers which
>      respond to mapping queries.   I gather it is a global query
>      server system as with LISP-ALT or TRRP and that ITRs are all
>      caching ITRs.

There is a separate mapping service for each enterprise.
Border Gateways (which are also known as PRL routers in
ISATAP and VET, and are also known as "default mappers"
in APT) have synchronized mapping tables that cover all
inner IP prefixes reachable from within the enterprise.
Border Gateways also provide default forwarding services
for reaching inner IP prefixes that can only be reached
outside of the enterprise.

All BRs (i.e., all ITRs) cache the mappings they receive
in their Forwarding Information Base.

>      Are the mapping queries and the query servers which send back
>      the reply all operating on the "outer" address space, the
>      "inner" or both?

Using the default mapping option, Border Gateways are
themselves xTRs that receive encapsulated packets,
decapsulate them, and send encapsulated ICMP redirects
back. So, both outer and inner space are used

Using the DNS resolution option, the BR performing the
query can locate a DNS server using the outer IP address
space only and get back an outer IP (i.e., unencapsulated
DNS response). Alternatively, it can use encapsulated
DNS queries using both inner and outer address space.
This may in fact be an important consideration for
encapsulations that use IPsec. 

>  3 - How ITRs do reachability testing to ETRs, and make decisions
>      about which ETR to use.  Ivip doesn't do it this way, but LISP
>      and APT do - so as far as I know, so does RANGER.

With RANGER, mapping resolution returns a list of ETR
RLOCs that are potential next-hops toward an EID prefix.
Locator liveness testing is done in the data plane, and
if an RLOC appears to be failing, the ITR tries another.

>  4 - One or two concrete examples of site multihoming.

OK.
 
>  5 - Likewise RANGER's "site mobility" and an explanation of how this
>      differs in principle and practice from "end system mobility".

OK.

>  6 - What "reuse of outer address space" means, with some examples.
>      I gather that, for instance, IPv4 space would be "outer" in the
>      way you are depicting RANGER - analogous to LISP's RLOC space.
>      "Inner space" I think is analogous to LISP's EID space - and
>      in your preferred example is IPv6 space.

For example, the IPv4 address space behind most home
user's NAT boxes is taken from 192.168/16. That means
that that (outer) IP prefix space is spatially reused
among all such disjoint home networks.

>  7 - I understand a "legacy" host, such as an IPv4 host would keep
>      working normally, and wouldn't be able to access anything in the
>      inner address space (IPv6).  But what about existing IPv6
>      hosts in networks which don't implement RANGER?  Will they
>      still be able to communicate with any IPv6 host in any of the
>      RANGER equipped networks?

An IPv6 host on a native IPv6 link would not notice any
change if the IPv6 router were to begin using RANGER.
 
>  8 - I understand, in your preferred example, that IPv4 acts like
>      RLOC space and IPv6 like EID space.  I guess that means that
>      each network somehow only needs to have a routing system which
>      handles a subset of the IPv6 space, with the rest accessible
>      via ITRs and the mapping system.

Correct.
 
>      If you could explain clearly how RANGER achieves a reduction in
>      DFZ size, while providing multihoming, TE and portability, that
>      would be great.

Using the IPv6 example above, IPv6 prefixes go in the
mapping table of a parent enterprise only; they do not
go in the RIB of all parent enterprise border routers.

>      I guess this means the IPv4 DFZ, where
>      all the VET tunnels occur.

In the Internet core, yes - the IPv4 DFZ. In "child"
enterprises-within-enterprises, the VET tunnels occur
within the borders of those child enterprises.

>      Is there anything like an IPv6 DFZ
>      in RANGER?

Not that I can think of at the moment.

> It is always difficult explaining something new to people you you
> don't know, via a unidirectional link such as a written document.  It
> is hard to avoid using terms which mean something detailed and
> specific to the author, but mean little - or something different - to
> the reader.

Is there an agreed common terminology for RRG map/encaps?
If not, isn't it sufficient for RANGER to define its own
terms within its own scope?

> Your response has definitely helped me understand what you are trying
> to achieve, but I probably won't be diving into VET or SEAL soon.  My
> overall experience is that you describe things in such high-level
> terms, quite a few of which I don't understand in the specific way
> you do, and that I have a very hard time constructing a nuts and
> bolts model in my head of what RANGER would be like.
> 
> It helps to know the goals of RANGER - as I think you have described
> more clearly in this reply than I in the I-D.  However, in order for
> me to I feel I understand something I need to imagine a number of
> building blocks which I understand very clearly, and then imagine
> them strung together and interacting.

If you can grasp the RANGER Border Router/Gateway
building blocks, you are most of the way there. 

> Then I can start to consider whether I think the whole thing 
> will work!

Again, VET and SEAL give the details on how it works
and a fair amount it is already working in prototype
and production code.

> I probably won't have time to build such an understanding of RANGER
> in the foreseeable future, but I am keen to read anything more you
> can say about it on the list, and I am sure other people would be
> interested too.

Hope this has helped.

Fred
fred.l.templin@boeing.com

> 
>   - Robin
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 12:30:04 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0E203A6AC8; Mon,  2 Feb 2009 12:30:03 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F7703A6ABC for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 12:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level: 
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599]
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 4tiDPhe+rViH for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 12:30:01 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by core3.amsl.com (Postfix) with ESMTP id 718DC3A6933 for <rrg@irtf.org>; Mon,  2 Feb 2009 12:30:01 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so1871907rvb.7 for <rrg@irtf.org>; Mon, 02 Feb 2009 12:29:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=8HG4T7A+ntmN7j0VBQ/nvg1Qwg2w8WELApLQNJhSoa8=; b=rVLrQ1YOjpDlYTlKctPoNNVOYowm4Be8R6yr8+pEFHiKhWdROfa2TKrv6nduUqt6K6 F+PmXYOOFKOfBZCrdm4KKydwAXd18IioLsA8F9zPVymjZK4GAt1hXo2IEiDFFCQN0Fq3 ECuw8ejnlqo8ZaFGH+Ox7UdpZC2vZPdXfKJTI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=sHZnNJpDdogzk1pJEPyuMccdn1BIuIsBV6ziRiiuHcHhr/2F0ANLs+IM5X5TsHYKa/ 9RxodsvZm3YoUIAvTgXKqM1bUxzj3qVNM9LABKNzwAE0cLI7eq/rvrLp7XVrQFr3bA3o Rmwuu0chzdg+6Bf/viY+Dw/QoK6M9/9EML5JA=
Received: by 10.141.36.10 with SMTP id o10mr1307847rvj.237.1233606581942; Mon, 02 Feb 2009 12:29:41 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id g31sm10110348rvb.2.2009.02.02.12.29.40 (version=SSLv3 cipher=RC4-MD5); Mon, 02 Feb 2009 12:29:41 -0800 (PST)
Message-ID: <498757B6.4070507@gmail.com>
Date: Tue, 03 Feb 2009 09:29:42 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  rrg@irtf.org,  int-area@ietf.org
References: <B0585DFE-4A47-481C-BABB-881BF179F827@cisco.com>	<39C363776A4E8C4A94691D2BD9D1C9A10581F02F@XCH-NW-7V2.nw.nos.boeing.com> <20090202173838.GD1164@cisco.com>
In-Reply-To: <20090202173838.GD1164@cisco.com>
Subject: Re: [rrg] [Int-area] RANGER BOF - call for participation
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-02-03 06:38, Scott Brim wrote:
> If you hold it, I will come.

Ditto (unless of course there is a bad clash or my travel
funding doesn't materialise).

   Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 12:31:59 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 615A128C24C; Mon,  2 Feb 2009 12:31:59 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FD4528C177; Mon,  2 Feb 2009 12:31:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599]
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 WbYMbuYgOcqB; Mon,  2 Feb 2009 12:31:56 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id 74A8D28C264; Mon,  2 Feb 2009 12:31:45 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n12KVHgE001378;  Mon, 2 Feb 2009 12:31:17 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n12KVG4W001377; Mon, 2 Feb 2009 12:31:16 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Mon, 2 Feb 2009 12:31:16 -0800
From: David Meyer <dmm@1-4-5.net>
To: Scott Brim <swb@employees.org>, Christopher Morrow <morrowc.lists@gmail.com>, Christian Vogt <christian.vogt@ericsson.com>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, rrg RG <rrg@irtf.org>, lisp@ietf.org
Message-ID: <20090202203116.GA1345@1-4-5.net>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com>
MIME-Version: 1.0
In-Reply-To: <20090202184247.GE1164@cisco.com>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0756306327=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============0756306327==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU"
Content-Disposition: inline


--EeQfGwPcQSOJBaQU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 02, 2009 at 01:42:47PM -0500, Scott Brim wrote:
> Excerpts from Christopher Morrow on Mon, Feb 02, 2009 01:21:19PM -0500:
> > > According to your email to Robin, LISP/ALT currently makes the follow=
ing
> > > tradeoff:  Portability of EID prefixes is limited geographically in
> > > order to curb path stretch along the ALT topology to the maximum that
> > > can happen within a geographical region.
> > >
> > > That's possible, of course.  The cost is that networks scattered over
> > > different parts of the world, such as those of enterprises with global
> > > presence, cannot use a continuous address space internally -- even if
> > > they all attach to the same provider.
> >=20
> > cant they? I thought one of the nice things about the loc/id split was
> > I could number my internals out of whatever I wanted, spread over
> > creation and the attachment points were the only things that required
> > aggregation, no?
>=20
> Sure, but if one of your sites is in New Zealand, and has a prefix
> where the physical ALT hierarchy is optimized for sites in Europe, a
> source in New Zealand trying to contact your site would see more delay
> during the Map-Request/Reply exchange, even though it they are in the
> same town.  However, Map-Request/Reply exchanges don't happen very
> often, and the delay will be low (round trip across the Internet).

	Or not at all if you're not the first folks communicating
	between the sites.

	Dave

--EeQfGwPcQSOJBaQU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmHWBQACgkQORgD1qCZ2KcV3ACeO7MFklzB7u7V/KCyIpr7/8Wr
S0sAni65mdy1vXOB6rQX92J+rNKol3vk
=3Ct5
-----END PGP SIGNATURE-----

--EeQfGwPcQSOJBaQU--

--===============0756306327==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============0756306327==--

From rrg-bounces@irtf.org  Mon Feb  2 12:51:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A81C028C25D; Mon,  2 Feb 2009 12:51:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD26828C260 for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 12:51:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599]
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 3i0Vrr3N60wD for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 12:51:44 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by core3.amsl.com (Postfix) with ESMTP id D0DA528C249 for <rrg@irtf.org>; Mon,  2 Feb 2009 12:51:44 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so1881083rvb.7 for <rrg@irtf.org>; Mon, 02 Feb 2009 12:51:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=axIUEBpnhbpOqFrP1L+rBhGDDyMD1RZpvywBTAz76d8=; b=WWVhx2fZDWHpEyxWjsHVQ4qXofmExN6WxD/ozgBdwdfefSGFky7lnuZcim5HiJlzJg Q9Y7yWDboEu6BZ5O8WBI30GMaNqvyIM/DxXU8vM+TXf4gTe4nBEKpT6bGKmZ6VK6y67b MsCM213ezMiV2QwSOffHcJMiSzE4SjKnfQJTw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=stYMq0QFwfDsTtIw1PtuWFGLFrRZh118QK/jGLK9Kwn4I9UJUU254K/+/FO99gY8Av sSTZ+Je5N0x8VztCEBeN4Te24BHQb99FhJ3IWrPtUAgyYwRVV4JEta1Kh1WWitfrRp12 j0/yx4F/V63MUzVZ1viw3kB7FjQ8UKBCndMn8=
Received: by 10.140.201.6 with SMTP id y6mr2213230rvf.298.1233607885361; Mon, 02 Feb 2009 12:51:25 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id k2sm10169506rvb.6.2009.02.02.12.51.22 (version=SSLv3 cipher=RC4-MD5); Mon, 02 Feb 2009 12:51:24 -0800 (PST)
Message-ID: <49875CCE.2070909@gmail.com>
Date: Tue, 03 Feb 2009 09:51:26 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: David Meyer <dmm@1-4-5.net>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au>	<6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>	<3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>	<75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>	<20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net>
In-Reply-To: <20090202203116.GA1345@1-4-5.net>
Cc: int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, Christian Vogt <christian.vogt@ericsson.com>, rrg RG <rrg@irtf.org>, lisp@ietf.org
Subject: Re: [rrg] [Int-area] [lisp] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-02-03 09:31, David Meyer wrote:
> On Mon, Feb 02, 2009 at 01:42:47PM -0500, Scott Brim wrote:
>> Excerpts from Christopher Morrow on Mon, Feb 02, 2009 01:21:19PM -0500:
>>>> According to your email to Robin, LISP/ALT currently makes the following
>>>> tradeoff:  Portability of EID prefixes is limited geographically in
>>>> order to curb path stretch along the ALT topology to the maximum that
>>>> can happen within a geographical region.
>>>>
>>>> That's possible, of course.  The cost is that networks scattered over
>>>> different parts of the world, such as those of enterprises with global
>>>> presence, cannot use a continuous address space internally -- even if
>>>> they all attach to the same provider.
>>> cant they? I thought one of the nice things about the loc/id split was
>>> I could number my internals out of whatever I wanted, spread over
>>> creation and the attachment points were the only things that required
>>> aggregation, no?
>> Sure, but if one of your sites is in New Zealand, and has a prefix
>> where the physical ALT hierarchy is optimized for sites in Europe, a
>> source in New Zealand trying to contact your site would see more delay
>> during the Map-Request/Reply exchange, even though it they are in the
>> same town.  However, Map-Request/Reply exchanges don't happen very
>> often, and the delay will be low (round trip across the Internet).
> 
> 	Or not at all if you're not the first folks communicating
> 	between the sites.

A couple of points on this.

1. Large companies with their own international networks will
surely never adopt a solution which doesn't allow them to have
a straightforward, consistent and 100% internally managed
addressing plan.

2. They also won't adopt a solution in which local customers
experience world-crossing delays for accessing local sites.
They will use DNS tricks, redirects, CDNs, and overlay routing
to get round this.

It's to be hoped that loc/id solutions such as LISP will be viewed
as a help in this game rather than as a new enemy.

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 13:10:51 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0510A28C233; Mon,  2 Feb 2009 13:10:51 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4890D28C1FF for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 13:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.542
X-Spam-Level: 
X-Spam-Status: No, score=-6.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 fplhlC0kUcws for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 13:10:50 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 9FF4E28C21E for <rrg@irtf.org>; Mon,  2 Feb 2009 13:10:49 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,367,1231113600"; d="scan'208";a="35691738"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 02 Feb 2009 21:09:24 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n12L9Na1029987;  Mon, 2 Feb 2009 16:09:23 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n12L9NiX004825; Mon, 2 Feb 2009 21:09:23 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 16:09:23 -0500
Received: from cisco.com ([10.86.245.246]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Feb 2009 16:09:22 -0500
Date: Mon, 2 Feb 2009 16:09:13 -0500
From: Scott Brim <swb@employees.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20090202210913.GB16207@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, David Meyer <dmm@1-4-5.net>, Christopher Morrow <morrowc.lists@gmail.com>, Christian Vogt <christian.vogt@ericsson.com>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, rrg RG <rrg@irtf.org>, lisp@ietf.org
References: <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <49875CCE.2070909@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <49875CCE.2070909@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 02 Feb 2009 21:09:23.0114 (UTC) FILETIME=[85A028A0:01C9857A]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, Christian Vogt <christian.vogt@ericsson.com>, rrg RG <rrg@irtf.org>, lisp@ietf.org
Subject: Re: [rrg] [Int-area] [lisp] Please respond: Questions from the	IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Brian E Carpenter on Tue, Feb 03, 2009 09:51:26AM +1300:
> 1. Large companies with their own international networks will
> surely never adopt a solution which doesn't allow them to have
> a straightforward, consistent and 100% internally managed
> addressing plan.
> 
> 2. They also won't adopt a solution in which local customers
> experience world-crossing delays for accessing local sites.
> They will use DNS tricks, redirects, CDNs, and overlay routing
> to get round this.
> 
> It's to be hoped that loc/id solutions such as LISP will be viewed
> as a help in this game rather than as a new enemy.

As John Z pointed out, the company has a lot of control over how this
is done.  With coordination between xTRs (in the case of ALT), the
Map-Request can go to a "near" one and the Map-Reply can carry a
specific answer.  Or not.  Complexity can be pushed outside, or be
placed in the company's edge (control only), or brought all the way in
to internal routing.  You choose your trade-off points.
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 13:17:45 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4CAF3A6B32; Mon,  2 Feb 2009 13:17:45 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F65B3A6B4A; Mon,  2 Feb 2009 13:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599]
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 oOLlB+40qfif; Mon,  2 Feb 2009 13:17:44 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id 44CC03A68EC; Mon,  2 Feb 2009 13:17:42 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n12LHAt6003561;  Mon, 2 Feb 2009 13:17:10 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n12LHARi003560; Mon, 2 Feb 2009 13:17:10 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Mon, 2 Feb 2009 13:17:10 -0800
From: David Meyer <dmm@1-4-5.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20090202211710.GA3526@1-4-5.net>
References: <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <49875CCE.2070909@gmail.com>
MIME-Version: 1.0
In-Reply-To: <49875CCE.2070909@gmail.com>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, Christian Vogt <christian.vogt@ericsson.com>, rrg RG <rrg@irtf.org>, lisp@ietf.org
Subject: Re: [rrg] [Int-area] [lisp] Please respond: Questions from the	IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2049548097=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============2049548097==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA"
Content-Disposition: inline


--W/nzBZO5zC0uMSeA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> A couple of points on this.
>=20
> 1. Large companies with their own international networks will
> surely never adopt a solution which doesn't allow them to have
> a straightforward, consistent and 100% internally managed
> addressing plan.
 =20
	No doubt.

> 2. They also won't adopt a solution in which local customers
> experience world-crossing delays for accessing local sites.
> They will use DNS tricks, redirects, CDNs, and overlay routing
> to get round this.

	Again, no doubt.

> It's to be hoped that loc/id solutions such as LISP will be viewed
> as a help in this game rather than as a new enemy.

	One would hope so.

	Dave

--W/nzBZO5zC0uMSeA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmHYtUACgkQORgD1qCZ2KdTPACeP4VLfPQ+bjunQ6Z/KU15fWqc
TT0AoI8PiLJID0CKyzra3r1UKLmK/N7G
=YDap
-----END PGP SIGNATURE-----

--W/nzBZO5zC0uMSeA--

--===============2049548097==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============2049548097==--

From rrg-bounces@irtf.org  Mon Feb  2 14:18:30 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5049328C1F8; Mon,  2 Feb 2009 14:18:30 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C2123A6BD3; Mon,  2 Feb 2009 14:18:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.133
X-Spam-Level: 
X-Spam-Status: No, score=-0.133 tagged_above=-999 required=5 tests=[AWL=-0.420, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 Ov0jvvoPw2lz; Mon,  2 Feb 2009 14:18:28 -0800 (PST)
Received: from imo-m20.mx.aol.com (imo-m20.mx.aol.com [64.12.137.1]) by core3.amsl.com (Postfix) with ESMTP id D05633A6BCD; Mon,  2 Feb 2009 14:18:21 -0800 (PST)
Received: from HeinerHummel@aol.com by imo-m20.mx.aol.com  (mail_out_v39.1.) id z.c40.519a850f (32915); Mon, 2 Feb 2009 17:15:52 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <c40.519a850f.36b8ca98@aol.com>
Date: Mon, 2 Feb 2009 17:15:52 EST
To: dmm@1-4-5.net, brian.e.carpenter@gmail.com
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Cc: int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org, christian.vogt@ericsson.com, rrg@irtf.org, rw@firstpr.com.au
Subject: Re: [rrg] [Int-area] [lisp] Please respond: Questions from the IESG as to whe...
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2083440533=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============2083440533==
Content-Type: multipart/alternative; boundary="-----------------------------1233612952"


-------------------------------1233612952
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
In einer eMail vom 02.02.2009 22:17:36 Westeurop=E4ische Normalzeit schreibt=
 =20
dmm@1-4-5.net:

>  It's to be hoped that loc/id solutions such as LISP will be viewed
> as  a help in this game rather than as a new enemy.

One would  hope so.

Dave



LISP/ALT reminds me of the lie baron Muenchhausen story, who told his =20
listeners how he rescued himself from drowning: "I grabbed my hair and pulle=
d =20
myself out of the water".
=20
Heiner

-------------------------------1233612952
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In einer eMail vom 02.02.2009 22:17:36 Westeurop=E4ische Normalzeit sch=
reibt=20
dmm@1-4-5.net:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>&gt;=20
  It's to be hoped that loc/id solutions such as LISP will be viewed<BR>&gt;=
 as=20
  a help in this game rather than as a new enemy.<BR><BR>&nbsp; &nbsp; One w=
ould=20
  hope so.<BR><BR>&nbsp; &nbsp; Dave<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>LISP/ALT reminds me of the lie baron Muenchhausen story, who told his=20
listeners how he rescued himself from drowning: "I grabbed my hair and pulle=
d=20
myself out of the water".</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1233612952--

--===============2083440533==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============2083440533==--

From rrg-bounces@irtf.org  Mon Feb  2 18:45:06 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41FD93A68C3; Mon,  2 Feb 2009 18:45:06 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4BED3A68C3 for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 18:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.583
X-Spam-Level: 
X-Spam-Status: No, score=-1.583 tagged_above=-999 required=5 tests=[AWL=0.312,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
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 7fUfgjQ0Ge2t for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 18:45:04 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id B47263A67A3 for <rrg@irtf.org>; Mon,  2 Feb 2009 18:45:03 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 36645175D52; Tue,  3 Feb 2009 13:20:14 +1100 (EST)
Message-ID: <4987A966.1040406@firstpr.com.au>
Date: Tue, 03 Feb 2009 13:18:14 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au>	<6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>	<3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>	<75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>	<20090202184247.GE1164@cisco.com>	<20090202203116.GA1345@1-4-5.net> <49875CCE.2070909@gmail.com>
In-Reply-To: <49875CCE.2070909@gmail.com>
Cc: int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org, Christian Vogt <christian.vogt@ericsson.com>
Subject: Re: [rrg] [Int-area] [lisp] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Some of this discussion about the merits of LISP-ALT and of other
schemes is only happening on the RRG list and so is not on the other
lists crossposted in this reply.

  http://www.irtf.org/pipermail/rrg/


Hi Brian,

You wrote, in part:

> 1. Large companies with their own international networks will
> surely never adopt a solution which doesn't allow them to have
> a straightforward, consistent and 100% internally managed
> addressing plan.

I agree.  In my view, this means they want and need portable address
space.  I think placing "portable" anywhere near "address" in a
sentence makes some peoples' teeth itch, including especially
yourself!  But I think this is what networks want and need: stable
public address space they retain for year after year, and can use via
any ISP, ideally being able to split it up very finely between
multiple ISPs and to change which ISP they use it with - quickly and
with little cost to themselves or other people.

The core-edge separation schemes LISP, APT and Ivip all provide
portable address space, like PI space, but not handled directly by
BGP, not obtained in necessarily big chunks and probably obtained
from some company or other organisation, rather than directly from an
RIR.

Also, this new kind of space (I call it Scalable PI space) can be
sliced up much more finely by the scheme's mapping system, down to
the individual IP address, compared to the administrative limits
placed on BGP's finesse, such as /24 for IPv4.  (Ivip only goes to
/64 resolution for IPv6.)  This space will have initial and ongoing
costs, but it won't involve BGP expertise, BGP routers, being an AS etc.


> 2. They also won't adopt a solution in which local customers
> experience world-crossing delays for accessing local sites.
> They will use DNS tricks, redirects, CDNs, and overlay routing
> to get round this.

I agree.  This rules out the use of a core-edge separation scheme
with a global query server system (LISP-CONS, LISP-ALT and TRRP).
There are ways of caching the mapping closer to ITRs, but this raises
problems.


> It's to be hoped that loc/id solutions such as LISP will be viewed
> as a help in this game rather than as a new enemy.

I tend to think that HIP is a real locator ID separation system.  I
don't think of LISP, APT or Ivip in these terms.

I think "Core edge separation scheme" is a better general term for
LISP, APT, Ivip and TRRP.  (Maybe RANGER too.)

But I agree - if LISP-ALT only provides a global query server system
and if it became "The Routing Scaling Solution" for solving the
routing scaling problem, then I think many people would consider the
delays and fragility of a global query server system sufficient
reason not to adopt the scheme.  Yet, in order to solve the routing
scaling problem, we need pretty much all end-user networks, large and
small (who want multihoming, portability etc.) to adopt the one scheme.

  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Feb  2 19:52:43 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FDF03A6B46; Mon,  2 Feb 2009 19:52:43 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4F593A6B46 for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 19:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.451
X-Spam-Level: 
X-Spam-Status: No, score=-103.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 AJvGRiCU-L2A for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 19:52:41 -0800 (PST)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id CFFDF3A699A for <rrg@irtf.org>; Mon,  2 Feb 2009 19:52:40 -0800 (PST)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 14490574; Mon, 02 Feb 2009 22:21:52 -0500
Message-Id: <447844B6-050F-405F-8718-6F47C930BDF0@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <4987A966.1040406@firstpr.com.au>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 2 Feb 2009 22:22:21 -0500
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au>	<6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>	<3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>	<75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>	<20090202184247.GE1164@cisco.com>	<20090202203116.GA1345@1-4-5.net> <49875CCE.2070909@gmail.com> <4987A966.1040406@firstpr.com.au>
X-Mailer: Apple Mail (2.930.3)
Cc: int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org, Christian Vogt <christian.vogt@ericsson.com>, RRG <rrg@irtf.org>
Subject: Re: [rrg] [Int-area] [lisp] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Feb 2, 2009, at 9:18 PM, Robin Whittle wrote:

> Some of this discussion about the merits of LISP-ALT and of other
> schemes is only happening on the RRG list and so is not on the other
> lists crossposted in this reply.
>

Can people please stop posting this discussion to 4 lists.

Regards
Marshall

>  http://www.irtf.org/pipermail/rrg/
>
>
> Hi Brian,
>
> You wrote, in part:
>
>> 1. Large companies with their own international networks will
>> surely never adopt a solution which doesn't allow them to have
>> a straightforward, consistent and 100% internally managed
>> addressing plan.
>
> I agree.  In my view, this means they want and need portable address
> space.  I think placing "portable" anywhere near "address" in a
> sentence makes some peoples' teeth itch, including especially
> yourself!  But I think this is what networks want and need: stable
> public address space they retain for year after year, and can use via
> any ISP, ideally being able to split it up very finely between
> multiple ISPs and to change which ISP they use it with - quickly and
> with little cost to themselves or other people.
>
> The core-edge separation schemes LISP, APT and Ivip all provide
> portable address space, like PI space, but not handled directly by
> BGP, not obtained in necessarily big chunks and probably obtained
> from some company or other organisation, rather than directly from an
> RIR.
>
> Also, this new kind of space (I call it Scalable PI space) can be
> sliced up much more finely by the scheme's mapping system, down to
> the individual IP address, compared to the administrative limits
> placed on BGP's finesse, such as /24 for IPv4.  (Ivip only goes to
> /64 resolution for IPv6.)  This space will have initial and ongoing
> costs, but it won't involve BGP expertise, BGP routers, being an AS  
> etc.
>
>
>> 2. They also won't adopt a solution in which local customers
>> experience world-crossing delays for accessing local sites.
>> They will use DNS tricks, redirects, CDNs, and overlay routing
>> to get round this.
>
> I agree.  This rules out the use of a core-edge separation scheme
> with a global query server system (LISP-CONS, LISP-ALT and TRRP).
> There are ways of caching the mapping closer to ITRs, but this raises
> problems.
>
>
>> It's to be hoped that loc/id solutions such as LISP will be viewed
>> as a help in this game rather than as a new enemy.
>
> I tend to think that HIP is a real locator ID separation system.  I
> don't think of LISP, APT or Ivip in these terms.
>
> I think "Core edge separation scheme" is a better general term for
> LISP, APT, Ivip and TRRP.  (Maybe RANGER too.)
>
> But I agree - if LISP-ALT only provides a global query server system
> and if it became "The Routing Scaling Solution" for solving the
> routing scaling problem, then I think many people would consider the
> delays and fragility of a global query server system sufficient
> reason not to adopt the scheme.  Yet, in order to solve the routing
> scaling problem, we need pretty much all end-user networks, large and
> small (who want multihoming, portability etc.) to adopt the one  
> scheme.
>
>  - Robin
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Feb  3 10:37:55 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C3503A6C5E; Tue,  3 Feb 2009 10:37:55 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CEC13A69D2; Tue,  3 Feb 2009 10:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level: 
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 24D+ycTyA4Dr; Tue,  3 Feb 2009 10:37:52 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id F2C603A6806; Tue,  3 Feb 2009 10:37:48 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n13IbETF027626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Feb 2009 10:37:24 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n13IbEhd022923; Tue, 3 Feb 2009 10:37:14 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n13Ib9OM022630; Tue, 3 Feb 2009 10:37:14 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 3 Feb 2009 10:37:13 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 3 Feb 2009 10:33:22 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10586649A@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Resend: RANGER BOF - call for participation
Thread-Index: AcmDBTLZUbaYGQdGQ1aj2tAZfubKMAAGdDEAAMKRmyA=
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "RRG" <rrg@irtf.org>, <int-area@ietf.org>, <routing-discussion@ietf.org>,  <ranger@ietf.org>
X-OriginalArrivalTime: 03 Feb 2009 18:37:13.0113 (UTC) FILETIME=[6E225090:01C9862E]
Subject: [rrg] Resend: RANGER BOF - call for participation
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Please see below for a resend of the IETF74 RANGER BOF
call for participation, including a link for subscribing
to the 'ranger@ietf.org' list which is now active. Please
post further discussion to 'ranger@ietf.org'.

Thanks - Fred
fred.l.templin@boeing.com

-----Original Message-----
From: Templin, Fred L 
Sent: Friday, January 30, 2009 1:21 PM
To: rrg@irtf.org; int-area@ietf.org
Subject: [Int-area] RANGER BOF - call for participation

A community of interest is being formed to gauge
whether there is sufficient interest to host a BOF
on "Routing and Addressing in Next-Generation
EnteRprises (RANGER)" at IETF74.

Please see below for proposed BOF agenda, and comment
on the RRG and int-area lists while we wait for the
ranger list to come up.

Fred Templin
fred.l.templin@boeing.com



Routing and Addressing in Next-Generation EnteRprises (RANGER) BOF
===================================================================

Chairs:  TBD

Reponsible AD:  TBD (INT Area; Routing Area)

Mailing List:  ranger at ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/ranger
Archive: http://www.ietf.org/mail-archive/web/ranger

Duration:  2 hours

Expected Attendance: 50

Conflicts: LISP BOF, NAT66 BOF, int-area open meeting,
           IRTF rrg meeting

Summary
=======

RANGER [1] is a scalable architecture for routing and
addressing in next-generation enterprise networks, where
an "enterprise" [2] can be as small as a SOHO network,
as dynamic as a Mobile Ad-hoc Network (MANET) [3] or as
large as the global Internet itself [4]. The architecture
is manifested through Virtual Enterprise Traversal (VET)
[5], in which IP-in-IP encapsulation provides a virtual
view of each enterprise as a Non-Broadcast, Multiple-
Access (NBMA) link.

RANGER is recursive, in that multiple enterprises can be
joined together in a nested "enterprise-within-enterprise"
fashion. In this way, the same RANGER principles that
apply in lower levels of recursion can extend upwards
to parent enterprises and ultimately to the core of the
global Internet itself. Furthermore, it is also worth
considering whether today's global Internet represents a
limiting condition for recursion, or if other Internets
could be manifested as "parallel universes" and joined
together at still higher levels of recursion.

The RANGER architecture is manifested through composite
technologies including Virtual Enterprise Traversal (VET),
the Subnetwork Encapsulation and Adaptation Layer (SEAL)
[6], the Intra-Site Automatic Tunnel Addressing Protocol
(ISATAP) [7], and many others. Noting that combinations
with other technologies are also possible, the issues
addressed either in full or in part by RANGER include:

- IPv6/IPv4 coexistence and transition
- scalable routing and addressing
- provider-independent addressing and its
  relation to provide-aggregated addressing
- site mobility and multi-homing
- ingress filtering for multi-homed sites
- address and prefix autoconfiguration
- border router discovery
- router-to-router tunneling
- neighbor discovery over tunnels
- MTU determination for tunnels.

As seen in the above list, the RANGER architecture
provides a framework for addressing a broad range of
problem areas that currently limit the functionality,
growth and maturation of today's Internet. Therefore,
it is the purpose of this BOF to discuss the formation
of an IETF WG to produce the following work items:

1) An Informational RFC describing the RANGER architecture.
   This document to provide a high-level overview of the
   RANGER enterprise-within-enterprise framework, its
   constituent technologies, and its domain of
   applicability.

2) An RFC specification of Virtual Enterprise Traversal
   (VET). This document to specify the inner workings of
   IP-in-IP encapsulation and its associated mechanisms
   within the RANGER context.

3) An RFC specification of the Subnetwork Encapsulation
   and Adaptation Layer (SEAL). This document to specify
   an encapsulation sublayer used to provide enhanced
   packet identification and tunnel MTU robustness.

4) Other work items within scope as determined, e.g.,
   by working group/BOF consensus, etc.

Agenda
======

- Administrivia (Chairs, 5 min)

- Purpose of BOF (Chairs, 10 min) [see above]

- Routing and Addressing in Next Generation EnteRprises
  (RANGER) (20 min)

- Virtual Enterprise Traversal (VET) (20 min)

- Subnetwork Encapsulation and Adaptation Layer (SEAL)
  (20 min)

- Proposed Charter (Chairs, 10 min)

- Questions/Next Steps (Chairs, 30 min)


Documents:
==========

[1] Templin, F., "Routing and Addressing in Next-Generation
    EnteRprises (RANGER), 'draft-templin-ranger',
    work-in-progress, January 2009.

[2] Bound, J., et. al., "IPv6 Enterprise Network Analysis -
    IP Layer 3 Focus", IETF RFC 4852, April 2007.

[3] Corson, S., et. al., "Mobile Ad hoc Networking (MANET):
    Routing Protocol Performance Issues and Evaluation
    Considerations", IETF RFC 2501, January 1999.

[4] IRTF Routing Research Group, http://www.irtf.org/rrg

[5] Templin, F., "Virtual Enterprise Traversal (VET)",
    'draft-templin-autoconf-dhcp', work-in-progress,
    January 2009.

[6] Templin, F., "Subnetwork Encapsulation and Adaptation
    Layer (SEAL)", 'draft-templin-seal', work-in-progress,
    December 2009.

[7] Templin, F., et. al., "Intra-Site Automatic Tunnel
    Addressing Protocol (ISATAP)", IETF RFC 5214, March 2008. 
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From brian.e.carpenter@gmail.com  Tue Feb  3 12:19:19 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE9F83A6A4A for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 12:19:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level: 
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599]
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 c7liW6nrZzCm for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 12:19:18 -0800 (PST)
Received: from mail-gx0-f20.google.com (mail-gx0-f20.google.com [209.85.217.20]) by core3.amsl.com (Postfix) with ESMTP id 8B3783A6805 for <rrg@irtf.org>; Tue,  3 Feb 2009 12:19:18 -0800 (PST)
Received: by gxk13 with SMTP id 13so2696891gxk.7 for <rrg@irtf.org>; Tue, 03 Feb 2009 12:18:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jxkwZPKT+NGPicb+zsRwSGKjO5toYBAiRHFF8C3cS6o=; b=nWCmdUpRuMD6F7UPdus5gS0Iqu/+aTcEPQV7vWfhrqCK+BMrOxeHnwRivtbGKF7Ch9 RPsv84YglpgtwaO2KOCMOZccTlrOJTkwckl6g6ZRqfT2Uim7Is16DrntpihOQLbRMS2b 2DR/veks6ebz3L77Pa/7I8z5dwjTSdGIpLSyM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Tw5uPwcZzDJOSgoDXJa2t1Gd4C1B70kA8DGBw7vnWNFQ2z59e5WXFU6muBJOW6jqG+ 3D0IlkZGMGq9Eb6pyx+MIzru228HFkn6F1MUGm4MpQUH+pJswg3dWrXQ4QbvuYU+iZwx tLS7eY4uFw2aA4wJdv+CvrAHB3b5mLLEZ012k=
Received: by 10.142.210.8 with SMTP id i8mr559970wfg.139.1233692338010; Tue, 03 Feb 2009 12:18:58 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 31sm10037024wff.23.2009.02.03.12.18.56 (version=SSLv3 cipher=RC4-MD5); Tue, 03 Feb 2009 12:18:57 -0800 (PST)
Message-ID: <4988A6AC.4090304@gmail.com>
Date: Wed, 04 Feb 2009 09:18:52 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Zwiebel <jzwiebel@cisco.com>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au>	<6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>	<3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>	<75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>	<20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com>
In-Reply-To: <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: rrg RG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>, Christian Vogt <christian.vogt@ericsson.com>
Subject: [rrg] Policy-based mapping? [was Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2009 20:19:19 -0000

John,

(I trimmed this to just RRG. My comment isn't specific to LISP/ALT.)

On 2009-02-03 10:09, John Zwiebel wrote:
> 
> On Feb 2, 2009, at 10:31 AM, David Meyer wrote:
> 
>>>>
>>>> cant they? I thought one of the nice things about the loc/id split was
>>>> I could number my internals out of whatever I wanted, spread over
>>>> creation and the attachment points were the only things that required
>>>> aggregation, no?
>>>
>>> Sure, but if one of your sites is in New Zealand, and has a prefix
>>> where the physical ALT hierarchy is optimized for sites in Europe, a
>>> source in New Zealand trying to contact your site would see more delay
>>> during the Map-Request/Reply exchange, even though it they are in the
>>> same town.  However, Map-Request/Reply exchanges don't happen very
>>> often, and the delay will be low (round trip across the Internet).
>>
>>     Or not at all if you're not the first folks communicating
>>     between the sites.
> 
> As dino said, you can.
> 
> Let's say the site was using 10/8
> 
> The xTR in Europe would advertise 10/8 into the ALT.
> The xTR in NZ would advertise 10/8 into the ALT
> 
> If you're in NZ, your map-request would be routed over the ALT to that xTR
> If you're in Europe, your map-request would be routed over the ALT to
> that xTR.
> 
> If it is desired, the EID owner can modify the RLOC advertisements so that
> encapsulated data packets will go to the RLOC he wants them to.
> 
> If you want to move the EID-prefix to a different geographical location,
> (NZ to Timbuctu)
> withdraw the route from NZ and start advertising it from Timbuctu.  Yes
> the RLOC
> will change.  The ALT hierarchy doesn't change.

That sounds like policy-based mapping and would create interesting
commercial side-effects just like BGP policy does. It also suggests that
explicit scoping of map entries would be desirable, filtering rules for
propagation of map entries too, and maybe there would be a risk of
black holes in the map. That all sounds very familiar.

    Brian

From jenster@cs.ucla.edu  Tue Feb  3 13:15:27 2009
Return-Path: <jenster@cs.ucla.edu>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9AB13A6B9F for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 13:15:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.449
X-Spam-Level: 
X-Spam-Status: No, score=-4.449 tagged_above=-999 required=5 tests=[AWL=-1.850, BAYES_00=-2.599]
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 JRqoCGKS737Y for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 13:15:27 -0800 (PST)
Received: from out-31.smtp.ucla.edu (out-31.smtp.ucla.edu [169.232.48.161]) by core3.amsl.com (Postfix) with ESMTP id 02ECE3A69D0 for <rrg@irtf.org>; Tue,  3 Feb 2009 13:15:26 -0800 (PST)
Received: from mail.ucla.edu (mail.ucla.edu [169.232.48.150]) by smtp-6.smtp.ucla.edu (8.14.3/8.14.3) with ESMTP id n13LEpFJ032700; Tue, 3 Feb 2009 13:14:52 -0800
Received: from [192.168.1.100] (adsl-75-4-226-87.dsl.irvnca.sbcglobal.net [75.4.226.87]) (authenticated bits=0) by mail.ucla.edu (8.13.8/8.13.8) with ESMTP id n13LEncZ030931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 3 Feb 2009 13:14:49 -0800
From: Dan Jen <jenster@cs.ucla.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4988A6AC.4090304@gmail.com>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com> <4988A6AC.4090304@gmail.com>
Content-Type: text/plain
Date: Tue, 03 Feb 2009 13:14:48 -0800
Message-Id: <1233695688.26154.106.camel@JenXPS>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.3 
Content-Transfer-Encoding: 7bit
X-Probable-Spam: no
X-Spam-Hits: 0.654
X-Scanned-By: smtp.ucla.edu on 169.232.48.241
Cc: John Zwiebel <jzwiebel@cisco.com>, rrg RG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>, Christian Vogt <christian.vogt@ericsson.com>
Subject: Re: [rrg] Policy-based mapping? [was Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2009 21:15:27 -0000

On 2009-02-03 10:09, John Zwiebel wrote:
> The xTR in Europe would advertise 10/8 into the ALT.
> > The xTR in NZ would advertise 10/8 into the ALT
> > 
> > If you're in NZ, your map-request would be routed over the ALT to
> that xTR
> > If you're in Europe, your map-request would be routed over the ALT
> to
> > that xTR.
> > 
> > If it is desired, the EID owner can modify the RLOC advertisements
> so that
> > encapsulated data packets will go to the RLOC he wants them to.
> > 
> > If you want to move the EID-prefix to a different geographical
> location,
> > (NZ to Timbuctu)
> > withdraw the route from NZ and start advertising it from Timbuctu.
> Yes
> > the RLOC
> > will change.  The ALT hierarchy doesn't change.


I thought that the big motivation behind the ALT heirarchy was that ALT
nodes can aggregate prefixes aggressively higher up the ALT heirarchy.
If you don't care about aggregation, then why have an ALT tree at all? 


- Dan Jen








From jzwiebel@cisco.com  Tue Feb  3 19:03:41 2009
Return-Path: <jzwiebel@cisco.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 142C93A6903 for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 19:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.555
X-Spam-Level: 
X-Spam-Status: No, score=-6.555 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 vYSNRPD+r5XR for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 19:03:40 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 299593A6B93 for <rrg@irtf.org>; Tue,  3 Feb 2009 19:03:40 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,375,1231113600";  d="scan'208,217";a="242426356"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 04 Feb 2009 03:03:21 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n1433KKW027852;  Tue, 3 Feb 2009 19:03:20 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1433Kf7004911; Wed, 4 Feb 2009 03:03:20 GMT
Received: from xmb-sjc-22c.amer.cisco.com ([128.107.191.47]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 3 Feb 2009 19:03:20 -0800
Received: from [10.0.1.4] ([10.21.116.164]) by xmb-sjc-22c.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Feb 2009 19:03:16 -0800
In-Reply-To: <1233695688.26154.106.camel@JenXPS>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com> <4988A6AC.4090304@gmail.com> <1233695688.26154.106.camel@JenXPS>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: multipart/alternative; boundary=Apple-Mail-18--141162122
Message-Id: <4E732951-9CB8-425A-8072-F2F70E4ECC16@cisco.com>
From: John Zwiebel <jzwiebel@cisco.com>
Date: Tue, 3 Feb 2009 17:03:11 -1000
To: Dan Jen <jenster@cs.ucla.edu>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 04 Feb 2009 03:03:16.0770 (UTC) FILETIME=[2048B020:01C98675]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2346; t=1233716601; x=1234580601; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jzwiebel@cisco.com; z=From:=20John=20Zwiebel=20<jzwiebel@cisco.com> |Subject:=20Re=3A=20[rrg]=20Policy-based=20mapping?=20[was= 20Please=20respond=3A=20Questions=20from=20the=20IESG=20as=2 0to=20whether=20a=20WG=20forming=20BOF=20is=20necessary=20fo r=20LISP] |Sender:=20; bh=B9WbUtsHbUaqvqaxfuxxWo600ney4bvx/aoaGyvxKS8=; b=acAmrmuqiq70/1nPpxLfuRmPapKxeUjd2kjzSuBdfzwYrkBw5unJFJ3svM mplo1ZDqAp4vbQOvylU6qDNWFxiz4M80PNSgaFY7QoOJVLCkoTOJsUagunvS /K7JcvcP7x;
Authentication-Results: sj-dkim-4; header.From=jzwiebel@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: John Zwiebel <jzwiebel@cisco.com>, rrg RG <rrg@irtf.org>, Christian Vogt <christian.vogt@ericsson.com>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Policy-based mapping? [was Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 03:03:41 -0000

--Apple-Mail-18--141162122
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On Feb 3, 2009, at 11:14 AM, Dan Jen wrote:

>
>
> I thought that the big motivation behind the ALT heirarchy was that  
> ALT
> nodes can aggregate prefixes aggressively higher up the ALT heirarchy.
> If you don't care about aggregation, then why have an ALT tree at all?
>
>

It depends on how you divide and assign the EID space.

Much of the aggregation happens just by deploying LISP/ALT since the
route advertised into the ALT by the xTR is already aggregated.


--Apple-Mail-18--141162122
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br><div><div>On Feb 3, 2009, at 11:14 AM, Dan Jen wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><p =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; font: 10.0px Monaco; =
min-height: 14.0px"><br></p> <p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px; font: 10.0px Monaco; min-height: 14.0px"><br></p> <p =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><font face=3D"Monaco" size=3D"2"=
 style=3D"font: 10.0px Monaco">I thought that the big motivation behind =
the ALT heirarchy was that ALT</font></p> <p style=3D"margin: 0.0px =
0.0px 0.0px 0.0px"><font face=3D"Monaco" size=3D"2" style=3D"font: =
10.0px Monaco">nodes can aggregate prefixes aggressively higher up the =
ALT heirarchy.</font></p> <p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px"><font face=3D"Monaco" size=3D"2" style=3D"font: 10.0px Monaco">If =
you don't care about aggregation, then why have an ALT tree at all?<span =
class=3D"Apple-converted-space">=A0</span></font></p> <p style=3D"margin: =
0.0px 0.0px 0.0px 0.0px; font: 10.0px Monaco; min-height: =
14.0px"><br></p> <p style=3D"margin: 0.0px 0.0px 0.0px 0.0px; font: =
10.0px Monaco; min-height: 14.0px"><br></p> =
</blockquote></div><br><div>It depends on how you divide and assign the =
EID space.</div><div><br></div><div>Much of the aggregation happens just =
by deploying LISP/ALT since the</div><div>route advertised into the ALT =
by the xTR is already aggregated.=A0</div><div><br></div></body></html>=

--Apple-Mail-18--141162122--

From jenster@cs.ucla.edu  Tue Feb  3 19:20:15 2009
Return-Path: <jenster@cs.ucla.edu>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 080283A6B98 for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 19:20:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.832
X-Spam-Level: 
X-Spam-Status: No, score=-5.832 tagged_above=-999 required=5 tests=[AWL=0.767,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 FPtnNxWdN3wR for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 19:20:14 -0800 (PST)
Received: from out-21.smtp.ucla.edu (out-21.smtp.ucla.edu [169.232.47.166]) by core3.amsl.com (Postfix) with ESMTP id 4198D3A6B31 for <rrg@irtf.org>; Tue,  3 Feb 2009 19:20:14 -0800 (PST)
Received: from mail.ucla.edu (mail.ucla.edu [169.232.47.145]) by smtp-4.smtp.ucla.edu (8.14.3/8.14.3) with ESMTP id n143J2N6001470; Tue, 3 Feb 2009 19:19:02 -0800
Received: from [192.168.1.100] (adsl-75-4-226-87.dsl.irvnca.sbcglobal.net [75.4.226.87]) (authenticated bits=0) by mail.ucla.edu (8.13.8/8.13.8) with ESMTP id n143J1Qk003055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 3 Feb 2009 19:19:01 -0800
From: Dan Jen <jenster@cs.ucla.edu>
To: John Zwiebel <jzwiebel@cisco.com>
In-Reply-To: <4E732951-9CB8-425A-8072-F2F70E4ECC16@cisco.com>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com> <4988A6AC.4090304@gmail.com> <1233695688.26154.106.camel@JenXPS> <4E732951-9CB8-425A-8072-F2F70E4ECC16@cisco.com>
Content-Type: text/plain
Date: Tue, 03 Feb 2009 19:19:01 -0800
Message-Id: <1233717541.26154.130.camel@JenXPS>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.3 
Content-Transfer-Encoding: 7bit
X-Probable-Spam: no
X-Spam-Hits: 0.654
X-Scanned-By: smtp.ucla.edu on 169.232.47.244
Cc: rrg RG <rrg@irtf.org>, Christian Vogt <christian.vogt@ericsson.com>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Policy-based mapping? [was Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 03:20:15 -0000

On Tue, 2009-02-03 at 17:03 -1000, John Zwiebel wrote:
> 
> Much of the aggregation happens just by deploying LISP/ALT since the
> route advertised into the ALT by the xTR is already aggregated. 

But then there is no need for a heirarchy right?  We could get the same
benefits by having a set of public-use routers that can return map
replies, peered in a flat format.  

The motivation behind a heirarchical structure for the ALT-LAT was
aggressive aggregation, which leads to the issues articulated by Brian,
where globally-spread sites have to send all map requests through one
geographical point, leading to some major stretch.

However John, you're right that IF edge sites are willing to use LISP's
TE methods, they won't have to prefix split for TE.  This means 1 prefix
per edge site, which is better than today.  But then, as I said, we can
get the same benefit without an ALT tree.


Dan Jen


From dino@cisco.com  Tue Feb  3 19:30:27 2009
Return-Path: <dino@cisco.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C490E3A6C43 for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 19:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OKZe-0aUDO2s for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 19:30:26 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id E1BB73A68E7 for <rrg@irtf.org>; Tue,  3 Feb 2009 19:30:26 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,376,1231113600"; d="scan'208";a="128358414"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 04 Feb 2009 03:30:07 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n143U7M4020316;  Tue, 3 Feb 2009 19:30:07 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n143U7lh026566; Wed, 4 Feb 2009 03:30:07 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 3 Feb 2009 19:30:07 -0800
Received: from [192.168.1.2] ([10.21.77.162]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 3 Feb 2009 19:30:06 -0800
Message-Id: <848928DE-9523-4850-B17E-7A32F4C594B6@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Dan Jen <jenster@cs.ucla.edu>
In-Reply-To: <1233717541.26154.130.camel@JenXPS>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 3 Feb 2009 19:30:07 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com> <4988A6AC.4090304@gmail.com> <1233695688.26154.106.camel@JenXPS> <4E732951-9CB8-425A-8072-F2F70E4ECC16@cisco.com> <1233717541.26154.130.camel@JenXPS>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 04 Feb 2009 03:30:06.0959 (UTC) FILETIME=[E00807F0:01C98678]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1303; t=1233718207; x=1234582207; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20Policy-based=20mapping?=20[was= 20Please=20respond=3A=20Questions=20from=20the=20IESG=20as=2 0to=20whether=20a=20WG=20forming=20BOF=20is=20necessary=20fo r=20LISP] |Sender:=20; bh=DXbhrqua2zZFlKpNYpO1eWeWCdOFXqOgNOqKoOskiXE=; b=U/YSDeflDzv3iOWAyz0EOrOrhMxlTtpTI9V8NIvamYkHpENkTh+AOmBfTQ pIymfGKIE/kJlxHzRuTVZJtLi3WJs65+reoMv9J9PPI7V2ZHCXXdfs4nMVZn /5Tn+sCOhU;
Authentication-Results: sj-dkim-4; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: John Zwiebel <jzwiebel@cisco.com>, rrg RG <rrg@irtf.org>, Christian Vogt <christian.vogt@ericsson.com>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Policy-based mapping? [was Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 03:30:27 -0000

> On Tue, 2009-02-03 at 17:03 -1000, John Zwiebel wrote:
>>
>> Much of the aggregation happens just by deploying LISP/ALT since the
>> route advertised into the ALT by the xTR is already aggregated.
>
> But then there is no need for a heirarchy right?  We could get the  
> same
> benefits by having a set of public-use routers that can return map
> replies, peered in a flat format.
>
> The motivation behind a heirarchical structure for the ALT-LAT was
> aggressive aggregation, which leads to the issues articulated by  
> Brian,
> where globally-spread sites have to send all map requests through one
> geographical point, leading to some major stretch.

Dan, this is very simple, we do and will have a hierarchical  
structure. And when there are allocations they have to be reported  
within an aggregation boundary.

That's it!

Dino

> However John, you're right that IF edge sites are willing to use  
> LISP's
> TE methods, they won't have to prefix split for TE.  This means 1  
> prefix
> per edge site, which is better than today.  But then, as I said, we  
> can
> get the same benefit without an ALT tree.
>
>
> Dan Jen
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg


From jenster@cs.ucla.edu  Tue Feb  3 19:49:16 2009
Return-Path: <jenster@cs.ucla.edu>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03DFF3A68E8 for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 19:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.024
X-Spam-Level: 
X-Spam-Status: No, score=-6.024 tagged_above=-999 required=5 tests=[AWL=0.575,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 b8x5hwJYCOxn for <rrg@core3.amsl.com>; Tue,  3 Feb 2009 19:49:15 -0800 (PST)
Received: from out-56.smtp.ucla.edu (out-56.smtp.ucla.edu [169.232.46.165]) by core3.amsl.com (Postfix) with ESMTP id 586263A68E7 for <rrg@irtf.org>; Tue,  3 Feb 2009 19:49:15 -0800 (PST)
Received: from mail.ucla.edu (mail.ucla.edu [169.232.48.150]) by smtp-11.smtp.ucla.edu (8.14.3/8.14.3) with ESMTP id n143mckC025408;  Tue, 3 Feb 2009 19:48:39 -0800
Received: from [192.168.1.100] (adsl-75-4-226-87.dsl.irvnca.sbcglobal.net [75.4.226.87]) (authenticated bits=0) by mail.ucla.edu (8.13.8/8.13.8) with ESMTP id n143maxC012771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 3 Feb 2009 19:48:36 -0800
From: Dan Jen <jenster@cs.ucla.edu>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <848928DE-9523-4850-B17E-7A32F4C594B6@cisco.com>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com> <4988A6AC.4090304@gmail.com> <1233695688.26154.106.camel@JenXPS> <4E732951-9CB8-425A-8072-F2F70E4ECC16@cisco.com> <1233717541.26154.130.camel@JenXPS> <848928DE-9523-4850-B17E-7A32F4C594B6@cisco.com>
Content-Type: text/plain
Date: Tue, 03 Feb 2009 19:48:36 -0800
Message-Id: <1233719316.26154.131.camel@JenXPS>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.3 
Content-Transfer-Encoding: 7bit
X-Probable-Spam: no
X-Spam-Hits: 0.654
X-Scanned-By: smtp.ucla.edu on 169.232.46.247
Cc: John Zwiebel <jzwiebel@cisco.com>, rrg RG <rrg@irtf.org>, Christian Vogt <christian.vogt@ericsson.com>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Policy-based mapping? [was Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 03:49:16 -0000

On Tue, 2009-02-03 at 19:30 -0800, Dino Farinacci wrote:
> Dan, this is very simple, we do and will have a hierarchical  
> structure. And when there are allocations they have to be reported  
> within an aggregation boundary.
> 
> That's it!
> 

Cool, that's as I thought then.  Thanks.


- Dan Jen

> Dino


From swb@employees.org  Wed Feb  4 05:02:19 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AC4728C114 for <rrg@core3.amsl.com>; Wed,  4 Feb 2009 05:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level: 
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 binw1EokdYvY for <rrg@core3.amsl.com>; Wed,  4 Feb 2009 05:02:18 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 2A1A628C0D7 for <rrg@irtf.org>; Wed,  4 Feb 2009 05:02:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,378,1231113600"; d="scan'208";a="242744234"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 04 Feb 2009 13:01:58 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n14D1wV4020365 for <rrg@irtf.org>; Wed, 4 Feb 2009 05:01:58 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n14D1vOW025261 for <rrg@irtf.org>; Wed, 4 Feb 2009 13:01:58 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 4 Feb 2009 08:01:58 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 4 Feb 2009 08:01:57 -0500
Date: Wed, 4 Feb 2009 08:01:53 -0500
From: Scott Brim <swb@employees.org>
To: rrg@irtf.org
Message-ID: <20090204130153.GA5334@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg@irtf.org
References: <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com> <4988A6AC.4090304@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4988A6AC.4090304@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 04 Feb 2009 13:01:58.0027 (UTC) FILETIME=[C30585B0:01C986C8]
Authentication-Results: sj-dkim-1; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] Policy-based mapping? [was Please respond: Questions	from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 13:02:19 -0000

Excerpts from Brian E Carpenter on Wed, Feb 04, 2009 09:18:52AM +1300:
> > Let's say the site was using 10/8
> > 
> > The xTR in Europe would advertise 10/8 into the ALT.  The xTR in
> > NZ would advertise 10/8 into the ALT
> > 
> > If you're in NZ, your map-request would be routed over the ALT to
> > that xTR If you're in Europe, your map-request would be routed
> > over the ALT to that xTR.
> > 
> > If it is desired, the EID owner can modify the RLOC advertisements
> > so that encapsulated data packets will go to the RLOC he wants
> > them to.
> > 
> > If you want to move the EID-prefix to a different geographical
> > location, (NZ to Timbuctu) withdraw the route from NZ and start
> > advertising it from Timbuctu.  Yes the RLOC will change.  The ALT
> > hierarchy doesn't change.
> 
> That sounds like policy-based mapping and would create interesting
> commercial side-effects just like BGP policy does. It also suggests
> that explicit scoping of map entries would be desirable, filtering
> rules for propagation of map entries too, and maybe there would be a
> risk of black holes in the map. That all sounds very familiar.

First help me understand your terms.  "Policy-based mapping" means to
me that the result of a mapping lookup would vary depending on who was
asking.  

This is different from BGP in that mappings are not propagated
hop-by-hop.  They are sent directly from replier to requestor.
Different answers would not collide in the middle, nor need to be
generated in the middle.  There is no middle.

Does "scoping of map entries" mean the same thing?  Does it mean that
different authorities would have different answers for all queriers?  

Also, I don't see why there would be black holes in the map unless the
originator of mapping info put them there intentionally, or are you
suggesting there could be more chance for configuration problems?
There shouldn't be any non-deterministic interactions in the middle of
the network as with a hop-by-hop dissemination protocol.

Could you please be more explicit about "this all sounds familiar"?
On any topic, let's nail down the issues as specifically as possible.  

Thanks ... Scott

From swb@employees.org  Wed Feb  4 05:16:18 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9500728C16F for <rrg@core3.amsl.com>; Wed,  4 Feb 2009 05:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level: 
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 4me53wh9sf56 for <rrg@core3.amsl.com>; Wed,  4 Feb 2009 05:16:17 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id DF5E13A6B80 for <rrg@irtf.org>; Wed,  4 Feb 2009 05:16:17 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,378,1231113600"; d="scan'208";a="242749939"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 04 Feb 2009 13:15:58 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n14DFwE4005103 for <rrg@irtf.org>; Wed, 4 Feb 2009 05:15:58 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n14DFwTq029200 for <rrg@irtf.org>; Wed, 4 Feb 2009 13:15:58 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 4 Feb 2009 08:15:58 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 4 Feb 2009 08:15:57 -0500
Date: Wed, 4 Feb 2009 08:15:51 -0500
From: Scott Brim <swb@employees.org>
To: rrg RG <rrg@irtf.org>
Message-ID: <20090204131551.GF1861@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg RG <rrg@irtf.org>
References: <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net> <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com> <4988A6AC.4090304@gmail.com> <1233695688.26154.106.camel@JenXPS>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1233717541.26154.130.camel@JenXPS> <1233695688.26154.106.camel@JenXPS>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 04 Feb 2009 13:15:58.0006 (UTC) FILETIME=[B7B02560:01C986CA]
Authentication-Results: sj-dkim-4; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] Policy-based mapping? [was Please respond: Questions	from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 13:16:18 -0000

Excerpts from Dan Jen on Tue, Feb 03, 2009 01:14:48PM -0800:
> I thought that the big motivation behind the ALT heirarchy was that ALT
> nodes can aggregate prefixes aggressively higher up the ALT heirarchy.
> If you don't care about aggregation, then why have an ALT tree at all? 

There is information on where to find mappings and the information in
the mappings themselves.  Where to find mappings is aggregated and
pushed on the ALT.  Map-Reply messages themselves may contain more or
less specific prefixes than those injected into the ALT, but they are
sent directly between replier and requestor.  


From brian.e.carpenter@gmail.com  Wed Feb  4 12:59:15 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5CA73A6B4F for <rrg@core3.amsl.com>; Wed,  4 Feb 2009 12:59:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level: 
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599]
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 qu-MvhNl3UWE for <rrg@core3.amsl.com>; Wed,  4 Feb 2009 12:59:15 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by core3.amsl.com (Postfix) with ESMTP id 00B723A68F7 for <rrg@irtf.org>; Wed,  4 Feb 2009 12:59:14 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so3032172rvb.7 for <rrg@irtf.org>; Wed, 04 Feb 2009 12:58:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=qxccLiIH7/P6XLdE3tJv8j5NC0xAuesDG6JjpeBPURw=; b=vclRdT1dHunRtf5UMznnD2PYIpyxMqOoYEjFdaXHbRK4ZtYXia44MZ0qMwWPlNTXxx HDWwmIsiYLUm2km38i+8RwXU4ovNuUssuwssdkQ1CbIMuWJt/m9NL6QNfYXuD/OFjRxY vNhvGlNYVFFrq9uuOWNMKpP6boEgNv7TA9WSA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Z6SCQ9n32o+4QWazB1wcK9K44CIQl190OHpAvoZH6LLShz+ZlcRDqqc9m738EcwYLl rvnVLOmXbTn94EvUO1a6v1Chye9b2YoTJVtetm9qnGHwgD7dtkgICqZFFSyORNAYm1HT ogW3oo2LlCgr9AcSQ213e0TlWs/Yk8dsUe1eQ=
Received: by 10.141.176.6 with SMTP id d6mr1687904rvp.175.1233781135134; Wed, 04 Feb 2009 12:58:55 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id k37sm12699322rvb.0.2009.02.04.12.58.53 (version=SSLv3 cipher=RC4-MD5); Wed, 04 Feb 2009 12:58:54 -0800 (PST)
Message-ID: <498A018C.90806@gmail.com>
Date: Thu, 05 Feb 2009 09:58:52 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>,  rrg@irtf.org
References: <200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au>	<6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>	<3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>	<75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com>	<20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net>	<388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com>	<4988A6AC.4090304@gmail.com> <20090204130153.GA5334@cisco.com>
In-Reply-To: <20090204130153.GA5334@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [rrg] Policy-based mapping? [was Please respond: Questions	from the IESG as to whether a WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 20:59:15 -0000

Hi Scott,

On 2009-02-05 02:01, Scott Brim wrote:
> Excerpts from Brian E Carpenter on Wed, Feb 04, 2009 09:18:52AM +1300:
>>> Let's say the site was using 10/8
>>>
>>> The xTR in Europe would advertise 10/8 into the ALT.  The xTR in
>>> NZ would advertise 10/8 into the ALT
>>>
>>> If you're in NZ, your map-request would be routed over the ALT to
>>> that xTR If you're in Europe, your map-request would be routed
>>> over the ALT to that xTR.
>>>
>>> If it is desired, the EID owner can modify the RLOC advertisements
>>> so that encapsulated data packets will go to the RLOC he wants
>>> them to.
>>>
>>> If you want to move the EID-prefix to a different geographical
>>> location, (NZ to Timbuctu) withdraw the route from NZ and start
>>> advertising it from Timbuctu.  Yes the RLOC will change.  The ALT
>>> hierarchy doesn't change.
>> That sounds like policy-based mapping and would create interesting
>> commercial side-effects just like BGP policy does. It also suggests
>> that explicit scoping of map entries would be desirable, filtering
>> rules for propagation of map entries too, and maybe there would be a
>> risk of black holes in the map. That all sounds very familiar.
> 
> First help me understand your terms.  "Policy-based mapping" means to
> me that the result of a mapping lookup would vary depending on who was
> asking.  

Yes, that is the effect, whatever the mechanism.

> 
> This is different from BGP in that mappings are not propagated
> hop-by-hop.  They are sent directly from replier to requestor.
> Different answers would not collide in the middle, nor need to be
> generated in the middle.  There is no middle.
> 
> Does "scoping of map entries" mean the same thing?  Does it mean that
> different authorities would have different answers for all queriers?  

I guess the answer to that depends on the specific mapping mechanism.
ALT is only one mechanism, after all. I could imagine mechanisms where
there are multiple possible sources for the map entry for a specific EID,
and that would allow for explicit scoping of a given version of the map
entry. If there can only be one authoritative source per EID, then
the notion of scope is a bit artificial. (A scope would be defined as
a set of queriers who all get the same answer, fwiw.)

> 
> Also, I don't see why there would be black holes in the map unless the
> originator of mapping info put them there intentionally, or are you
> suggesting there could be more chance for configuration problems?
> There shouldn't be any non-deterministic interactions in the middle of
> the network as with a hop-by-hop dissemination protocol.

Once you allow for any kind of policy, there could be black holes
I think. In terms of my immediate previous comment, the black hole
scope would be the set of queriers who all get no answer. That could
be intentional or accidental.

> Could you please be more explicit about "this all sounds familiar"?

I mean that once you have policy mechanisms in the map, you will
get the same sort of interaction between the policy mechanisms and
business relationships or AUPs that we have in BGP. Who knows where
that might lead?

    Brian

From tony.li@tony.li  Thu Feb  5 21:45:26 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A52D3A6A0A for <rrg@core3.amsl.com>; Thu,  5 Feb 2009 21:45:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599]
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 lqmlDWNGa0jC for <rrg@core3.amsl.com>; Thu,  5 Feb 2009 21:45:25 -0800 (PST)
Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id E027C3A6A05 for <rrg@irtf.org>; Thu,  5 Feb 2009 21:45:24 -0800 (PST)
Received: from OMTA03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA10.westchester.pa.mail.comcast.net with comcast id CL1b1b03m0bG4ec5AVlTdp; Fri, 06 Feb 2009 05:45:27 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA03.westchester.pa.mail.comcast.net with comcast id CVlC1b0015Up7oj3PVlF80; Fri, 06 Feb 2009 05:45:25 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Enke Chen'" <enkechen@cisco.com>, "'Danny McPherson'" <danny@tcb.net>
References: <49853070.1030808@cisco.com> <2908A80F-45DF-4B8E-A882-B6921B3893C5@tcb.net> <498BBEE7.1050105@cisco.com>
Date: Thu, 5 Feb 2009 21:45:17 -0800
Message-ID: <873CA4EBD6E840B690DAEADEDEE387A5@ad.redback.com>
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.5579
In-Reply-To: <498BBEE7.1050105@cisco.com>
Thread-Index: AcmIFN3g8qQ7j1WhQN6xF338oLAawwACQWuw
Cc: rrg@irtf.org
Subject: Re: [rrg] BGP scaling limit
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 05:45:26 -0000

Gentlemen,

This discussion is strictly out of scope for RRG.  This is about BGP
internals, not about routing and addressing architectures.  Please take it
to IDR, where it would be most appropriate.

Regards,
Tony
 

|-----Original Message-----
|From: Enke Chen [mailto:enkechen@cisco.com] 
|Sent: Thursday, February 05, 2009 8:39 PM
|To: Danny McPherson
|Cc: rrg@irtf.org; tony.li@tony.li; Enke Chen
|Subject: Re: [rrg] BGP scaling limit
|
|Danny McPherson wrote:
|>
|> On Jan 31, 2009, at 10:17 PM, Enke Chen wrote:
|>>
|>> So here is an alternative (operationally):
|>>
|>>     accept MEDs from each other and perform longest-exit.
|>>
|>> The MEDs could be set by the sender based on the location 
|(community)
|>> so that at most 2 or 3 peering locations would advertise the same
|>> MED.
|>>
|>> For example, for a particular prefix originated from New York:
|>>
|>>       Peering Location         MED
|>>       -----------------------------
|>>        New York / DC           10
|>>
|>>                 Chicago/ Denver                       20
|>>                 SFO / LA                                 30
|>>                 .....
|>>
|>> The location/community based route-map should be uniform (i.e., 
|>> identical) at the peering
|>> locations.
|>>
|>> This approach should reduce the number paths significantly, and yet 
|>> maintain redundancy
|>> and convergence properties in a network.
|>
|> The increasing number of interconnections will still be
|> necessary, and the number of internally amplified routes
|> will grow accordingly.  With each BGP speaker or Route
|> Reflector set/cluster MEDs would possibly decrease the
|> number of routes contained in the core (as every router
|> wouldn't default to advertising the local paths as best)
|> but it only marginally improves the problem, which is still
|> highly topologically dependent and constrained by the
|> current BGP internal scaling model.
|
|Marginally???  The approach reduces the number of paths to be 
|a constant
|(chosen by a provider) from being proportional to the number of peering
|locations.
|
|>
|> Furthermore, MEDs trigger lots of other badness (e.g.,
|> oscillation), require inter-provider coordination and
|> normalization (e.g., with different IGPs and metric space,
|> internal metric allocation models and multipliers vary
|> considerably, etc..), can make peer gaming much simpler,
|> and are usually broken when considering routes originated
|> in multiple locations from an adjacent peer AS.
|
|The actual metrics/MED do not require coordination between providers.
|What is needed is for the providers to accept the metric/MED from
|each other.
|
|MED induced oscillation is a concern, but it is rare.
| 
|>
|> I.e., MEDs should turn closest-exit (hot potato) routing
|> into best-exit routing (cold potato/?), but in my experience
|> most often result in mashed potato routing (e.g., S 7.1.1
|> of RFC 4277).
|
|It is all about tradeoffs.  As you might remember,  InternetMCI used to
|accept MEDs from other providers and it worked just fine
|
|-- Enke
|.
|
|


From jzwiebel@cisco.com  Mon Feb  2 13:10:14 2009
Return-Path: <jzwiebel@cisco.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64D2128C268 for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 13:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.548
X-Spam-Level: 
X-Spam-Status: No, score=-6.548 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 Ej1sjvMq0FyG for <rrg@core3.amsl.com>; Mon,  2 Feb 2009 13:10:14 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 3E1A628C1CC for <rrg@irtf.org>; Mon,  2 Feb 2009 13:10:14 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,367,1231113600"; d="scan'208,217";a="29169245"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 02 Feb 2009 21:09:42 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n12L9gUc029982;  Mon, 2 Feb 2009 13:09:42 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n12L9g64028568; Mon, 2 Feb 2009 21:09:42 GMT
Received: from xmb-sjc-22c.amer.cisco.com ([128.107.191.47]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 2 Feb 2009 13:09:42 -0800
Received: from [10.0.1.4] ([10.21.89.42]) by xmb-sjc-22c.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Feb 2009 13:09:17 -0800
In-Reply-To: <20090202203116.GA1345@1-4-5.net>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <75cb24520902021021o5f277314x18f6b31e6857c199@mail.gmail.com> <20090202184247.GE1164@cisco.com> <20090202203116.GA1345@1-4-5.net>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: multipart/alternative; boundary=Apple-Mail-9--248800725
Message-Id: <388C09CF-4492-4592-8AA9-96A9262586A7@cisco.com>
From: John Zwiebel <jzwiebel@cisco.com>
Date: Mon, 2 Feb 2009 11:09:13 -1000
To: David Meyer <dmm@1-4-5.net>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 02 Feb 2009 21:09:17.0081 (UTC) FILETIME=[82079890:01C9857A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5828; t=1233608983; x=1234472983; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jzwiebel@cisco.com; z=From:=20John=20Zwiebel=20<jzwiebel@cisco.com> |Subject:=20Re=3A=20[lisp]=20[rrg]=20Please=20respond=3A=20 Questions=20from=20the=20IESG=20as=20to=09whether=20a=20WG=2 0forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=AwatDfC87kqHMJ2BT0lwdo4DCM4c3WZOZy+t7HLXnOM=; b=W9MmxX21FPZfs66Euc+zTczxzUnUsrWQNggDIQQ8mbg58UHqm6CQFL6WEb UCBw8M7uZVOAItJ6wPO03BkhWjNr8S+DGRA/wkirTe/4eBSBQ7E6/8YZ3DtH tdO95fXX1+fY0oRdSPs174cL0q2zfH0veyzt2CFE5MPj31SHpMnMg=;
Authentication-Results: sj-dkim-1; header.From=jzwiebel@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
X-Mailman-Approved-At: Fri, 06 Feb 2009 08:16:35 -0800
Cc: int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, Christian Vogt <christian.vogt@ericsson.com>, rrg RG <rrg@irtf.org>, John Zwiebel <jzwiebel@cisco.com>, lisp@ietf.org
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2009 21:10:14 -0000

--Apple-Mail-9--248800725
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On Feb 2, 2009, at 10:31 AM, David Meyer wrote:

>>>
>>> cant they? I thought one of the nice things about the loc/id  
>>> split was
>>> I could number my internals out of whatever I wanted, spread over
>>> creation and the attachment points were the only things that  
>>> required
>>> aggregation, no?
>>
>> Sure, but if one of your sites is in New Zealand, and has a prefix
>> where the physical ALT hierarchy is optimized for sites in Europe, a
>> source in New Zealand trying to contact your site would see more  
>> delay
>> during the Map-Request/Reply exchange, even though it they are in the
>> same town.  However, Map-Request/Reply exchanges don't happen very
>> often, and the delay will be low (round trip across the Internet).
>
> 	Or not at all if you're not the first folks communicating
> 	between the sites.

As dino said, you can.

Let's say the site was using 10/8

The xTR in Europe would advertise 10/8 into the ALT.
The xTR in NZ would advertise 10/8 into the ALT

If you're in NZ, your map-request would be routed over the ALT to  
that xTR
If you're in Europe, your map-request would be routed over the ALT to  
that xTR.

If it is desired, the EID owner can modify the RLOC advertisements so  
that
encapsulated data packets will go to the RLOC he wants them to.

If you want to move the EID-prefix to a different geographical  
location, (NZ to Timbuctu)
withdraw the route from NZ and start advertising it from Timbuctu.   
Yes the RLOC
will change.  The ALT hierarchy doesn't change.
--Apple-Mail-9--248800725
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br><div><div>On Feb 2, 2009, at 10:31 AM, David Meyer wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><p style=3D"margin: 0.0px 0.0px =
0.0px 20.0px; font: 10.0px Monaco; min-height: 14.0px"><br></p> <p =
style=3D"margin: 0.0px 0.0px 0.0px 20.0px"><font face=3D"Monaco" =
size=3D"2" style=3D"font: 10.0px Monaco">cant they? I thought one of the =
nice things about the loc/id split was</font></p> <p style=3D"margin: =
0.0px 0.0px 0.0px 20.0px"><font face=3D"Monaco" size=3D"2" style=3D"font: =
10.0px Monaco">I could number my internals out of whatever I wanted, =
spread over</font></p> <p style=3D"margin: 0.0px 0.0px 0.0px =
20.0px"><font face=3D"Monaco" size=3D"2" style=3D"font: 10.0px =
Monaco">creation and the attachment points were the only things that =
required</font></p> <p style=3D"margin: 0.0px 0.0px 0.0px 20.0px"><font =
face=3D"Monaco" size=3D"2" style=3D"font: 10.0px Monaco">aggregation, =
no?</font></p> </blockquote><p style=3D"margin: 0.0px 0.0px 0.0px =
10.0px; font: 10.0px Monaco; min-height: 14.0px"><br></p> <p =
style=3D"margin: 0.0px 0.0px 0.0px 10.0px"><font face=3D"Monaco" =
size=3D"2" style=3D"font: 10.0px Monaco">Sure, but if one of your sites =
is in New Zealand, and has a prefix</font></p> <p style=3D"margin: 0.0px =
0.0px 0.0px 10.0px"><font face=3D"Monaco" size=3D"2" style=3D"font: =
10.0px Monaco">where the physical ALT hierarchy is optimized for sites =
in Europe, a</font></p> <p style=3D"margin: 0.0px 0.0px 0.0px =
10.0px"><font face=3D"Monaco" size=3D"2" style=3D"font: 10.0px =
Monaco">source in New Zealand trying to contact your site would see more =
delay</font></p> <p style=3D"margin: 0.0px 0.0px 0.0px 10.0px"><font =
face=3D"Monaco" size=3D"2" style=3D"font: 10.0px Monaco">during the =
Map-Request/Reply exchange, even though it they are in the</font></p> <p =
style=3D"margin: 0.0px 0.0px 0.0px 10.0px"><font face=3D"Monaco" =
size=3D"2" style=3D"font: 10.0px Monaco">same town.<span =
class=3D"Apple-converted-space">=A0 </span>However, Map-Request/Reply =
exchanges don't happen very</font></p> <p style=3D"margin: 0.0px 0.0px =
0.0px 10.0px"><font face=3D"Monaco" size=3D"2" style=3D"font: 10.0px =
Monaco">often, and the delay will be low (round trip across the =
Internet).</font></p> </blockquote><p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px; font: 10.0px Monaco; min-height: 14.0px"><br></p> <p =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><font face=3D"Monaco" size=3D"2"=
 style=3D"font: 10.0px Monaco"><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Or not at all if you're not the =
first folks communicating</font></p> <p style=3D"margin: 0.0px 0.0px =
0.0px 0.0px"><font face=3D"Monaco" size=3D"2" style=3D"font: 10.0px =
Monaco"><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>between the sites.</font></p> </blockquote></div><br><div>As dino =
said, you can.</div><div><br></div><div>Let's say the site was using =
10/8</div><div><br></div><div>The xTR in Europe would advertise 10/8 =
into the ALT.</div><div>The xTR in NZ would advertise 10/8 into the =
ALT</div><div><br></div><div>If you're in NZ, your map-request would be =
routed over the ALT to that xTR</div><div>If you're in Europe, your =
map-request would be routed over the ALT to that =
xTR.</div><div><br></div><div>If it is desired, the EID owner can modify =
the RLOC advertisements so that</div><div>encapsulated data packets will =
go to the RLOC he wants them to.</div><div><br></div><div>If you want to =
move the EID-prefix to a different geographical location, (NZ to =
Timbuctu)</div><div>withdraw=A0the route from NZ and start advertising =
it from Timbuctu. =A0Yes the RLOC</div><div>will change. =A0The =
ALT=A0hierarchy=A0doesn't change.</div></body></html>=

--Apple-Mail-9--248800725--

From danny@tcb.net  Thu Feb  5 19:57:25 2009
Return-Path: <danny@tcb.net>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D72133A698F for <rrg@core3.amsl.com>; Thu,  5 Feb 2009 19:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.081
X-Spam-Level: 
X-Spam-Status: No, score=-1.081 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
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 kvjAPRT8mcES for <rrg@core3.amsl.com>; Thu,  5 Feb 2009 19:57:25 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 16D363A6961 for <rrg@irtf.org>; Thu,  5 Feb 2009 19:57:25 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0) id 1934B2684EA; Thu,  5 Feb 2009 20:57:25 -0700 (MST)
Received: from jchouinard-sim-100.eng.ellacoya.com (97-122-99-176.hlrn.qwest.net [97.122.99.176]) (authenticated-user danny) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Thu, 05 Feb 2009 20:57:24 -0700 (MST) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=97.122.99.176; client-port=55764; syn-fingerprint=65535:55:1:64:M1408,N,W3,N,N,T,S; data-bytes=0
Message-Id: <2908A80F-45DF-4B8E-A882-B6921B3893C5@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: Enke Chen <enkechen@cisco.com>
In-Reply-To: <49853070.1030808@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 5 Feb 2009 20:57:23 -0700
References: <49853070.1030808@cisco.com>
X-Mailer: Apple Mail (2.930.3)
X-Mailman-Approved-At: Fri, 06 Feb 2009 08:16:35 -0800
Cc: rrg@irtf.org
Subject: Re: [rrg] BGP scaling limit
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 03:57:25 -0000

On Jan 31, 2009, at 10:17 PM, Enke Chen wrote:
>
> So here is an alternative (operationally):
>
>     accept MEDs from each other and perform longest-exit.
>
> The MEDs could be set by the sender based on the location (community)
> so that at most 2 or 3 peering locations would advertise the same
> MED.
>
> For example, for a particular prefix originated from New York:
>
>       Peering Location         MED
>       -----------------------------
>        New York / DC           10
>
>                 Chicago/ Denver                       20
>                 SFO / LA                                 30
>                 .....
>
> The location/community based route-map should be uniform (i.e.,  
> identical) at the peering
> locations.
>
> This approach should reduce the number paths significantly, and yet  
> maintain redundancy
> and convergence properties in a network.

The increasing number of interconnections will still be
necessary, and the number of internally amplified routes
will grow accordingly.  With each BGP speaker or Route
Reflector set/cluster MEDs would possibly decrease the
number of routes contained in the core (as every router
wouldn't default to advertising the local paths as best)
but it only marginally improves the problem, which is still
highly topologically dependent and constrained by the
current BGP internal scaling model.

Furthermore, MEDs trigger lots of other badness (e.g.,
oscillation), require inter-provider coordination and
normalization (e.g., with different IGPs and metric space,
internal metric allocation models and multipliers vary
considerably, etc..), can make peer gaming much simpler,
and are usually broken when considering routes originated
in multiple locations from an adjacent peer AS.

I.e., MEDs should turn closest-exit (hot potato) routing
into best-exit routing (cold potato/?), but in my experience
most often result in mashed potato routing (e.g., S 7.1.1
of RFC 4277).

-danny

From enkechen@cisco.com  Thu Feb  5 20:39:10 2009
Return-Path: <enkechen@cisco.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6543628C1C3 for <rrg@core3.amsl.com>; Thu,  5 Feb 2009 20:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.479
X-Spam-Level: 
X-Spam-Status: No, score=-6.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 t9AqO0UQNaTF for <rrg@core3.amsl.com>; Thu,  5 Feb 2009 20:39:09 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 5C3863A6A03 for <rrg@irtf.org>; Thu,  5 Feb 2009 20:39:09 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,389,1231113600"; d="scan'208";a="244011481"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 06 Feb 2009 04:39:09 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n164d94Z010427;  Thu, 5 Feb 2009 20:39:09 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n164d9an027393; Fri, 6 Feb 2009 04:39:09 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 5 Feb 2009 20:39:09 -0800
Received: from [10.21.71.223] ([10.21.71.223]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 5 Feb 2009 20:39:08 -0800
Message-ID: <498BBEE7.1050105@cisco.com>
Date: Thu, 05 Feb 2009 20:39:03 -0800
From: Enke Chen <enkechen@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
References: <49853070.1030808@cisco.com> <2908A80F-45DF-4B8E-A882-B6921B3893C5@tcb.net>
In-Reply-To: <2908A80F-45DF-4B8E-A882-B6921B3893C5@tcb.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Feb 2009 04:39:08.0456 (UTC) FILETIME=[D961D280:01C98814]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2616; t=1233895149; x=1234759149; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=enkechen@cisco.com; z=From:=20Enke=20Chen=20<enkechen@cisco.com> |Subject:=20Re=3A=20[rrg]=20BGP=20scaling=20limit |Sender:=20; bh=7IHuIbbelXWpgmlNDFe1as9KNYIerK1In77CO8lkS9I=; b=SEY/yCPklOjmEfAaj1J8utIkqrBmR187lAonZcbXfX3RMqcipUWB2iXKzv y6FFJ4xdWdQatVdAJ9OtS8aPZtUK58UXjU2fBpy+Thlo+v0oEQD0xyNXkLp7 gb3BamR1+e;
Authentication-Results: sj-dkim-2; header.From=enkechen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
X-Mailman-Approved-At: Fri, 06 Feb 2009 08:16:35 -0800
Cc: rrg@irtf.org, Enke Chen <enkechen@cisco.com>
Subject: Re: [rrg] BGP scaling limit
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 04:39:10 -0000

Danny McPherson wrote:
>
> On Jan 31, 2009, at 10:17 PM, Enke Chen wrote:
>>
>> So here is an alternative (operationally):
>>
>>     accept MEDs from each other and perform longest-exit.
>>
>> The MEDs could be set by the sender based on the location (community)
>> so that at most 2 or 3 peering locations would advertise the same
>> MED.
>>
>> For example, for a particular prefix originated from New York:
>>
>>       Peering Location         MED
>>       -----------------------------
>>        New York / DC           10
>>
>>                 Chicago/ Denver                       20
>>                 SFO / LA                                 30
>>                 .....
>>
>> The location/community based route-map should be uniform (i.e., 
>> identical) at the peering
>> locations.
>>
>> This approach should reduce the number paths significantly, and yet 
>> maintain redundancy
>> and convergence properties in a network.
>
> The increasing number of interconnections will still be
> necessary, and the number of internally amplified routes
> will grow accordingly.  With each BGP speaker or Route
> Reflector set/cluster MEDs would possibly decrease the
> number of routes contained in the core (as every router
> wouldn't default to advertising the local paths as best)
> but it only marginally improves the problem, which is still
> highly topologically dependent and constrained by the
> current BGP internal scaling model.

Marginally???  The approach reduces the number of paths to be a constant
(chosen by a provider) from being proportional to the number of peering
locations.

>
> Furthermore, MEDs trigger lots of other badness (e.g.,
> oscillation), require inter-provider coordination and
> normalization (e.g., with different IGPs and metric space,
> internal metric allocation models and multipliers vary
> considerably, etc..), can make peer gaming much simpler,
> and are usually broken when considering routes originated
> in multiple locations from an adjacent peer AS.

The actual metrics/MED do not require coordination between providers.
What is needed is for the providers to accept the metric/MED from
each other.

MED induced oscillation is a concern, but it is rare.
 
>
> I.e., MEDs should turn closest-exit (hot potato) routing
> into best-exit routing (cold potato/?), but in my experience
> most often result in mashed potato routing (e.g., S 7.1.1
> of RFC 4277).

It is all about tradeoffs.  As you might remember,  InternetMCI used to
accept MEDs from other providers and it worked just fine

-- Enke
.


From Fred.L.Templin@boeing.com  Fri Feb  6 17:49:03 2009
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC0E13A6AEB; Fri,  6 Feb 2009 17:49:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.426
X-Spam-Level: 
X-Spam-Status: No, score=-6.426 tagged_above=-999 required=5 tests=[AWL=0.173,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 xJhFxlcAwj06; Fri,  6 Feb 2009 17:49:03 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 1732C3A6875; Fri,  6 Feb 2009 17:48:55 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n171mfm9015900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Feb 2009 17:48:47 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n171mfux027530; Fri, 6 Feb 2009 17:48:41 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n171mdTN027488; Fri, 6 Feb 2009 17:48:41 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 6 Feb 2009 17:48:40 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C988C6.3320B160"
Date: Fri, 6 Feb 2009 17:48:39 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1058A5BBE@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-templin-ranger-07.txt 
Thread-Index: AcmIxb+Rp30vSR9yS2eqjwogXJkO3AAABCqQ
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "RRG" <rrg@irtf.org>, <int-area@ietf.org>, <routing-discussion@ietf.org>,  <ranger@ietf.org>
X-OriginalArrivalTime: 07 Feb 2009 01:48:40.0267 (UTC) FILETIME=[3351C9B0:01C988C6]
Subject: [rrg] FW: I-D Action:draft-templin-ranger-07.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Feb 2009 01:49:04 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C988C6.3320B160
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

FYI, the RANGER specification has been updated based
on review input (see below). Comments to the list or
to the author welcome.

Fred Templin
fred.l.templin@boeing.com

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Friday, February 06, 2009 5:45 PM
To: i-d-announce@ietf.org
Subject: I-D Action:draft-templin-ranger-07.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : Routing and Addressing in Next-Generation
EnteRprises (RANGER)
	Author(s)       : F. Templin
	Filename        : draft-templin-ranger-07.txt
	Pages           : 25
	Date            : 2009-02-06

RANGER is an architectural framework for scalable routing and
addressing in next generation enterprise networks.  The term
"enterprise network" within this context extends to a wide variety of
use cases and deployment scenarios, where an "enterprise" can be as
small as a SOHO network, as dynamic as a Mobile Ad-hoc Network, as
complex as a multi-organizational corporation, or as large as the
global Internet itself.  Such networks will require an architected
solution for the coordination of routing and addressing plans with
accommodations for scalability, provider-independence, mobility,
multi-homing and security.  These considerations are particularly
true for existing deployments, but the same principles apply even for
clean-slate approaches.  The RANGER architecture addresses these
requirements, and provides a comprehensive framework for IPv6/IPv4
coexistence.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-templin-ranger-07.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.

------_=_NextPart_001_01C988C6.3320B160
Content-Type: application/octet-stream;
	name="draft-templin-ranger-07.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-templin-ranger-07.URL
Content-Disposition: attachment;
	filename="draft-templin-ranger-07.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC10ZW1wbGluLXJhbmdlci0wNy50eHQNCg==

------_=_NextPart_001_01C988C6.3320B160
Content-Type: text/plain;
	name="ATT6591595.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT6591595.txt
Content-Disposition: attachment;
	filename="ATT6591595.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCkludGVybmV0LURyYWZ0IGRpcmVj
dG9yaWVzOiBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sDQpvciBmdHA6Ly9mdHAuaWV0
Zi5vcmcvaWV0Zi8xc2hhZG93LXNpdGVzLnR4dA0K

------_=_NextPart_001_01C988C6.3320B160--

From lixia@cs.ucla.edu  Fri Feb 13 18:01:39 2009
Return-Path: <lixia@cs.ucla.edu>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BCE83A6901 for <rrg@core3.amsl.com>; Fri, 13 Feb 2009 18:01:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 82mtWgsiWTQ4 for <rrg@core3.amsl.com>; Fri, 13 Feb 2009 18:01:34 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 867C13A67B0 for <rrg@irtf.org>; Fri, 13 Feb 2009 18:01:31 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id C157839E80C5 for <rrg@irtf.org>; Fri, 13 Feb 2009 18:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2XL3-XSDn3q for <rrg@irtf.org>; Fri, 13 Feb 2009 18:01:38 -0800 (PST)
Received: from [10.0.1.2] (cpe-98-151-48-138.socal.res.rr.com [98.151.48.138]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 3E29739E807A for <rrg@irtf.org>; Fri, 13 Feb 2009 18:01:38 -0800 (PST)
Message-Id: <665CECBA-1B95-45F5-841C-EAC200DB7137@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: rrg@irtf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 13 Feb 2009 18:01:37 -0800
References: <20090214010942.179083A68F7@core3.amsl.com>
X-Mailer: Apple Mail (2.930.3)
Subject: [rrg] Fwd: RRG - Requested sessions have been scheduled for IETF 74
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Feb 2009 02:01:39 -0000

Begin forwarded message:

> From: IETF Secretariat <agenda@ietf.org>
> Date: February 13, 2009 5:09:42 PM PST
> To: tli@cisco.com
> Cc: lixia@cs.ucla.edu,falk@bbn.com,session-request@ietf.org
> Subject: RRG - Requested sessions have been scheduled for IETF 74
>
> Dear Tony Li,
>
> The sessions that you have requested have been scheduled.
> Below is the scheduled session information followed by
> the information of sessions that you have requested.
>
> RRG Session 1 (2.5 hours)
> Friday, Morning Session I 0900-1130
> Room Name: Breakout 4
> ----------------------------------------------
> RRG Session 2 (2.5 hours)
> Friday, Afternoon Session I 1300-1400
> Room Name: Breakout 4
> ----------------------------------------------
>
>
>
> Requested Information:
>
>
> ---------------------------------------------------------
> Working Group Name: RRG
> Area Name:
> Session Requester: Tony Li
>
> Number of Sessions: 2
> Length of Session(s):  2.5 hours
>                       2.5 hours
>
> Number of Attendees: 75
> Conflicts to Avoid:
>  First Priority:  idr isis ospf rtgarea rtgwg
>
> Special Requests:
>  As usual, we would appreciate all day on Friday, if that's possible.
> ---------------------------------------------------------
>
>


From tony.li@tony.li  Sat Feb 14 00:36:04 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25C8F3A68BB for <rrg@core3.amsl.com>; Sat, 14 Feb 2009 00:36:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 xPg1BcgVr+-G for <rrg@core3.amsl.com>; Sat, 14 Feb 2009 00:36:03 -0800 (PST)
Received: from QMTA08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by core3.amsl.com (Postfix) with ESMTP id 555853A67BD for <rrg@irtf.org>; Sat, 14 Feb 2009 00:35:58 -0800 (PST)
Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA08.emeryville.ca.mail.comcast.net with comcast id FkQi1b0090FhH24A8kc5RN; Sat, 14 Feb 2009 08:36:05 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id Fkbs1b0045Up7oj8Ukbu7Q; Sat, 14 Feb 2009 08:36:03 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Lixia Zhang'" <lixia@cs.ucla.edu>, <rrg@irtf.org>
References: <20090214010942.179083A68F7@core3.amsl.com> <665CECBA-1B95-45F5-841C-EAC200DB7137@cs.ucla.edu>
Date: Sat, 14 Feb 2009 00:36:01 -0800
Message-ID: <37910490190A42D79AD68326484DA891@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <665CECBA-1B95-45F5-841C-EAC200DB7137@cs.ucla.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AcmOSDXo2HtmvaCIQaGR5siCQQVzlQANtxtw
Subject: Re: [rrg] Fwd: RRG - Requested sessions have been scheduled for IETF 74
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Feb 2009 08:36:04 -0000

And.... The agenda is now open.

If you have an agenda topic, please let us know by March 15th.  (Beware the
ides of March ;-).

Tony
 

|-----Original Message-----
|From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On 
|Behalf Of Lixia Zhang
|Sent: Friday, February 13, 2009 6:02 PM
|To: rrg@irtf.org
|Subject: [rrg] Fwd: RRG - Requested sessions have been 
|scheduled for IETF 74
|
|
|
|Begin forwarded message:
|
|> From: IETF Secretariat <agenda@ietf.org>
|> Date: February 13, 2009 5:09:42 PM PST
|> To: tli@cisco.com
|> Cc: lixia@cs.ucla.edu,falk@bbn.com,session-request@ietf.org
|> Subject: RRG - Requested sessions have been scheduled for IETF 74
|>
|> Dear Tony Li,
|>
|> The sessions that you have requested have been scheduled.
|> Below is the scheduled session information followed by
|> the information of sessions that you have requested.
|>
|> RRG Session 1 (2.5 hours)
|> Friday, Morning Session I 0900-1130
|> Room Name: Breakout 4
|> ----------------------------------------------
|> RRG Session 2 (2.5 hours)
|> Friday, Afternoon Session I 1300-1400
|> Room Name: Breakout 4
|> ----------------------------------------------
|>
|>
|>
|> Requested Information:
|>
|>
|> ---------------------------------------------------------
|> Working Group Name: RRG
|> Area Name:
|> Session Requester: Tony Li
|>
|> Number of Sessions: 2
|> Length of Session(s):  2.5 hours
|>                       2.5 hours
|>
|> Number of Attendees: 75
|> Conflicts to Avoid:
|>  First Priority:  idr isis ospf rtgarea rtgwg
|>
|> Special Requests:
|>  As usual, we would appreciate all day on Friday, if that's possible.
|> ---------------------------------------------------------
|>
|>
|
|_______________________________________________
|rrg mailing list
|rrg@irtf.org
|http://www.irtf.org/mailman/listinfo/rrg
|


From swb@employees.org  Sun Feb 15 14:58:12 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1CC43A6A65 for <rrg@core3.amsl.com>; Sun, 15 Feb 2009 14:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=-0.400,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 bNXiBwBuC3qQ for <rrg@core3.amsl.com>; Sun, 15 Feb 2009 14:58:12 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id D32323A67D4 for <rrg@irtf.org>; Sun, 15 Feb 2009 14:58:11 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,213,1233532800"; d="scan'208";a="37137241"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 15 Feb 2009 22:58:18 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n1FMwHep000391 for <rrg@irtf.org>; Sun, 15 Feb 2009 17:58:17 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n1FMwHdK020746 for <rrg@irtf.org>; Sun, 15 Feb 2009 22:58:17 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 15 Feb 2009 17:58:17 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 15 Feb 2009 17:58:17 -0500
Date: Sun, 15 Feb 2009 17:58:10 -0500
From: Scott Brim <swb@employees.org>
To: RRG <rrg@irtf.org>
Message-ID: <20090215225810.GI43732@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, RRG <rrg@irtf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 15 Feb 2009 22:58:17.0800 (UTC) FILETIME=[E3F8DC80:01C98FC0]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Subject: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Feb 2009 22:58:13 -0000

A few thoughts on this quick draft:

Pure higher-layer approaches aren't acceptable:

  - We knew that already, for operational reasons other than
    renumbering, for example the shim6 argument.  

  - But that doesn't mean those technologies aren't essential, because
    even if an endpoint only has a single locator within a domain,
    both endpoints and networks will be multihomed and/or mobile, so
    they will at least appear to have multiple locators in global
    routing.  Shim6, HIP, SCTP, Multipath ... all are potentially very
    useful.  It's probably outside of the scope of RRG since they do
    nothing to solve routing scaling, but it is an extremely important
    area for the future of the Internet.

The question is translation versus encapsulation.

  - That's being hotly discussed outside of RRG, for example AI6.  I'm
    wondering: will RRG's role only be as a forum where people can
    compare the results of the discussions and experiments being done
    elsewhere?

Thanks ... Scott

From marcelo@it.uc3m.es  Sun Feb 15 23:47:47 2009
Return-Path: <marcelo@it.uc3m.es>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FA283A6A98 for <rrg@core3.amsl.com>; Sun, 15 Feb 2009 23:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.05
X-Spam-Level: 
X-Spam-Status: No, score=-5.05 tagged_above=-999 required=5 tests=[AWL=0.750,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 eG4b+gXKBiac for <rrg@core3.amsl.com>; Sun, 15 Feb 2009 23:47:46 -0800 (PST)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id 6A8053A6A7D for <rrg@irtf.org>; Sun, 15 Feb 2009 23:47:46 -0800 (PST)
Received: from marcelo-bagnulos-macbook-pro.local (217.pool85-53-134.dynamic.orange.es [85.53.134.217]) by smtp02.uc3m.es (Postfix) with ESMTP id 0CE8E6BAB5B; Mon, 16 Feb 2009 08:47:52 +0100 (CET)
Message-ID: <49991A28.8080007@it.uc3m.es>
Date: Mon, 16 Feb 2009 08:47:52 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>, RRG <rrg@irtf.org>
References: <20090215225810.GI43732@cisco.com>
In-Reply-To: <20090215225810.GI43732@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.5.0.1026-16466.005
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 07:47:47 -0000

Hi Scott,

Scott Brim escribió:
> A few thoughts on this quick draft:
>
> Pure higher-layer approaches aren't acceptable:
>
>   - We knew that already, for operational reasons other than
>     renumbering, for example the shim6 argument.  
>
>   

what is the shim6 argument?

>   - But that doesn't mean those technologies aren't essential, because
>     even if an endpoint only has a single locator within a domain,
>     both endpoints and networks will be multihomed and/or mobile, so
>     they will at least appear to have multiple locators in global
>     routing.  Shim6, HIP, SCTP, Multipath ... all are potentially very
>     useful.  It's probably outside of the scope of RRG since they do
>     nothing to solve routing scaling, 

what do you mean they do nothing to solve the routing scalability?
If every site and host uses only PA addresses, the routing system would 
scale in the order of ISPs, reducing the contribution by the multihomed 
sites.


Regards, marcelo

> but it is an extremely important
>     area for the future of the Internet.
>
> The question is translation versus encapsulation.
>
>   - That's being hotly discussed outside of RRG, for example AI6.  I'm
>     wondering: will RRG's role only be as a forum where people can
>     compare the results of the discussions and experiments being done
>     elsewhere?
>
> Thanks ... Scott
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>
>   


From tony.li@tony.li  Mon Feb 16 07:55:28 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C16923A6A8B for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 07:55:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.399,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 HQqmmmE4VlBP for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 07:55:28 -0800 (PST)
Received: from QMTA05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by core3.amsl.com (Postfix) with ESMTP id CFDB53A6B3A for <rrg@irtf.org>; Mon, 16 Feb 2009 07:55:27 -0800 (PST)
Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA05.westchester.pa.mail.comcast.net with comcast id Gd771b0070mv7h055fvev8; Mon, 16 Feb 2009 15:55:38 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA11.westchester.pa.mail.comcast.net with comcast id GfvU1b0035Up7oj3XfvWx6; Mon, 16 Feb 2009 15:55:36 +0000
From: "Tony Li" <tony.li@tony.li>
To: <rrg@irtf.org>
Date: Mon, 16 Feb 2009 07:54:48 -0800
Message-ID: <EA957E459C91406A948E4FFB63EDC53C@ad.redback.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0036_01C9900B.DC75FDD0"
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
thread-index: AcmPNwvBKn//zKwIRcOiLKgmVvc8aABF9NFA
Subject: [rrg] FW: I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 15:55:28 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0036_01C9900B.DC75FDD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 
FYI...



|-----Original Message-----
|From: i-d-announce-bounces@ietf.org 
|[mailto:i-d-announce-bounces@ietf.org] On Behalf Of 
|Internet-Drafts@ietf.org
|Sent: Saturday, February 14, 2009 10:30 PM
|To: i-d-announce@ietf.org
|Subject: I-D Action:draft-irtf-rrg-recommendation-00.txt 
|
|A New Internet-Draft is available from the on-line 
|Internet-Drafts directories.
|
|	Title           : Preliminary Recommendation for a 
|Routing Architecture
|	Author(s)       : T. Li
|	Filename        : draft-irtf-rrg-recommendation-00.txt
|	Pages           : 15
|	Date            : 2009-02-14
|
|It is commonly recognized that the Internet routing and addressing
|architecture is facing challenges in scalability, multi-homing, and
|inter-domain traffic engineering.  This document is the Routing
|Research Group's prelimnary recommendation for a new routing
|architecture.
|
|This document is a work in progress.
|
|A URL for this Internet-Draft is:
|http://www.ietf.org/internet-drafts/draft-irtf-rrg-recommendati
|on-00.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.
|

------=_NextPart_000_0036_01C9900B.DC75FDD0
Content-Type: Message/External-body;
	name="draft-irtf-rrg-recommendation-00.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="draft-irtf-rrg-recommendation-00.txt"

Content-Type: text/plain
Content-ID: <2009-02-14221546.I-D@ietf.org>


------=_NextPart_000_0036_01C9900B.DC75FDD0
Content-Type: text/plain;
	name="ATT00326.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="ATT00326.txt"

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

------=_NextPart_000_0036_01C9900B.DC75FDD0--


From Fred.L.Templin@boeing.com  Mon Feb 16 08:00:45 2009
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F9173A6B3A for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 08:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 LbD54Rz-p2Zd for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 08:00:39 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 1260A3A6B73 for <rrg@irtf.org>; Mon, 16 Feb 2009 08:00:39 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n1GG0VNt017297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 16 Feb 2009 08:00:32 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n1GG0VWC028887; Mon, 16 Feb 2009 10:00:31 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n1GG0TEP028690; Mon, 16 Feb 2009 10:00:31 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 16 Feb 2009 08:00:28 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 16 Feb 2009 07:59:45 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10592015E@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <37910490190A42D79AD68326484DA891@ad.redback.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Fwd: RRG - Requested sessions have been scheduled forIETF 74
Thread-Index: AcmOSDXo2HtmvaCIQaGR5siCQQVzlQANtxtwAHQP29A=
References: <20090214010942.179083A68F7@core3.amsl.com><665CECBA-1B95-45F5-841C-EAC200DB7137@cs.ucla.edu> <37910490190A42D79AD68326484DA891@ad.redback.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: <tony.li@tony.li>, "Lixia Zhang" <lixia@cs.ucla.edu>, <rrg@irtf.org>
X-OriginalArrivalTime: 16 Feb 2009 16:00:28.0662 (UTC) FILETIME=[B003B960:01C9904F]
Subject: Re: [rrg] Fwd: RRG - Requested sessions have been scheduled forIETF 74
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 16:00:45 -0000

Tony,=20

> -----Original Message-----
> From: Tony Li [mailto:tony.li@tony.li]=20
> Sent: Saturday, February 14, 2009 12:36 AM
> To: 'Lixia Zhang'; rrg@irtf.org
> Subject: Re: [rrg] Fwd: RRG - Requested sessions have been=20
> scheduled forIETF 74
>=20
>=20
>=20
> And.... The agenda is now open.
>=20
> If you have an agenda topic, please let us know by March=20
> 15th.  (Beware the
> ides of March ;-).

What are the procedures this time? Send to chairs only?
Send to a member of the program committee? Other?

Thanks - Fred
fred.l.templin@boeing.com

>=20
> Tony
> =20
>=20
> |-----Original Message-----
> |From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On=20
> |Behalf Of Lixia Zhang
> |Sent: Friday, February 13, 2009 6:02 PM
> |To: rrg@irtf.org
> |Subject: [rrg] Fwd: RRG - Requested sessions have been=20
> |scheduled for IETF 74
> |
> |
> |
> |Begin forwarded message:
> |
> |> From: IETF Secretariat <agenda@ietf.org>
> |> Date: February 13, 2009 5:09:42 PM PST
> |> To: tli@cisco.com
> |> Cc: lixia@cs.ucla.edu,falk@bbn.com,session-request@ietf.org
> |> Subject: RRG - Requested sessions have been scheduled for IETF 74
> |>
> |> Dear Tony Li,
> |>
> |> The sessions that you have requested have been scheduled.
> |> Below is the scheduled session information followed by
> |> the information of sessions that you have requested.
> |>
> |> RRG Session 1 (2.5 hours)
> |> Friday, Morning Session I 0900-1130
> |> Room Name: Breakout 4
> |> ----------------------------------------------
> |> RRG Session 2 (2.5 hours)
> |> Friday, Afternoon Session I 1300-1400
> |> Room Name: Breakout 4
> |> ----------------------------------------------
> |>
> |>
> |>
> |> Requested Information:
> |>
> |>
> |> ---------------------------------------------------------
> |> Working Group Name: RRG
> |> Area Name:
> |> Session Requester: Tony Li
> |>
> |> Number of Sessions: 2
> |> Length of Session(s):  2.5 hours
> |>                       2.5 hours
> |>
> |> Number of Attendees: 75
> |> Conflicts to Avoid:
> |>  First Priority:  idr isis ospf rtgarea rtgwg
> |>
> |> Special Requests:
> |>  As usual, we would appreciate all day on Friday, if=20
> that's possible.
> |> ---------------------------------------------------------
> |>
> |>
> |
> |_______________________________________________
> |rrg mailing list
> |rrg@irtf.org
> |http://www.irtf.org/mailman/listinfo/rrg
> |
>=20
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>=20

From swb@employees.org  Mon Feb 16 08:17:27 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A0D33A6C2C for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 08:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6
X-Spam-Level: 
X-Spam-Status: No, score=-6 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 QCFuN2cLsuxa for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 08:17:26 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 25FD73A682E for <rrg@irtf.org>; Mon, 16 Feb 2009 08:17:26 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,217,1233532800"; d="scan'208";a="135530791"
Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-3.cisco.com with ESMTP; 16 Feb 2009 16:17:36 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id n1GGHaiS029048;  Mon, 16 Feb 2009 08:17:36 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1GGHTqp008907; Mon, 16 Feb 2009 16:17:36 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 16 Feb 2009 11:17:35 -0500
Received: from sbrim-mbp.local ([10.86.247.187]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 16 Feb 2009 11:17:35 -0500
Message-ID: <4999919E.2070006@employees.org>
Date: Mon, 16 Feb 2009 11:17:34 -0500
From: Scott Brim <swb@employees.org>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <20090215225810.GI43732@cisco.com> <49991A28.8080007@it.uc3m.es>
In-Reply-To: <49991A28.8080007@it.uc3m.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 16 Feb 2009 16:17:35.0413 (UTC) FILETIME=[14017E50:01C99052]
Authentication-Results: sj-dkim-5; header.From=swb@employees.org; dkim=neutral
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 16:17:27 -0000

marcelo bagnulo braun allegedly wrote on 02 16 2009 2:47 AM:
> Hi Scott,
> 
> Scott Brim escribió:
>> A few thoughts on this quick draft:
>>
>> Pure higher-layer approaches aren't acceptable:
>>
>>   - We knew that already, for operational reasons other than
>>     renumbering, for example the shim6 argument. 
>>   
> 
> what is the shim6 argument?

The argument that took place between the IETF and network operators when
shim6 was recommended.

>>   - But that doesn't mean those technologies aren't essential, because
>>     even if an endpoint only has a single locator within a domain,
>>     both endpoints and networks will be multihomed and/or mobile, so
>>     they will at least appear to have multiple locators in global
>>     routing.  Shim6, HIP, SCTP, Multipath ... all are potentially very
>>     useful.  It's probably outside of the scope of RRG since they do
>>     nothing to solve routing scaling, 
> 
> what do you mean they do nothing to solve the routing scalability?
> If every site and host uses only PA addresses, the routing system would
> scale in the order of ISPs, reducing the contribution by the multihomed
> sites.

But that won't happen, because it requires site renumbering, multiple
locators per host within a domain, extra policy management and so on --
the things we discovered were operational showstoppers.  The host-based
mechanisms are vitally important but not as solutions to routing problems.


Scott


From jmh@joelhalpern.com  Mon Feb 16 08:27:47 2009
Return-Path: <jmh@joelhalpern.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 011B628C115 for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 08:27:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.051
X-Spam-Level: 
X-Spam-Status: No, score=-3.051 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 XGptElMNZWYf for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 08:27:46 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 5EEB028B797 for <rrg@irtf.org>; Mon, 16 Feb 2009 08:27:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id BDF4943024C; Mon, 16 Feb 2009 08:27:56 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-52-247.clppva.btas.verizon.net [71.161.52.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id A5BBB430238; Mon, 16 Feb 2009 08:27:55 -0800 (PST)
Message-ID: <49999407.6090800@joelhalpern.com>
Date: Mon, 16 Feb 2009 11:27:51 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>
References: <20090215225810.GI43732@cisco.com> <49991A28.8080007@it.uc3m.es> <4999919E.2070006@employees.org>
In-Reply-To: <4999919E.2070006@employees.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 16:27:47 -0000

I would say that the shim6 "argument" you are referencing has several 
difficulties in trying to apply it.
1) It was based on a faulty understanding of shim6.
2) It was based on the premise that operators should have total and 
absolute control over traffic engineering.

As I understood the argument, the claim was that shim6 "prevented" 
operator traffic engineering.  It didn't it restricted the scope to 
engineering traffic that was explicitly addressed to given access points.
More importantly in our context, the exact same argument can be made 
against CPE based LSIP, or any CPE based map-and-encaps.
In fact, given that the operator traffic engineering is typically based 
on incoming traffic engineering (outbound traffic is much easier to 
handle), the same "shim6 operator concern" can be applied even to PE 
based LISP or map-and-encapss solutions.

Hence, if that argument is valid against host based solutions, then we 
are completely out of luck.

Yours,
Joel

Scott Brim wrote:
> marcelo bagnulo braun allegedly wrote on 02 16 2009 2:47 AM:
>> Hi Scott,
>>
>> Scott Brim escribió:
>>> A few thoughts on this quick draft:
>>>
>>> Pure higher-layer approaches aren't acceptable:
>>>
>>>   - We knew that already, for operational reasons other than
>>>     renumbering, for example the shim6 argument. 
>>>   
>> what is the shim6 argument?
> 
> The argument that took place between the IETF and network operators when
> shim6 was recommended.

From HeinerHummel@aol.com  Mon Feb 16 10:15:38 2009
Return-Path: <HeinerHummel@aol.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8A2F3A6B3C for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 10:15:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.197
X-Spam-Level: **
X-Spam-Status: No, score=2.197 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, SARE_SUB_RAND_LETTRS4=0.799]
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 RDrM9TUlWXjm for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 10:15:38 -0800 (PST)
Received: from imo-m12.mail.aol.com (imo-m12.mx.aol.com [64.12.143.100]) by core3.amsl.com (Postfix) with ESMTP id 122BE3A69E3 for <rrg@irtf.org>; Mon, 16 Feb 2009 10:15:16 -0800 (PST)
Received: from HeinerHummel@aol.com by imo-m12.mx.aol.com  (mail_out_v39.1.) id 9.bfe.57e88f97 (65099) for <rrg@irtf.org>; Mon, 16 Feb 2009 13:13:59 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <bfe.57e88f97.36cb06e7@aol.com>
Date: Mon, 16 Feb 2009 13:13:59 EST
To: rrg@irtf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1234808039"
X-Mailer: 9.0 SE for Windows sub 5021
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 18:15:38 -0000

-------------------------------1234808039
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
In einer eMail vom 16.02.2009 17:28:23 Westeurop=E4ische Normalzeit schreibt=
 =20
jmh@joelhalpern.com:

Hence,  if that argument is valid against host based solutions, then we=20
are  completely out of luck.

Yours,
Joel



Strategy A:=20
 LISP-ALT may be viewed as some outsourcing trick - however  staying inside=20
the same inertial frame.
=20
Strategy B:
Appears to be out of luck - see above.
=20
Strategy C:
Besides overcoming  the scalability problem and making Moore's law =20
applicable to routing etc., it would also enable  multihoming where  both  n=
etwork=20
and/or  end users may impose path changes such that  different egress router=
s from=20
different ISPs are passed.
=20
Multihoming can be considered as a special kind of ANYCAST whereby it makes=20=
=20
sense to change the anycast dest. node within the IP packet flow and also a=20=
=20
single packet's anycast destination node in the middle of the path (because=20
each  of these anycast destination nodes would deliver it to the same end us=
er).
Network reasons like traffic jam or temporary drop outs may cause detours =20
and a detour might be such that a different anycast dest. node becomes more=20=
=20
suitable to go for.
Yes, these are not ECMP alternative paths but genuine detours which to =20
offer/handle would be part of strategy C as well.
=20
Heiner
=20
=20
=20
=20
=20

-------------------------------1234808039
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16809" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In einer eMail vom 16.02.2009 17:28:23 Westeurop=E4ische Normalzeit sch=
reibt=20
jmh@joelhalpern.com:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>Hence,=20
  if that argument is valid against host based solutions, then we <BR>are=20
  completely out of luck.<BR><BR>Yours,<BR>Joel<BR></FONT></BLOCKQUOTE></DIV=
>
<DIV></DIV>
<DIV>Strategy A: </DIV>
<DIV>&nbsp;LISP-ALT may be viewed as some outsourcing trick&nbsp;- however=20
staying inside the same inertial frame.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Strategy B:</DIV>
<DIV>Appears to be out of luck - see above.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Strategy C:</DIV>
<DIV>Besides overcoming &nbsp;the scalability problem and making Moore's law=
=20
applicable to routing etc., it would also enable&nbsp; multihoming where=20
both&nbsp;&nbsp;network and/or&nbsp; end users may impose path changes such=20=
that=20
different egress routers from different ISPs are passed.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Multihoming can be considered as a special kind of ANYCAST whereby it m=
akes=20
sense to change the anycast dest. node within the IP packet flow and also a=20
single packet's anycast destination node in the middle of the path (because=20=
each=20
of these anycast destination nodes would deliver it to the same end user).</=
DIV>
<DIV>Network reasons like traffic jam or temporary drop outs may cause detou=
rs=20
and&nbsp;a detour might be such that a different anycast dest. node becomes=20=
more=20
suitable to go for.</DIV>
<DIV>Yes,&nbsp;these are not ECMP alternative paths but genuine detours whic=
h to=20
offer/handle would be part of strategy C as well.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1234808039--

From tony.li@tony.li  Mon Feb 16 12:59:22 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 834E63A6D0C for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 12:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
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 1VxZZqsv1l1a for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 12:59:21 -0800 (PST)
Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id 9D58C3A6AA2 for <rrg@irtf.org>; Mon, 16 Feb 2009 12:59:21 -0800 (PST)
Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA10.westchester.pa.mail.comcast.net with comcast id GiMU1b0040QuhwU5AkzY5g; Mon, 16 Feb 2009 20:59:32 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA02.westchester.pa.mail.comcast.net with comcast id GkzH1b00G5Up7oj3NkzLWy; Mon, 16 Feb 2009 20:59:30 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, "'Lixia Zhang'" <lixia@cs.ucla.edu>, <rrg@irtf.org>
References: <20090214010942.179083A68F7@core3.amsl.com><665CECBA-1B95-45F5-841C-EAC200DB7137@cs.ucla.edu> <37910490190A42D79AD68326484DA891@ad.redback.com> <39C363776A4E8C4A94691D2BD9D1C9A10592015E@XCH-NW-7V2.nw.nos.boeing.com>
Date: Mon, 16 Feb 2009 12:59:25 -0800
Message-ID: <0F5EB7FBE3C74E9A80D07BC918AB242C@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10592015E@XCH-NW-7V2.nw.nos.boeing.com>
Thread-Index: AcmOSDXo2HtmvaCIQaGR5siCQQVzlQANtxtwAHQP29AACnqu0A==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [rrg] Fwd: RRG - Requested sessions have been scheduled forIETF 74
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2009 20:59:22 -0000

 

|What are the procedures this time? Send to chairs only?
|Send to a member of the program committee? Other?


As always, please send submissions to the program committee.  The members of
the committee can be found on our wiki page:
http://trac.tools.ietf.org/group/irtf/trac/wiki/RoutingResearchGroup

Tony


From brian.e.carpenter@gmail.com  Mon Feb 16 17:51:31 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A44693A6A00 for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 17:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=-0.399, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 Z9bJe28rPlNX for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 17:51:31 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by core3.amsl.com (Postfix) with ESMTP id EED623A682A for <rrg@irtf.org>; Mon, 16 Feb 2009 17:51:30 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id b25so2013361rvf.7 for <rrg@irtf.org>; Mon, 16 Feb 2009 17:51:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=2vpHUR3fV+djbAjZPnO05KSDbN/FlgJPEHkydIbxLq0=; b=j/GqXBFPOKgNsPt+jH++h+P58kC+t6JsxBMPYXOqb3MjMRxshGB4u+T2shCAxJp/Jq szHjZiA3sy75R0Up9RL/WFnQdzhxUlzactkaRWICjQjgLXmL2np8CiIZv3NZ+aKKVG4a QWZq5kqMKeoo5VQ8AAzTniMs8AAk0qRjlTwig=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=YYjC7+tuDIg5x+UXmiPLlDKhoVxCAMI4M+JVHP9ma4DbmMqu1NS+lAShpopA/w062m IGRHq6cXz81W7gTtJ963Nk7Ym6zoSAnFpKIa345ScKiTkqpJGJr7rQZTuYRFB/aNLTx1 /aV/4UtPMjqbMHx0+zP4Y7pJgg0r0XUABAbMY=
Received: by 10.142.238.4 with SMTP id l4mr2650132wfh.339.1234835500299; Mon, 16 Feb 2009 17:51:40 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 27sm6940685wfa.10.2009.02.16.17.51.38 (version=SSLv3 cipher=RC4-MD5); Mon, 16 Feb 2009 17:51:39 -0800 (PST)
Message-ID: <499A1827.6030302@gmail.com>
Date: Tue, 17 Feb 2009 14:51:35 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>
References: <20090215225810.GI43732@cisco.com> <49991A28.8080007@it.uc3m.es> <4999919E.2070006@employees.org>
In-Reply-To: <4999919E.2070006@employees.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 01:51:31 -0000

On 2009-02-17 05:17, Scott Brim wrote:
> marcelo bagnulo braun allegedly wrote on 02 16 2009 2:47 AM:
>> Hi Scott,
>>
>> Scott Brim escribi=C3=B3:
>>> A few thoughts on this quick draft:
>>>
>>> Pure higher-layer approaches aren't acceptable:
>>>
>>>   - We knew that already, for operational reasons other than
>>>     renumbering, for example the shim6 argument.=20
>>>  =20
>> what is the shim6 argument?
>=20
> The argument that took place between the IETF and network operators whe=
n
> shim6 was recommended.

SHIM6 is in development, so I don't think it's ever been recommended yet,=

and anyway it's not the RRG's job to decide. So can we just
say that solutions above the network layer (including shim6, sctp
and multipath transport) are simply out of scope: the RRG has decided
not to work on them. Anything else is speculation.

>=20
>>>   - But that doesn't mean those technologies aren't essential, becaus=
e
>>>     even if an endpoint only has a single locator within a domain,
>>>     both endpoints and networks will be multihomed and/or mobile, so
>>>     they will at least appear to have multiple locators in global
>>>     routing.  Shim6, HIP, SCTP, Multipath ... all are potentially ver=
y
>>>     useful.  It's probably outside of the scope of RRG since they do
>>>     nothing to solve routing scaling,=20
>> what do you mean they do nothing to solve the routing scalability?
>> If every site and host uses only PA addresses, the routing system woul=
d
>> scale in the order of ISPs, reducing the contribution by the multihome=
d
>> sites.
>=20
> But that won't happen, because it requires site renumbering, multiple
> locators per host within a domain, extra policy management and so on --=

> the things we discovered were operational showstoppers.  The host-based=

> mechanisms are vitally important but not as solutions to routing proble=
ms.

Actually, they are things we opined are currently viewed as operational
showstoppers. I believe the telcos used to view TCP/IP as an operational
showstopper. It just isn't worth the argument; just say that the RRG deci=
ded
not to consider these as in scope.

    Brian


From tony.li@tony.li  Mon Feb 16 21:52:27 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B87953A69CE for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 21:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[AWL=-0.320,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 6I9dm0yQ3oZN for <rrg@core3.amsl.com>; Mon, 16 Feb 2009 21:52:26 -0800 (PST)
Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id 772D33A69B1 for <rrg@irtf.org>; Mon, 16 Feb 2009 21:52:26 -0800 (PST)
Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA01.westchester.pa.mail.comcast.net with comcast id GtoL1b0030QuhwU51tsYbU; Tue, 17 Feb 2009 05:52:32 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA02.westchester.pa.mail.comcast.net with comcast id GtsF1b00F5Up7oj3NtsJiC; Tue, 17 Feb 2009 05:52:30 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "'Scott Brim'" <swb@employees.org>
References: <20090215225810.GI43732@cisco.com> <49991A28.8080007@it.uc3m.es><4999919E.2070006@employees.org> <499A1827.6030302@gmail.com>
Date: Mon, 16 Feb 2009 21:51:38 -0800
Message-ID: <17ADF9A21CBD494BA84BBB8B47ABB544@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <499A1827.6030302@gmail.com>
Thread-Index: AcmQok5U4O65DO9rT6iLuJvhwf3iuwAIMWrw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 05:52:28 -0000

 

Hi Brian,


|> The argument that took place between the IETF and network 
|operators when
|> shim6 was recommended.
|
|SHIM6 is in development, so I don't think it's ever been 
|recommended yet,
|and anyway it's not the RRG's job to decide. 


I distinctly recall it being recommended at a NANOG long ago and the ensuing
broohaha.

|So can we just
|say that solutions above the network layer (including shim6, sctp
|and multipath transport) are simply out of scope: the RRG has decided
|not to work on them. Anything else is speculation.


Except that that's not exactly true.  The RRG has not exactly declared them
out of scope.  So far, solutions that are above the networking layer require
per-host renumbering, and we have consensus that those solutions are not
acceptable.  If someone figured out an architecture (possibly combining
automated renumbering technology) that fixed things above the network layer
in an acceptable fashion, we would definitely consider it.

Tony


From dmm@1-4-5.net  Tue Feb 17 07:34:58 2009
Return-Path: <dmm@1-4-5.net>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6499928C10A for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 07:34:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 zZX2Dtrt4qC3 for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 07:34:57 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id 71ECF28B56A for <rrg@irtf.org>; Tue, 17 Feb 2009 07:34:57 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n1HFZ6wO014751;  Tue, 17 Feb 2009 07:35:06 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n1HFZ5Hx014750; Tue, 17 Feb 2009 07:35:05 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 17 Feb 2009 07:35:05 -0800
From: David Meyer <dmm@1-4-5.net>
To: Tony Li <tony.li@tony.li>
Message-ID: <20090217153505.GA14448@1-4-5.net>
References: <20090215225810.GI43732@cisco.com> <499A1827.6030302@gmail.com> <17ADF9A21CBD494BA84BBB8B47ABB544@ad.redback.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI"
Content-Disposition: inline
In-Reply-To: <17ADF9A21CBD494BA84BBB8B47ABB544@ad.redback.com>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 15:34:58 -0000

--+HP7ph2BbKc20aGI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> |SHIM6 is in development, so I don't think it's ever been=20
> |recommended yet,
> |and anyway it's not the RRG's job to decide.=20
>=20
> I distinctly recall it being recommended at a NANOG long ago and the ensu=
ing
> broohaha.

	Do you mean shim6 was recommended at a NANOG? I don't
	remember that, so can you be more specific? I don't
	remember what "broohaha" you're talking about either, so
	more specificity on that would be helpful as well.

	That said, there was a flurry of activity in various
	operator fora (RIPE, NANOG, APRICOT) in the 2006-2007
	timeframe (for what should be obvious reasons). See=20
	http://www.nanog.org/meetings/nanog35/agenda.php or=20
	http://www.nanog.org/meetings/nanog37/agenda.php for
	example.=20

	In addition, for those interested in understanding why
	operators have been/are concerned, I highly recommend

	 http://www.nanog.org/meetings/nanog35/presentations/schiller.pdf

	as a place to start.

	Dave

=09

--+HP7ph2BbKc20aGI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkma2SkACgkQORgD1qCZ2KejPQCfUvILgtWQCCWk/p1CWKV2x6L/
esMAn2If0AxcKijv3mATSNfi11TBCv1F
=aZb2
-----END PGP SIGNATURE-----

--+HP7ph2BbKc20aGI--

From brian.e.carpenter@gmail.com  Tue Feb 17 12:09:31 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFFA53A693C for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 12:09:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.142
X-Spam-Level: 
X-Spam-Status: No, score=-2.142 tagged_above=-999 required=5 tests=[AWL=-0.342, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 5yb3epyOtYp7 for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 12:09:31 -0800 (PST)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by core3.amsl.com (Postfix) with ESMTP id CE00F3A69D6 for <rrg@irtf.org>; Tue, 17 Feb 2009 12:09:30 -0800 (PST)
Received: by an-out-0708.google.com with SMTP id b6so1975615ana.37 for <rrg@irtf.org>; Tue, 17 Feb 2009 12:09:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=7T4iMvK1JeyZ59v3VFu1CznbWK7JFywLDiZHATl9PLk=; b=Pt+7cyEcWqO/Jd5ounBQpR2c9CfNhmEcDoCbUGRJSdTphRM93jBhNVxYxpJT3XMaXR 2qoffHKqef8BJGXuXqDgvhOMCCVxBQCYYPWfOF6DFaN6PnqpUQ3GtGxryElIKGD65ZKE ZKbutNPP1O++9wfj8+nyvd/km1i++0ne+TgW8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=UUUFfAwezGZeFTkWtFQinYqL1V/TnNqnezJAQkINf9r/1K/xEpaD4F4m3pbqnuGOU5 8rDdJBrKyJYwUED+5KSMHbpOY06yfAJTebzVh4IWzyLncyDDxwDF3SHH24x20huGPAzh Zy4pVY0/lr2Jp15QICkJwyDUdzikKLRHgWhvw=
Received: by 10.143.12.11 with SMTP id p11mr531470wfi.19.1234901380578; Tue, 17 Feb 2009 12:09:40 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 24sm18498370wff.42.2009.02.17.12.09.38 (version=SSLv3 cipher=RC4-MD5); Tue, 17 Feb 2009 12:09:40 -0800 (PST)
Message-ID: <499B197F.4010605@gmail.com>
Date: Wed, 18 Feb 2009 09:09:35 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tony.li@tony.li
References: <20090215225810.GI43732@cisco.com> <49991A28.8080007@it.uc3m.es><4999919E.2070006@employees.org> <499A1827.6030302@gmail.com> <17ADF9A21CBD494BA84BBB8B47ABB544@ad.redback.com>
In-Reply-To: <17ADF9A21CBD494BA84BBB8B47ABB544@ad.redback.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 20:09:31 -0000

On 2009-02-17 18:51, Tony Li wrote:
>  
> 
> Hi Brian,
> 
> 
> |> The argument that took place between the IETF and network 
> |operators when
> |> shim6 was recommended.
> |
> |SHIM6 is in development, so I don't think it's ever been 
> |recommended yet,
> |and anyway it's not the RRG's job to decide. 
> 
> 
> I distinctly recall it being recommended at a NANOG long ago and the ensuing
> broohaha.

Advocated, certainly. Brouhaha, certainly. But every still shim6 document still
contains the words "valid for a maximum of six months" and it isn't even
aimed at ISPs anyway.

> 
> |So can we just
> |say that solutions above the network layer (including shim6, sctp
> |and multipath transport) are simply out of scope: the RRG has decided
> |not to work on them. Anything else is speculation.
> 
> 
> Except that that's not exactly true.  The RRG has not exactly declared them
> out of scope.  So far, solutions that are above the networking layer require
> per-host renumbering, and we have consensus that those solutions are not
> acceptable.  If someone figured out an architecture (possibly combining
> automated renumbering technology) that fixed things above the network layer
> in an acceptable fashion, we would definitely consider it.

Right. So the wording needs to be more subtle.

   Brian

From brian.e.carpenter@gmail.com  Tue Feb 17 12:13:44 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 655633A6AF9 for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 12:13:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 z5kIqzN7OnMb for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 12:13:43 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by core3.amsl.com (Postfix) with ESMTP id 853173A6882 for <rrg@irtf.org>; Tue, 17 Feb 2009 12:13:43 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 27so2842620wfd.7 for <rrg@irtf.org>; Tue, 17 Feb 2009 12:13:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vylQbZnDaWGq2v7TlwtPFV+h9re9+8AwXipg8y2DEvE=; b=uMe80k0g8SYuGxWD+k3N2cZ3ZBEx+nZNrGDkqxlYNFzGl6MAGHc5+kNiJqsvx7GlU1 bZTPfyYQ75YGVhBbB8LO/C9cwByBQ2ube1p2AjqksneCdVnRQckt2znqQQDESv/24Sag dqrHG51U9mA93eoEzB9moUepQPieN5u7NRpkg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=UrNkrIgExkwfAvIHg/+TFB5FaNwjI0NJSm492tbxRrzMHXo+sDi3A6NaO8wDaeelJ1 /Nic3XcL1ra85nfCoB+nPERYG7xpBLbnWt+FvvI0K0dUN2LGudYxNRcOLHpcdjmVI+yh y2oXiobcvYRcDxJvF39ebzkp2izZ28dyqOIig=
Received: by 10.142.100.1 with SMTP id x1mr1979056wfb.256.1234901634835; Tue, 17 Feb 2009 12:13:54 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 20sm8626122wfi.12.2009.02.17.12.13.52 (version=SSLv3 cipher=RC4-MD5); Tue, 17 Feb 2009 12:13:54 -0800 (PST)
Message-ID: <499B1A7E.3050702@gmail.com>
Date: Wed, 18 Feb 2009 09:13:50 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: David Meyer <dmm@1-4-5.net>
References: <20090215225810.GI43732@cisco.com> <499A1827.6030302@gmail.com> <17ADF9A21CBD494BA84BBB8B47ABB544@ad.redback.com> <20090217153505.GA14448@1-4-5.net>
In-Reply-To: <20090217153505.GA14448@1-4-5.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 20:13:44 -0000

> 	In addition, for those interested in understanding why
> 	operators have been/are concerned, I highly recommend
> 
> 	 http://www.nanog.org/meetings/nanog35/presentations/schiller.pdf

That was a good talk, but 3 years ago, and I think Marcelo will tell you
that shim6 has evolved since then.

   Brian

From dmm@1-4-5.net  Tue Feb 17 14:44:49 2009
Return-Path: <dmm@1-4-5.net>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EED843A6A8A for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 14:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 aosTLRLDkw5P for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 14:44:49 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id 6B2CF3A6A97 for <rrg@irtf.org>; Tue, 17 Feb 2009 14:44:29 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n1HMicHC029338;  Tue, 17 Feb 2009 14:44:38 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n1HMicaQ029337; Tue, 17 Feb 2009 14:44:38 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 17 Feb 2009 14:44:38 -0800
From: David Meyer <dmm@1-4-5.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20090217224438.GA29319@1-4-5.net>
References: <20090215225810.GI43732@cisco.com> <499A1827.6030302@gmail.com> <17ADF9A21CBD494BA84BBB8B47ABB544@ad.redback.com> <20090217153505.GA14448@1-4-5.net> <499B1A7E.3050702@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3"
Content-Disposition: inline
In-Reply-To: <499B1A7E.3050702@gmail.com>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2009 22:44:50 -0000

--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 18, 2009 at 09:13:50AM +1300, Brian E Carpenter wrote:
>=20
> > 	In addition, for those interested in understanding why
> > 	operators have been/are concerned, I highly recommend
> >=20
> > 	 http://www.nanog.org/meetings/nanog35/presentations/schiller.pdf
>=20
> That was a good talk, but 3 years ago, and I think Marcelo will tell you
> that shim6 has evolved since then.

	And?

	Dave


--r5Pyd7+fXNt84Ff3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmbPdYACgkQORgD1qCZ2KfavgCdGKemJxfGfn+LwF88QbnyO/k2
LywAn2Y45vdf+R0m3clle9Hud6FSIy6C
=u4s8
-----END PGP SIGNATURE-----

--r5Pyd7+fXNt84Ff3--

From brian.e.carpenter@gmail.com  Tue Feb 17 16:58:20 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 236693A6A1A for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 16:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.066
X-Spam-Level: 
X-Spam-Status: No, score=-2.066 tagged_above=-999 required=5 tests=[AWL=-0.266, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 BW3xcZdYWrxF for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 16:58:19 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by core3.amsl.com (Postfix) with ESMTP id 5188E3A6839 for <rrg@irtf.org>; Tue, 17 Feb 2009 16:58:19 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id b25so2532433rvf.7 for <rrg@irtf.org>; Tue, 17 Feb 2009 16:58:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=KQLemE1wERZPiwHPoI5CtB01dfPwXWj3wTnwmOt12vw=; b=svOfbvLzigZcaDLF1qQUgLLsAQmT90SsIROTiEXXimMTS8Z3hzy92+6q5TlmiUEc03 8NM7ac1077HTxf6+mhfs6vpfUMdhozVSbPYxxAbrAYKHHgjLu+pgFWLBJccNq9YL+RmG JYJ4+Ia1DNHUsFpslJXEC+a+Ltcql4jr6ziRo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=WZdfWVYozmPi5bskulP9fptRtbZKR9zJAGPWH0yep3VJGq6SPktHkNoWVgltlPkPn4 +g0mxXIWoZfvxUJxt3TZga7lsumj1UxddPyXY0e4Tao2pkiHnmfDBBcwW2TqwO1jAqrW QO3VZIB+ulr72VL0W/o8N0BFg/RgKKlLMBcJM=
Received: by 10.141.168.2 with SMTP id v2mr3818rvo.47.1234918709673; Tue, 17 Feb 2009 16:58:29 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id b8sm15220250rvf.8.2009.02.17.16.58.28 (version=SSLv3 cipher=RC4-MD5); Tue, 17 Feb 2009 16:58:29 -0800 (PST)
Message-ID: <499B5D32.909@gmail.com>
Date: Wed, 18 Feb 2009 13:58:26 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <20090215063001.A53163A6980@core3.amsl.com>
In-Reply-To: <20090215063001.A53163A6980@core3.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2009 00:58:20 -0000

Hi,

Thanks for this draft. A few more comments from me:

> 3.1.1.  Transport

Probably useful to state that this is layer 4. I understand that over
at the ITU-T they have changed the meaning of the word 'transport' to
mean layer 2 (presumably in an effort to forget about OSI).

...
>    The consensus of the
>    group is that such site renumbering is a completely unacceptable
>    requirement and as such, these types of solutions are not of interest
>    for further exploration.

Mild rewrite as

   The consensus of the
   group is that such site renumbering is widely unacceptable for
   operational reasons and thus, these types of solutions are not of
   interest for further exploration in this group.

> 3.1.2.  Translation

Reading further, it occurred to me that this really should
be called Map & Translate, and that we should distinguish
stateful and stateless translation.

Also distinguish reversible and non-reversible translation.

It would be good if this and the following section brought out
the isomorphisms and differences between translation and
encapsulation very clearly.
(NAT is just swapping RLOC and EID, for example, but NAPT is
munging EIDs together before doing the swap.)

> 4.1.  No manual renumbering of end hosts
> 
>    There is clear consensus in the group that renumbering of sites must
>    not require manual intervention on a per-host basis.  

Yes. You might consider a reference to draft-carpenter-renum-needs-work
(the -02 draft will be out in a day or two). I'm not suggesting that
should be an RRG document; in fact it's being discussed in the IETF
Ops Area. But it does discuss exactly this topic.

    Brian

From rw@firstpr.com.au  Tue Feb 17 22:55:21 2009
Return-Path: <rw@firstpr.com.au>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8228E28C1AA for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 22:55:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.096 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, SARE_SUB_RAND_LETTRS4=0.799]
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 LWMLhBuVj4uK for <rrg@core3.amsl.com>; Tue, 17 Feb 2009 22:55:20 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 18FA328C1A3 for <rrg@irtf.org>; Tue, 17 Feb 2009 22:55:19 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 96924175D1D; Wed, 18 Feb 2009 17:55:30 +1100 (EST)
Message-ID: <499BB0E4.1050206@firstpr.com.au>
Date: Wed, 18 Feb 2009 17:55:32 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [rrg] draft-irtf-rrg-recommendation-00 - Modified-Header Forwarding (MHF)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2009 06:55:21 -0000

Hi Tony,

I fully support the recommendation that we spend another year
devising our final recommendation.


Here is some suggested text to add after "3.1.3 Map & Encap".

The two MHF techniques are:

  ETR Address Forwarding (EAF) - for IPv4  (A4g)
  30 bits for the ETR address
  http://tools.ietf.org/html/draft-whittle-ivip4-etr-addr-forw


  Prefix Label Forwarding (PLF) - for IPv6  (A4f)
  19 or 20 bits to identify the BGP advertised prefix of the ETR
  http://www.firstpr.com.au/ip/ivip/ivip6/


  Regards

    - Robin



3.1.4 Map & Forward with Modified Header Forwarding (MHF)

An alternative mechanism to Map & Encap retains the mapping system
and overall structure of tunneling the traffic packet across the DFZ
to a tunnel endpoint device at the RLOC address - which forwards the
packet directly to the destination network.  Instead of
encapsulation, Modified Header Forwarding (MHF) alters the IP header
of the original packet to include sufficient bits to specify part or
all of the RLOC address of the tunnel endpoint device.  That device
restores the original state of the IP header and forwards the traffic
packet directly to the destination network.

Strategy A4f (below) provides enough bits in a modified IPv6 header
for routers to forward the packet to the ISP network which contains
the RLOC device.  Strategy A4g encodes a 30 bit RLOC address into a
modified IPv4 header so the packet can be forwarded all the way to
the tunnel endpoint.

The primary advantages of these techniques are elimination of
encapsulation overhead and of the Path MTU Discovery problems which
are inherent in any encapsulation-based tunneling solution.

The primary disadvantage is the need for all DFZ, and some internal,
routers to be upgraded to recognise the altered IP header format.
For IPv4 an additional constraint is lack of support for fragmented
packets or fragmentable packets longer than some constant, likely to
be somewhat less than 1500 bytes.  However, similar constraints may
apply to any system which adequately manages the PMTUD problems
caused by encapsulation.

These techniques could be used by adapting any Map & Encap
architecture which does not need to carry further bits of information
with the traffic packet and which does not require the tunnel
endpoint to be able to determine which device tunneled the packet.
For such an architecture, MHF could be used as a more efficient
long-term alternative to encapsulation.

Alternatively, if the routers could be upgraded in time for the
introduction of the scalable routing solution, these techniques could
be used from the outset, eliminating the need for development of
encapsulation techniques and of solutions to the resultant PMTUD
problems.












From tonyli@redback.com  Wed Feb 18 23:18:38 2009
Return-Path: <tonyli@redback.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 082903A6975 for <rrg@core3.amsl.com>; Wed, 18 Feb 2009 23:18:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 UkV6JI0DK6Od for <rrg@core3.amsl.com>; Wed, 18 Feb 2009 23:18:37 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id 780573A6783 for <rrg@irtf.org>; Wed, 18 Feb 2009 23:18:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 536A413D236 for <rrg@irtf.org>; Wed, 18 Feb 2009 23:18:50 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10679-03 for <rrg@irtf.org>; Wed, 18 Feb 2009 23:18:50 -0800 (PST)
Received: from rbsjx.ad.redback.com (rbsjxh2.redback.com [155.53.14.106]) by prattle.redback.com (Postfix) with ESMTP id 0CA9913D235 for <rrg@irtf.org>; Wed, 18 Feb 2009 23:18:50 -0800 (PST)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by rbsjxh2.ad.redback.com ([155.53.14.106]) with mapi; Wed, 18 Feb 2009 23:18:49 -0800
From: Tony Li <tonyli@redback.com>
To: RRG <rrg@irtf.org>
Date: Wed, 18 Feb 2009 23:18:44 -0800
Thread-Topic: Program committee mailing list bug fix
Thread-Index: AcmSYkxZ2sH+Xhz7RkeV0uTVtKIwTg==
Message-ID: <B701736AA609BA4AB6555D5E7BC490FB9E91B23417@RBSJX.ad.redback.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Subject: [rrg] Program committee mailing list bug fix
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2009 07:18:38 -0000

Hi all,

It's come to our attention that the advertised mailing list for the program=
 committee was incorrect. =20

Our wiki page has now been corrected.  If you've send a message previously,=
 please resend it to the new address.

Our apologies for the error.

Tony

From brian.e.carpenter@gmail.com  Fri Feb 20 13:07:09 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD8A73A63D3 for <rrg@core3.amsl.com>; Fri, 20 Feb 2009 13:07:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 F7G8uhMEHVuz for <rrg@core3.amsl.com>; Fri, 20 Feb 2009 13:07:09 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.185]) by core3.amsl.com (Postfix) with ESMTP id 72D3A28C1FA for <rrg@irtf.org>; Fri, 20 Feb 2009 13:07:05 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so761755tic.11 for <rrg@irtf.org>; Fri, 20 Feb 2009 13:07:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:content-type :content-transfer-encoding; bh=jb79tuBvh3Utixd8RJbJSbEqwrqZvP0eVkX1p0usrHg=; b=lGLtk0jl9JIV7h9EUnho/E8sotG45OMCWVO+1Nxk2n6xhZAhObGMGdxyRMX6SnGTLw SeARVmBhidTESdWxhE9zCTFkleiWjFXPLWiPCljSi3Eu9o3GlBICqBmDjaL3NQChXoli M+HpdJQ2dNuBwG1LsdRvTHLIUMN3TMfxjYNq4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; b=kZQgcVidAaOshxq20/HKvxeMM23vuSwnX6uVH9Bekavhi8bZ+KMujJppFuDD8jJhzD og7LEvnivsU62NRW8y2ymzQpAh/27KdK5C9ZHWDaqYLlNCgnsE77R6R0Qs4+1YceKN+4 z4ESo+6wQXwaFHkviF+9gAInh/03PhCgVdII0=
Received: by 10.110.69.5 with SMTP id r5mr1610364tia.36.1235164039742; Fri, 20 Feb 2009 13:07:19 -0800 (PST)
Received: from ?10.1.1.4? (118-92-129-217.dsl.dyn.ihug.co.nz [118.92.129.217]) by mx.google.com with ESMTPS id 14sm1874663tim.9.2009.02.20.13.07.17 (version=SSLv3 cipher=RC4-MD5); Fri, 20 Feb 2009 13:07:18 -0800 (PST)
Message-ID: <499F1B82.3090209@gmail.com>
Date: Sat, 21 Feb 2009 10:07:14 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: RJ Atkinson <rja@extremenetworks.com>
Subject: [rrg] Renumbering needs work version 02
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2009 21:07:09 -0000

A draft on this topic has been updated:
http://www.ietf.org/internet-drafts/draft-carpenter-renum-needs-work-02.txt

Comments and discussion are invited on the OPS Area list,
ops-area@ietf.org

  Brian Carpenter
  Ran Atkinson
  Hannu Flinck

P.S. Apologies if you receive multiple copies, but that seems
preferable to cross-posting to multiple lists.



From swb@employees.org  Sat Feb 21 12:41:57 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 213BE28C1A6 for <rrg@core3.amsl.com>; Sat, 21 Feb 2009 12:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.938
X-Spam-Level: 
X-Spam-Status: No, score=-4.938 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, FAKE_REPLY_C=2.012, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 D4fTuvl-151K for <rrg@core3.amsl.com>; Sat, 21 Feb 2009 12:41:53 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id C361828C139 for <rrg@irtf.org>; Sat, 21 Feb 2009 12:41:52 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,246,1233532800"; d="scan'208";a="37937789"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 21 Feb 2009 20:42:07 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n1LKg7RF002629 for <rrg@irtf.org>; Sat, 21 Feb 2009 15:42:07 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1LKg7YG002859 for <rrg@irtf.org>; Sat, 21 Feb 2009 20:42:07 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 21 Feb 2009 15:42:07 -0500
Received: from cisco.com ([10.86.241.2]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 21 Feb 2009 15:42:07 -0500
Date: Sat, 21 Feb 2009 15:42:02 -0500
From: Scott Brim <swb@employees.org>
To: rrg@irtf.org
Message-ID: <20090221204202.GN54483@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg@irtf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 21 Feb 2009 20:42:07.0223 (UTC) FILETIME=[DC684070:01C99464]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Feb 2009 20:41:57 -0000

Hi.  A few questions ...

> 3.1.  A Mechanism Taxonomy
> 
>    In this taxonomy, solutions are grouped by the primary mechanisms
>    that they use to achieve their goals.

I'm wondering, in the categories {transport, translation,
encapsulation}, where would you put shim6?  It's below transport.
Would you say rewriting is translation?  Would you say an addition of
a header is an encapsulation?   

> 3.1.2.  Translation
> 
>    Translation solutions are characterized by a translation
>    operation between an identifier to a locator and back to an
>    identifier as the packet traverses the network.

Now that I've pondered this a little, I can't think of any approach
that does that (translate from identifier to locator and back again).
GSE only does it in one direction (->RLOC for source, ->ID for
destination).  GSE uses identifiers internally but does not need to
translate outgoing destination addresses or incoming source addresses
since they are already in RLOC form and must stay that way.  NAT-based
approaches and Six/One Router are also one-way: the local source
address is translated to an RLOC when outgoing, and the destination
address is translated to a local address when incoming.  Also except
for GSE and ILNP, the local "thing" is not an "identifier" in the
sense that the term is used here, a topology-independent name of a
single endpoint, or node ID.  It is a locator with limited scope.
Except in the case of GSE and ILNP it still names an attachment point
and has topological significance.

> 3.3.1.  Strategy A
> 
>    Local routing is based on an address, which functions as a GUID,
>    SID component and local locator,

Should this be an "and/or" or "or" instead of an "and"?  Or is this
supposed to be an in-line definition of "address"?  A local locator is
not necessarily also part of a session ID.

> 3.3.2.2.  Identifier variants
> 
>    B2a  Each host has a single numeric identifer to which the
>         locators are attached.  This identifier is used by the
>         layer-4/5 and higher protocols to compose the SID.
> 
>    B2b  Each service provided by a host has a globally unique,
>         hierarchical character-string identifier to which the
>         locators are attached.  Clients initiating communication
>         with that service negotiate a numeric SID which is unique
>         only within the scope of that service.

In this section I don't see the relevance of "numeric" and
"character-string".  To the functions using these identifiers, they
are just bits, regardless of what semantics a human might see in them.

Scott

From brian.e.carpenter@gmail.com  Sat Feb 21 13:02:54 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76EC428C139 for <rrg@core3.amsl.com>; Sat, 21 Feb 2009 13:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.399,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 2MrTQd8ZQhcf for <rrg@core3.amsl.com>; Sat, 21 Feb 2009 13:02:53 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.190]) by core3.amsl.com (Postfix) with ESMTP id 0D8513A6892 for <rrg@irtf.org>; Sat, 21 Feb 2009 13:02:52 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so1015399tic.11 for <rrg@irtf.org>; Sat, 21 Feb 2009 13:03:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=4m5IwbTNyXcjXJZEyYZuCJ21QTmIyjhQhuphwBbEkiw=; b=t5wih18vF1vAPEJOBsETnHkNik98OKVdbI4fUfGVwht4Qz+M1p3UkR/03lHdVz/mkt 9Jgbbh2wQ0LS6FPQQVcfPLMwyjptho0FOl/JGHq4TsccB91Me7TtjnZt3XaO8tCH2/wq ZATx/6cBdmOstcmuCQuYy9gQTCKlNPJn8iFvg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=UL+qS5OWRCe8k/FMIdYNYVjqpWIh3jT/u+67pCOY+8/w3xElp/Y2W6mM0CH8i3BdjV RXIclfLC2UTqhXNxSm6420cLs4qvNyGHZRnzjuftgrKA+77xEbveNQOCEw6eT5SzatXo +VFFmgA4V5F59BYJJ1KAi3/0h0vwJtOgMfB5c=
Received: by 10.110.92.8 with SMTP id p8mr3166304tib.19.1235250187729; Sat, 21 Feb 2009 13:03:07 -0800 (PST)
Received: from ?10.1.1.4? (118-92-121-122.dsl.dyn.ihug.co.nz [118.92.121.122]) by mx.google.com with ESMTPS id d7sm2202969tib.2.2009.02.21.13.03.04 (version=SSLv3 cipher=RC4-MD5); Sat, 21 Feb 2009 13:03:06 -0800 (PST)
Message-ID: <49A06C03.3050101@gmail.com>
Date: Sun, 22 Feb 2009 10:02:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>,  rrg@irtf.org
References: <20090221204202.GN54483@cisco.com>
In-Reply-To: <20090221204202.GN54483@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Feb 2009 21:02:54 -0000

Scott,

On 2009-02-22 09:42, Scott Brim wrote:
> Hi.  A few questions ...
> 
>> 3.1.  A Mechanism Taxonomy
>>
>>    In this taxonomy, solutions are grouped by the primary mechanisms
>>    that they use to achieve their goals.
> 
> I'm wondering, in the categories {transport, translation,
> encapsulation}, where would you put shim6?  It's below transport.
> Would you say rewriting is translation?  Would you say an addition of
> a header is an encapsulation?   
> 
>> 3.1.2.  Translation
>>
>>    Translation solutions are characterized by a translation
>>    operation between an identifier to a locator and back to an
>>    identifier as the packet traverses the network.
> 
> Now that I've pondered this a little, I can't think of any approach
> that does that (translate from identifier to locator and back again).
> GSE only does it in one direction (->RLOC for source, ->ID for
> destination).  

Shim6 does both translations in the case that ULID != RLOC, which
I think also answers your previous question. But certainly,
reversibility vs non-reversibility, and whether the translation
affects source, destination, or both, are facets of the taxonomy, I think.

    Brian

GSE uses identifiers internally but does not need to
> translate outgoing destination addresses or incoming source addresses
> since they are already in RLOC form and must stay that way.  NAT-based
> approaches and Six/One Router are also one-way: the local source
> address is translated to an RLOC when outgoing, and the destination
> address is translated to a local address when incoming.  Also except
> for GSE and ILNP, the local "thing" is not an "identifier" in the
> sense that the term is used here, a topology-independent name of a
> single endpoint, or node ID.  It is a locator with limited scope.
> Except in the case of GSE and ILNP it still names an attachment point
> and has topological significance.
> 
>> 3.3.1.  Strategy A
>>
>>    Local routing is based on an address, which functions as a GUID,
>>    SID component and local locator,
> 
> Should this be an "and/or" or "or" instead of an "and"?  Or is this
> supposed to be an in-line definition of "address"?  A local locator is
> not necessarily also part of a session ID.
> 
>> 3.3.2.2.  Identifier variants
>>
>>    B2a  Each host has a single numeric identifer to which the
>>         locators are attached.  This identifier is used by the
>>         layer-4/5 and higher protocols to compose the SID.
>>
>>    B2b  Each service provided by a host has a globally unique,
>>         hierarchical character-string identifier to which the
>>         locators are attached.  Clients initiating communication
>>         with that service negotiate a numeric SID which is unique
>>         only within the scope of that service.
> 
> In this section I don't see the relevance of "numeric" and
> "character-string".  To the functions using these identifiers, they
> are just bits, regardless of what semantics a human might see in them.
> 
> Scott
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
> 

From swb@employees.org  Sat Feb 21 13:16:44 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37A733A69AA for <rrg@core3.amsl.com>; Sat, 21 Feb 2009 13:16:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.801
X-Spam-Level: 
X-Spam-Status: No, score=-5.801 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 A5R8uiADePEk for <rrg@core3.amsl.com>; Sat, 21 Feb 2009 13:16:42 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id ABEAB3A693F for <rrg@irtf.org>; Sat, 21 Feb 2009 13:16:42 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,246,1233532800"; d="scan'208";a="37939247"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 21 Feb 2009 21:16:58 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n1LLGvgN009921;  Sat, 21 Feb 2009 16:16:57 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n1LLGvFM015136; Sat, 21 Feb 2009 21:16:57 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 21 Feb 2009 16:16:57 -0500
Received: from cisco.com ([10.86.241.2]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 21 Feb 2009 16:16:57 -0500
Date: Sat, 21 Feb 2009 16:16:55 -0500
From: Scott Brim <swb@employees.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20090221211655.GO54483@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, RRG <rrg@irtf.org>
References: <20090215063001.A53163A6980@core3.amsl.com> <499B5D32.909@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <499B5D32.909@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 21 Feb 2009 21:16:57.0163 (UTC) FILETIME=[BA1BC9B0:01C99469]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Feb 2009 21:16:44 -0000

Excerpts from Brian E Carpenter on Wed, Feb 18, 2009 01:58:26PM +1300:
> Probably useful to state that this is layer 4. I understand that over
> at the ITU-T they have changed the meaning of the word 'transport' to
> mean layer 2 (presumably in an effort to forget about OSI).

They forgot about OSI years ago.  For a good time see
http://www.itu.int/rec/T-REC-Y.110/en on roles and "added value",
http://www.niven-jenkins.co.uk/An%20introduction%20to%20functional%20architecture.pdf,
and http://www.itu.int/rec/T-REC-Y.2611/en for functional
architecture.  For example in Y.2611 (where "identifier" is a
more-generic including both "name" and "address"):

    Identification is required in each layer network of the NGN
    transport stratum. A given entity will be assigned one or more
    identifiers depending on the function of that entity. FPBN layer
    network identifiers are independent of any client (and any server)
    layer network identifiers even if they share the same syntax or
    structure. At the boundary of a layer network, mapping and/or
    translation mechanisms are required in order to set up
    relationships between the identifier used by the client layer
    network and the identifier used by the server layer network.  

    NOTE â€“ Identifiers could be determined from multiple discontinuous
    fields. The global uniqueness of an identifier may be provided by
    the context as well as the identifier itself. 

    Whether a given identifier is considered to be a name or an
    address is dependent on several factors including the perspective
    (and location) of the entity that is using (or mapping to) that
    identifier.  The same identifier can be considered an address to
    one entity and a name to a different entity because their
    perspective is different. 

> >    The consensus of the
> >    group is that such site renumbering is a completely unacceptable
> >    requirement and as such, these types of solutions are not of interest
> >    for further exploration.
> 
> Mild rewrite as
> 
>    The consensus of the
>    group is that such site renumbering is widely unacceptable for
>    operational reasons and thus, these types of solutions are not of
>    interest for further exploration in this group.

+1

> > 3.1.2.  Translation
> 
> Reading further, it occurred to me that this really should
> be called Map & Translate

I don't see why.  Suppose I'm doing GSE.  I have a simple algorithm
for swapping the upper bits of an address field, and the algorithm is
always the same.  Is that really mapping?  I don't know of any
proposals that do actual mapping and then translating.

> , and that we should distinguish
> stateful and stateless translation.
> 
> Also distinguish reversible and non-reversible translation.

Yes

> It would be good if this and the following section brought out
> the isomorphisms and differences between translation and
> encapsulation very clearly.

Yes

> (NAT is just swapping RLOC and EID, for example, but NAPT is
> munging EIDs together before doing the swap.)

I don't know what you mean, munging EIDs together.  Do you mean
that it uses pieces from different headers?

Scott

From brian.e.carpenter@gmail.com  Sat Feb 21 14:10:43 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CFF53A68DE for <rrg@core3.amsl.com>; Sat, 21 Feb 2009 14:10:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.399,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 vqpkZcqzjT+M for <rrg@core3.amsl.com>; Sat, 21 Feb 2009 14:10:42 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.189]) by core3.amsl.com (Postfix) with ESMTP id 894603A677D for <rrg@irtf.org>; Sat, 21 Feb 2009 14:10:42 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so1021877tic.11 for <rrg@irtf.org>; Sat, 21 Feb 2009 14:10:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=tBa3gYD6Sd/NH423lUjx9N3diKgafFb6Q4UfHq5tPFE=; b=kc+ekhVlNzV1enpjVG65yuOdGW1j1DaNR8l0JkXkrzsBRl63TX/kIXhW/ShJi/AkR9 G3H9ACtisCBPbOZ2FjYqPZgwjvIgakdZQ+moj+xoFv/Co5WTyY/Z7jCNJg2xN5wCSVCS lmG5FZhMnGJ2I2wBz9bzkkvBC8BMnB2MgGw9g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=jeh5q9TywqNO7drV8ipb7i4nTZBadMR9uoAyR6tjz7DKw1WSwN/Cn/vMKYnMTeL+2i rWpEnWT7V2BZqxLfdahlSfx7YRICohHXgoIeWozIXXw9/RPpmjpWrC2b2YDSRdh6D/+L r3eZSdh86v/Tp1wASg8Wm60n6FZYMVy+V0tAA=
Received: by 10.110.31.5 with SMTP id e5mr3221102tie.35.1235254256958; Sat, 21 Feb 2009 14:10:56 -0800 (PST)
Received: from ?10.1.1.3? (118-93-173-24.dsl.dyn.ihug.co.nz [118.93.173.24]) by mx.google.com with ESMTPS id 14sm2229600tim.9.2009.02.21.14.10.54 (version=SSLv3 cipher=RC4-MD5); Sat, 21 Feb 2009 14:10:55 -0800 (PST)
Message-ID: <49A07BE8.4090804@gmail.com>
Date: Sun, 22 Feb 2009 11:10:48 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>, RRG <rrg@irtf.org>
References: <20090215063001.A53163A6980@core3.amsl.com> <499B5D32.909@gmail.com> <20090221211655.GO54483@cisco.com>
In-Reply-To: <20090221211655.GO54483@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Feb 2009 22:10:43 -0000

Scott,


On 2009-02-22 10:16, Scott Brim wrote:
> Excerpts from Brian E Carpenter on Wed, Feb 18, 2009 01:58:26PM +1300:

...
>     Whether a given identifier is considered to be a name or an
>     address is dependent on several factors including the perspective
>     (and location) of the entity that is using (or mapping to) that
>     identifier.  The same identifier can be considered an address to
>     one entity and a name to a different entity because their
>     perspective is different.

Absolutely true.


...

>>> 3.1.2.  Translation
>> Reading further, it occurred to me that this really should
>> be called Map & Translate
> 
> I don't see why.  Suppose I'm doing GSE.  I have a simple algorithm
> for swapping the upper bits of an address field, and the algorithm is
> always the same.  Is that really mapping?  I don't know of any
> proposals that do actual mapping and then translating.

I agree that in most cases the mapping is algorithmic or trivial.
But if you classify shim6 here, it's actually building a small map
for each ULID (~=EID) that it handles.

...

>> (NAT is just swapping RLOC and EID, for example, but NAPT is
>> munging EIDs together before doing the swap.)
> 
> I don't know what you mean, munging EIDs together.  Do you mean
> that it uses pieces from different headers?

No, I mean that it folds many EIDs into one RLOC, using the port
numbers to demultiplex.

   Brian

From tony.li@tony.li  Mon Feb 23 11:41:11 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C62128C111 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 11:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.066
X-Spam-Level: 
X-Spam-Status: No, score=-2.066 tagged_above=-999 required=5 tests=[AWL=-0.266, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 bGHmg+APv7Ag for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 11:41:10 -0800 (PST)
Received: from QMTA04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by core3.amsl.com (Postfix) with ESMTP id 0DDC53A69A2 for <rrg@irtf.org>; Mon, 23 Feb 2009 11:41:09 -0800 (PST)
Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA04.westchester.pa.mail.comcast.net with comcast id KTSb1b0080ldTLk54XhUP0; Mon, 23 Feb 2009 19:41:29 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA04.westchester.pa.mail.comcast.net with comcast id KXhF1b0035Up7oj3QXhHtq; Mon, 23 Feb 2009 19:41:26 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Scott Brim'" <swb@employees.org>, <rrg@irtf.org>
References: <20090221204202.GN54483@cisco.com>
Date: Mon, 23 Feb 2009 11:41:16 -0800
Message-ID: <18AE350EBE534FD69400A43F609967B6@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmUZOeZSaYTXly+QxK7sBYMWrV0jABhMQUg
In-Reply-To: <20090221204202.GN54483@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 19:41:11 -0000

Hi Scott,

|> 3.1.  A Mechanism Taxonomy
|> 
|>    In this taxonomy, solutions are grouped by the primary mechanisms
|>    that they use to achieve their goals.
|
|I'm wondering, in the categories {transport, translation,
|encapsulation}, where would you put shim6?  It's below transport.
|Would you say rewriting is translation?  Would you say an addition of
|a header is an encapsulation?   


As I've said in prior email, I'm less interested in refining this taxonomy.
I agree that there's arguments to put Shim6 in either translation or in map
& encap.  This doesn't seem like a productive argument.


|> 3.1.2.  Translation
|> 
|>    Translation solutions are characterized by a translation
|>    operation between an identifier to a locator and back to an
|>    identifier as the packet traverses the network.
|
|Now that I've pondered this a little, I can't think of any approach
|that does that (translate from identifier to locator and back again).


NAT, for example.


|Also except
|for GSE and ILNP, the local "thing" is not an "identifier" in the
|sense that the term is used here, a topology-independent name of a
|single endpoint, or node ID.  It is a locator with limited scope.


This is a terminology nit.  We've defined "identifier" to have zero
topological significance.  However, that's just taking a black-and-white
view of the world.  It's not unreasonable to have a name that has both
identification semantics and local locator scope.


|> 3.3.1.  Strategy A
|> 
|>    Local routing is based on an address, which functions as a GUID,
|>    SID component and local locator,
|
|Should this be an "and/or" or "or" instead of an "and"?  Or is this
|supposed to be an in-line definition of "address"?  A local locator is
|not necessarily also part of a session ID.


Yes, I think that this is an inline (and local) definition of address.
Obviously, that's not a requirement, just the local definition.


|> 3.3.2.2.  Identifier variants
|> 
|>    B2a  Each host has a single numeric identifer to which the
|>         locators are attached.  This identifier is used by the
|>         layer-4/5 and higher protocols to compose the SID.
|> 
|>    B2b  Each service provided by a host has a globally unique,
|>         hierarchical character-string identifier to which the
|>         locators are attached.  Clients initiating communication
|>         with that service negotiate a numeric SID which is unique
|>         only within the scope of that service.
|
|In this section I don't see the relevance of "numeric" and
|"character-string".  To the functions using these identifiers, they
|are just bits, regardless of what semantics a human might see in them.


Agreed, this is diverging from the conceptual and into the engineering.
References removed here, as well as others that I could trivially find.

Thanks,
Tony


From tony.li@tony.li  Mon Feb 23 11:41:19 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71A5928C0F2 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 11:41:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.028
X-Spam-Level: 
X-Spam-Status: No, score=-2.028 tagged_above=-999 required=5 tests=[AWL=-0.228, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 pg32w2oFScFS for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 11:41:18 -0800 (PST)
Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by core3.amsl.com (Postfix) with ESMTP id 68C7528C0EB for <rrg@irtf.org>; Mon, 23 Feb 2009 11:41:18 -0800 (PST)
Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA06.westchester.pa.mail.comcast.net with comcast id KSzW1b00M0ldTLk56XhdJ1; Mon, 23 Feb 2009 19:41:37 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA04.westchester.pa.mail.comcast.net with comcast id KXhF1b0035Up7oj3QXhV10; Mon, 23 Feb 2009 19:41:35 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "'RRG'" <rrg@irtf.org>
References: <20090215063001.A53163A6980@core3.amsl.com> <499B5D32.909@gmail.com>
Date: Mon, 23 Feb 2009 11:41:16 -0800
Message-ID: <240116669D2F480D83B018E09A985B49@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmRZA0klfWZIY1uS4qWmg5RIC18OwEfqOuQ
In-Reply-To: <499B5D32.909@gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 19:41:19 -0000

Hi Brian,

Thanks for the comments. 

|> 3.1.1.  Transport
|
|Probably useful to state that this is layer 4. I understand that over
|at the ITU-T they have changed the meaning of the word 'transport' to
|mean layer 2 (presumably in an effort to forget about OSI).


Sure thing.  BTW, my understanding is that the PSTN folks were using
'transport' long ago to describe their TDM hierarchy.  In fact, it was these
newfangled packet folks that redefined 'transport'.  ;-)


|>    The consensus of the
|>    group is that such site renumbering is a completely unacceptable
|>    requirement and as such, these types of solutions are not 
|of interest
|>    for further exploration.
|
|Mild rewrite as
|
|   The consensus of the
|   group is that such site renumbering is widely unacceptable for
|   operational reasons and thus, these types of solutions are not of
|   interest for further exploration in this group.


Sure.


|> 3.1.2.  Translation
|
|Reading further, it occurred to me that this really should
|be called Map & Translate, and that we should distinguish
|stateful and stateless translation.


True, but ALL solutions require mapping.  


|Also distinguish reversible and non-reversible translation.


I agree with the differentiation, but I'm really less interested in refining
the taxonomy from section 3.1 unless there's some clear, tangible benefit.
At this point, I'm much more interested in putting our efforts into the
section 3.3 approach.


|> 4.1.  No manual renumbering of end hosts
|> 
|>    There is clear consensus in the group that renumbering of 
|sites must
|>    not require manual intervention on a per-host basis.  
|
|Yes. You might consider a reference to draft-carpenter-renum-needs-work
|(the -02 draft will be out in a day or two). I'm not suggesting that
|should be an RRG document; in fact it's being discussed in the IETF
|Ops Area. But it does discuss exactly this topic.


Plug added.  ;-)

Tony


From tony.li@tony.li  Mon Feb 23 11:41:28 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBAA73A6A34 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 11:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 s2eA3sYxwrHf for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 11:41:27 -0800 (PST)
Received: from QMTA02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by core3.amsl.com (Postfix) with ESMTP id 57C703A69A2 for <rrg@irtf.org>; Mon, 23 Feb 2009 11:41:27 -0800 (PST)
Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA02.westchester.pa.mail.comcast.net with comcast id KT9o1b0070ldTLk52XhmRN; Mon, 23 Feb 2009 19:41:46 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA04.westchester.pa.mail.comcast.net with comcast id KXhF1b0035Up7oj3QXhd77; Mon, 23 Feb 2009 19:41:44 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Robin Whittle'" <rw@firstpr.com.au>, "'RRG'" <rrg@irtf.org>
References: <499BB0E4.1050206@firstpr.com.au>
Date: Mon, 23 Feb 2009 11:41:16 -0800
Message-ID: <1F676BC3FEF04EA197A9211C84FCAE4A@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmRle7XTXeAbcNQRNuY8J2+lPRWLAESdHUQ
In-Reply-To: <499BB0E4.1050206@firstpr.com.au>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00 - Modified-Header Forwarding(MHF)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 19:41:28 -0000

Robin,

Thank you very much for your suggestion.  However, section 3.1.3 (and, for
that matter, all of section 3.1) is much more general than section 3.3.1.4.
I believe that those two techniques are covered quite adequately there.

Regards,
Tony
 

|-----Original Message-----
|From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On 
|Behalf Of Robin Whittle
|Sent: Tuesday, February 17, 2009 10:56 PM
|To: RRG
|Subject: [rrg] draft-irtf-rrg-recommendation-00 - 
|Modified-Header Forwarding(MHF)
|
|Hi Tony,
|
|I fully support the recommendation that we spend another year
|devising our final recommendation.
|
|
|Here is some suggested text to add after "3.1.3 Map & Encap".
|
|The two MHF techniques are:
|
|  ETR Address Forwarding (EAF) - for IPv4  (A4g)
|  30 bits for the ETR address
|  http://tools.ietf.org/html/draft-whittle-ivip4-etr-addr-forw
|
|
|  Prefix Label Forwarding (PLF) - for IPv6  (A4f)
|  19 or 20 bits to identify the BGP advertised prefix of the ETR
|  http://www.firstpr.com.au/ip/ivip/ivip6/
|
|
|  Regards
|
|    - Robin
|
|
|
|3.1.4 Map & Forward with Modified Header Forwarding (MHF)
|
|An alternative mechanism to Map & Encap retains the mapping system
|and overall structure of tunneling the traffic packet across the DFZ
|to a tunnel endpoint device at the RLOC address - which forwards the
|packet directly to the destination network.  Instead of
|encapsulation, Modified Header Forwarding (MHF) alters the IP header
|of the original packet to include sufficient bits to specify part or
|all of the RLOC address of the tunnel endpoint device.  That device
|restores the original state of the IP header and forwards the traffic
|packet directly to the destination network.
|
|Strategy A4f (below) provides enough bits in a modified IPv6 header
|for routers to forward the packet to the ISP network which contains
|the RLOC device.  Strategy A4g encodes a 30 bit RLOC address into a
|modified IPv4 header so the packet can be forwarded all the way to
|the tunnel endpoint.
|
|The primary advantages of these techniques are elimination of
|encapsulation overhead and of the Path MTU Discovery problems which
|are inherent in any encapsulation-based tunneling solution.
|
|The primary disadvantage is the need for all DFZ, and some internal,
|routers to be upgraded to recognise the altered IP header format.
|For IPv4 an additional constraint is lack of support for fragmented
|packets or fragmentable packets longer than some constant, likely to
|be somewhat less than 1500 bytes.  However, similar constraints may
|apply to any system which adequately manages the PMTUD problems
|caused by encapsulation.
|
|These techniques could be used by adapting any Map & Encap
|architecture which does not need to carry further bits of information
|with the traffic packet and which does not require the tunnel
|endpoint to be able to determine which device tunneled the packet.
|For such an architecture, MHF could be used as a more efficient
|long-term alternative to encapsulation.
|
|Alternatively, if the routers could be upgraded in time for the
|introduction of the scalable routing solution, these techniques could
|be used from the outset, eliminating the need for development of
|encapsulation techniques and of solutions to the resultant PMTUD
|problems.
|
|
|
|
|
|
|
|
|
|
|
|_______________________________________________
|rrg mailing list
|rrg@irtf.org
|http://www.irtf.org/mailman/listinfo/rrg
|


From brian.e.carpenter@gmail.com  Mon Feb 23 16:20:37 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C90E3A68E6 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 16:20:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.181
X-Spam-Level: 
X-Spam-Status: No, score=-1.181 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, SARE_SUB_RAND_LETTRS4=0.799]
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 Rkr6E2-dqZix for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 16:20:36 -0800 (PST)
Received: from mail-gx0-f158.google.com (mail-gx0-f158.google.com [209.85.217.158]) by core3.amsl.com (Postfix) with ESMTP id 72F3C3A6981 for <rrg@irtf.org>; Mon, 23 Feb 2009 16:20:33 -0800 (PST)
Received: by gxk2 with SMTP id 2so1958517gxk.7 for <rrg@irtf.org>; Mon, 23 Feb 2009 16:20:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+RrLj+Fz5lx8oKxWmzgeGgDqO006EGW3zQeQAoG/DDM=; b=tW0CNyN+9PEF3mdP/q4RiyCsQ+Nr6gO0O4A0mNEuCkxvL5pfyfUjjaIwnZbujU9/1P iuAyn9njhV8N5IpwXN4iZxI7KnVdkukoeMfTQwyDd8rSCaru6ouTOeAxJyrqnbONK8h1 OOQ/STcyH0CrOmQUXXn9umVosxgpZoBM6MVA4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=rzmO4wK9UO6vtGKfLxgoymh4O3Tvs181IP8ZoLGr7RAbC8cHT0lO986gtSohRvhQDT 7oPOeegTF7DFwIBhs+/g4JpazoAxg+iYSHmBfIai03KJ+R3QXYsMluHm9568cCum/HEw +8dYZMZcmxhiidZMz+Rp33b3dfnxvPqstV3DY=
Received: by 10.110.95.3 with SMTP id s3mr6812421tib.17.1235434850188; Mon, 23 Feb 2009 16:20:50 -0800 (PST)
Received: from ?172.31.8.42? ([222.128.247.2]) by mx.google.com with ESMTPS id u12sm2630238tia.18.2009.02.23.16.20.48 (version=SSLv3 cipher=RC4-MD5); Mon, 23 Feb 2009 16:20:49 -0800 (PST)
Message-ID: <49A33D61.1070007@gmail.com>
Date: Tue, 24 Feb 2009 13:20:49 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tony.li@tony.li
References: <20090215063001.A53163A6980@core3.amsl.com> <499B5D32.909@gmail.com> <240116669D2F480D83B018E09A985B49@ad.redback.com>
In-Reply-To: <240116669D2F480D83B018E09A985B49@ad.redback.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 00:20:37 -0000

> |Also distinguish reversible and non-reversible translation.
> 
> 
> I agree with the differentiation, but I'm really less interested in refining
> the taxonomy from section 3.1 unless there's some clear, tangible benefit.
> At this point, I'm much more interested in putting our efforts into the
> section 3.3 approach.

Fair enough, but I think that from the point of view of making referrals
and any other "address" dependencies in upper layers work, reversible
translation is in itself a clear benefit, almost isomorphic with encap/decap.

   Brian

From rw@firstpr.com.au  Mon Feb 23 17:38:41 2009
Return-Path: <rw@firstpr.com.au>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF2913A68B5 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 17:38:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.096 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, SARE_SUB_RAND_LETTRS4=0.799]
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 K9IRsn2rL2LN for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 17:38:41 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id AAADC3A657C for <rrg@irtf.org>; Mon, 23 Feb 2009 17:38:40 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 2399A175BEA; Tue, 24 Feb 2009 12:38:57 +1100 (EST)
Message-ID: <49A34F39.1070406@firstpr.com.au>
Date: Tue, 24 Feb 2009 12:36:57 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <499BB0E4.1050206@firstpr.com.au> <1F676BC3FEF04EA197A9211C84FCAE4A@ad.redback.com>
In-Reply-To: <1F676BC3FEF04EA197A9211C84FCAE4A@ad.redback.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00 - Modified-Header	Forwarding(MHF)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 01:38:41 -0000

Hi Tony,

I disagree with your apparent view that the 3.1 taxonomy is adequate
as it stands:

> Thank you very much for your suggestion.  However, section 3.1.3 (and, for
> that matter, all of section 3.1) is much more general than section 3.3.1.4.
> I believe that those two techniques are covered quite adequately there.

I think that if you are to have the 3.1 taxonomy, it should be
extended to cover all the architectures - or that a note be added
that this only covers a subset of the currently proposed
architectures.  Unless there is a note to the contrary, readers will
assume that each taxonomy has a place for every one of the architectures.

My understanding of the 3.1 taxonomy is that describes the set of
primary mechanisms by which routing scaling architectures achieve
their goals.  I understand these are broad divisions and that other
taxonomies divide the architectures more finely.

The "Modified Header Forwarding" techniques do not fit at all into
your current 3.1 taxonomy.  They are not Transport, Translation or
Map & Encap.  In many ways these MHF techniques resemble Map & Encap,
but there is no encapsulation, and therefore no overhead or PMTUD
problems.

I think that if you retain the 3.1 taxonomy you should add, at the
bare minimum, something like this:

   3.1.4 Map & Forward with Modified Header Forwarding (MHF)

   An alternative mechanism to Map & Encap retains the mapping system
   and overall structure of tunneling the traffic packet across the
   DFZ to a tunnel endpoint device at the RLOC address - which
   forwards the packet directly to the destination network.  Instead
   of encapsulation, Modified Header Forwarding (MHF) alters the IP
   header of the original packet to include sufficient bits to
   specify part or all of the RLOC address of the tunnel endpoint
   device.

   These two techniques are described below as strategies A4f and
   A4g.  They both require upgraded DFZ and other routers but avoid
   Map & Encap's problems of encapsulation overhead and Path MTU
   Discovery problems.


In the long term, upgrading all the routers is not a problem.  The
system could be introduced as Map & Encap and transition later to
using MHF instead.  Perhaps, by the time we implement the solution,
it will be practical to upgrade the DFZ routers anyway, and therefore
 avoid the PMTUD problems of encapsulation entirely.

I believe that these MHF techniques are by far the best long-term
approach for any core-edge separation architecture.  I believe they
should be a part of however many taxonomies which are used in this
document.

I will write in another message some changes I suggest to the 3.3.1
section to better cover Ivip's Map & Encap approaches and "Map &
Forward with Modified Headers".


  Regards

    - Robin


From tony.li@tony.li  Mon Feb 23 22:47:08 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2CAE3A6840 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 22:47:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.678
X-Spam-Level: 
X-Spam-Status: No, score=-0.678 tagged_above=-999 required=5 tests=[AWL=-1.478, BAYES_50=0.001, SARE_SUB_RAND_LETTRS4=0.799]
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 5CrfaJ1Bt+y2 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 22:47:07 -0800 (PST)
Received: from QMTA09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by core3.amsl.com (Postfix) with ESMTP id 1721A3A679C for <rrg@irtf.org>; Mon, 23 Feb 2009 22:47:06 -0800 (PST)
Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA09.westchester.pa.mail.comcast.net with comcast id Kidp1b0050mv7h059inS1s; Tue, 24 Feb 2009 06:47:26 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA11.westchester.pa.mail.comcast.net with comcast id KinD1b0085Up7oj3XinGl1; Tue, 24 Feb 2009 06:47:24 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <20090215063001.A53163A6980@core3.amsl.com> <499B5D32.909@gmail.com> <240116669D2F480D83B018E09A985B49@ad.redback.com> <49A33D61.1070007@gmail.com>
Date: Mon, 23 Feb 2009 22:47:24 -0800
Message-ID: <C42267640D8E4AA48ABB2C284BC41350@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmWFcMwH6EfM/1eR522mOcM8n06XwANfEGQ
In-Reply-To: <49A33D61.1070007@gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 06:47:08 -0000

 

|Fair enough, but I think that from the point of view of making 
|referrals
|and any other "address" dependencies in upper layers work, reversible
|translation is in itself a clear benefit, almost isomorphic 
|with encap/decap.


Agree.

Tony


From tony.li@tony.li  Mon Feb 23 22:52:46 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05CF13A6765 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 22:52:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.623
X-Spam-Level: 
X-Spam-Status: No, score=-0.623 tagged_above=-999 required=5 tests=[AWL=-1.237, BAYES_40=-0.185, SARE_SUB_RAND_LETTRS4=0.799]
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 y5hikf8BGIz3 for <rrg@core3.amsl.com>; Mon, 23 Feb 2009 22:52:45 -0800 (PST)
Received: from QMTA04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by core3.amsl.com (Postfix) with ESMTP id 2C3313A6839 for <rrg@irtf.org>; Mon, 23 Feb 2009 22:52:45 -0800 (PST)
Received: from OMTA08.westchester.pa.mail.comcast.net ([76.96.62.12]) by QMTA04.westchester.pa.mail.comcast.net with comcast id Kis11b0020Fqzac54it4zr; Tue, 24 Feb 2009 06:53:04 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA08.westchester.pa.mail.comcast.net with comcast id Kita1b00F5Up7oj3Uitd9N; Tue, 24 Feb 2009 06:53:44 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Robin Whittle'" <rw@firstpr.com.au>, "'RRG'" <rrg@irtf.org>
References: <499BB0E4.1050206@firstpr.com.au> <1F676BC3FEF04EA197A9211C84FCAE4A@ad.redback.com> <49A34F39.1070406@firstpr.com.au>
Date: Mon, 23 Feb 2009 22:53:04 -0800
Message-ID: <7ED36056565B411CB561F2DF62262F3F@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmWIKzcFy80NiOxR0+hhYvRhzxIEgAK6mOA
In-Reply-To: <49A34F39.1070406@firstpr.com.au>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00 - Modified-Header	Forwarding(MHF)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 06:52:46 -0000

 

Hi Robin,


|I disagree with your apparent view that the 3.1 taxonomy is adequate
|as it stands:


Then you mistake my intent completely.  The taxonomy in 3.1 is inadequate
and not particularly helpful and not really worth further refinement.  It's
included mostly out of completeness.

Tony


From rw@firstpr.com.au  Tue Feb 24 00:45:45 2009
Return-Path: <rw@firstpr.com.au>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 052D63A685D for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 00:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.204
X-Spam-Level: 
X-Spam-Status: No, score=0.204 tagged_above=-999 required=5 tests=[AWL=-1.300,  BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, SARE_SUB_RAND_LETTRS4=0.799]
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 lOyN8ELamM+K for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 00:45:44 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 2DDE03A6A78 for <rrg@irtf.org>; Tue, 24 Feb 2009 00:45:44 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 0A3E4175D2A; Tue, 24 Feb 2009 19:46:02 +1100 (EST)
Message-ID: <49A3B352.3040807@firstpr.com.au>
Date: Tue, 24 Feb 2009 19:44:02 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: 'RRG' <rrg@irtf.org>
References: <499BB0E4.1050206@firstpr.com.au> <1F676BC3FEF04EA197A9211C84FCAE4A@ad.redback.com> <49A34F39.1070406@firstpr.com.au> <7ED36056565B411CB561F2DF62262F3F@ad.redback.com>
In-Reply-To: <7ED36056565B411CB561F2DF62262F3F@ad.redback.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00 - Modified-Header	Forwarding(MHF)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 08:45:45 -0000

Hi Tony,

You wrote:

> |I disagree with your apparent view that the 3.1 taxonomy is adequate
> |as it stands:
> 
> Then you mistake my intent completely.  The taxonomy in 3.1 is inadequate
> and not particularly helpful and not really worth further refinement.  It's
> included mostly out of completeness.

But the current text gives no indication that this 3.1 taxonomy is
inadequate.  I don't see the value in "completeness" if it means
including every possible taxonomy, including those which are inadequate.

I suggest that if you don't want to improve it, that you either
clearly state it is incomplete or remove it.

My first preference is for improving it and my second is for removing it.

  - Robin


From rw@firstpr.com.au  Tue Feb 24 02:45:45 2009
Return-Path: <rw@firstpr.com.au>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B79E3A6A90 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 02:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.663
X-Spam-Level: 
X-Spam-Status: No, score=-0.663 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, SARE_SUB_RAND_LETTRS4=0.799]
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 1hU7exzLlPkN for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 02:45:42 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id B122D3A67FD for <rrg@irtf.org>; Tue, 24 Feb 2009 02:45:41 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 44D91175A86; Tue, 24 Feb 2009 21:45:59 +1100 (EST)
Message-ID: <49A3CF70.2020602@firstpr.com.au>
Date: Tue, 24 Feb 2009 21:44:00 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [rrg] Ivip map-encap & MHF in draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 10:45:45 -0000

Here are some suggestions for improving:

  http://tools.ietf.org/html/draft-irtf-rrg-recommendation-00

to properly describe the architectural elements which are part of the
Ivip proposal.  This is an update of:

  Re: [rrg] Summary of architectural solution space - Ivip still
  isn't properly covered  (2008-12-21)
  http://www.irtf.org/pipermail/rrg/2008-December/000526.html


I think there are multiple problems with section 3.3.  As it stands
at present, it is based on Bill Herrin's page (sixth draft):

   http://bill.herrin.us/network/rrgarchitectures.html

You can see from my attempt to match actual proposed architectures to
this taxonomy:

   http://www.firstpr.com.au/ip/ivip/rrgarch/

that I think this taxonomy needs quite a lot of work to ensure it
properly covers the most prominent proposals.


3.3.1.1. Variants

  I think A1c or perhaps A1b best describes Ivip.  I am not sure if
  A1a or perhaps A1b applies to any architecture which has been
  proposed.



3.3.1.2. Mapping approaches

  As I wrote here:

    http://www.irtf.org/pipermail/rrg/2008-December/000526.html

  I think none of A2a, A2b or A2c adequately describe Ivip.

  A2b comes closest, but it is not true to say of Ivip that:

     "The registry pushes all incremental changes in near-real time
      to all encoders which add RLOCs to the packets."

  That implies all ITRs get all mapping changes, which is not
  the case with Ivip - or with APT.  I think A2b does not match any
  proposed architecture.

  I suggest a new item be added (or maybe to replace A2b):

  A2d.  GUIDs dynamically mapped to each RLOC are pushed towards a
        central or distributed registry as they change. The registry
        pushes all incremental changes in near-real time to all
        full database query servers in ISP and/or end-user networks.
        The encoders request mapping from these local query servers.
        The response has a caching time and the local query server
        will push any changed mapping to an encoder if it receives
        such a change for mapping which matches a recent query which
        is still within its caching time.  There may be one or more
        full database query servers in each ISP and there may be one
        or more layers of caching query servers between these and the
        encoders.

  For brevity, I am leaving out other important things such as it
  being possible for an end-user network to have its own query
  servers, including full-database and/or caching, for its own ITRs
  - and the option of having the ITR function in sending hosts (not
  behind NAT).

  I think APT should have its own separate description.


3.3.1.3. Failure handling approaches

  I suggest A3b be replaced by:

    A3b. End-user networks are responsible for controlling the
         mapping of their EID address space.  They may do this
         directly or they may contract a third party to do this
         for them.  Each EID prefix (or non-prefix, contiguous,
         range of address space: one or more contiguous IPv4
         addresses or IPv6 /64s) is mapped to a single RLOC
         address.   With strategy A2d, for reasons such as a
         multihoming link failure, to implement inbound traffic
         engineering, or to implement address portability when
         moving to another ISP, the end-user network causes the
         mapping to change to the new RLOC address, and this is
         conveyed to all full database query servers in near real
         time.  These push the changed mapping to any encoders which
         may need it, based on previous queries and the caching
         times of the responses.



3.3.1.4. Compatibility approaches

  The current A4d is a rough description of LISP's approach to
  PMTUD.  It does not adequately describe Ivip's approach.

  I suggest this new version of A4d to make it clearer that this is
  one of at least two ways of dealing with the PMTUD problems caused
  by encapsulation:

  A4d  Standard IPv4 and IPv6 packets are tunnelled while they
       transit the Internet core, by encapsulating them with
       a header in which the source address is that of the encoder.
       Path-MTU problems in routers between the encoder and decoder
       are handled by sending a Packet To Big (PTB) to the encoder
       which must construct a valid PTB message and send it to the
       originating host.  As noted below {pointing to the new text
       below I suggest for 3.3.1.6) this requires the encoder to
       retain significant state, the encapsulation header to
       include a nonce and the original PTB to contain enough of the
       offending packet to include the nonce.


            (I guess APT would use much the same approach as
             LISP's, although the work would be split in some way
             between the ITR and Default Mapper, whereas in LISP it
             is all done by the ITR - "encoder" in this document.)

  I think this is a good, terse, description of LISP's stateful
  approach to PMTUD.  However, to keep it short, I haven't mentioned
  one important thing - that this approach is unlikely to support
  hosts sending fragmentable packets longer than some length a little
  less than 1500 bytes.  We don't want jumboframe-inclined hosts
  sending 9000 byte fragmentable packets in a world where DFZ links
  often or even sometimes have 1500 byte MTUs, the ITR dutifully
  encapsulating them and then having them fragmented into 8 or more
  pieces there or en-route to the ETR.


  I suggest this new item be added.  I will call it A4h, but
  these should probably be reordered in the final draft so the
  following comes after A4d:

  A4h  Standard IPv4 and IPv6 packets are tunnelled while they
       transit the Internet core, by encapsulating them with
       IP-in-IP, with no other header information and with the source
       address of the outer header being that of the originating
       host.  The encoder maintains an upper and lower estimate of
       the PMTU to each decoder it is currently tunneling packets to.
       When a traffic packet arrives at the encoder which, with
       encapsulation overhead, would have a length exceeding the
       upper estimate of the PMTU to the relevant decoder, the
       encoder sends a PTB to the originating host.  When the
       encapsulated length is less than the lower estimate, the
       encoder encapsulates and tunnels the packet normally.

       When the encapsulated length falls between the two estimates,
       the encoder splits the packet and sends it as two.  One short
       packet is encapsulated with the outer source address being
       that of the original sending host.  The other packet has the
       same length as the traffic packet would have if it were
       normally encapsulated.  Both packets contain a nonce and
       potentially other information to enable the decoder to
       positively acknowledge the correct receipt of both packets.
       The longer packet's outer source address is that of the
       encoder, so if it exceeds the next hop MTU of an intermediate
       router, that router will send a PTB to the encoder.  That PTB
       should contain enough of the encapsulation header to include
       the nonce.  This, the positive acknowledgement or lack thereof
       from the decoder, and subsequent packets from the
       originating host will enable the encoder to progressively
       adjust its lower and upper estimates of PMTU for this decoder
       until they match.  The encoder is able to send a valid PTB
       to the sending host if the pair of packets did not
       successfully reach the decoder.


  I know this is longish, but map-encap's PMTUD problems are
  difficult to solve.  This is a really short description of
  the best approach I can think of - actually the only one I
  think which could work.  This is more fully developed than
  LISP's stateful approach.

  It avoids sending nonces or any other header guff beyond basic
  IP-in-IP encapsulation for the great majority of packets.  Only
  those few packets whose length falls within the current zone of
  uncertainty a (between the lower and upper estimates of PMTU) are
  given this special dual-packet treatment.  Every such treatment
  will enable the ITR to narrow the zone of uncertainty by either
  raising its lower estimate of PMTU or dropping its upper estimate.

  This is a good enough overall description for the taxonomy, but it
  doesn't describe everything, for instance how the encoder (ITR)
  needs to periodically test that the current estimates of PMTU
  are not too high or too low.


  Here are improved versions of the descriptions of Ivip's
  Modified Header Forwarding techniques.  I am trying to keep
  them brief.


   A4f  For IPv6, rather than encapsulate the packet to tunnel it to
        the decoder, use a modified header format in which
        19 or 20 bits of the IPv6 header's flow label are used
        to contain enough information about the RLOC (such as
        which of a range of DFZ prefixes the RLOC is within) for the
        packet to be forwarded by suitably modified routers to the
        correct ISP network for that RLOC.  The encoder sets these
        bits and  the decoder restores the original state of the
        packet.


   A4g  For IPv4, rather than encapsulate the packet to tunnel it
        to the decoder, use a modified header format containing
        the 30 bit RLOC address of the decoder so suitably modified
        routers will forward the packet to the decoder.  These bits
        are currently used for the More Fragments flag, the Fragment
        Offset and the Header Checksum.  The encoder sets these
        bits and the decoder restores the original state of the
        packet.  The encoder does not accept fragments or
        fragmentable packets longer than some constant, likely to
        be marginally below 1500 bytes.



The descriptions of these approaches in 3.3.1.x are exceedingly
minimal.  I don't know why everything has to be so terse.  Internet
drafts are printed on 100% recycled electrons, and I think it is
important to help people - including those outside the RRG - identify
and understand the various possible architectures as clearly as
possible.

The taxonomy should clearly cover every seriously proposed
architecture - and should probably not cover anything else without
noting that such an architecture may be possible, but has not yet
been proposed.


I think that if the RRG's recommendation (even if it is an interim
summary of progress to date) is is to have any discussion of the
strengths and weaknesses of various approaches, then that discussion
should be full and detailed, not just some terse, arbitrarily
truncated subset of what a fully detailed list of strengths and
weaknesses would be.  I think the best way to do this is for the
individual strategies to have a fuller description than at present,
including probably their most prominent strengths and weaknesses.
Otherwise, many important aspects of the strategies would need to be
mentioned in the later evaluation of strengths and weaknesses.



3.3.1.6. Major criticisms

  This statement is inadequate:

    Handling path-MTU is a usually problem since the packets
    in the core are different than the origin host would recognize.

  This does not apply to "Map & Forward with Modified Header
  Forwarding" because the router which creates the PTB message can
  reconstruct the original state of the packet, and so can generate a
  perfectly valid PTB which will be recognised by the sending host.
  Also, since there is no  packet overhead, the MTU value returned in
  the PTB message gives the sending host the correct guidance on how
  long a packet it can send to avoid MTU problems at that router in
  the future.

  I am wary of the term "genuinely clean", but will retain it in
  what follows.

  I suggest this new text for 3.3.1.6:

    There don't appear to be any genuinely clean ways of implementing
    strategy A.

    Encapsulation-based approaches raise Path MTU Discovery problems
    for two reasons.

    Firstly, the encapsulated packet is longer than the packet sent
    by the sending host, meaning that any MTU value returned by a
    router in a PTB message does not give the sending host the
    information it needs to avoid the MTU limitation.  Secondly, the
    PTB as generated by the router is will not be recognised by the
    sending host, either due to the encapsulated packet being
    different to that sent (if the outer source address is that of
    the sending host) and/or (if the outer source address is that of
    the encapsulating router) due to the PTB being sent to the
    encapsulating router, rather than the sending host.  In the
    latter case, a successful solution to the PMTUD problem relies on
    the encapsulating router (encoder) being able to securely
    construct a valid PTB to be sent to the sending host.  This in
    turn involves significant processing at that encoder and the
    retention of a problematic amount of state: for each packet sent
    which might cause MTU problems.  It also relies on the
    encapsulated packet having a nonce in its headers and the
    original PTB carrying enough of that packet to include the
    nonce - which is more than is required by RFC 1191.

    Forwarding with modified headers does not involve the PMTUD
    and overhead problems which are inherent in encapsulation.  The
    router at which the MTU limit is reached can reconstruct the
    original packet as sent by the originating host, and so can create
    a valid PTB.

    However, forwarding with modified headers involves upgrades to
    all core routers and some or many internal routers.  This is
    feasible in the long-term, so an encapsulation system could
    and arguably should migrate to a modified header forwarding
    system over time.  Depending on the flexibility of the installed
    base of routers and on the urgency of introduction, it may be
    possible to introduce a scalable routing architecture without
    using encapsulation by using just modified header forwarding from
    the outset.

    For IPv4, with either modified header forwarding or encapsulation
    and the PMTUD management required for encapsulation, it seems
    unlikely that it will be possible to support fragments, or
    fragmentable packets longer than a constant which is likely to be
    somewhat below 1500 bytes.


I can't see a terser way of summing up the PMTUD problems of Map &
Encap and how MHF differs.

Unless there is a robust, efficient method of solving the PMTUD
problems, these problems are a show-stopper for Map & Encap.  If the
RRG's report is going to discuss the strengths and weaknesses of the
various approaches, then I think the discussion must be much more
complete than the current, overly terse, rather than piecemeal text.


I have avoided mentioning how Ivip's approach involves only a handful
of packets getting the special handling required for PMTUD, and how
those include a nonce, but that all other traffic packets include no
such nonce, thereby reducing the overhead.  Nor have I mentioned the
reason why Ivip sends encapsulated packets with the outer source
address being that of the sending host (to automatically extend
border router ingress filtering of source addresses to the
decapsulated packet, by way of the ETR dropping packets where the
inner source address does not match the outer source address).



The next sentence is inadequate too:

  Extra bandwidth is consumed by the ingress tunnel router figuring
  out whether the egress tunnel router is still available and
  functioning.

I suggest this be replaced with something like:

  Extra bandwidth, in addition to that required to distribute
  mapping, may be consumed by some Strategy A approaches.

  For instance, some architectures use A3a - multiple RLOCs per
  EID - with the encoders (ingress tunnel routers) being responsible
  for individually determining which RLOC address to use when
  encapsulating packets.  Multiple RLOC addresses are required
  because these architectures use A2c or some other non-real-time
  approach to mapping distribution.  The encoders are therefore
  required to individually determine reachability to each encoder
  they are currently tunneling packets to.  This involves extra
  state, computational load and bandwidth consumption by each encoder
  and probably each decoder.   While this approach may be capable of
  coping better with some localised outages than A4h, it involves
  considerable scaling problems for busy encoders and decoders.

  Extra bandwidth is consumed by all encapsulation approaches.  A4h
  encapsulation consists only of IP-in-IP header (except when
  the encoder is discovering the PMTUD to a decoder).  Encapsulation
  architectures other than A4h add additional headers, such as a UDP
  header followed by an architecture-specific header to each
  traffic packet.  When probing PMTU, A4h involves extra complexity
  for the encoder and decoder, with an additional short packet and a
  differently encapsulated full-length packet, with further packets
  needed for the decoder to acknowledge receipt of one or both
  packets.  However, this probing activity is only prompted by
  longer traffic packets which are used as the probes.  It is
  self-limiting since each such probe reduces the uncertainty the
  encoder has about the PMTU to a given decoder.


This sentence needs to be changed too:

  Border filtering of source addresses becomes problematic.

This is true of LISP, APT and TRRP - but Ivip shouldn't be tarred
with the same brush.

Here is a suggested replacement.

  The encapsulation architectures which use the encoder's address
  in the outer header involve significant problems with border
  filtering of incoming packets based on source address - for
  instance to stop spoofing of source addresses inside an ISP's
  network.   For such architectures (A4d), the only solution seems
  to be to replicate this expensive filtering on the decapsulated
  packets, at every decoder (egress tunnel router).

  With strategy A4h, border filtering of source addresses can
  be extended to the decapsulated packets much more easily - by
  the ETR dropping any inner packets whose source address do not
  match the outer source address.

  Strategies A4f and A4g have no problems with this filtering,
  since the modified border routers will continue to filter on the
  source address, which is unchanged in the header.


This sentence is another instance of a statement which applies to
LISP, as currently conceived, but not to Ivip:

   Deployment may require heavy weight "for the public good" relays
   in the non-upgraded part of the Internet to facilitate migration.

Depending on your view of APT's handling of packets from non-upgraded
networks (which I think is more favourable if there is a single APT
island, rather than multiple such islands) the above statement is not
an adequate assessment of APT either.

Here is a suggestion which retains the critique of LISP - which
currently has no business plan for Proxy Tunnel Routers (or a
technical arrangement supporting ownership and running which could
lead to a favourable business plan) but which recognises that Ivip
has more promising arrangements.  This would need to be modified or
extended to adequately describe APT and TRRP.  (TRRP's approach
involves a bunch of sticks and carrots which would be challenging to
describe in a concise manner!)

  In order to be attractive for early adoptors, Strategy A
  architectures need a means of handling packets sent from networks
  which lack encoders.  This raises technical and business problems,
  considering the strong desirability of these packets reaching a
  suitable "open", "proxy" or "relay" encoder which is not too far
  out of the path the packet needs to take to the correct decoder.

  Since these "open" (etc.) encoders need to be in the DFZ, and so
  need to advertise prefixes in order to attract these raw packets
  from non-upgraded networks, it is vital for routing scaling reasons
  that each such advertisement covers the EID space of a very large
  number of end-user networks.

  These constraints lead to questions of who is to operate this
  presumably widely spread set of "open" encoders, who is to manage
  the large blocks of address space from which EIDs are subdivided,
  and how the operators of these encoders will be paid according to
  the widely varying traffic they handle for packets addressed to
  different end-user networks.

  These problems are not necessarily incapabable of solution.  The
  best outcome will involve technical arrangements specifically
  intended to support address management and other business
  arrangements which make it attractive for organisations to
  operate these one or more globally distributed networks
  of "open", "proxy" or "relay" encoders.

For a fuller discussion of what I am trying to summarize here, see:

  Business incentives for LISP PTRs and Ivip OITRDs
  http://psg.com/lists/rrg/2008/msg02021.html


These sentences do apply properly to Ivip:

   During the transition period, it appears difficult to remove
   legacy prefixes from the global routing table.  The best that can
   be done is to advertise aggregates of legacy prefixes from the
   relays.  This may have an impact on stretch.

I am not sure how well they apply to LISP or APT, since there is
little or nothing in those proposals about how end-user networks will
gain new EID space, or convert their current PI space to EID space.

The concept of a "transition period" is not necessarily valid.  There
may never be a complete switch-over of all end-user networks to the
new form of addressing.  Ivip is not predicated on there being a
complete switch-over.  The idea is to make the new kind of space so
attractive to end-user networks of all types and of all sizes (at
least those which require multihoming, portability and/or mobility)
that over time, the great majority of end-user networks will adopt
the new space.  In this model, the routing scaling problem can still
be solved without a complete transition.

The first sentence above seems to assume that EID space will often or
always be created by converting existing PI prefixes.  That will be
part of the story, I am sure - for instance for large corporate and
university networks with PI space today, who decide to adopt the new
form of scalable addressing.  However, since the various scalable
routing architectures are intended to scale to a vastly higher number
of end-user networks (billions) than have PI space today (one or so
hundred thousand?), clearly, in the future, most such end-user
networks will be getting fresh address space which is already part of
the new addressing scheme.  The first sentence's concern does not
apply to the EID space of all those "new" end-user networks.

"Stretch" (longer total paths than would otherwise be the case) would
be a problem if the "relays" (meaning LISP Proxy Tunnel Routers) are
not widely distributed.  (Actually, it is OK to have PTRs or their
Ivip equivalents - OITRDs - only in one area, as long as all the ETRs
for EID prefixes advertised by those PTRs or OITRDs are in the same
area.  I am assuming a more general case which must provide generally
optimal paths when both the sending hosts and the ETRs are freely
distributed all over the world.)

If my above suggested text is included, I don't think we need these
last 3 sentences ("During ..", "The best ..." and "This may ...").
There are challenges.  I think Ivip has a promising set of technical
and business measures to solve them - and that the other proposals so
far do not.

We do need to discuss the problems of support of packets from
non-upgraded networks, since lack of this would be a show-stopper for
any map-encap or map-forward-with-modified-headers architecture.

Without going into much longer discussions, I think my text above
discusses the challenges and indicates that solutions seem to be
possible, but are not yet developed for all architectures.


The current discussion says nothing of the ability of various
Strategy A architectures to support mobility.  Current mobile IP
approaches are limited in scope, and only work for IPv6. They are
essential for mobility within a particular network but not suited to
the real problem of providing seamless global mobility across every
kind of access network.

So just adding map-encap or map-forward without special consideration
of mobility is not going to enable a better total mobility outcome
than what is currently possible with MIPv6.

Mobility support for map-encap or map-forward does not involve
changing the mapping every time the MN gets a new CoA.  The only
feasible solution seems to be to use two-way tunnels from each CoA to
an ETR-like "Translating Tunnel Router" (TTR), as described here:

  TTR Mobility Extensions for Core-Edge Separation Solutions to the
  Internet's Routing Scaling Problem
  http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf

This approach does not add any complexity to the core-edge separation
scheme itself, since the TTRs behave like any other ETR or ITR.

The near-real-time mapping approach of Ivip, or any other
architecture which adopts the A2d approach, as described above, is
clearly in a better position to adapt quickly to end-user needs to
change the mapping to a new TTR than the non-real-time approaches of
A2a (LISP-NERD) or A2c (LISP-ALT, APT and TRRP).


I suggest some new text such as:


   The optimal new routing and addressing architecture should
   arguably provide maximal support for mobility on a global scale.
   Existing mobile IP approaches are for IPv6 only and tend to rely
   on additional capabilities in the access network and/or on
   a "home agent" router, which may not be close to the
   mobile node's current location - raising performance and
   efficiency problems.

   While strategy A architectures may not pose inherent difficulties
   for existing mobile IP techniques, it would be an advantage if
   an architecture supported potentially new mobility techniques
   which provided global mobility, with any access network, with
   generally optimal path lengths and without reliance on any
   fixed "home agent" or on particular capabilities of access
   networks.


  - Robin








From swb@employees.org  Tue Feb 24 03:43:41 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 404FE3A6849 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 03:43:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.801
X-Spam-Level: 
X-Spam-Status: No, score=-5.801 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 olZQoQU1EEKi for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 03:43:40 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 552033A682A for <rrg@irtf.org>; Tue, 24 Feb 2009 03:43:40 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,258,1233532800"; d="scan'208";a="38235852"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 24 Feb 2009 11:43:58 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n1OBhwB2017040;  Tue, 24 Feb 2009 06:43:58 -0500
Received: from sbrim-mbp.local (ssh-rtp-2.cisco.com [64.102.8.172]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1OBhwOG029220; Tue, 24 Feb 2009 11:43:58 GMT
Message-ID: <49A3DD7E.9010403@employees.org>
Date: Tue, 24 Feb 2009 06:43:58 -0500
From: Scott Brim <swb@employees.org>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: tony.li@tony.li
References: <20090221204202.GN54483@cisco.com> <18AE350EBE534FD69400A43F609967B6@ad.redback.com>
In-Reply-To: <18AE350EBE534FD69400A43F609967B6@ad.redback.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: rrg@irtf.org
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 11:43:41 -0000

Tony Li allegedly wrote on 02 23 2009 2:41 PM:
> |> 3.1.2.  Translation
> |> 
> |>    Translation solutions are characterized by a translation
> |>    operation between an identifier to a locator and back to an
> |>    identifier as the packet traverses the network.
> |
> |Now that I've pondered this a little, I can't think of any approach
> |that does that (translate from identifier to locator and back again).
> 
> NAT, for example.

NAT translates from a local locator to a global locator ("RLOC" in the
terminology you want us to adopt).  You say

> It's not unreasonable to have a name that has both
> identification semantics and local locator scope.

That's true, and what matters in the case of NAT is the "local locator"
semantics.  NAT is not treating the address field it translates as an
endpoint identifier, but as an address.  That's why I say NAT doesn't do
what you said it does.

> |> 3.3.1.  Strategy A

If we end up using this classification scheme in our recommendation to
the IETF, one thing we need to do is name these strategy buckets in ways
that are easier to remember than "A", "B", etc.


Scott

From swb@employees.org  Tue Feb 24 04:09:39 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A76AD3A6A20 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 04:09:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.801
X-Spam-Level: 
X-Spam-Status: No, score=-5.801 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 PqPMC5Ia0dk2 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 04:09:38 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 9FEB63A67A4 for <rrg@irtf.org>; Tue, 24 Feb 2009 04:09:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,258,1233532800"; d="scan'208";a="38199132"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 24 Feb 2009 12:09:57 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n1OC9vah024515 for <rrg@irtf.org>; Tue, 24 Feb 2009 07:09:57 -0500
Received: from cisco.com (ssh-rtp-2.cisco.com [64.102.8.172]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1OC9uYs004866 for <rrg@irtf.org>; Tue, 24 Feb 2009 12:09:57 GMT
Date: Tue, 24 Feb 2009 07:09:54 -0500
From: Scott Brim <swb@employees.org>
To: rrg@irtf.org
Message-ID: <20090224120954.GE55901@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg@irtf.org
References: <20090215063001.A53163A6980@core3.amsl.com> <499B5D32.909@gmail.com> <240116669D2F480D83B018E09A985B49@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <240116669D2F480D83B018E09A985B49@ad.redback.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 12:09:39 -0000

Excerpts from Tony Li on Mon, Feb 23, 2009 11:41:16AM -0800:
> At this point, I'm much more interested in putting our efforts into
> the section 3.3 approach.

Tony: I hadn't realized, when (from my point of view) people were
helping Bill sort out ways of thinking about approaches, that you were
intending to promote the result as the main part of what we would put
it our recommendation to the IETF.  I suppose I could go along with
that, even though it's a surprise, but I believe it's going to take a
lot of editing before it's ready to hand off.  I can contribute what I
think should happen, but as co-chair, how do you think we should
proceed?  For example, are you hoping to have something to present in
RTGarea?

Scott

From falk@bbn.com  Tue Feb 24 07:39:08 2009
Return-Path: <falk@bbn.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 326023A69F2 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 07:39:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.271
X-Spam-Level: 
X-Spam-Status: No, score=-1.271 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, SARE_SUB_RAND_LETTRS4=0.799]
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 0VkxMV8Y0t8r for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 07:39:07 -0800 (PST)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id B8A6C3A6820 for <rrg@irtf.org>; Tue, 24 Feb 2009 07:39:05 -0800 (PST)
Received: from dhcp89-081-004.bbn.com ([128.89.81.4]) by mx3.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <falk@bbn.com>) id 1LbzNR-0000iO-Ax; Tue, 24 Feb 2009 10:39:21 -0500
Message-ID: <49A414A9.8060002@bbn.com>
Date: Tue, 24 Feb 2009 10:39:21 -0500
From: Aaron Falk <falk@bbn.com>
Organization: BBN Technologies
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: rfc-editor@rfc-editor.org
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Internet Research Steering Group <irsg@isi.edu>, rrg@irtf.org, Lixia Zhang <lixia@CS.UCLA.EDU>
Subject: [rrg] Request to publish IRTF doc draft-irtf-routing-history-09.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 15:39:08 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>RFC Editor-<br>
<br>
Please publish draft-irtf-routing-history-09.txt [1] as an Historical
IRTF RFC. The document has been approved for publication by the IRSG
and also reviewed for IETF conflict by the IESG. See below for details
on the IESG and prior reviews. Please copy all correspondence to the
document shepherd, Lixia Zhang <a class="moz-txt-link-rfc2396E" href="mailto:lixia@CS.UCLA.EDU">&lt;lixia@CS.UCLA.EDU&gt;</a>.&nbsp; <br>
<br>
--aaron<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt">http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt</a><br>
<br>
---<br>
Aaron Falk<br>
Chair<br>
Internet Research Task Force<br>
(617) 500-5960<br>
<a class="moz-txt-link-freetext" href="http://www.irtf.org">http://www.irtf.org</a><br>
<br>
<br>
Begin forwarded message:<br>
&gt; Aaron,<br>
&gt;<br>
&gt; this is a request to publish the following document as a
historical RFC:<br>
&gt;
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt">http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt</a><br>
&gt;<br>
&gt; This document has gone through RRG review and IRSG review.<br>
&gt; Please see the issue tracker under ticket #12:<br>
&gt;<br>
&gt; <a class="moz-txt-link-freetext" href="http://trac.tools.ietf.org/group/irtf/trac/ticket/12">http://trac.tools.ietf.org/group/irtf/trac/ticket/12</a><br>
&gt;<br>
&gt; Summary of review:<br>
&gt; - This document was a report on RRG activities around 2001-2002.<br>
&gt; It went through RRG reviews around that time.<br>
&gt; - The last round of RRG review was conducted in early 2007, and<br>
&gt; received no comments for changes.<br>
&gt; - The final revision was reviewed by the IRSG members David McGrew<br>
&gt; and Kevin Fall, both voted YES on the IRSG Poll for this revision.<br>
&gt; No objection was received during the IRSG Poll.<br>
&gt;<br>
&gt; I have updated the status to: IRSG review concluded.<br>
&gt;<br>
&gt; Let me know if I need to do anything else.<br>
&gt;<br>
&gt; thanks,<br>
&gt;<br>
&gt; Lixia Zhang<br>
&gt; Document Shepherd<br>
<br>
also<br>
<br>
&gt;<br>
&gt;<br>
&gt; This document reports the analysis of the state of the Internet<br>
&gt; domain-based routing system, concentrating on Inter-Domain Routing<br>
&gt; (IDR) and also considering the relationship between inter-domain
and<br>
&gt; intra-domain routing. This analysis was carried out around year
2001<br>
&gt; by looking at the routing system as appeared in 2001, with
editorial<br>
&gt; additions reflecting developments up to 2006.<br>
&gt;<br>
&gt; Since this document summarizes discussions held several years ago
by<br>
&gt; members of the IRTF Routing Research Group (IRTF RRG) and other<br>
&gt; interested parties, it is published with the support of the IRTF
RRG<br>
&gt; as a historical RFC to serve as a record of the work completed
around<br>
&gt; 2001, and with the understanding that it does not necessarily<br>
&gt; represent either the latest technical understanding or the
technical<br>
&gt; consensus of the research group at the date of publication.<br>
&gt;<br>
&gt; Lixia Zhang Document Shepherd<br>
<br>
finally<br>
<br>
<blockquote type="cite">
  <div class="moz-text-plain" wrap="true" graphical-quote="true"
 style="font-family: -moz-fixed; font-size: 13px;" lang="x-unicode">
  <pre wrap="">The IESG has no problem with the publication of 'Analysis of 
Inter-Domain Routing Requirements and History'
&lt;draft-irtf-routing-history-10.txt&gt; as a Historic. 

The IESG would also like the IRSG to review the comments in 
the datatracker 
(<a class="moz-txt-link-freetext"
 href="https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&amp;dTag=8375&amp;rfc_flag=0">https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&amp;dTag=8375&amp;rfc_flag=0</a>)
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Ross Callon.

A URL of this Internet-Draft is:
<a class="moz-txt-link-freetext"
 href="http://www.ietf.org/internet-drafts/draft-irtf-routing-history-10.txt">http://www.ietf.org/internet-drafts/draft-irtf-routing-history-10.txt</a>


The process for such documents is described at
<a class="moz-txt-link-freetext"
 href="http://www.rfc-editor.org/indsubs.html">http://www.rfc-editor.org/indsubs.html</a>.

Thank you,

The IESG Secretary


Technical Summary

   This document analyses the state of the Internet domain-based routing
   system, concentrating on Inter-Domain Routing (IDR) and also
   considering the relationship between inter-domain and intra-domain
   routing.  The analysis is carried out with respect to RFC 1126 and
   other IDR requirements and design efforts looking at the routing
   system as it appeared to be in 2001 with editorial additions
   reflecting developments up to 2006.  It is the companion document to
   "A Set of Possible Requirements for a Future Routing Architecture"
   [I-D.irtf-routing-reqs], which is a discussion of requirements for
   the future routing architecture, addressing systems developments and
   future routing protocols.  This document summarizes discussions held
   several years ago by members of the IRTF Routing Research Group (IRTF
   RRG) and other interested parties.  The document is published with
   the support of the IRTF RRG as a record of the work completed at that
   time, but with the understanding that it does not necessarily
   represent either the latest technical understanding or the technical
   concensus of the research group at the date of publication.

Working Group Summary

   This is an IRTF output, and is being considered by the IESG only 
   to consider whether there is any overlap or conflict with IETF work. 

Document Quality

   This is an informational document which is not subject to
   implementation. It has been carefully reviewed in the IRTF. 

Personnel

   Ross Callon has agreed to shepherd this through IESG review. 

RFC Editor Note
 
   This work does not conflict with IETF work, and we recommend that 
   the RFC editor publish this document.
  </pre>
  </div>
</blockquote>
<br>
<br>
</tt>
</body>
</html>

From falk@bbn.com  Tue Feb 24 08:09:44 2009
Return-Path: <falk@bbn.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA15628C102 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 08:09:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.69
X-Spam-Level: 
X-Spam-Status: No, score=-1.69 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 fg+JCLmX2sS3 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 08:09:43 -0800 (PST)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 72FAC28B23E for <rrg@irtf.org>; Tue, 24 Feb 2009 08:09:43 -0800 (PST)
Received: from dhcp89-081-004.bbn.com ([128.89.81.4]) by mx3.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <falk@bbn.com>) id 1Lbzbl-0000yM-CU; Tue, 24 Feb 2009 10:54:09 -0500
Message-ID: <49A41821.3070903@bbn.com>
Date: Tue, 24 Feb 2009 10:54:09 -0500
From: Aaron Falk <falk@bbn.com>
Organization: BBN Technologies
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: rfc-editor@rfc-editor.org
References: <49A414A9.8060002@bbn.com>
In-Reply-To: <49A414A9.8060002@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Internet Research Steering Group <irsg@ISI.EDU>, rrg@irtf.org, Lixia Zhang <lixia@CS.UCLA.EDU>
Subject: Re: [rrg] [IRSG] Request to publish IRTF doc draft-irtf-routing-history-09.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 16:09:44 -0000

Correct URL:
http://tools.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt

Aaron Falk wrote:
> RFC Editor-
>
> Please publish draft-irtf-routing-history-09.txt [1] as an Historical
> IRTF RFC. The document has been approved for publication by the IRSG
> and also reviewed for IETF conflict by the IESG. See below for details
> on the IESG and prior reviews. Please copy all correspondence to the
> document shepherd, Lixia Zhang <lixia@CS.UCLA.EDU>. 
>
> --aaron
>
> [1] http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt
>
> ---
> Aaron Falk
> Chair
> Internet Research Task Force
> (617) 500-5960
> http://www.irtf.org
>
>
> Begin forwarded message:
> > Aaron,
> >
> > this is a request to publish the following document as a historical RFC:
> > http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt
> >
> > This document has gone through RRG review and IRSG review.
> > Please see the issue tracker under ticket #12:
> >
> > http://trac.tools.ietf.org/group/irtf/trac/ticket/12
> >
> > Summary of review:
> > - This document was a report on RRG activities around 2001-2002.
> > It went through RRG reviews around that time.
> > - The last round of RRG review was conducted in early 2007, and
> > received no comments for changes.
> > - The final revision was reviewed by the IRSG members David McGrew
> > and Kevin Fall, both voted YES on the IRSG Poll for this revision.
> > No objection was received during the IRSG Poll.
> >
> > I have updated the status to: IRSG review concluded.
> >
> > Let me know if I need to do anything else.
> >
> > thanks,
> >
> > Lixia Zhang
> > Document Shepherd
>
> also
>
> >
> >
> > This document reports the analysis of the state of the Internet
> > domain-based routing system, concentrating on Inter-Domain Routing
> > (IDR) and also considering the relationship between inter-domain and
> > intra-domain routing. This analysis was carried out around year 2001
> > by looking at the routing system as appeared in 2001, with editorial
> > additions reflecting developments up to 2006.
> >
> > Since this document summarizes discussions held several years ago by
> > members of the IRTF Routing Research Group (IRTF RRG) and other
> > interested parties, it is published with the support of the IRTF RRG
> > as a historical RFC to serve as a record of the work completed around
> > 2001, and with the understanding that it does not necessarily
> > represent either the latest technical understanding or the technical
> > consensus of the research group at the date of publication.
> >
> > Lixia Zhang Document Shepherd
>
> finally
>
>> The IESG has no problem with the publication of 'Analysis of 
>> Inter-Domain Routing Requirements and History'
>> <draft-irtf-routing-history-10.txt> as a Historic. 
>>
>> The IESG would also like the IRSG to review the comments in 
>> the datatracker 
>> (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=8375&rfc_flag=0)
>> related to this document and determine whether or not they merit 
>> incorporation into the document. Comments may exist in both the ballot 
>> and the comment log. 
>>
>> The IESG contact person is Ross Callon.
>>
>> A URL of this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-irtf-routing-history-10.txt
>>
>>
>> The process for such documents is described at
>> http://www.rfc-editor.org/indsubs.html.
>>
>> Thank you,
>>
>> The IESG Secretary
>>
>>
>> Technical Summary
>>
>>    This document analyses the state of the Internet domain-based routing
>>    system, concentrating on Inter-Domain Routing (IDR) and also
>>    considering the relationship between inter-domain and intra-domain
>>    routing.  The analysis is carried out with respect to RFC 1126 and
>>    other IDR requirements and design efforts looking at the routing
>>    system as it appeared to be in 2001 with editorial additions
>>    reflecting developments up to 2006.  It is the companion document to
>>    "A Set of Possible Requirements for a Future Routing Architecture"
>>    [I-D.irtf-routing-reqs], which is a discussion of requirements for
>>    the future routing architecture, addressing systems developments and
>>    future routing protocols.  This document summarizes discussions held
>>    several years ago by members of the IRTF Routing Research Group (IRTF
>>    RRG) and other interested parties.  The document is published with
>>    the support of the IRTF RRG as a record of the work completed at that
>>    time, but with the understanding that it does not necessarily
>>    represent either the latest technical understanding or the technical
>>    concensus of the research group at the date of publication.
>>
>> Working Group Summary
>>
>>    This is an IRTF output, and is being considered by the IESG only 
>>    to consider whether there is any overlap or conflict with IETF work. 
>>
>> Document Quality
>>
>>    This is an informational document which is not subject to
>>    implementation. It has been carefully reviewed in the IRTF. 
>>
>> Personnel
>>
>>    Ross Callon has agreed to shepherd this through IESG review. 
>>
>> RFC Editor Note
>>  
>>    This work does not conflict with IETF work, and we recommend that 
>>    the RFC editor publish this document.
>>   
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> IRSG mailing list
> IRSG@mailman.isi.edu
> http://mailman.isi.edu/mailman/listinfo/irsg
>   

From falk@bbn.com  Tue Feb 24 08:12:56 2009
Return-Path: <falk@bbn.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E4BA3A6A7C for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 08:12:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level: 
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, SARE_SUB_RAND_LETTRS4=0.799]
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 K0tXe6tcKN1T for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 08:12:55 -0800 (PST)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 0C67B3A6403 for <rrg@irtf.org>; Tue, 24 Feb 2009 08:12:55 -0800 (PST)
Received: from dhcp89-081-004.bbn.com ([128.89.81.4]) by mx3.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <falk@bbn.com>) id 1LbzNT-0000iS-Av; Tue, 24 Feb 2009 10:39:23 -0500
Message-ID: <49A414AB.4050102@bbn.com>
Date: Tue, 24 Feb 2009 10:39:23 -0500
From: Aaron Falk <falk@bbn.com>
Organization: BBN Technologies
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Internet Research Steering Group <irsg@isi.edu>, rrg@irtf.org, Lixia Zhang <lixia@CS.UCLA.EDU>
Subject: [rrg] Request to publish IRTF doc draft-irtf-routing-reqs-10.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 16:12:56 -0000

RFC Editor-

Please publish draft-irtf-routing-reqs-10.txt [1] as an Historical IRTF
RFC. The document has been approved for publication by the IRSG and also
reviewed for IETF conflict by the IESG. See below for details on the
IESG and prior reviews. Please copy all correspondence to the document
shepherd, Lixia Zhang <lixia@CS.UCLA.EDU>.

--aaron

[1] http://tools.ietf.org/id/draft-irtf-routing-reqs-10.txt

---
Aaron Falk
Chair
Internet Research Task Force
(617) 500-5960
http://www.irtf.org


Begin forwarded message:
> Aaron,
>
> this is a request to publish the following document as a historical RFC:
> http://tools.ietf.org/id/draft-irtf-routing-reqs-10.txt
>
> This document has gone through RRG review and IRSG review.
> Please see the issue tracker under ticket #16:
>
> http://trac.tools.ietf.org/group/irtf/trac/ticket/16
> (somehow I could not change the version# from 09 to 10)
>
> Summary of review:
> - This document was a report on RRG activities around 2001-2002.
> It went through RRG reviews around that time.
> - The last round of RRG review was conducted in early 2007, and
> received no comments for changes.
> - IRSG members Jeremy Mineweaser and Juergen Schoenwaelder
> reviewed -08 version during IRSG Poll and provided valuable comments.
> After the authors addressed the comments in later revisions,
> both voted YES for the revision. No objection was received.
>
> I have updated the status to: IRSG review concluded.
>
>
> thanks,
>
> Lixia Zhang
> Document Shepherd

also

>
>
> The requirements for routing architectures described in this document
> were produced by two sub-groups under the IRTF Routing Research Group
> in 2001, with some editorial updates up to 2006.
>
> Since this document summarizes discussions held sevenl years ago by
> members of the IRTF Routing Research Group (IRTF RRG) and other
> interested parties, it is published with the support of the IRTF RRG
> as a historical RFC to serve as a record of the work completed around
> 2001, and with the understanding that it does not necessarily
> represent either the latest technical understanding or the technical
> consensus of the research group at the date of publication.
>
> Lixia Zhang
>
> Document Shepherd


finally

> The IESG has no problem with the publication of 'A Set of Possible 
> Requirements for a Future Routing Architecture' 
> <draft-irtf-routing-reqs-11.txt> as a Historic RFC. 
>
> The IESG would also like the IRSG to review the comments in 
> the datatracker 
> (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=10743&rfc_flag=0)
> related to this document and determine whether or not they merit 
> incorporation into the document. Comments may exist in both the ballot 
> and the comment log. 
>
> The IESG contact person is Ross Callon.
>
> A URL of this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-irtf-routing-reqs-11.txt
>
>
> The process for such documents is described at
> http://www.rfc-editor.org/indsubs.html.
>
> Thank you,
>
> The IESG Secretary
>
> Technical Summary
>
>    The requirements for routing architectures described in this document
>    were produced by two sub-groups under the IRTF Routing Research Group
>    in 2001, with some editorial updates up to 2006.  The two sub-groups
>    worked independently, and the resulting requirements represent two
>    separate views of the problem and of what is required to fix the
>    problem.  This document may usefully serve as part of the recommended
>    reading for anyone who works on routing architecture designs for the
>    Internet in the future.
>
>    The document is published with the support of the IRTF RRG as a
>    record of the work completed at that time, but with the understanding
>    that it does not necessarily represent either the latest technical
>    understanding or the technical consensus of the research group at the
>    date of publication.
>
> Working Group Summary
>
>    This is an IRTF output, and is being considered by the IESG only 
>    to consider whether there is any overlap or conflict with IETF work. 
>
> Document Quality
>
>    This is an informational document which is not subject to
>    implementation. It has been carefully reviewed in the IRTF. 
>
> Personnel
>
>    Ross Callon has agreed to shepherd this through IESG review. 
>
> RFC Editor Note
>
>    This work does not conflict with IETF work, and we recommend that 
>    the RFC editor publish this document.
>   



From falk@bbn.com  Tue Feb 24 08:12:59 2009
Return-Path: <falk@bbn.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 550673A6ADA for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 08:12:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, SARE_SUB_RAND_LETTRS4=0.799]
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 9eLJUfB2rhL9 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 08:12:58 -0800 (PST)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 1FA933A6AD1 for <rrg@irtf.org>; Tue, 24 Feb 2009 08:12:58 -0800 (PST)
Received: from dhcp89-081-004.bbn.com ([128.89.81.4]) by mx3.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <falk@bbn.com>) id 1Lbzbi-0000yG-AO; Tue, 24 Feb 2009 10:54:06 -0500
Message-ID: <49A4181E.2080801@bbn.com>
Date: Tue, 24 Feb 2009 10:54:06 -0500
From: Aaron Falk <falk@bbn.com>
Organization: BBN Technologies
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: rfc-editor@rfc-editor.org
References: <49A414AB.4050102@bbn.com>
In-Reply-To: <49A414AB.4050102@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Internet Research Steering Group <irsg@ISI.EDU>, rrg@irtf.org, Lixia Zhang <lixia@CS.UCLA.EDU>
Subject: Re: [rrg] [IRSG] Request to publish IRTF doc draft-irtf-routing-reqs-10.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 16:12:59 -0000

Correct URL:
http://tools.ietf.org/internet-drafts/draft-irtf-routing-reqs-10.txt

Aaron Falk wrote:
> RFC Editor-
>
> Please publish draft-irtf-routing-reqs-10.txt [1] as an Historical IRTF
> RFC. The document has been approved for publication by the IRSG and also
> reviewed for IETF conflict by the IESG. See below for details on the
> IESG and prior reviews. Please copy all correspondence to the document
> shepherd, Lixia Zhang <lixia@CS.UCLA.EDU>.
>
> --aaron
>
> [1] http://tools.ietf.org/id/draft-irtf-routing-reqs-10.txt
>
> ---
> Aaron Falk
> Chair
> Internet Research Task Force
> (617) 500-5960
> http://www.irtf.org
>
>
> Begin forwarded message:
>   
>> Aaron,
>>
>> this is a request to publish the following document as a historical RFC:
>> http://tools.ietf.org/id/draft-irtf-routing-reqs-10.txt
>>
>> This document has gone through RRG review and IRSG review.
>> Please see the issue tracker under ticket #16:
>>
>> http://trac.tools.ietf.org/group/irtf/trac/ticket/16
>> (somehow I could not change the version# from 09 to 10)
>>
>> Summary of review:
>> - This document was a report on RRG activities around 2001-2002.
>> It went through RRG reviews around that time.
>> - The last round of RRG review was conducted in early 2007, and
>> received no comments for changes.
>> - IRSG members Jeremy Mineweaser and Juergen Schoenwaelder
>> reviewed -08 version during IRSG Poll and provided valuable comments.
>> After the authors addressed the comments in later revisions,
>> both voted YES for the revision. No objection was received.
>>
>> I have updated the status to: IRSG review concluded.
>>
>>
>> thanks,
>>
>> Lixia Zhang
>> Document Shepherd
>>     
>
> also
>
>   
>> The requirements for routing architectures described in this document
>> were produced by two sub-groups under the IRTF Routing Research Group
>> in 2001, with some editorial updates up to 2006.
>>
>> Since this document summarizes discussions held sevenl years ago by
>> members of the IRTF Routing Research Group (IRTF RRG) and other
>> interested parties, it is published with the support of the IRTF RRG
>> as a historical RFC to serve as a record of the work completed around
>> 2001, and with the understanding that it does not necessarily
>> represent either the latest technical understanding or the technical
>> consensus of the research group at the date of publication.
>>
>> Lixia Zhang
>>
>> Document Shepherd
>>     
>
>
> finally
>
>   
>> The IESG has no problem with the publication of 'A Set of Possible 
>> Requirements for a Future Routing Architecture' 
>> <draft-irtf-routing-reqs-11.txt> as a Historic RFC. 
>>
>> The IESG would also like the IRSG to review the comments in 
>> the datatracker 
>> (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=10743&rfc_flag=0)
>> related to this document and determine whether or not they merit 
>> incorporation into the document. Comments may exist in both the ballot 
>> and the comment log. 
>>
>> The IESG contact person is Ross Callon.
>>
>> A URL of this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-irtf-routing-reqs-11.txt
>>
>>
>> The process for such documents is described at
>> http://www.rfc-editor.org/indsubs.html.
>>
>> Thank you,
>>
>> The IESG Secretary
>>
>> Technical Summary
>>
>>    The requirements for routing architectures described in this document
>>    were produced by two sub-groups under the IRTF Routing Research Group
>>    in 2001, with some editorial updates up to 2006.  The two sub-groups
>>    worked independently, and the resulting requirements represent two
>>    separate views of the problem and of what is required to fix the
>>    problem.  This document may usefully serve as part of the recommended
>>    reading for anyone who works on routing architecture designs for the
>>    Internet in the future.
>>
>>    The document is published with the support of the IRTF RRG as a
>>    record of the work completed at that time, but with the understanding
>>    that it does not necessarily represent either the latest technical
>>    understanding or the technical consensus of the research group at the
>>    date of publication.
>>
>> Working Group Summary
>>
>>    This is an IRTF output, and is being considered by the IESG only 
>>    to consider whether there is any overlap or conflict with IETF work. 
>>
>> Document Quality
>>
>>    This is an informational document which is not subject to
>>    implementation. It has been carefully reviewed in the IRTF. 
>>
>> Personnel
>>
>>    Ross Callon has agreed to shepherd this through IESG review. 
>>
>> RFC Editor Note
>>
>>    This work does not conflict with IETF work, and we recommend that 
>>    the RFC editor publish this document.
>>   
>>     
>
>
> _______________________________________________
> IRSG mailing list
> IRSG@mailman.isi.edu
> http://mailman.isi.edu/mailman/listinfo/irsg
>   

From tony.li@tony.li  Tue Feb 24 13:05:12 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 026B23A6982 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 13:05:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level: 
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[AWL=-0.662, BAYES_05=-1.11, SARE_SUB_RAND_LETTRS4=0.799]
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 EaJ46euLI0m1 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 13:05:11 -0800 (PST)
Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id 01C633A6403 for <rrg@irtf.org>; Tue, 24 Feb 2009 13:05:10 -0800 (PST)
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59]) by QMTA10.westchester.pa.mail.comcast.net with comcast id Kn551b00N1GhbT85Ax5VuR; Tue, 24 Feb 2009 21:05:29 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA07.westchester.pa.mail.comcast.net with comcast id Kx4u1b0035Up7oj3Tx5Hn8; Tue, 24 Feb 2009 21:05:27 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Scott Brim'" <swb@employees.org>, <rrg@irtf.org>
References: <20090215063001.A53163A6980@core3.amsl.com><499B5D32.909@gmail.com><240116669D2F480D83B018E09A985B49@ad.redback.com> <20090224120954.GE55901@cisco.com>
Date: Tue, 24 Feb 2009 13:05:06 -0800
Message-ID: <5D94CFED9DC7442E9834E84AA3399573@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmWeNbBmDEPegUMSaiKSbqNrZt1wgAO8jyw
In-Reply-To: <20090224120954.GE55901@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 21:05:12 -0000

Scott,
 
|Tony: I hadn't realized, when (from my point of view) people were
|helping Bill sort out ways of thinking about approaches, that you were
|intending to promote the result as the main part of what we would put
|it our recommendation to the IETF.  


And I hadn't realized that Bill was going to be so productive in putting
something useful together.  


|I suppose I could go along with
|that, even though it's a surprise, but I believe it's going to take a
|lot of editing before it's ready to hand off.  I can contribute what I
|think should happen, but as co-chair, how do you think we should
|proceed?


FWIW, I would like to get more of Bill's involvement, but his day job seems
to be pressing him right now.  Lacking that, I'd welcome any editorial or
clarification changes that folks would like to propose.  I'm a bit more
hesitant about making significant changes without Bill's approval, but we
certainly can do so.

As always, other insights into the problem, discussions of architectural
conclusions that we can clearly draw and other conceptual items leading to
an architectural proposal are most welcome.  There's a lot more than could
be in this document outside of just taxonomy (e.g., mental question du jour:
do identifiers need to be globally unique?).


|  For example, are you hoping to have something to present in
|RTGarea?


No, no need.  As always, we owe a report to the IRTF Chair.  Nothing less,
nothing more.

Tony


From tony.li@tony.li  Tue Feb 24 13:05:22 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCB143A69E5 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 13:05:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.662
X-Spam-Level: 
X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 g6MtP25uF5jd for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 13:05:21 -0800 (PST)
Received: from QMTA07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id A7D4E3A69E6 for <rrg@irtf.org>; Tue, 24 Feb 2009 13:05:21 -0800 (PST)
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59]) by QMTA07.westchester.pa.mail.comcast.net with comcast id KmdC1b00B1GhbT857x5hE1; Tue, 24 Feb 2009 21:05:41 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA07.westchester.pa.mail.comcast.net with comcast id Kx4u1b0035Up7oj3Tx5Vu4; Tue, 24 Feb 2009 21:05:36 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Scott Brim'" <swb@employees.org>
References: <20090221204202.GN54483@cisco.com> <18AE350EBE534FD69400A43F609967B6@ad.redback.com> <49A3DD7E.9010403@employees.org>
Date: Tue, 24 Feb 2009 13:05:06 -0800
Message-ID: <36F9305DC7C44F129AD71567B468ED79@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmWdTmwYVbtZJz/SMu6B/oIhBM2wwAOLbdQ
In-Reply-To: <49A3DD7E.9010403@employees.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: rrg@irtf.org
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 21:05:22 -0000

Hi Scott,
 

|NAT translates from a local locator to a global locator ("RLOC" in the
|terminology you want us to adopt).  


Actually, I'm not pushing a given terminology, just documenting what seems
to have evolved.


|You say
|
|> It's not unreasonable to have a name that has both
|> identification semantics and local locator scope.
|
|That's true, and what matters in the case of NAT is the "local locator"
|semantics.  NAT is not treating the address field it translates as an
|endpoint identifier, but as an address.  That's why I say NAT 
|doesn't do
|what you said it does.


Fair point.  You're right, the text in 3.1.2 is poor.  Let's take a pass at
fixing it:

Translation solutions are characterized by converting an original local
source name to a global name and then from the global name back to a final
local destination name.  The global names are assigned in an aggregatable
fashion to provide scalability.

Work for you?


|> |> 3.3.1.  Strategy A
|
|If we end up using this classification scheme in our recommendation to
|the IETF, one thing we need to do is name these strategy 
|buckets in ways
|that are easier to remember than "A", "B", etc.


Actually, I like it.  It's completely neutral, it avoids all of the
arguments about natural language naming, and it clear and succinct.  

Tony


From tony.li@tony.li  Tue Feb 24 13:05:30 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93BFE3A6A11 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 13:05:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.466
X-Spam-Level: 
X-Spam-Status: No, score=-0.466 tagged_above=-999 required=5 tests=[AWL=-1.080, BAYES_40=-0.185, SARE_SUB_RAND_LETTRS4=0.799]
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 WC8b0AT+gpdG for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 13:05:29 -0800 (PST)
Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id A9FA73A69FE for <rrg@irtf.org>; Tue, 24 Feb 2009 13:05:29 -0800 (PST)
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59]) by QMTA01.westchester.pa.mail.comcast.net with comcast id KrUZ1b06Y1GhbT851x5p28; Tue, 24 Feb 2009 21:05:49 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA07.westchester.pa.mail.comcast.net with comcast id Kx4u1b0035Up7oj3Tx5fxf; Tue, 24 Feb 2009 21:05:47 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Robin Whittle'" <rw@firstpr.com.au>, "'RRG'" <rrg@irtf.org>
References: <499BB0E4.1050206@firstpr.com.au> <1F676BC3FEF04EA197A9211C84FCAE4A@ad.redback.com> <49A34F39.1070406@firstpr.com.au> <7ED36056565B411CB561F2DF62262F3F@ad.redback.com> <49A3B352.3040807@firstpr.com.au>
Date: Tue, 24 Feb 2009 13:05:06 -0800
Message-ID: <4D03D69542B54178BF7348D76D6C8180@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmWXFX0I8RyIGbrTsO/8WHs2LUoxwAUDfGw
In-Reply-To: <49A3B352.3040807@firstpr.com.au>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [rrg] draft-irtf-rrg-recommendation-00 - Modified-Header	Forwarding(MHF)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 21:05:30 -0000

 

|But the current text gives no indication that this 3.1 taxonomy is
|inadequate.  I don't see the value in "completeness" if it means
|including every possible taxonomy, including those which are 
|inadequate.
|
|I suggest that if you don't want to improve it, that you either
|clearly state it is incomplete or remove it.


Fair enough.  I've added some text to clearly focus us on section 3.3.

Tony


From HeinerHummel@aol.com  Tue Feb 24 14:21:42 2009
Return-Path: <HeinerHummel@aol.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 499EF28C144 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 14:21:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.941
X-Spam-Level: *
X-Spam-Status: No, score=1.941 tagged_above=-999 required=5 tests=[AWL=0.256,  BAYES_05=-1.11, HTML_MESSAGE=0.001, J_CHICKENPOX_61=0.6, MIME_QP_LONG_LINE=1.396, SARE_SUB_RAND_LETTRS4=0.799]
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 iai8phUdsTkY for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 14:21:41 -0800 (PST)
Received: from imo-m26.mail.aol.com (imo-m26.mx.aol.com [64.12.137.7]) by core3.amsl.com (Postfix) with ESMTP id A1C2128C165 for <rrg@irtf.org>; Tue, 24 Feb 2009 14:21:40 -0800 (PST)
Received: from HeinerHummel@aol.com by imo-m26.mx.aol.com  (mail_out_v39.1.) id 9.c77.4324dbb2 (65100) for <rrg@irtf.org>; Tue, 24 Feb 2009 17:21:01 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <c77.4324dbb2.36d5ccf9@aol.com>
Date: Tue, 24 Feb 2009 17:21:45 EST
To: rrg@irtf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1235514105"
X-Mailer: 9.0 SE for Windows sub 5021
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 22:21:42 -0000

-------------------------------1235514105
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
In einer eMail vom 24.02.2009 22:05:43 Westeurop=E4ische Normalzeit schreibt=
 =20
tony.li@tony.li:

As  always, other insights into the problem, discussions of  architectural
conclusions that we can clearly draw and other conceptual  items leading to
an architectural proposal are most welcome.  There's  a lot more than could
be in this document outside of just taxonomy (e.g.,  mental question du jour=
:
do identifiers need to be globally  unique?).






Earlier I gave two answers to above "question du jour" wrt  strategy  C:
While strategy C (TARA) is not yet completely deployed, IPv4 addresses have=20=
=20
to be globally unique, but not thereafter.
Globally uniqueness of IPv4 addresses is definitively needed for the =20
incremental deployment phase.
The reason: The hereby employed router's view of a well  reduced/sparsed=20
internet topology will also consist of non-TARA GRE-tunnels  which interconn=
ect=20
isolated TARA subnetworks. The computation of  these GRE-tunnels rely on the=
=20
global uniqueness of IPv4.
=20
Having said this, I like to ask the following question du jour:
Does jumping ahead with some particular strategy (e.g. with  LISP/ALT) harm=20
all the other potential solutions ?
=20
Speaking in favor of strategy C, the answer is " Yes, it harms".
Its objective, to reduce the classic BGP tables continuously, means: From =20
some point in time a TARA-router should stop disseminating its own user =20
reachabilities. Concurrently any other TARA-router will have to do    what i=
s called=20
default-mapping in ALT: it has to advertise reachability with  prefix length=
 0=20
as to attract IP flows from the non-TARA surrounding.
=20
Hence, there is a competition with ALT-routers who do the same. Of course, =20
by chance,a TARA-router may be in the way to some ALT-router  -- and vice =20
versus.
=20
Because I think that ANY strategy needs a concept for incremental =20
deployability, i.e. might need  that default-mapping mechanism. It is  indee=
d a pretty=20
general and not a ALT-specific mechanism.=20
=20
IMHO, this aspect should be considered prior voting for  a LISP working grou=
p=20
in the IETF.
=20
So I repeat my question du jour: does LISP/ALT jumping ahead hurt ?
=20
Heiner
=20
=20
=20
=20
=20
=20
=20
=20

-------------------------------1235514105
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16809" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In einer eMail vom 24.02.2009 22:05:43 Westeurop=E4ische Normalzeit sch=
reibt=20
tony.li@tony.li:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>As=20
  always, other insights into the problem, discussions of=20
  architectural<BR>conclusions that we can clearly draw and other conceptual=
=20
  items leading to<BR>an architectural proposal are most welcome.&nbsp; Ther=
e's=20
  a lot more than could<BR>be in this document outside of just taxonomy (e.g=
.,=20
  mental question du jour:<BR>do identifiers need to be globally=20
  unique?).<BR><BR><BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV>
<DIV>Earlier I gave two answers to above "question du jour" wrt &nbsp;strate=
gy=20
C:</DIV>
<DIV>While strategy C (TARA) is not yet completely deployed, IPv4 addresses=20=
have=20
to be globally unique, but not thereafter.</DIV>
<DIV>Globally uniqueness of IPv4 addresses is definitively needed for the=20
incremental deployment phase.</DIV>
<DIV>The reason: The hereby employed&nbsp;router's view of a well=20
reduced/sparsed internet topology will also consist of non-TARA GRE-tunnels=20
which interconnect isolated TARA subnetworks.&nbsp;The computation of=20
these&nbsp;GRE-tunnels rely on the global uniqueness of IPv4.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Having said this, I like to ask the following question du jour:</DIV>
<DIV>Does jumping ahead&nbsp;with some particular strategy (e.g.&nbsp;with=20
LISP/ALT)&nbsp;harm all the other potential solutions ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Speaking in favor of strategy C, the answer is " Yes, it harms".</DIV>
<DIV>Its objective, to reduce the classic BGP tables continuously, means: Fr=
om=20
some point in time a TARA-router should stop disseminating its own user=20
reachabilities. Concurrently any other TARA-router will have to do&nbsp;&nbs=
p;=20
what is called default-mapping in ALT: it has to advertise reachability with=
=20
prefix length 0 as to attract&nbsp;IP flows from the non-TARA surrounding.</=
DIV>
<DIV>&nbsp;</DIV>
<DIV>Hence, there is a competition with ALT-routers who do the same. Of cour=
se,=20
by chance,a TARA-router may be in the way to some ALT-router&nbsp; -- and vi=
ce=20
versus.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Because I think that ANY strategy needs a concept for incremental=20
deployability, i.e. might need&nbsp; that default-mapping mechanism.&nbsp;It=
 is=20
indeed a&nbsp;pretty general and not a ALT-specific mechanism. </DIV>
<DIV>&nbsp;</DIV>
<DIV>IMHO, this&nbsp;aspect should be considered&nbsp;prior voting for=20
a&nbsp;LISP&nbsp;working group in the IETF.</DIV>
<DIV>&nbsp;</DIV>
<DIV>So I repeat my question du jour: does LISP/ALT jumping ahead hurt ?</DI=
V>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1235514105--

From tony.li@tony.li  Tue Feb 24 15:02:20 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F7093A6A92 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 15:02:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.596
X-Spam-Level: 
X-Spam-Status: No, score=-1.596 tagged_above=-999 required=5 tests=[AWL=0.204,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 tbf6npXDJiU8 for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 15:02:19 -0800 (PST)
Received: from QMTA03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by core3.amsl.com (Postfix) with ESMTP id 223BB3A6941 for <rrg@irtf.org>; Tue, 24 Feb 2009 15:02:19 -0800 (PST)
Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51]) by QMTA03.westchester.pa.mail.comcast.net with comcast id Kmzx1b00516LCl053z2fRh; Tue, 24 Feb 2009 23:02:39 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA06.westchester.pa.mail.comcast.net with comcast id Kz2U1b0065Up7oj3Sz2Wae; Tue, 24 Feb 2009 23:02:37 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Robin Whittle'" <rw@firstpr.com.au>, "'RRG'" <rrg@irtf.org>
References: <49A3CF70.2020602@firstpr.com.au>
Date: Tue, 24 Feb 2009 15:02:38 -0800
Message-ID: <CBF89A2B19964CC497ADC7799434C9A2@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmWcWeU27e4ro44QPemOzDQNGomvgAXvGTA
In-Reply-To: <49A3CF70.2020602@firstpr.com.au>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [rrg] Ivip map-encap & MHF in draft-irtf-rrg-recommendation-00
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 23:02:20 -0000

Hi Robin,


Thank you for your note.  I'd like to respond to the meta-issues you raise.


|The descriptions of these approaches in 3.3.1.x are exceedingly
|minimal.  I don't know why everything has to be so terse.  Internet
|drafts are printed on 100% recycled electrons, and I think it is
|important to help people - including those outside the RRG - identify
|and understand the various possible architectures as clearly as
|possible.


Unfortunately, length and detail do not create clarity.  Instead, they
frequently obscure it.  The point of having broad, overall descriptions is
to first describe the key aspects of the particular segment of the solution
space.  These create abstractions that we can actually discuss and
manipulate in some pragmatic fashion without drowning in implementation
detail.

Yes, once we have made the key architectural decisions at the uppermost
layers of the solution space, then we can and should recurse downwards into
more detail, but until then, the details simply serve as noise in conflict
with any insights and generalizations that we might have.


|The taxonomy should clearly cover every seriously proposed
|architecture - and should probably not cover anything else without
|noting that such an architecture may be possible, but has not yet
|been proposed.


I strongly disagree.  The point of the taxonomy is to cover as much of the
solution space as we can possibly see.  Specific proposals are only points
in this space and our top-down decision making should have us first try for
consensus at the broadest possible levels of abstraction.


Regards,
Tony


From rw@firstpr.com.au  Tue Feb 24 23:23:59 2009
Return-Path: <rw@firstpr.com.au>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B55673A686C for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 23:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.171
X-Spam-Level: 
X-Spam-Status: No, score=-1.171 tagged_above=-999 required=5 tests=[AWL=0.725,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
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 ZTzx57-M35+O for <rrg@core3.amsl.com>; Tue, 24 Feb 2009 23:23:58 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 754F33A6B6A for <rrg@irtf.org>; Tue, 24 Feb 2009 23:23:57 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 694F8175D97; Wed, 25 Feb 2009 18:24:16 +1100 (EST)
Message-ID: <49A4F1AA.8070205@firstpr.com.au>
Date: Wed, 25 Feb 2009 18:22:18 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <49A3CF70.2020602@firstpr.com.au> <CBF89A2B19964CC497ADC7799434C9A2@ad.redback.com>
In-Reply-To: <CBF89A2B19964CC497ADC7799434C9A2@ad.redback.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [rrg] Brevity, abstraction & detail; Consensus on Bill's divisions and Strategy A?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2009 07:23:59 -0000

Following on from Tony's message in "Re: [rrg] Ivip map-encap & MHF
in draft-irtf-rrg-recommendation-00":
http://www.ietf.org/mail-archive/web/rrg/current/msg04546.html

Short version:     What is meant by "abstract"?

                   Concern about deciding too hastily between
                   what is relevant in an architectural discussion
                   and what is implicitly irrelevant "implementation
                   detail".

                   Likewise, concern about over-emphasising the value
                   of brevity.

                   Can the RRG form rough consensus that Bill's
                   top level taxonomic divisions are adequate?

                   What about consensus that the best solution will
                   be found within the core-edge separation division
                   - Strategy A?


Hi Tony,

Regarding the scope of the taxonomies and the level of detail in the
divisions of the taxonomies you wrote:


> |The descriptions of these approaches in 3.3.1.x are exceedingly
> |minimal.  I don't know why everything has to be so terse.  Internet
> |drafts are printed on 100% recycled electrons, and I think it is
> |important to help people - including those outside the RRG - identify
> |and understand the various possible architectures as clearly as
> |possible.
> 
> Unfortunately, length and detail do not create clarity.  

Yes, but clarity can only be achieved with sufficient length and
detail.  This is assuming clarity means more than simplicity and lack
of ambiguity - that a clear description of the architecture or class
of possible architectures is sufficient to clearly distinguish it
from all other divisions of the solution space.

A clear description of a division in the architectural taxonomy will
not be excessively brief and will most likely be written by someone
who fully understands at least one architecture which fits within
that division.


> Instead, they frequently obscure it.  

OK - but do you think any of the text I suggested obscures clarity?

If so, please propose simpler versions.

With one exception (my attempt to improve A4d, which covers LISP and
maybe to some extent APT) all the changes I made concern the
architectural principles used in the Ivip proposal.

Since I chose and/or devised these architectural principles for my
proposal, and since I assert that the previous text (or lack of text)
is inadequate for properly describing these architectural principles,
I think my suggested text should be the starting point for
discussions about how to properly describe these divisions of the
taxonomy.

The I-D, RFC, recommendation or whatever it will be:

  http://tools.ietf.org/html/draft-irtf-rrg-recommendation-00

will be an important reference for everyone who is involved in the
future architecture of the Net.  It results from a dozen or so
face-to-face meetings and 6,272 mailing list messages (RAM and RRG,
38Mb including headers).

A central feature of the recommendation will be the one or more
taxonomies.  I think it is essential that the taxonomic divisions and
sub-divisions be described clearly - in terms we in the RRG
understand and in terms which other people will understand.

I think it is rather tortuous using "encoder" and "decoder" when
"ITR" and "ETR" are more communicative and accurate, but I understand
you are trying to keep the discussion as general as possible.


> The point of having broad, overall descriptions is
> to first describe the key aspects of the particular segment of the solution
> space.  These create abstractions that we can actually discuss and
> manipulate in some pragmatic fashion without drowning in implementation
> detail.

While I am all for brainstorming, I am not convinced that much good
will come from abstract manipulations of very high level constructs
which distinguish the highest level divisions in the solution space,
such as the difference between core-edge separation, core-edge
elimination and one or more clean-slate approaches which do not
involve cores or edges at all.

I don't want to get in the way of such discussions, but I think most
people in this field went through this stuff two years ago.

We are not trying to design an idealised network.  We are very
tightly constrained by the need for the scalable routing solution to
be voluntarily adopted by the great majority of end-user networks
which want multihoming, TE and portability -  none of whom can be
assumed to have any direct concern with the costs born by ISPs due to
routing scaling problems.

So the solution has to have clear, immediate, benefits for the great
majority of such end-user networks, as well as being attractive to
most ISPs and to whatever new and existing entities will be involved
in running various aspects of the solution.

This rules out significant changes to host protocols, operating
systems or applications.

It rules out having to renumber the network when choosing a new ISP.

IMHO it rules out expecting people to abandon IPv4 and adopt IPv6.

It rules out changes to the interdomain routing system which would
disrupt the BGP DFZ.

I think the RRG could probably reach rough consensus now that this
rules out all approaches other than core-edge separation schemes -
"Strategy A".

I am only really interested in the different architectural approaches
to core-edge separation.


You and Ran Atkinson seem to be wary of drowning in "implementation
detail", "engineering detail" etc.

But how do you decide what is "implementation detail" and so,
presumably unworthy of consideration in an "architectural" discussion.

"Pragmatic" surely means discussing things in a way which considers
all the potential barriers to success - which involves a great deal
of detail about challenges and potential solutions.  This goes right
down to bits, bytes, milliwatts, nanoseconds and exact methods of
achieving some pretty tricky things: AKA "implementation details".

I think this low valuation of "engineering detail" is not shared by
many people who have something important to contribute to a scalable
routing solution.  This results in curious outcomes such as Dino
occasionally writing to the list, as if his tail was between his
legs, discussing something he considers important in an apologetic
manner, because it seems to be an "implementation detail".  More
often, I suspect, people don't write at all.


Please consider the new text I proposed in my message:

  http://www.ietf.org/mail-archive/web/rrg/current/msg04535.html

For instance A4h, which is intended to create a proper place in the
taxonomy for the architectural elements which I chose for Ivip's
encapsulation approach.

A successful encapsulation architecture must involve a secure,
scalable approach to handling PMTUD problems.  So I think the two
things need to be described together.  I assert that this A4h text,
or something like it, is needed to properly describe the division
within the A4 space which encompasses the encapsulation and PMTUD
architecture I chose for Ivip.  A4h is exclusive thing to Ivip -
anyone can use it.

I also assert that A4h is different enough from A4d (an attempt to
describe a division in the architectural taxonomy which encompasses
LISP's "statefull" approach) to warrant a separate place in the
taxonomy.  For instance, for almost all traffic packets, A4h avoids
the use of UDP or any other headers apart from IP-in-IP.  A4h also
maintains for all packets the use of the outer source address being
that of the originating host - which makes it very easy to extend
border filtering on source address to decapsulated packets, as
explained in my proposed replacement text for Bill's short sentence
on "Border filtering".


I think I understand your desire for abstract thinking in order to
find new ideas, new combinations of existing ideas etc. - and to
avoid being bogged down in existing combinations and ways of thinking.

However, since I think you don't contribute much "abstract"
discussion to the list, but frequently urge me and others to write
and think with greater abstraction or at a more "architectural"
level, I am unsure what it is you want.  Perhaps you could give some
examples - concrete enough so I can understand them!


> Yes, once we have made the key architectural decisions at the
> uppermost layers of the solution space, then we can and should
> recurse downwards into more detail, but until then, the details
> simply serve as noise in conflict with any insights and
> generalizations that we might have.

I don't understand this at all.

Bill's taxonomy casts a pretty wide net.

It is clear that a number of teams and individuals looked at the
whole scene two or so years ago and concluded that the only way
forward was a core-edge separation scheme.  I think this is the
correct decision.  Initially, that meant Map-Encap.  Now it also
includes Map-Translate (Six/One Router) and Map-Forward using
modified IP headers.

This resulted in a handful of architectures with some things in
common and many significant differences.

Only by discovering differences between actual architectures that
someone is proposing (or perhaps has just dreamed up but does not
seriously propose) can we determine the need of divisions in the
taxonomy.  This gives rise to the need for suitably detailed
descriptions of those divisions.

These details are vital and in no way resemble "noise".


You may choose to apply a "higher" (more "abstract", less "detailed")
distinction between what constitutes a good description of a
significant division between sub-spaces of the total design space
than someone else does.

However, if a designer or a proponent of a particular architecture
asserts that their architecture needs its own division in the
taxonomy, and/or if they assert that they need a different, perhaps
more detailed, description than you consider adequate, then I suggest
that the designer's suggested text be sympathetically considered for
inclusion in the draft report in full.


> |The taxonomy should clearly cover every seriously proposed
> |architecture - and should probably not cover anything else without
> |noting that such an architecture may be possible, but has not yet
> |been proposed.
> 
> I strongly disagree.  The point of the taxonomy is to cover as much of the
> solution space as we can possibly see.  Specific proposals are only points
> in this space and our top-down decision making should have us first try for
> consensus at the broadest possible levels of abstraction.

OK - I agree.

I agree with the overall divisions in Bill's taxonomy.

Does anyone disagree with these divisions?  Should some be removed,
added or described in different ways?

My guess is that there would be good consensus in the RRG that the
overall divisions in Bill's taxonomy are adequate.  Then the question
becomes how to sub-divide each of those divisions.

However, if we also have consensus that the best practical solution
will certainly be a core-edge separation scheme, then we should be
concentrating our attention on Strategy A.

It doesn't really matter if we haven't delineated every architectural
option in some other Strategy N - as long as we have established that
any architecture meeting the criteria of Strategy N is a non-starter,
for instance due to it being impossible to introduce voluntarily, for
instance due to its need for new stacks, APIs and/or applications.


In that process of discussing subdivisions within the taxonomy, I
suggest caution in imposing restrictions regarding brevity or degree
of abstraction.

If someone who has devised or chosen an architecture, or some
architectural principle, asserts that the taxonomy needs to be
changed in order to clearly accommodate that architecture, then I
think there would need to be some pretty careful discussion and broad
support from the RRG before it was decided that their proposed text
was too long, too detailed or unnecessary.


  Regards

     - Robin


From pfrejborg@gmail.com  Wed Feb 25 01:16:42 2009
Return-Path: <pfrejborg@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 746523A6A63 for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 01:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.307
X-Spam-Level: 
X-Spam-Status: No, score=-2.307 tagged_above=-999 required=5 tests=[AWL=0.292,  BAYES_00=-2.599]
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 J4IaKf7VIBRL for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 01:16:41 -0800 (PST)
Received: from mail-fx0-f160.google.com (mail-fx0-f160.google.com [209.85.220.160]) by core3.amsl.com (Postfix) with ESMTP id 6C2BA3A69EC for <rrg@irtf.org>; Wed, 25 Feb 2009 01:16:41 -0800 (PST)
Received: by fxm4 with SMTP id 4so5976120fxm.7 for <rrg@irtf.org>; Wed, 25 Feb 2009 01:16:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=Irc7DcVcge8Hen8n5wdpvsPRnnguQ74Kl1R1CFSRZAc=; b=oRlr8jq3+hOmASf7eW8ACtoW4AslSoADQlSOL76cIeOH/bj4bWz3YbzfD4/kmM6gna ApwvuTsrzBp5M8uC1PVvB/aNAZW4+1tWDRv2XVouX+45uS66D6/MUo4G1jtx+hzHsXtI kIp41yx5sBgEIYoAhXzCMqIcGpUvAcWjcPtM8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=AMi0PQgW9xEo7Qn7xfW7iEUw7hkZq/wNF3SMYdKEA3dPAGj+20lAnPj1TPOIbPI3sI oJLyr0vUTkMVVnSazR17wXX/Wcw2VbEB0G5WiiNkGg6brqLdjpipwfTz3lR8ghmb410w TPQQo69VcxuVWKdyrCdMciMiGL9USyhrVovyk=
MIME-Version: 1.0
Received: by 10.86.83.2 with SMTP id g2mr328223fgb.1.1235553419755; Wed, 25  Feb 2009 01:16:59 -0800 (PST)
Date: Wed, 25 Feb 2009 11:16:59 +0200
Message-ID: <5bc37fd40902250116r2eb8c384n79f887cb5708fa9d@mail.gmail.com>
From: Patrick Frejborg <pfrejborg@gmail.com>
To: rrg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [rrg] New draft, the hierachial IPv4 framework
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2009 09:16:42 -0000

There is a new draft published trying to address the routing
architecture of Internet
http://tools.ietf.org/id/draft-frejborg-hipv4-00.txt

   This draft describes a framework how the current IPv4 address
   structure can be extended towards a similar hierarchical numbering
   structure as used in the Public Switched Telephone Network and bring
   hierarchy to the routing architecture of Internet. The framework
   requires extensions to the existing Domain Name System architecture,
   the existing IPv4 stack of the end systems (hosts) and to routers in
   the Internet. The framework can be implemented incrementally to the
   hosts, databases and routers.

The idea is quite simple, it will require changes to all disciplines
but from the networking point of view it will not require changes to
the current forwarding plane except that a new networking element
(LISP Switch Router) is needed at each Autonomous System or at several
AS controlled by an ISP. This framework will bring hierarchy to both
the IPv4 addressing structure and to the routing architecture of
Internet.

I do have a presentation available, but lacking a FTP server resource

-- patte

From swb@employees.org  Wed Feb 25 05:10:05 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4422E3A688A for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 05:10:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.8
X-Spam-Level: 
X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 KhxDu+OqL2CW for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 05:10:04 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 2F8B73A680B for <rrg@irtf.org>; Wed, 25 Feb 2009 05:10:04 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,265,1233532800"; d="scan'208";a="38380453"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 25 Feb 2009 13:10:23 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n1PDANjG028830;  Wed, 25 Feb 2009 08:10:23 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1PDANcr019740; Wed, 25 Feb 2009 13:10:23 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 25 Feb 2009 08:10:23 -0500
Received: from cisco.com ([10.86.240.80]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Feb 2009 08:10:23 -0500
Date: Wed, 25 Feb 2009 08:10:20 -0500
From: Scott Brim <swb@employees.org>
To: Tony Li <tony.li@tony.li>
Message-ID: <20090225131020.GG89665@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Tony Li <tony.li@tony.li>, rrg@irtf.org
References: <20090224120954.GE55901@cisco.com> <5D94CFED9DC7442E9834E84AA3399573@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5D94CFED9DC7442E9834E84AA3399573@ad.redback.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 25 Feb 2009 13:10:23.0335 (UTC) FILETIME=[6AE22770:01C9974A]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: rrg@irtf.org
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2009 13:10:05 -0000

Tony,

Here is what I see:

  - There have been a number of attempts at characterizing the
    solution space.  Once upon a time we were trying to establish
    dimensions along which they could be compared quantitatively.
    Lately we've just settled for describing them.  You took one of
    the more recent attempts and incorporated it in a draft you wrote,
    and are proposing that it represent the RRG's position on how to
    think about solutions in order to select one.  

  - You are applying strong control on the content -- if you disagree
    with an idea your position has strong weight -- but this conflicts
    with your stated role as "editor" and your position as co-chair in
    which you are mainly trying to create consensus.  If you want to
    be in an author role, please say so.

  - The conceptual framework was lifted from Bill Herrin and you do
    not want any modifications to happen without Bill's involvement.
    You want his opinions to carry significant weight.  But once you
    take the framework and put it in the RRG's draft, it isn't Bill's
    anymore.  

Here is what I would like to happen:

  - Consensus discussion on what should go in a recommendation draft.
    A categorization of solutions is probably a good idea but it isn't
    enough -- we should talk about how we think it in particular can
    be used, but also how we think the draft as a whole might be used
    by the IETF to make progress.  As it stands I don't think the
    draft is very useful to the IETF.

  - Consensus discussion on what's in it already, particularly (of
    course) the chunking of approaches into categories.  In this,
    sorry Bill but you're just another individual.  

I was relieved to hear that you aren't trying to submit a draft before
this meeting.  I will write up what I can on this over the next few
weeks.  I'm about to go on a four-cities-in-a-week tour so I won't be
able to produce anything for the group to get their teeth into until
the 2nd week of March, but I request a time slot in the RRG agenda to
present some proposals.  If all goes well I won't need it, but I would
like to reserve the slot just in case.  

Thanks ... Scott

From tony.li@tony.li  Wed Feb 25 13:32:08 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9920D3A6B95 for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 13:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.609
X-Spam-Level: 
X-Spam-Status: No, score=-1.609 tagged_above=-999 required=5 tests=[AWL=0.191,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 he-YTOOYyUnl for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 13:32:07 -0800 (PST)
Received: from QMTA02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by core3.amsl.com (Postfix) with ESMTP id 92C3D3A6AA7 for <rrg@irtf.org>; Wed, 25 Feb 2009 13:32:07 -0800 (PST)
Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA02.emeryville.ca.mail.comcast.net with comcast id LM2E1b01M0FhH24A2MYV8A; Wed, 25 Feb 2009 21:32:29 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id LMYC1b00C5Up7oj8UMYEci; Wed, 25 Feb 2009 21:32:26 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Scott Brim'" <swb@employees.org>
References: <20090224120954.GE55901@cisco.com> <5D94CFED9DC7442E9834E84AA3399573@ad.redback.com> <20090225131020.GG89665@cisco.com>
Date: Wed, 25 Feb 2009 13:32:12 -0800
Message-ID: <7DA41AA183CB46008B4E57BAD4C3BE5D@ad.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmXSncz85DhEKjWRq2gM2oFUULY2QAKE4Pw
In-Reply-To: <20090225131020.GG89665@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: rrg@irtf.org
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2009 21:32:08 -0000

Hi Scott, 

|  - There have been a number of attempts at characterizing the
|    solution space.  Once upon a time we were trying to establish
|    dimensions along which they could be compared quantitatively.
|    Lately we've just settled for describing them.  You took one of
|    the more recent attempts and incorporated it in a draft you wrote,
|    and are proposing that it represent the RRG's position on how to
|    think about solutions in order to select one.  


More precisely, I'm interested in using it as one means of thinking about
the problem space.  I'm not saying it's the only one.  It seems useful, so
let's use it.


|  - You are applying strong control on the content -- if you disagree
|    with an idea your position has strong weight -- but this conflicts
|    with your stated role as "editor" and your position as co-chair in
|    which you are mainly trying to create consensus.  If you want to
|    be in an author role, please say so.


Yes, as "editor" of this document, I'm exercising stronger control over the
content here.  This is not in conflict with my stated role as a 'neutral'
co-chair, where I'm not an advocate of any given particular proposal.  As
you well know, I've always been an advocate of us making forward progress.
At this time, this seems to be the best way to move forward.


|  - The conceptual framework was lifted from Bill Herrin and you do
|    not want any modifications to happen without Bill's involvement.
|    You want his opinions to carry significant weight.  But once you
|    take the framework and put it in the RRG's draft, it isn't Bill's
|    anymore.


More precisely, I'm concerned about taking Bill's work, citing it as his
(absolutely necessary, of course) and then modifying it without his assent.
Obviously, we can make it clear that this is a diverging derivative, but I'm
still hopeful that we can get Bill's involvement.  

That said, the first priority is to make forward progress.  If that means
that his taxonomy needs improvement, then that needs to happen.  If it's a
significant change, then we'll attribute Bill, make the change, and diverge
from his direction.


|Here is what I would like to happen:
|
|  - Consensus discussion on what should go in a recommendation draft.
|    A categorization of solutions is probably a good idea but it isn't
|    enough -- we should talk about how we think it in particular can
|    be used, but also how we think the draft as a whole might be used
|    by the IETF to make progress.  As it stands I don't think the
|    draft is very useful to the IETF.


Again, the IETF is irrelevant.  This is our internal process.

I support the idea of a consensus discussion of what should go into the
draft, and that's already what's happening.  Yes, the draft is not supposed
to just be about taxonomy.  I would definitely like to add more consensus
items to it and I welcome and encourage the discussion.  I'd like to
explicitly invite folks to open new topics for consensus (in an orderly,
polite and sensible fashion, of course).


|I was relieved to hear that you aren't trying to submit a draft before
|this meeting.


I _have_ submitted a draft before the meeting.  That's what you are already
reading.  I will be submitting an update to it at the end of this week (or
sooner, depending on other events).


|I will write up what I can on this over the next few
|weeks.  I'm about to go on a four-cities-in-a-week tour so I won't be
|able to produce anything for the group to get their teeth into until
|the 2nd week of March, but I request a time slot in the RRG agenda to
|present some proposals.  If all goes well I won't need it, but I would
|like to reserve the slot just in case.  


I welcome that and again point your to our normal process for requesting
agenda slots.

Cheers,
Tony


From christian.vogt@ericsson.com  Wed Feb 25 19:15:55 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 173603A6844 for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 19:15:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=-0.399,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 dyZYQjS63fkA for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 19:15:54 -0800 (PST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 4453C3A6BB8 for <rrg@irtf.org>; Wed, 25 Feb 2009 19:15:54 -0800 (PST)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n1Q3GCWX004300; Wed, 25 Feb 2009 21:16:12 -0600
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 25 Feb 2009 21:16:12 -0600
Received: from [155.53.229.77] ([155.53.229.77]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 25 Feb 2009 21:16:12 -0600
Message-Id: <E21E8B89-57E0-40FB-819A-A10B045E63DE@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Scott Brim <swb@employees.org>
In-Reply-To: <20090221204202.GN54483@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 25 Feb 2009 19:16:15 -0800
References: <20090221204202.GN54483@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 26 Feb 2009 03:16:12.0323 (UTC) FILETIME=[93A32F30:01C997C0]
Cc: rrg@irtf.org
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 03:15:55 -0000

On Feb 21, 2009, Scott Brim wrote:

>> 3.1.2.  Translation
>>
>>   Translation solutions are characterized by a translation
>>   operation between an identifier to a locator and back to an
>>   identifier as the packet traverses the network.
>
> Now that I've pondered this a little, I can't think of any approach
> that does that (translate from identifier to locator and back again).


Scott -

All address indirection solutions that are application-transparent do
map both source and destination addresses at both ends.  I.e., you have
four mappings per packets:  The respective local addresses (source
address at the sending side; destination address at the destination
side) are mapped to achieve provider independence.  The respective
remote addresses are mapped to achieve application transparency.

> NAT-based approaches and Six/One Router are also one-way: the local
> source address is translated to an RLOC when outgoing, and the
> destination address is translated to a local address when incoming.

As you mention Six/One Router -- this solution proposal actually has two
modes:  One mode is NOT application-transparent; this, as you say, maps
only the respective local addresses (two mappings per packet).  But
Six/One Router also has an application-transparent mode, which performs
all four mappings per packet.  The two modes are called Unilateral mode
and Bilateral mode, respectively.

And FWIW:  Six/One Router, Unilateral mode == NAT66.

- Christian



From swb@employees.org  Wed Feb 25 19:23:05 2009
Return-Path: <swb@employees.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A4413A6844 for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 19:23:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.8
X-Spam-Level: 
X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 lQ0g6T-VJONr for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 19:23:04 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id EC3C43A6813 for <rrg@irtf.org>; Wed, 25 Feb 2009 19:23:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,268,1233532800"; d="scan'208";a="38442683"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 26 Feb 2009 03:23:24 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n1Q3NONN016154;  Wed, 25 Feb 2009 22:23:24 -0500
Received: from cisco.com (ssh-rtp-2.cisco.com [64.102.8.172]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1Q3NO06028629; Thu, 26 Feb 2009 03:23:24 GMT
Date: Wed, 25 Feb 2009 22:23:22 -0500
From: Scott Brim <swb@employees.org>
To: Christian Vogt <christian.vogt@ericsson.com>
Message-ID: <20090226032322.GD17652@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Christian Vogt <christian.vogt@ericsson.com>, rrg@irtf.org
References: <20090221204202.GN54483@cisco.com> <E21E8B89-57E0-40FB-819A-A10B045E63DE@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E21E8B89-57E0-40FB-819A-A10B045E63DE@ericsson.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: rrg@irtf.org
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 03:23:05 -0000

Excerpts from Christian Vogt on Wed, Feb 25, 2009 07:16:15PM -0800:
> On Feb 21, 2009, Scott Brim wrote:
>
>>> 3.1.2.  Translation
>>>
>>>   Translation solutions are characterized by a translation
>>>   operation between an identifier to a locator and back to an
>>>   identifier as the packet traverses the network.
>>
>> Now that I've pondered this a little, I can't think of any approach
>> that does that (translate from identifier to locator and back again).
>
>
> Scott -
>
> All address indirection solutions that are application-transparent do
> map both source and destination addresses at both ends.  I.e., you have
> four mappings per packets:  The respective local addresses (source
> address at the sending side; destination address at the destination
> side) are mapped to achieve provider independence.  The respective
> remote addresses are mapped to achieve application transparency.

You just helped make my point.  The sentence says translation is from
an "identifier" to a "locator" and back again.  The scenario you
describe is not that, it's between global and local addresses.

>> NAT-based approaches and Six/One Router are also one-way: the local
>> source address is translated to an RLOC when outgoing, and the
>> destination address is translated to a local address when incoming.
>
> As you mention Six/One Router -- this solution proposal actually has two
> modes:  One mode is NOT application-transparent; this, as you say, maps
> only the respective local addresses (two mappings per packet).  But
> Six/One Router also has an application-transparent mode, which performs
> all four mappings per packet.  The two modes are called Unilateral mode
> and Bilateral mode, respectively.
>
> And FWIW:  Six/One Router, Unilateral mode == NAT66.

Agreed.

From christian.vogt@ericsson.com  Wed Feb 25 19:53:11 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 536FB3A6A0D for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 19:53:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.133
X-Spam-Level: 
X-Spam-Status: No, score=-6.133 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 Vyy0RewDFRbw for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 19:53:09 -0800 (PST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id DBB9A28C1D7 for <rrg@irtf.org>; Wed, 25 Feb 2009 19:52:44 -0800 (PST)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n1Q3quEu009351; Wed, 25 Feb 2009 21:52:56 -0600
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 25 Feb 2009 21:52:56 -0600
Received: from [155.53.229.77] ([155.53.229.77]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 25 Feb 2009 21:52:55 -0600
Message-Id: <BB6B08A5-2AAC-420B-B8C5-002102751511@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Tony Li <tony.li@tony.li>, Scott Brim <swb@employees.org>
In-Reply-To: <18AE350EBE534FD69400A43F609967B6@ad.redback.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 25 Feb 2009 19:52:58 -0800
References: <20090221204202.GN54483@cisco.com> <18AE350EBE534FD69400A43F609967B6@ad.redback.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 26 Feb 2009 03:52:55.0667 (UTC) FILETIME=[B4EECC30:01C997C5]
Cc: Routing Research Group Mailing List <rrg@irtf.org>
Subject: Re: [rrg] I-D Action: draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 03:53:11 -0000

Scott and Tony -

> |In this section I don't see the relevance of "numeric" and
> |"character-string".  To the functions using these identifiers, they
> |are just bits, regardless of what semantics a human might see in  
> them.
>
> Agreed, this is diverging from the conceptual and into the  
> engineering.

While the differentiation between "numeric" and "character-string" may
indeed not be directly relevant at the conceptual level, I think the
differentiation that Bill actually had in mind was between human-
readable and non-human-readable identifiers.  This does have conceptual
significance:  Since, ultimately, the identifier presented to the user
will have to be human-readable, solutions that use non-human-readable
identifiers will necessarily introduce a new layer of indirection,
whereas solutions that use a human-readable identifier don't have to.

FWIW, in Minneapolis, I presented a host-based solution [1] that uses
human-readable identifiers, and that does without a new indirection
layer.  The identifiers are DNS names.

- Christian

[1] http://users.piuha.net/chvogt/pub/2008/vogt-2008-hostname-oriented-stack.pdf



From christian.vogt@ericsson.com  Wed Feb 25 20:02:17 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C87F33A6BAF for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 20:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.085
X-Spam-Level: 
X-Spam-Status: No, score=-6.085 tagged_above=-999 required=5 tests=[AWL=-0.285, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 eCjmto0IjK9S for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 20:02:17 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 0383F3A6A0D for <rrg@irtf.org>; Wed, 25 Feb 2009 20:02:16 -0800 (PST)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n1Q49WpB018841; Wed, 25 Feb 2009 22:09:32 -0600
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 25 Feb 2009 22:02:35 -0600
Received: from [155.53.229.77] ([155.53.229.77]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 25 Feb 2009 22:02:35 -0600
Message-Id: <AB04B72B-9659-4D9C-9FDE-86EBC3F3DAEC@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Scott Brim <swb@employees.org>
In-Reply-To: <20090226032322.GD17652@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 25 Feb 2009 20:02:37 -0800
References: <20090221204202.GN54483@cisco.com> <E21E8B89-57E0-40FB-819A-A10B045E63DE@ericsson.com> <20090226032322.GD17652@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 26 Feb 2009 04:02:35.0100 (UTC) FILETIME=[0E4D41C0:01C997C7]
Cc: rrg@irtf.org
Subject: Re: [rrg] I-D Action: draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 04:02:17 -0000

Scott -

> You just helped make my point.  The sentence says translation is from
> an "identifier" to a "locator" and back again.  The scenario you
> describe is not that, it's between global and local addresses.

The mapping could be between any two name-spaces, whether one of them is
an identifier or not.  In fact, Shim6 is an example of an application-
transparent, translation-based method that maps between identifiers and
locators -- where the identifier is a recycled locator of which the
topological meaning is ignored.

- Christian



From drc@virtualized.org  Wed Feb 25 21:04:26 2009
Return-Path: <drc@virtualized.org>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9670C3A696D for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 21:04:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.582
X-Spam-Level: 
X-Spam-Status: No, score=-5.582 tagged_above=-999 required=5 tests=[AWL=0.218,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 sWPOtft4Yfri for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 21:04:25 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id E18F93A687F for <rrg@irtf.org>; Wed, 25 Feb 2009 21:04:25 -0800 (PST)
Received: from [10.0.1.6] (cpe-70-95-123-210.hawaii.res.rr.com [70.95.123.210]) by virtualized.org (Postfix) with ESMTP id C61D548D30B; Wed, 25 Feb 2009 21:04:45 -0800 (PST)
Message-Id: <4D6A025D-8BE6-4A29-A997-75C4D67CB747@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Christian Vogt <christian.vogt@ericsson.com>
In-Reply-To: <E21E8B89-57E0-40FB-819A-A10B045E63DE@ericsson.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 25 Feb 2009 19:04:42 -1000
References: <20090221204202.GN54483@cisco.com> <E21E8B89-57E0-40FB-819A-A10B045E63DE@ericsson.com>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] I-D Action:draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 05:04:26 -0000

Hi,

Just a minor point:

On Feb 25, 2009, at 5:16 PM, Christian Vogt wrote:
> All address indirection solutions that are application-transparent do
> map both source and destination addresses at both ends.  I.e., you  
> have
> four mappings per packets:  The respective local addresses (source
> address at the sending side; destination address at the destination
> side) are mapped to achieve provider independence.  The respective
> remote addresses are mapped to achieve application transparency.

Yes, you need a mapping on both sides, but no, you don't need to do  
all 4 per packet. You can leave the source identifier unmapped.  You  
map the destination identifier to destination locator at the source  
edge and unmap the destination locator back into the destination  
identifer at the destination edge.  You only need to map the source  
when you need to send something back (yes, if you have multiple edge  
devices at the source, it can make it a bit more difficult to find the  
one the packet came out of if you need to).

As I said, a minor point.

Regards,
-drc


From christian.vogt@ericsson.com  Wed Feb 25 22:08:35 2009
Return-Path: <christian.vogt@ericsson.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BCC828C1F2 for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 22:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.05
X-Spam-Level: 
X-Spam-Status: No, score=-6.05 tagged_above=-999 required=5 tests=[AWL=-0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 f73VmpwGm-0i for <rrg@core3.amsl.com>; Wed, 25 Feb 2009 22:08:32 -0800 (PST)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 3D90528C1EE for <rrg@irtf.org>; Wed, 25 Feb 2009 22:08:32 -0800 (PST)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n1Q68oTQ021132; Thu, 26 Feb 2009 00:08:52 -0600
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 26 Feb 2009 00:08:49 -0600
Received: from [155.53.229.77] ([155.53.229.77]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 26 Feb 2009 00:08:49 -0600
Message-Id: <A28821A0-1B8E-4739-A1EE-8ACCA7653903@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: David Conrad <drc@virtualized.org>
In-Reply-To: <4D6A025D-8BE6-4A29-A997-75C4D67CB747@virtualized.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 25 Feb 2009 22:08:52 -0800
References: <20090221204202.GN54483@cisco.com> <E21E8B89-57E0-40FB-819A-A10B045E63DE@ericsson.com> <4D6A025D-8BE6-4A29-A997-75C4D67CB747@virtualized.org>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 26 Feb 2009 06:08:49.0297 (UTC) FILETIME=[B0E00010:01C997D8]
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] I-D Action: draft-irtf-rrg-recommendation-00.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 06:08:35 -0000

David Conrad wrote:

> Yes, you need a mapping on both sides, but no, you don't need to do  
> all
> 4 per packet. You can leave the source identifier unmapped.  [...]

That's correct, David.

At least, assuming that there won't be ingress filtering after the
source-side mapping.  But given that ingress filtering is typically
performed at the edge, I do agree with you.

That said, I think the main point here is not the number of mappings per
packet, but rather whether we want to be application-transparent.  After
all, the need for bilateral support, and for a global mapping system,
exists if and only if we want to be application-transparent.

- Christian



From tony.li@tony.li  Sat Feb 28 07:55:25 2009
Return-Path: <tony.li@tony.li>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6CC73A686D for <rrg@core3.amsl.com>; Sat, 28 Feb 2009 07:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level: 
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[AWL=0.179,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 1KqDbZEzWrEY for <rrg@core3.amsl.com>; Sat, 28 Feb 2009 07:55:25 -0800 (PST)
Received: from QMTA06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by core3.amsl.com (Postfix) with ESMTP id D989F3A67AD for <rrg@irtf.org>; Sat, 28 Feb 2009 07:55:24 -0800 (PST)
Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by QMTA06.emeryville.ca.mail.comcast.net with comcast id MR1m1b00816AWCUA6TvpCh; Sat, 28 Feb 2009 15:55:49 +0000
Received: from TONYLTM9XP ([155.53.1.254]) by OMTA06.emeryville.ca.mail.comcast.net with comcast id MTvg1b0055Up7oj8STviCr; Sat, 28 Feb 2009 15:55:47 +0000
From: "Tony Li" <tony.li@tony.li>
To: <rrg@irtf.org>
Date: Sat, 28 Feb 2009 07:55:25 -0800
Message-ID: <47E6903D80A8428D943098D2E285B1E7@ad.redback.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_015F_01C99979.EE55C220"
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AcmZDcemPW4XSdSGSg2lP3tUGoTgygAryBng
Subject: [rrg] FW: I-D ACTION:draft-irtf-rrg-recommendation-01.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Feb 2009 15:55:25 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_015F_01C99979.EE55C220
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

	

FYI, next rev.

Tony
 

|-----Original Message-----
|From: i-d-announce-bounces@ietf.org 
|[mailto:i-d-announce-bounces@ietf.org] On Behalf Of 
|Internet-Drafts@ietf.org
|Sent: Friday, February 27, 2009 11:00 AM
|To: i-d-announce@ietf.org
|Subject: I-D ACTION:draft-irtf-rrg-recommendation-01.txt 
|
|A New Internet-Draft is available from the on-line Internet-Drafts 
|directories.
|
|
|	Title		: Preliminary Recommendation for a 
|Routing Architecture
|	Author(s)	: T. Li
|	Filename	: draft-irtf-rrg-recommendation-01.txt
|	Pages		: 15
|	Date		: 2009-2-27
|	
|It is commonly recognized that the Internet routing and addressing
|   architecture is facing challenges in scalability, multi-homing, and
|   inter-domain traffic engineering.  This document reports 
|the Routing    Research Group's prelimnary findings from its 
|efforts towards
|   developing a recommendation for a scalable routing architecture.
|
|   This document is a work in progress.
|
|A URL for this Internet-Draft is:
|http://www.ietf.org/internet-drafts/draft-irtf-rrg-recommendation-01.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.
|

------=_NextPart_000_015F_01C99979.EE55C220
Content-Type: Message/External-body;
	name="draft-irtf-rrg-recommendation-01.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="draft-irtf-rrg-recommendation-01.txt"

Content-Type: text/plain
Content-ID: <2009-2-27105202.I-D@ietf.org>


------=_NextPart_000_015F_01C99979.EE55C220
Content-Type: text/plain;
	name="ATT00196.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="ATT00196.txt"

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

------=_NextPart_000_015F_01C99979.EE55C220--


From pfrejborg@gmail.com  Sat Feb 28 10:38:41 2009
Return-Path: <pfrejborg@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1EE83A67F6 for <rrg@core3.amsl.com>; Sat, 28 Feb 2009 10:38:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=-0.180,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 Q19YcM--PQXQ for <rrg@core3.amsl.com>; Sat, 28 Feb 2009 10:38:40 -0800 (PST)
Received: from mail-fx0-f160.google.com (mail-fx0-f160.google.com [209.85.220.160]) by core3.amsl.com (Postfix) with ESMTP id 0D0753A6A6D for <rrg@irtf.org>; Sat, 28 Feb 2009 10:38:39 -0800 (PST)
Received: by fxm4 with SMTP id 4so1592038fxm.7 for <rrg@irtf.org>; Sat, 28 Feb 2009 10:39:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LL9LVmpl3a/wI3BeOXtMSiiz8L0/3ZF2XY0+/OXxz/I=; b=vGme1oEe5Bo1GAd2NTsZSEJyoDn7aD9WwoWdFtvaL2N3DoNYrV8IIpE5anlPkhm81e sITwxuJZxcbddklsSjxwl7HVWUg7Rd/CER9LK9Cz+EGuCeIy5Xl3OguILZrLWl/o4B+l 7lxwZvRF5K3zBLSsS3kGbTAqt4X+7d+6xzkik=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=j3uMBNIe+QviC+ntSydE7zxgwk3K1h1DfHVm9uO97/EsV/kmzsbOaeMlZ2FQxWs6T7 8ePJV3ZnP4rjJQegWZ23XG/8nUEtz3iygOWjJWGggD0+PchFLs3LXi84X0lcR5SNWY4r OCqa3yBqcZWFLF6I8A+92zi8SaufFDRhFlcOg=
MIME-Version: 1.0
Received: by 10.181.197.5 with SMTP id z5mr1093483bkp.6.1235846343091; Sat, 28  Feb 2009 10:39:03 -0800 (PST)
In-Reply-To: <47E6903D80A8428D943098D2E285B1E7@ad.redback.com>
References: <47E6903D80A8428D943098D2E285B1E7@ad.redback.com>
Date: Sat, 28 Feb 2009 20:39:03 +0200
Message-ID: <5bc37fd40902281039i67af4f88kcae36cb4a164a0b5@mail.gmail.com>
From: Patrick Frejborg <pfrejborg@gmail.com>
To: tony.li@tony.li
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rrg@irtf.org
Subject: Re: [rrg] FW: I-D ACTION:draft-irtf-rrg-recommendation-01.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Feb 2009 18:38:42 -0000

I'm little bit concerned about this approach, for example my proposal
http://tools.ietf.org/html/draft-frejborg-hipv4-00
will fit into (among other strategies)
3.3.5.  Strategy E
   Make no routing architecture changes.

I'm not proposing any changes to the current routing architecture,
instead proposing changes to current disciplines and by adding some
components we could solve this issue.
We have already a hierarchial routing architecture. IGP have one or
two levels and then you achieve further hierarchy by adding BGP on
top. So adding a forth or fifth level to the current routing
architecture will not solve the problem, it will only become more
complicated to implement and maintain.

IMHO, the root cause to the situation we are in is the flat numbering
schema - if we don't deal with that problem now we have to deal with
it in the future.

The current routing architecture is superior, I rather leave that
untouched and go after the flat numbering schema - almost everything
else should be modified but not the routing architecture.

-- patte

2009/2/28 Tony Li <tony.li@tony.li>:
>
>
> FYI, next rev.
>
> Tony
>
>
> |-----Original Message-----
> |From: i-d-announce-bounces@ietf.org
> |[mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> |Internet-Drafts@ietf.org
> |Sent: Friday, February 27, 2009 11:00 AM
> |To: i-d-announce@ietf.org
> |Subject: I-D ACTION:draft-irtf-rrg-recommendation-01.txt
> |
> |A New Internet-Draft is available from the on-line Internet-Drafts
> |directories.
> |
> |
> | =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Preliminary Recommendation for =
a
> |Routing Architecture
> | =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : T. Li
> | =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-irtf-rrg-recommendation-01.=
txt
> | =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 15
> | =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2009-2-27
> |
> |It is commonly recognized that the Internet routing and addressing
> | =A0 architecture is facing challenges in scalability, multi-homing, and
> | =A0 inter-domain traffic engineering. =A0This document reports
> |the Routing =A0 =A0Research Group's prelimnary findings from its
> |efforts towards
> | =A0 developing a recommendation for a scalable routing architecture.
> |
> | =A0 This document is a work in progress.
> |
> |A URL for this Internet-Draft is:
> |http://www.ietf.org/internet-drafts/draft-irtf-rrg-recommendation-01.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.
> |
>
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>
>

From rw@firstpr.com.au  Sat Feb 28 20:47:57 2009
Return-Path: <rw@firstpr.com.au>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6B593A6883 for <rrg@core3.amsl.com>; Sat, 28 Feb 2009 20:47:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.384
X-Spam-Level: 
X-Spam-Status: No, score=0.384 tagged_above=-999 required=5 tests=[AWL=-1.120,  BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, SARE_SUB_RAND_LETTRS4=0.799]
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 SAUYXolWDFAL for <rrg@core3.amsl.com>; Sat, 28 Feb 2009 20:47:51 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id F06553A696F for <rrg@irtf.org>; Sat, 28 Feb 2009 20:47:42 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 922441759F8; Sun,  1 Mar 2009 15:48:05 +1100 (EST)
Message-ID: <49AA1313.2000409@firstpr.com.au>
Date: Sun, 01 Mar 2009 15:46:11 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [rrg] draft-irtf-rrg-recommendation-01 lacks suggested improvements
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Mar 2009 04:47:57 -0000

Hi Tony,

Your new draft (26 February):

  http://tools.ietf.org/html/draft-irtf-rrg-recommendation-01

does not include any of the changes and additions I suggested on 24
February:

 Ivip map-encap & MHF in draft-irtf-rrg-recommendation-00
 http://www.ietf.org/mail-archive/web/rrg/current/msg04535.html

You expanded the first two taxonomies:

  3.1 A Mechanism Taxonomy
  3.2 A Functional Taxonomy

but changed only a few words in the third:

  3.3 The Herrin Taxonomy

as can be seen from the Diff1 link from the current version.

You added a note about the taxonomies that "Section 3.3 is the
most useful so far and is where we will continue to focus our efforts."

I had suggested that if you do not expect a taxonomy to be complete
that you either delete it or indicate clearly that each such taxonomy
is incomplete.


On 17 February (message 4520) I had suggested an addition to the 3.1
taxonomy to make it more complete.

You wrote here:

  http://www.ietf.org/mail-archive/web/rrg/current/msg04533.html

     The taxonomy in 3.1 is inadequate and not particularly helpful
     and not really worth further refinement.

yet in version 01 you refined and extended 3.1 somewhat, without
including my suggested addition.


Your initial response to my suggested changes to 3.3, and my reply:

  http://www.ietf.org/mail-archive/web/rrg/current/msg04546.html
  http://www.ietf.org/mail-archive/web/rrg/current/msg04547.html


So far, my efforts to improve the draft have had little or no effect
 - and after reading your message 4546 I am unclear on what reasons
you might have for not accepting my suggestions or for not discussing
them in meaningful detail.

Maybe you plan to include or discuss these suggestions in detail -
but have not yet had time to do so.

I have made a page to track what I think is currently missing from
the draft of our forthcoming recommendations:

  http://www.firstpr.com.au/ip/ivip/RRG-2009/rec/


  - Robin

From rw@firstpr.com.au  Sat Feb 28 20:49:02 2009
Return-Path: <rw@firstpr.com.au>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15F033A6A44 for <rrg@core3.amsl.com>; Sat, 28 Feb 2009 20:49:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.129
X-Spam-Level: 
X-Spam-Status: No, score=-1.129 tagged_above=-999 required=5 tests=[AWL=0.766,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
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 DFfv9MsI-veZ for <rrg@core3.amsl.com>; Sat, 28 Feb 2009 20:48:55 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 1A3323A688B for <rrg@irtf.org>; Sat, 28 Feb 2009 20:48:55 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id CDDAA1759F8; Sun,  1 Mar 2009 15:49:17 +1100 (EST)
Message-ID: <49AA135B.1050209@firstpr.com.au>
Date: Sun, 01 Mar 2009 15:47:23 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: rrg@irtf.org
References: <5bc37fd40902250116r2eb8c384n79f887cb5708fa9d@mail.gmail.com>
In-Reply-To: <5bc37fd40902250116r2eb8c384n79f887cb5708fa9d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [rrg] New draft, the hierachial IPv4 framework
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Mar 2009 04:49:02 -0000

Hi Patrick,

While I haven't been able to understand exactly how your proposal

   http://tools.ietf.org/html/draft-frejborg-hipv4-00

would work, I think it could not be considered as the best approach
to the scalable routing problem for the following reasons:

1 - It involves extensive changes to host stacks, APIs and
    applications.

    In order to be effective, such as enabling a billion or
    whatever large number of multihomable end-user networks,
    without causing scaling problems, the solution needs to be
    very broadly accepted by most end-user networks of all types and
    sizes.  They will only do this if there is immediate benefit to
    them (in months) and very little in the way of risks and costs.

    A primary functional benefit of the Internet is 100% reachability
    of all hosts.  Any proposal such as yours which involves a new
    addressing system relying on host changes, means that all hosts
    adopting the new addressing system will be unreachable by those
    which have not upgraded their stack, API and applications.

    Therefore, your new addressing scheme would only be useful to
    most users once everyone has adopted it.  In the meantime, there
    are only costs (actually, impossibility of having all
    applications rewritten, even if you got the stacks rewritten)
    and few benefits for anyone who adopts it - so it would never in
    fact be adopted widely.

2 - Likewise, for routers and ISPs.

3 - Your proposal doesn't help with IPv6.  This would be widely
    regarded as a show-stopper, on the assumption that IPv6 is
    going to be the future Internet, replacing the IPv4 Internet.

    I am not convinced this is going to happen at all, or any time
    soon, but for most people in this field, any scalable routing and
    addressing solution must also have a solution for IPv6.  I am
    working on solutions for both IPv4 and IPv6.  I think IPv6
    is likely to achieve significant adoption, at least for cellphone
    systems, in the next decade.

The architectures used by the core-edge separation schemes LISP, APT,
Ivip and TRRP could all work for both IPv4 and IPv6, without
requiring host changes, while supporting packets from non-upgraded
networks, without creating any new address spaces.  They convert
parts of the existing IP address space into a special kind, which I
call "Scalable PI" space, which is highly suitable for end-user
networks needing multihoming, inbound TE and portability between ISPs.


I have had some thoughts about creating a new (third . . . ) Internet
using a 64 bit address space built by extending IPv4 IP addresses
into a gateway for another 2^32 addresses in the new system.
However, I think there are probably as many problems changing the
world over to such a new network as there are changing the world over
to IPv6.

You wrote:

> I do have a presentation available, but lacking a FTP server resource

I can provide a stable home for it and any other material you have
under some directory such as http://www.firstpr.com.au/ip/xxx/ .

  - Robin


