Mail Index

• Thread Index

• [RRG] Moving the list...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: ILNP Critique
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: ILNP Critique
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Re: ILNP Critique
  • From: Steven Blake <slblake@petri-meat.com>
• [RRG] Re: ILNP Critique
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Commetns about load split in LISP
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] A data point on transit MTU size
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] A data point on transit MTU size
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] A data point on transit MTU size
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Solving the routing scaling problem for internal networks too? Ivip may be able to help
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] 2 billion IP cellphones... IPv6 RIB burden adding to IPv4 burden in...
  • From: HeinerHummel@aol.com
• Re: [RRG] 2 billion IP cellphones... IPv6 RIB burden adding to IPv4 burden in the same router?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Solving the routing scaling problem for internal networks too? Ivi...
  • From: HeinerHummel@aol.com
• [RRG] Solving the routing scaling problem for internal networks too? Ivip may be able to help
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Wesley George <wgeorge@sprint.net>
• Re: [RRG] Re: Comparing APT & Ivip - new business models
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Charging for updates in BGP
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Charging for updates in BGP
  • From: Geoff Huston <gih@apnic.net>
• [RRG] Re: Charging for updates in BGP
  • From: Michael Meisel <meisel@cs.ucla.edu>
• [RRG] Re: Comparing APT & Ivip
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Charging for updates in BGP
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Comparing APT & Ivip
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Separation vs. Elimination
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Separation vs. Elimination
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] A data point on transit MTU size
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] A data point on transit MTU size
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Separation vs. Elimination
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] A data point on transit MTU size
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Separation vs. Elimination
  • From: Michael Meisel <meisel@cs.ucla.edu>
• RE: [RRG] A data point on transit MTU size
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Separation vs. Elimination
  • From: Michael Meisel <meisel@cs.ucla.edu>
• RE: [RRG] A data point on transit MTU size
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] A data point on transit MTU size
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] A data point on transit MTU size
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Separation vs. Elimination
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] A data point on transit MTU size
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] A data point on transit MTU size
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] A data point on transit MTU size
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] A data point on transit MTU size
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Separation vs. Elimination
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Separation vs. Elimination
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] A data point on transit MTU size
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: David Conrad <drc@virtualized.org>
• RE: [RRG] A data point on transit MTU size
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] A data point on transit MTU size
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] A data point on transit MTU size
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Separation vs. Elimination
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Separation vs. Elimination
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Billions of micronets / EID prefixes
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Billions of micronets / EID prefixes
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Separation vs. Elimination
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] A data point on transit MTU size
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] A data point on transit MTU size
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Marshall Eubanks <tme@multicasttech.com>
• RE: [RRG] Re: Fast and sparse mapping?
  • From: HeinerHummel@aol.com
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Billions of micronets / EID prefixes
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Separation vs. Elimination
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Separation vs. Elimination
  • From: Lan Wang <lanwang@memphis.edu>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: Re: [RRG] Re: Fast and sparse mapping?
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: Re: [RRG] Consequences of no renumbering...
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] Separation vs. Elimination
  • From: Dan Jen <jenster@cs.ucla.edu>
• Re: [RRG] Separation vs. Elimination
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Separation vs. Elimination
  • From: Dan Jen <jenster@cs.ucla.edu>
• Re: [RRG] Separation vs. Elimination
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Separation vs. Elimination
  • From: Dan Jen <jenster@cs.ucla.edu>
• Re: [RRG] Separation vs. Elimination
  • From: He Yan <yanhe@cs.colostate.edu>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Separation vs. Elimination
  • From: Dan Jen <jenster@cs.ucla.edu>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Separation vs. Elimination
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Separation vs. Elimination
  • From: Michael Menth <menth@informatik.uni-wuerzburg.de>
• [RRG] Separation vs. Elimination
  • From: Dan Jen <jenster@cs.ucla.edu>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Wesley George <wgeorge@sprint.net>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Roland Dobbins <rdobbins@cisco.com>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Jari Arkko <jari.arkko@piuha.net>
• RE: [RRG] Re: Fast and sparse mapping?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consequences of no renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Wesley George <wgeorge@sprint.net>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Roland Dobbins <rdobbins@cisco.com>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Bruce Curtis <bruce.curtis@ndsu.edu>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Roland Dobbins <rdobbins@cisco.com>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Bruce Curtis <bruce.curtis@ndsu.edu>
• Re: [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Elegance and the rejection of SHIM6 host-based multihoming
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] drafty draft of Dublin RRG meeting minutes
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Roland Dobbins <rdobbins@cisco.com>
• Re: [RRG] Re: Practical Proposals vs. endless theoretical discussions
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Consequences of no renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Consequences of no renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Re: Fast and sparse mapping?
  • From: Stephen Sprunk <stephen@sprunk.org>
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
• RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] drafty draft of Dublin RRG meeting minutes
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] NAT capabilities
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Consequences of no renumbering...
  • From: Eliot Lear <lear@cisco.com>
• [RRG] Re: Fast and sparse mapping? aggregated EIDs, OITRDs etc.
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Fast and sparse mapping?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by current IPv4 users
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Fast and sparse mapping?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consequences of no renumbering...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] IPv6
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] Consequences of no renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Commetns about load split in LISP
  • From: "Damian Lezama" <damian.lezama@hotmail.com>
• [RRG] IPv6
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Re: Practical Proposals vs. endless theoretical discussions
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Re: Practical Proposals vs. endless theoretical discussions
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] ILNP critique
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Consequences of no renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Consequences of no renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consequences of no renumbering...
  • From: David Williamson <dlw+rrg@tellme.com>
• RE: [RRG] Re: Practical Proposals vs. endless theoretical discussions
  • From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
• [RRG] NAT capabilities
  • From: RJ Atkinson <rja@extremenetworks.com>
• [RRG] Re: Practical Proposals vs. endless theoretical discussions
  • From: RJ Atkinson <rja@extremenetworks.com>
• [RRG] Practical proposals vs. endless theoretical discussions
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Consequences of no renumbering...
  • From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
• Re: [RRG] Consequences of no renumbering...
  • From: Eliot Lear <lear@cisco.com>
• RE: [RRG] Consequences of no renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Consequences of no renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Running on Empty: the challenge of managing Internet addresses
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consequences of no renumbering...
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consequences of no renumbering...
  • From: Robert Bonomi <bonomi@mail.r-bonomi.com>
• Re: [RRG] Consequences of no renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Renumbering and Renumbering
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Consequences of no renumbering...
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Consequences of no renumbering...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Consequences of no renumbering...
  • From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
• Re: [RRG] Consequences of no renumbering...
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Consequences of no renumbering...
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Consequences of no renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Consequences of no renumbering...
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• Re: [RRG] Consequences of no renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Consequences of no renumbering...
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Consequences of no renumbering...
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Consequences of no renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consequences of no renumbering...
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Consequences of no renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Renumbering...
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Multiple PA blocks
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Renumbering...
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Renumbering...
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] "No renumbering" for any networks precludes scalable support for packets from non-upgraded networks
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Consensus reached: renumbering
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: David Conrad <drc@virtualized.org>
• [RRG] Splitting the problem
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: RE: [RRG] Renumbering...
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Renumbering...
  • From: Stephen Sprunk <stephen@sprunk.org>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: Re: [RRG] Renumbering...
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Renumbering...
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Renumbering...
  • From: David Williamson <dlw+rrg@tellme.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: Re: [RRG] Stretch in case of LISP+ALT
  • From: "heinerhummel@kabelmail.de" <heinerhummel@kabelmail.de>
• Re: [RRG] Stretch in case of LISP+ALT
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Stretch in case of LISP+ALT
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Stretch in case of LISP+ALT
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] Consensus check: renumbering - all networks need not be treated the same
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Consensus check: renumbering
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Consensus check: renumbering
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] PI as a non-requirement
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Renumbering...
  • From: Eliot Lear <lear@cisco.com>
• Re: Re: [RRG] Renumbering...
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• [RRG] Administrivia: mailing list management
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Consensus check: renumbering
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: Re: [RRG] Consensus check: renumbering
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] Consensus check: renumbering
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Consensus check: renumbering
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Consensus check: renumbering - missing dimension
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Consensus check: renumbering - missing dimension
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Bruce Curtis <bruce.curtis@ndsu.edu>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Tim Chown <tjc@ecs.soton.ac.uk>
• Re: [RRG] Consensus check: renumbering - question lacks detail
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: "Christopher Morrow" <morrowc.lists@gmail.com>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: "Dale W. Carder" <dwcarder@wisc.edu>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: "Dale W. Carder" <dwcarder@wisc.edu>
• RE: [RRG] Consensus check: renumbering - missing dimension
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Consensus check: renumbering - missing dimension
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: "Christopher Morrow" <morrowc.lists@gmail.com>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Renumbering...
  • From: David Conrad <drc@virtualized.org>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Renumbering once might be OK when converting to Scalable PI (SPI space)
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Portability between mapping providers
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Paper: TTR Mobility Extensions for Core-Edge Separation Solutions
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Consensus check: renumbering - missing dimension
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus check: renumbering - missing dimension
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Consensus check: renumbering
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Consensus check: renumbering
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus check: renumbering
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• RE: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] Consensus check: renumbering
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] Consensus check: renumbering - 3 kinds of thing which might be renumbered
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus check: renumbering - 3 kinds of thing which might be renumbered
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Alternative to encapsulation: IPv4 ETR Address Forwarding (EAF)
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Consensus check: renumbering
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus check: renumbering
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] Consensus check: renumbering
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Eliot Lear <lear@cisco.com>
• RE: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] RE: ALT oeprational model
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Re: ALT oeprational model
  • From: Eliot Lear <lear@cisco.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Renumbering... mapping
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Renumbering...
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Renumbering...
  • From: Peter Sherbin <pesherb@yahoo.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Renumbering...
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Renumbering...
  • From: Peter Sherbin <pesherb@yahoo.com>
• Huh? Was: Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Will the flat ID and its corresponding resolution infrastracture be practicable? [RRG] Renumbering...
  • From: "Rolf Winter" <Rolf.Winter@nw.neclab.eu>
• re: [RRG] Will the flat ID and its corresponding resolution infrastracture be practicable? [RRG] Renumbering...
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Renumbering...
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Re: Abstracted Networking APIs
  • From: RJ Atkinson <rja@extremenetworks.com>
• RE: [RRG] Renumbering...
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Providers and providers
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Will the flat ID and its corresponding resolution infrastracture be practicable? [RRG] Renumbering...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: RE: [RRG] Renumbering...
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Providers and providers
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] Re: Providers and Providers
  • From: RJ Atkinson <rja@extremenetworks.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Providers and providers
  • From: David Conrad <drc@virtualized.org>
• RE: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Renumbering...
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Providers and providers
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Roland Dobbins <rdobbins@cisco.com>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Will the flat ID and its corresponding resolution infrastracture be practicable? [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Providers and providers
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Re: PI as a non-requirement
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Providers and providers
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Providers and providers
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Providers and providers
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Providers and providers
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Providers and providers
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Providers and providers
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Providers and providers
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Providers and providers
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] Re: PI as a non-requirement
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] PI as a non-requirement
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Renumbering... ACLs etc.
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] PI as a non-requirement
  • From: RJ Atkinson <rja@extremenetworks.com>
• [RRG] Providers and providers
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Renumbering...
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• [RRG] Will the flat ID and its corresponding resolution infrastracture be practicable? [RRG] Renumbering...
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Renumbering...
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: RE: [RRG] Renumbering...
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• RE: [RRG] Renumbering...
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• RE: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Renumbering...
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• re: [RRG] Renumbering...
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Renumbering...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• re: [RRG] Renumbering... ACLs etc.
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] Renumbering...
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• RE: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Scott Weeks" <Scott.Weeks@hawaiiantel.com>
• Re: [RRG] Renumbering... ACLs etc.
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: [RRG] Renumbering...
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] Renumbering...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering... ACLs etc.
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] Renumbering...
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Renumbering...
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Renumbering...
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] Renumbering... ACLs etc.
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Renumbering... ACLs etc.
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Renumbering... ACLs etc.
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Renumbering... ACLs etc.
  • From: Eliot Lear <lear@cisco.com>
• RE: [RRG] Renumbering... ACL alternatives?
  • From: Pekka Savola <pekkas@netcore.fi>
• RE: [RRG] Renumbering... ACLs etc.
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering... ACLs etc.
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Six/One Router: why have bilateral mode? Referrals . . .
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Moving towards a new set of Networking APIs
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Renumbering...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Renumbering... ACLs etc.
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Re: Six/One Router: why have bilateral mode? Referrals . . .
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Renumbering...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Six/One Router: why have bilateral mode? Referrals . . .
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Renumbering... ACLs etc.
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Renumbering...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Renumbering...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Renumbering...
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Moving towards a new set of Networking APIs
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Renumbering...
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Renumbering...
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Renumbering...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] A Late Response to Questions on Six/One Router
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] A Late Response to Questions on Six/One Router
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Renumbering...
  • From: Michael Menth <menth@informatik.uni-wuerzburg.de>
• Re: [RRG] Renumbering...
  • From: Pekka Savola <pekkas@netcore.fi>
• RE: [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Renumbering...
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Brian Carpenter <brian@cs.auckland.ac.nz>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Renumbering...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] Moving towards a new set of Networking APIs
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Renumbering...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: RE: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] Renumbering...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Renumbering...
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] Renumbering...
  • From: Stig Venaas <stig.venaas@uninett.no>
• RE: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• Popping up a level (was Re: [RRG] On identifiers, was: Re: Does every host need a FQDN)
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Renumbering...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Renumbering...
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Renumbering...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Perplexing PMTUD and packet length observations Oops: TSO
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] On identifiers, was: Re: Does every host need a FQDN
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Perplexing PMTUD and packet length observations Oops: TSO
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RR=
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• Re: [RRG] Logistics preferences...
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Perplexing PMTUD and packet length observations
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Perplexing PMTUD and packet length observations
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Perplexing PMTUD and packet length observations
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Perplexing PMTUD and packet length observations
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Perplexing PMTUD and packet length observations
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Perplexing PMTUD and packet length observations
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Logistics preferences...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Logistics preferences...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Perplexing PMTUD and packet length observations
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Perplexing PMTUD and packet length observations
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Logistics preferences...
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Scott Brim <swb@employees.org>
• [RRG] Perplexing PMTUD and packet length observations
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Re: Six/One Router revised 2008-07-12 - IPsec
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] GLI-Split
  • From: Michael Menth <menth@informatik.uni-wuerzburg.de>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Six/One Router revised 2008-07-12 - IPsec
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Re: Six/One Router revised 2008-07-12 - IPsec
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Six/One Router revised 2008-07-12 - IPsec
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Logistics preferences...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Re: Six/One Router revised 2008-07-12 - IPsec
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Re: Six/One Router revised 2008-07-12 - IPsec
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Six/One Router revised 2008-07-12 - IPsec
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Six/One Router revised 2008-07-12 - IPsec
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Logistics
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Logistics preferences...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] A Late Response to Questions on Six/One Router
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] thoughts on the design space 1: the space
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] A Late Response to Questions on Six/One Router
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] thoughts on the design space 1: the space
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Logistics preferences...
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] thoughts on the design space 1: the space
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Logistics preferences...
  • From: Steven Blake <slblake@petri-meat.com>
• RE: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Steven Blake <slblake@petri-meat.com>
• RE: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Sheng Jiang <shengjiang@huawei.com>
• Re: [RRG] Logistics preferences...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Logistics preferences...
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• RE: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Logistics preferences...
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Logistics preferences...
  • From: Benno Overeinder <benno@NLnetLabs.nl>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Ivip6 - Forwarding Label in the Core
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Steven Blake <slblake@petri-meat.com>
• Re: [RRG] Logistics preferences...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] draft-rja-ilnp-intro-01.txt
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Logistics preferences...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Logistics preferences...
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] Logistics preferences...
  • From: Scott Brim <swb@employees.org>
• RE: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Xu Xiaohu <xuxh@huawei.com>
• [RRG] RE: Logistics preferences...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Logistics preferences...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Logistics preferences...
  • From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
• Re: [RRG] Logistics preferences...
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Logistics preferences...
  • From: Brian Dickson <briand@ca.afilias.info>
• [RRG] Logistics preferences...
  • From: "Tony Li" <tony.li@tony.li>
• RE: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] draft-rja-ilnp-intro-01.txt
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] Ivip6 - Forwarding Label in the Core
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] A new brand of MPLS can do the job
  • From: "Heinrich Hummel" <heinerhummel@kabelmail.de>
• re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption - Dual Stack Lite
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Ivip6: number of "Flow Label" bits required
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption - Dual Stack Lite
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption - Dual Stack Lite: P2P usage rates
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption - Dual Stack Lite
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Short explanation: Ivip6's "Core Routing Label Forwarding"
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption - Dual Stack Lite
  • From: David Conrad <drc@virtualized.org>
• [RRG] Short explanation: Ivip6's "Core Routing Label Forwarding"
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] FLOWv6: IPv6 Flow Label to control DFZ forwarding
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] FLOWv6: IPv6 Flow Label to control DFZ forwarding
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] FLOWv6: IPv6 Flow Label to control DFZ forwarding
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] draft-rja-ilnp-intro-01.txt
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] draft-rja-ilnp-intro-01.txt
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Re: Ivip6: number of "Flow Label" bits required
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Ivip6: number of "Flow Label" bits required
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Ivip6: number of "Flow Label" bits required
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Ivip6 (previously FLOWv6), Ivip4 and Ivip
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] draft-rja-ilnp-intro-01.txt
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] thoughts on the design space 1: the space
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] thoughts on the design space 1: the space
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption - Dual Stack Lite
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: RFC3697 [Re: [RRG] FLOWv6: IPv6 Flow Label to control DFZ forwarding]
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] draft-rja-ilnp-intro-01.txt
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption - Dual Stack Lite
  • From: HeinerHummel@aol.com
• RE: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] draft-rja-ilnp-intro-01.txt
  • From: "Tony Li" <tony.li@tony.li>
• Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
  • From: xuxiaohu 41208 <xuxh@huawei.com>
• RE: RFC3697 [Re: [RRG] FLOWv6: IPv6 Flow Label to control DFZ forwarding]
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] position paper on resource pooling
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Re: position paper on resource pooling
  • From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
• [RRG] position paper on resource pooling
  • From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption - Dual Stack Lite
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] paper on separation of locators and identifiers
  • From: Aaron Falk <falk@bbn.com>
• Re: RFC3697 [Re: [RRG] FLOWv6: IPv6 Flow Label to control DFZ forwarding]
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] draft-rja-ilnp-intro-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RFC3697 [Re: [RRG] FLOWv6: IPv6 Flow Label to control DFZ forwarding]
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] thoughts on the design space 1: the space
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG]
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 1: the space
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] FLOWv6: IPv6 Flow Label to control DFZ forwarding
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Six/One Router revised 2008-07-12
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Six/One Router revised 2008-07-12
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Re: Difference between translation in LISP vs. Six/One Router -- Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Agenda changes...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: Difference between translation in LISP vs. Six/One Router -- Re: [RRG] Six/One Router Design Clarifications
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] thoughts on the design space 3: caching: FIBs, local query servers
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] thoughts on the design space 1: the space
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Difference between translation in LISP vs. Six/One Router -- Re: [RRG] Six/One Router Design Clarifications
  • From: David Meyer <dmm@1-4-5.net>
• Re: Difference between translation in LISP vs. Six/One Router -- Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Re: Difference between translation in LISP vs. Six/One Router -- Re: [RRG] Six/One Router Design Clarifications
  • From: David Meyer <dmm@1-4-5.net>
• Difference between translation in LISP vs. Six/One Router -- Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] LISP home page www.lisp4.net
  • From: David Meyer <dmm@1-4-5.net>
• [RRG] LISP home page www.lisp4.net
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Business incentives for LISP PTRs and Ivip OITRDs
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Map-encap, fragmentation, PMTUD etc.
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Map-encap, fragmentation, PMTUD etc.
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] Map-encap, fragmentation, PMTUD etc.
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Six/One Router Design Clarifications
  • From: Pekka Savola <pekkas@netcore.fi>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Current drafts
  • From: Luigi Iannone <Luigi.Iannone@uclouvain.be>
• Re: [RRG] Current drafts
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Current drafts
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• RE: [RRG] thoughts on the design space 1: the space
  • From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
• Re: [RRG] Mapping Distribution and Management: contribution for comments
  • From: HeinerHummel@aol.com
• RE: vulnerability of being attacked//RE: [RRG] Re: Should the identifier be used as local locator
  • From: "Tony Li" <tony.li@tony.li>
• vulnerability of being attacked//RE: [RRG] Re: Should the identifier be used as local locator
  • From: xuxiaohu 41208 <xuxh@huawei.com>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] thoughts on the design space 2: upper layer implications
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Mapping Distribution and Management: contribution for comments
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] a few draft towards convergence
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Mapping Distribution and Management: contribution for comments
  • From: ksriram@nist.gov
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: "William Herrin" <bill@herrin.us>
• [RRG] GLI-Split
  • From: Michael Menth <menth@informatik.uni-wuerzburg.de>
• Re: [RRG] Mapping Distribution and Management: contribution for comments
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Current drafts
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] a few draft towards convergence
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] thoughts on the design space 3: caching
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Marshall Eubanks <tme@multicasttech.com>
• RE: [RRG] thoughts on the design space 2: upper layer implications
  • From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
• RE: [RRG] thoughts on the design space 3: caching
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] thoughts on the design space 2: upper layer implications
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] Design Taxonomy/Analysis for Address-Indirection-Based Solutions
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] a new (not few) draft towards convergence
  • From: Dan Jen <jenster@cs.ucla.edu>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] a new (not few) draft towards convergence
  • From: Luigi Iannone <Luigi.Iannone@uclouvain.be>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "Tony Li" <tony.li@tony.li>
• re: [RRG] thoughts on the design space 3: caching
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] thoughts on the design space 3: caching
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Robin Whittle <rw@firstpr.com.au>
• re: [RRG] RE: Is the flat identifier acceptable
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] a new (not few) draft towards convergence
  • From: Dan Jen <jenster@cs.ucla.edu>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Re: Is the flat identifier acceptable
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] RE: Is the flat identifier acceptable
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] thoughts on the design space 3: caching
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] thoughts on the design space 3: caching
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] thoughts on the design space 3: caching
  • From: "William Herrin" <bill@herrin.us>
• [RRG] thoughts on the design space 4: encapsulate vs. translate
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] thoughts on the design space 3: caching
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] thoughts on the design space 2: upper layer implications
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] thoughts on the design space 1: the space
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] RE: Is the flat identifier acceptable
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] IEEE EUI-64 as an Identifier format
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] a new (not few) draft towards convergence
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] RE: Is the flat identifier acceptable
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] RE: Is the flat identifier acceptable
  • From: "Tony Li" <tony.li@tony.li>
• re: [RRG] RE: Is the flat identifier acceptable
  • From: Xu Xiaohu <xuxh@huawei.com>
• [RRG] RE: Is the flat identifier acceptable
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Is the flat identifier acceptable
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Brian Carpenter <brian@cs.auckland.ac.nz>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Drake, John E" <John.E.Drake2@boeing.com>
• Re: [RRG] Question about Six/One host and router
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] IEEE EUI-64 as an Identifier format
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] IEEE EUI-64 as an Identifier format
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] GSE?
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Moving forward...
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: ksriram@nist.gov
• [RRG] Review of ILNP -- plus a new idea
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "William Herrin" <bill@herrin.us>
• re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] RE: Abstraction action boundary & geo-aggregation router behavior
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "K. Sriram" <ksriram@nist.gov>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: HeinerHummel@aol.com
• RE: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "William Herrin" <bill@herrin.us>
• [RRG] a new (not few) draft towards convergence
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] RE: FIB challenges, RIB, BGP, DRAM limitations
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] RE: Abstraction action boundary & geo-aggregation router behavior
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] FIB challenges, RIB, BGP, DRAM limitations
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "Scott Weeks" <surfer@mauigateway.com>
• [RRG] Abstraction action boundary & geo-aggregation router behavior
  • From: Robin Whittle <rw@firstpr.com.au>
• re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Searching the RRG archives at mail-archive.com
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "Tony Li" <tony.li@tony.li>
• RE: Geo RIB-FIB compression, was: Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Opportunistic Topological Aggregation in the RIB->FIB Calculation?
  • From: "William Herrin" <bill@herrin.us>
• [RRG] a few draft towards convergence
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "William Herrin" <bill@herrin.us>
• Geo RIB-FIB compression, was: Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] Question about Six/One host and router
  • From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
• Geo RIB-FIB compression, was: Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Brian Dickson <briand@ca.afilias.info>
• RE: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] RRG scope avoids practical concerns
  • From: HeinerHummel@aol.com
• RE: [RRG] RRG scope avoids practical concerns
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] RRG scope avoids practical concerns
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Peter Sherbin <pesherb@yahoo.com>
• RE: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: HeinerHummel@aol.com
• RE: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Ricardo Oliveira <rveloso@CS.UCLA.EDU>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Geographic aggregation-based routing is at odds with reality
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Ricardo Oliveira <rveloso@cs.ucla.edu>
• Re: [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Geographic aggregation-based routing is at odds with reality
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Discussions in Dublin
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Geographic aggregation-based routing
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Publicly available LISP and shim6 implementations
  • From: David Meyer <dmm@1-4-5.net>
• [RRG] Mapping Distribution and Management: contribution for comments
  • From: "K. Sriram" <ksriram@nist.gov>
• RE: [RRG] Publicly available LISP and shim6 implementations
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Publicly available LISP and shim6 implementations
  • From: Luigi Iannone <Luigi.Iannone@uclouvain.be>
• RE: [RRG] Publicly available LISP and shim6 implementations
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Publicly available LISP and shim6 implementations
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• [RRG] Publicly available LISP and shim6 implementations
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] Current drafts
  • From: <louise.burness@bt.com>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Does LISP 3 use the cache mechanism on ITR for the EID-to-RLOC mapping?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Six/One Router Design Clarifications
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Six/One Router Design Clarifications
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Does LISP 3 use the cache mechanism on ITR for the EID-to-RLOC mapping?
  • From: "Dongxiao Xu" <njuxdx@gmail.com>
• Re: [RRG] Does LISP 3 use the cache mechanism on ITR for the EID-to-RLOC mapping?
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Does LISP 3 use the cache mechanism on ITR for the EID-to-RLOC mapping?
  • From: "Dongxiao Xu" <njuxdx@gmail.com>
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: Robert Bonomi <bonomi@mail.r-bonomi.com>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Abstraction of problem space
  • From: Brian Dickson <briand@ca.afilias.info>
• [RRG] Six/One Router Design Clarifications
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• [RRG] A Late Response to Questions on Six/One Router
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Abstraction of problem space
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Geographic aggregation-based routing
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Abstraction of problem space
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Geographic aggregation-based routing
  • From: HeinerHummel@aol.com
• [RRG] Geographic aggregation-based routing
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Abstraction of problem space
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Abstraction of problem space
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Abstraction of problem space
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Re: Should the identifier be used as local locator
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Terminology
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Should the identifier be used as local locator
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Should the identifier be used as local locator
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] Terminology
  • From: RJ Atkinson <rja@extremenetworks.com>
• [RRG] Re: Should the identifier be used as local locator
  • From: RJ Atkinson <rja@extremenetworks.com>
• [RRG] Re: Should the identifier be used as local locator
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: [RRG] Re: Should the identifier be used as local locator
  • From: <louise.burness@bt.com>
• [RRG] Re: Should the identifier be used as local locator
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Re: Should the identifier be used as local locator
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• re: [RRG] IEEE EUI-64 as an Identifier format
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] IEEE EUI-64 as an Identifier format
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: re: [RRG] IEEE EUI-64 as an Identifier format
  • From: "Hongbin Luo" <hbluo@bjtu.edu.cn>
• re: [RRG] Re: Should the identifier be used as local locator
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] IEEE EUI-64 as an Identifier format
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] IEEE EUI-64 as an Identifier format
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] perceived privacy issue
  • From: Peter Sherbin <pesherb@yahoo.com>
• RE: [RRG] IEEE EUI-64 as an Identifier format
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] IEEE EUI-64 as an Identifier format
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] perceived privacy issue
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] IEEE EUI-64 as an Identifier format
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] IEEE EUI-64 as an Identifier format
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Possible Identifier Properties
  • From: HeinerHummel@aol.com
• Re: [RRG] IEEE EUI-64 as an Identifier format
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] IEEE EUI-64 as an Identifier format
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] perceived privacy issue
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] IEEE EUI-64 as an Identifier format
  • From: RJ Atkinson <rja@extremenetworks.com>
• [RRG] perceived privacy issue
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Possible Identifier Properties
  • From: RJ Atkinson <rja@extremenetworks.com>
• RE: [RRG] Re: Should the identifier be used as local locator
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Terminology redux
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Terminology redux
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Terminology redux
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Terminology redux
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] Terminology redux
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Re: Should the identifier be used as local locator
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Peter Sherbin <pesherb@yahoo.com>
• re: [RRG] Re: Should the identifier be used as local locator
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Re: Should the identifier be used as local locator
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Should the identifier be used as local locator
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Should the identifier be used as local locator
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Re: Should the identifier be used as local locator
  • From: Scott Brim <swb@employees.org>
• [RRG] Re: Should the identifier be used as local locator
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• [RRG] Should the identifier be used as local locator
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "Tom Petch" <nwnetworks@dial.pipex.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Robert Bonomi <bonomi@mail.r-bonomi.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: Peter Sherbin <pesherb@yahoo.com>
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: "Tony Li" <tony.li@tony.li>
• Re: lisp-interest archive? [Re: [RRG] Re: LISP-ALT's long path problem again]
  • From: David Meyer <dmm@1-4-5.net>
• lisp-interest archive? [Re: [RRG] Re: LISP-ALT's long path problem again]
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] EXPLISP BOF at the Dublin IETF
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] EXPLISP BOF at the Dublin IETF
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: David Meyer <dmm@1-4-5.net>
• [RRG] Re: LISP-ALT's long path problem again
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] LISP-ALT's long path problem again
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• [RRG] OITRDs & PTRs: "partial deployment" support of packets from non-ITR networks
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] EXPLISP BOF at the Dublin IETF
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Not separate namespaces: Loc-ID-separation, map-encap etc.
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Re: Not separate namespaces: Loc-ID-separation, map-encap etc.
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Re: Not separate namespaces: Loc-ID-separation, map-encap etc.
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: David Williamson <dlw+rrg@tellme.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] Re: Not separate namespaces: Loc-ID-separation, map-encap etc.
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] EXPLISP BOF at the Dublin IETF
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] Not separate namespaces: Loc-ID-separation, map-encap etc.
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Committees vs. small teams, IPv4 fix absolutely required
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Moving forward...
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Moving forward...
  • From: Stephen Sprunk <stephen@sprunk.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: David Conrad <drc@virtualized.org>
• [RRG] Map-encap can & will reduce the cost of multihoming
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "James Kempf" <kempf@docomolabs-usa.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "James Kempf" <kempf@docomolabs-usa.com>
• RE: [RRG] IPv4: how bad, when to fix?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] IPv4: how bad, when to fix?
  • From: "Marcus Brunner" <Brunner@nw.neclab.eu>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: David Conrad <drc@virtualized.org>
• [RRG] Take 2: AA, BB, CC
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] IPv4: how bad, when to fix?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Shane Amante <shane@castlepoint.net>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "James Kempf" <kempf@docomolabs-usa.com>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: HeinerHummel@aol.com
• RE: [RRG] Long term clean-slate only for the RRG?
  • From: "Marcus Brunner" <Brunner@nw.neclab.eu>
• Re: [RRG] Long term clean-slate only for the RRG?
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: HeinerHummel@aol.com
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Conceptual vs. specific - another discussion list?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Long term clean-slate only for the RRG?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: David Williamson <dlw+rrg@tellme.com>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: Dan Jen <jenster@cs.ucla.edu>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] What does "architectural" mean?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] 3 potential consensus questions
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] What do we have consensus on?
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] Moving forward...
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Moving forward...
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Moving forward...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Moving forward...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] What do we have consensus on?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Moving forward...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Moving forward...
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Moving forward...
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] Moving forward...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Moving forward...
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Moving forward...
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Moving forward...
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Moving forward...
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] What do we have consensus on?
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] What do we have consensus on?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] What do we have consensus on?
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Origins of LISP PTRs / Ivip OITRDs
  • From: Robin Whittle <rw@firstpr.com.au>
• [vaf@cisco.com: Re: [RRG] Moving forward...]
  • From: Vince Fuller <vaf@cisco.com>
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Vince Fuller <vaf@cisco.com>
• RE: [RRG] Conceptual vs. specific - another discussion list?
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] Not address but topology aggregation
  • From: HeinerHummel@aol.com
• Re: [RRG] Conceptual vs. specific - another discussion list?
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Conceptual vs. specific - another discussion list?
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] the agenda for Dublin
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Conceptual vs. specific - another discussion list?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Moving forward...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• GSE, Six/One, and Beyond --- Re: [RRG] GSE?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• re: [RRG] Re: address reclamation
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] GSE History
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Re: address reclamation
  • From: Scott Brim <swb@employees.org>
• [RRG] Conceptual vs. specific - another discussion list?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Schedule
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] GSE?
  • From: David Williamson <dlw+rrg@tellme.com>
• Re: [RRG] GSE?
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• re: [RRG] GSE?
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] GSE?
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] GSE?
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Schedule
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: address reclamation
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] GSE?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Tom Vest <tvest@pch.net>
• RE: [RRG] IPv6 immediate benefits to some end-users?
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhapsmoreambitious
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] Re: IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] IPv6 immediate benefits to some end-users?
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: address reclamation
  • From: Jason Schiller <schiller@uu.net>
• Re: [RRG] GSE History
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Re: address reclamation
  • From: Per Heldal <heldal@eml.cc>
• [RRG] Re: address reclamation
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Per Heldal <heldal@eml.cc>
• Re: [RRG] GSE?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Per Heldal <heldal@eml.cc>
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Per Heldal <heldal@eml.cc>
• Re: [RRG] IPv6 immediate benefits to some end-users?
  • From: Jeroen Massar <jeroen@unfix.org>
• [RRG] IPv4/6/ngng or IPv4-map-encap then IPngng
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] IPv6 immediate benefits to some end-users?
  • From: Robin Whittle <rw@firstpr.com.au>
• re: [RRG] GSE?
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] GSE?
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] GSE?
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] GSE?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] GSE History
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhapsmore ambitious
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] GSE?
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] GSE History
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] GSE History
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] GSE History
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] GSE History
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] GSE History
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] GSE History
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] GSE History
  • From: RJ Atkinson <rja@extremenetworks.com>
• RE: [RRG] GSE?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] GSE?
  • From: "Mayutan A." <mayutan.arumaithurai@gmail.com>
• [RRG] GSE?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] NAT-PT and other approaches to IPv6 adoption
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhapsmore ambitious
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] NAT-PT and other approaches to IPv6 adoption
  • From: David Conrad <drc@virtualized.org>
• [RRG] Re: reachability
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Jeroen Massar <jeroen@unfix.org>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: David Conrad <drc@virtualized.org>
• [RRG] NAT-PT and other approaches to IPv6 adoption
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Jeroen Massar <jeroen@unfix.org>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Per Heldal <heldal@eml.cc>
• re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] arguments for map and encap
  • From: Michael Meisel <meisel@cs.ucla.edu>
• re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Dan Jen <jenster@cs.ucla.edu>
• RE: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] reachability
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Robin Whittle <rw@firstpr.com.au>
• re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] reachability
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] reachability
  • From: Bob Hinden <bob.hinden@nokia.com>
• Re: [RRG] Moving forward...
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Moving forward...
  • From: Bob Hinden <bob.hinden@nokia.com>
• Re: [RRG] Moving forward...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward... IPv4 now, IPv6 less urgent and perhaps more ambitious
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Moving forward...
  • From: "Ross Callon" <rcallon@juniper.net>
• [RRG] reachability
  • From: RJ Atkinson <rja@extremenetworks.com>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Tony's proposed statement
  • From: RJ Atkinson <rja@extremenetworks.com>
• Re: [RRG] Moving forward...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Moving forward...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Moving forward...
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Moving forward...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Moving forward...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Moving forward...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Moving forward...
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Moving forward...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward...
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Moving forward...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward...
  • From: Dan Jen <jenster@cs.ucla.edu>
• Re: [RRG] Moving forward...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Moving forward...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Moving forward...
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Moving forward...
  • From: David Williamson <dlw+rrg@tellme.com>
• Re: [RRG] Moving forward...
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Moving forward...
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• RE: [RRG] Moving forward...
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward...
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Moving forward...
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward...
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Moving forward...
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Moving forward...
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Moving forward...
  • From: Scott Brim <swb@employees.org>
• [RRG] Moving forward...
  • From: "Tony Li" <tony.li@tony.li>
• Geographical aggregation, was: Re: [RRG] RRG process clarification
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] CFP ReArch'08
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• [RRG] CFP ReArch'08
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• Re: [RRG] Consensus? 4 points so we can make progress
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? 4 points so we can make progress
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Consensus? 4 points so we can make progress
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? 4 points so we can make progress
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] What do we have consensus on?
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] Consensus? 4 points so we can make progress
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] What do we have consensus on?
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Embedded systems
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] What do we have consensus on?
  • From: Peter Sherbin <pesherb@yahoo.com>
• RE: [RRG] Consensus? 4 points so we can make progress
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Consensus? 4 points so we can make progress
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: "Doing It Right" (was Re: [RRG] Consensus? IPv4 scaling problem ...)
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Embedded systems
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] What do we have consensus on?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: [RRG] Consensus? 4 points so we can make progress
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: "Doing It Right" (was Re: [RRG] Consensus? IPv4 scaling problem ...)
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Consensus? 4 points so we can make progress
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] Consensus? 4 points so we can make progress
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Try again
  • From: HeinerHummel@aol.com
• Re: [RRG] Try again
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: "Doing It Right" (was Re: [RRG] Consensus? IPv4 scaling problem ...)
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Try again
  • From: HeinerHummel@aol.com
• [RRG] Try again
  • From: David Conrad <drc@virtualized.org>
• RE: [RRG] What do we have consensus on?
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: We can't bet the Internet on the imminent adoption of IPv6
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Re: We can't bet the Internet on the imminent adoption of IPv6
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Re: We can't bet the Internet on the imminent adoption of IPv6
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Consensus? 4 points so we can make progress
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Consensus? Scope of "It" in "Doing It Right"
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] We can't bet the Internet on the imminent adoption of IPv6
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Multi-homing & Changing IP address
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: "William Herrin" <bill@herrin.us>
• Re: "Doing It Right" (was Re: [RRG] Consensus? IPv4 scaling problem ...)
  • From: David Conrad <drc@virtualized.org>
• Re: "Doing It Right" (was Re: [RRG] Consensus? IPv4 scaling problem ...)
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: "Doing It Right" (was Re: [RRG] Consensus? IPv4 scaling problem ...)
  • From: David Conrad <drc@virtualized.org>
• RE: "Doing It Right" (was Re: [RRG] Consensus? IPv4 scaling problem ...)
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Peter Sherbin <pesherb@yahoo.com>
• "Doing It Right" (was Re: [RRG] Consensus? IPv4 scaling problem ...)
  • From: David Conrad <drc@virtualized.org>
• [RRG] Consensus? And the elephant in the room
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• RE: [RRG] Consensus? End-user networks need their own portableaddress space
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] What do we have consensus on?
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Consensus? Solution cannot require host upgrades
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] What do we have consensus on?
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Consensus? Users will not adopt solutions which result in "split-system" functionality
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: "Ross Callon" <rcallon@juniper.net>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Consensus? Solution cannot require host upgrades
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Identifiers & Security Associations
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by rel...
  • From: HeinerHummel@aol.com
• Re: [RRG] Consensus? Solution cannot require host upgrades
  • From: Eliot Lear <lear@cisco.com>
• RE: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] RE: What do we have consensus on?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? Solution cannot require host upgrades
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Identifiers & Security Associations
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Identifiers & Security Associations
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Identifiers & Security Associations
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] arguments for map and encap
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] RE: What do we have consensus on?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Consensus? Router-based Translation schemes can only work with duplicate address space
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? Solution cannot require host upgrades
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? End-user networks need their own portable address space
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus? Users will not adopt solutions which result in "split-system" functionality
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Consensus? Router-based Translation schemes can only work with duplicate address space
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Consensus? Solution cannot require host upgrades
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Consensus? End-user networks need their own portable address space
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Consensus? Users will not adopt solutions which result in "split-system" functionality
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Eliot Lear <lear@cisco.com>
• [RRG] Consensus? Router-based Translation schemes can only work with duplicate address space
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Consensus? Solution cannot require host upgrades
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Consensus? IPv4 scaling problem must be solved directly, not by relying on migration to IPv6
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Consensus? End-user networks need their own portable address space
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Consensus? Users will not adopt solutions which result in "split-system" functionality
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Arguments against Transport, Translation & Six/One Router
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Meeting/session in Dublin
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Meeting/session in Dublin
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Re: Arguments against Transport, Translation & Six/One Router
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [RRG] RE: What do we have consensus on?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Meeting/session in Dublin
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] arguments for map and encap
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] arguments for map and encap
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] arguments for map and encap
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] RE: What do we have consensus on?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] arguments for map and encap
  • From: David R Oran <oran@cisco.com>
• RE: [RRG] arguments for map and encap
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] arguments for map and encap
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] arguments for map and encap
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: [RRG] Arguments against Transport...
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] arguments for map and encap
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Arguments against Transport...
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Arguments against Transport, Translation & Six/One Router
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] What do we have consensus on?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] arguments for map and encap
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Arguments against Transport, Translation & Six/One Router
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Feasibility of transport based approaches?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Arguments against Transport, Translation & Six/One Router
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• RE: [RRG] Arguments against Transport, Translation & Six/One Router
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] arguments for map and encap
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Arguments against Transport, Translation & Six/One Router
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] arguments for map and encap
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] arguments for map and encap
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] arguments for map and encap
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Update on Six/One Router + A Call for Your Comments
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] arguments for map and encap
  • From: David R Oran <oran@cisco.com>
• RE: [RRG] arguments for map and encap
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] RRG materials from 71th IETF meeting
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] RRG materials from 71th IETF meeting
  • From: Xiaoming Fu <fu@cs.uni-goettingen.de>
• Re: [RRG] Comments to Draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] RRG materials from 71th IETF meeting
  • From: "Eduardo Ascenco Reis" <eduardo@intron.com.br>
• RE: [RRG] RE: Feasibility of transport based approaches?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Feasibility of transport based approaches?
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• [RRG] RE: Feasibility of transport based approaches?
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] arguments for map and encap
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Comments to Draft-lewis-lisp-interworking
  • From: <hannu.flinck@nsn.com>
• [RRG] Feasibility of transport based approaches?
  • From: <hannu.flinck@nsn.com>
• RE: [RRG] interesting presentations from RIPE
  • From: Per Heldal <heldal@eml.cc>
• re:[RRG] interesting presentations from RIPE
  • From: xuxiaohu 41208 <xuxh@huawei.com>
• Re: [RRG] interesting presentations from RIPE
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] RRG process clarification
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] RRG process clarification
  • From: Jari Arkko <jari.arkko@piuha.net>
• RE: [RRG] interesting presentations from RIPE
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] interesting presentations from RIPE
  • From: "Simon Schuetz" <Simon.Schuetz@nw.neclab.eu>
• RE: [RRG] arguments for map and encap
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] arguments for map and encap
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] RRG process clarification
  • From: RJ Atkinson <rja@extremenetworks.com>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] interesting presentations from RIPE
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] interesting presentations from RIPE
  • From: Danny McPherson <danny@arbor.net>
• Re: [RRG] interesting presentations from RIPE
  • From: ksriram@nist.gov
• [RRG] interesting presentations from RIPE
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] RRG process clarification
  • From: Robert Bonomi <bonomi@mail.r-bonomi.com>
• Re: [RRG] RRG process clarification
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] RRG process clarification
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] RRG process clarification
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] arguments for map and encap
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] RRG process clarification
  • From: xuxiaohu 41208 <xuxh@huawei.com>
• RE: [RRG] arguments for map and encap
  • From: <hannu.flinck@nsn.com>
• [RRG] arguments for map and encap
  • From: Michael Meisel <meisel@cs.ucla.edu>
• RE: [RRG] RRG process clarification
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] RRG process clarification
  • From: Ricardo Oliveira <rveloso@cs.ucla.edu>
• Re: [RRG] RRG process clarification
  • From: Ricardo Oliveira <rveloso@cs.ucla.edu>
• Re: [RRG] RRG process clarification
  • From: HeinerHummel@aol.com
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] RRG process clarification
  • From: HeinerHummel@aol.com
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] RRG process clarification
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] RRG process clarification
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] RRG process clarification
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• RE: [RRG] RRG process clarification
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] RRG process clarification
  • From: David R Oran <oran@cisco.com>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• RE: [RRG] RRG process clarification
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• re: [RRG] RRG process clarification
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] [Fwd: New Version Notification for draft-halpern-rrg-taxonomy-00]
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• RE: [RRG] Which Side to Control Ingress Link Selection?
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: HeinerHummel@aol.com
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• re: [RRG] RRG process clarification
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Taxonomy: 25 questions - updates & web page
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Updates to Ivip analysis and homepage
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] RRG process clarification
  • From: HeinerHummel@aol.com
• Re: [RRG] RRG process clarification
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] IPTM PMTUD with only DF=0 packets
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] SEAL & IPTM: differing goals
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] RRG process clarification
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Path MTU Discovery: a new approach
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] RRG process clarification
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] Routing RG charter
  • From: Dan Jen <jenster@cs.ucla.edu>
• [RRG] Routing RG charter
  • From: RJ Atkinson <rja@extremenetworks.com>
• RE: [RRG] Path MTU Discovery: a new approach
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Path MTU Discovery: a new approach
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Path MTU Discovery: a new approach
  • From: bill@herrin.us (William Herrin)
• [RRG] Newbies: Comparison of NERD, ALT, APT, Ivip & TRRP
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Taxonomy: 25 questions - updates & web page
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] RRG process clarification
  • From: HeinerHummel@aol.com
• RE: [RRG] Path MTU Discovery: a new approach
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] RRG process clarification
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Path MTU Discovery: a new approach
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Solving the Right Problem
  • From: <hannu.flinck@nsn.com>
• RE: [RRG] Which Side to Control Ingress Link Selection?
  • From: <hannu.flinck@nsn.com>
• RE: [RRG] Which Side to Control Ingress Link Selection?
  • From: <hannu.flinck@nsn.com>
• Re: [RRG] RRG process clarification
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] RRG process clarification
  • From: HeinerHummel@aol.com
• RE: [RRG] RRG process clarification
  • From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
• Re: [RRG] RRG process clarification
  • From: Eliot Lear <lear@cisco.com>
• re:Re: [RRG] RRG process clarification
  • From: xuxiaohu 41208 <xuxh@huawei.com>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] RRG process clarification
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] RRG process clarification
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Solving the Right Problem
  • From: Dan Jen <jenster@cs.ucla.edu>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] RRG process clarification
  • From: Lars Eggert <lars.eggert@nokia.com>
• Re: [RRG] RRG process clarification
  • From: Lars Eggert <lars.eggert@nokia.com>
• Re: [RRG] RRG process clarification
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] RRG process clarification
  • From: HeinerHummel@aol.com
• [RRG] complexity metric
  • From: Aaron Falk <falk@bbn.com>
• RE: [RRG] RRG process clarification
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Hosts using routing
  • From: HeinerHummel@aol.com
• Re: [RRG] Hosts using routing
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] RRG process clarification
  • From: Lars Eggert <lars.eggert@nokia.com>
• [RRG] Hosts using routing
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] RRG process clarification
  • From: Peter Sherbin <pesherb@yahoo.com>
• RE: [RRG] Which Side to Control Ingress Link Selection?
  • From: <louise.burness@bt.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] RRG process clarification
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Ivip business models: fast push & OITRDs
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Not moving the problem to the global mapping system
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Not moving the problem to the global mapping system
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: HeinerHummel@aol.com
• [RRG] 答复: [RRG] Which Side to Control Ingress Link Selection?
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] Which Side to Control Ingress Link Selection?
  • From: <hannu.flinck@nsn.com>
• Re: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architectu...
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architectu...
  • From: HeinerHummel@aol.com
• Re: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architectu...
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] updated nerd draft
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Not moving the problem to the global mapping system
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Not moving the problem to the global mapping system
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Moving the problem to the global mapping system - fast-push
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Not moving the problem to the global mapping system
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Re: Not moving the problem to the global mapping system
  • From: Michael Meisel <meisel@cs.ucla.edu>
• [RRG] Not moving the problem to the global mapping system
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Moving the problem to the global mapping system - fast-push
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Question about ITR and ETR deployment
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Moving the problem to the global mapping system - fast-push
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Question about ITR and ETR deployment
  • From: Scott Brim <swb@employees.org>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Moving the problem to the global mapping system
  • From: Michael Meisel <meisel@cs.ucla.edu>
• [RRG] Moving the problem to the global mapping system
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG]
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Question about ITR and ETR deployment
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] What does incremental deployment mean
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] What does incremental deployment mean
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] What does incremental deployment mean
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] What does incremental deployment mean
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Some comments on draft-farinacci-lisp-06
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] Some comments on draft-farinacci-lisp-06
  • From: Roland Bless <bless@tm.uka.de>
• [RRG] RE: SEAL, PMTUD, IPv6 header bloat, header compression
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] RE: Is ISATAP a practical solution? IPv6 adoption
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Question about ITR and ETR deployment
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] simplicity
  • From: Scott Brim <swb@employees.org>
• [RRG] SEAL, PMTUD, IPv6 header bloat, header compression
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] RE: Is ISATAP a practical solution? IPv6 adoption
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] RE: Is ISATAP a practical solution?
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] RE: Is ISATAP a practical solution?
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Some comments on draft-farinacci-lisp-06
  • From: David Meyer <dmm@1-4-5.net>
• [RRG] Some comments on draft-farinacci-lisp-06
  • From: Roland Bless <bless@tm.uka.de>
• Re: [RRG] RE: Is ISATAP a practical solution?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] RE: Is ISATAP a practical solution?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] RE: Is ISATAP a practical solution?
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] Is ISATAP a practical solution?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] What does incremental deployment mean
  • From: David R Oran <oran@cisco.com>
• RE: [RRG] What does incremental deployment mean
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Taxonomy: 25 questions - Heiner Hummel's proposal
  • From: HeinerHummel@aol.com
• Re: [RRG] Taxonomy: 25 questions - Heiner Hummel's proposal
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Taxonomy: 25 questions - Heiner Hummel's proposal
  • From: HeinerHummel@aol.com
• Re: [RRG] simplicity
  • From: "Victor Grishchenko" <victor.grishchenko@gmail.com>
• Re: [RRG] Taxonomy: 25 questions - Heiner Hummel's proposal
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Taxonomy: 25 questions
  • From: HeinerHummel@aol.com
• Re: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architecture Designs"
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Taxonomy: 25 questions
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Question about ITR and ETR deployment
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Re: Taxonomy: 25 questions
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architecture Designs"
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] simplicity
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Taxonomy: 25 questions
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] simplicity
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] simplicity
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Taxonomy: 25 questions
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] What does incremental deployment mean
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] What does incremental deployment mean
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] What does incremental deployment mean
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] LISP-ALT: coordination between ITRs and/or ETRs?
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] What does incremental deployment mean
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Question about ITR and ETR deployment
  • From: Scott Brim <swb@employees.org>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architectu...
  • From: <louise.burness@bt.com>
• Re: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architectu...
  • From: HeinerHummel@aol.com
• RE: [RRG] What does incremental deployment mean
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] What does incremental deployment mean
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] More discussion please: mapping churn
  • From: "William Herrin" <bill@herrin.us>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Question about ITR and ETR deployment
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Question about ITR and ETR deployment
  • From: "Gang Chen" <phdgang@gmail.com>
• RE: [RRG] More discussion please: mapping churn
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] More discussion please: mapping churn
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architecture Designs"
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] What does incremental deployment mean
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] What does incremental deployment mean
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] What does incremental deployment mean
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] new draft on " A Taxonomy for New Routing and Addressing Architecture Designs"
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] More discussion please: mapping churn
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] More discussion please: mapping churn
  • From: Eliot Lear <lear@cisco.com>
• [RRG] More discussion please: mapping churn
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] new draft on " A Taxonomy for New Routing and Addressing Architecture Designs"
  • From: Scott Brim <swb@employees.org>
• [RRG] What's research got to do with it
  • From: HeinerHummel@aol.com
• RE: [RRG] What does incremental deployment mean
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] What does incremental deployment mean
  • From: Pekka Savola <pekkas@netcore.fi>
• [RRG] Some updates to the HRA proposal
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] Trying to find a path forwards
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Trying to find a path forwards
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] What does incremental deployment mean
  • From: Marshall Eubanks <tme@multicasttech.com>
• re: [RRG] map change due to a path failure?
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] map change due to a path failure?
  • From: Eliot Lear <lear@cisco.com>
• RE: [RRG] What does incremental deployment mean
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] On "jack-down" models
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] On "jack-down" models
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] What does incremental deployment mean
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] On "jack-down" models
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] On "jack-down" models
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] On "jack-down" models
  • From: Pekka Nikander <pekka.nikander@nomadiclab.com>
• Re: [RRG] On "jack-down" models
  • From: Pekka Nikander <pekka.nikander@nomadiclab.com>
• RE: [RRG] On "jack-down" models
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] On "jack-down" models
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Mitigating the Downsides of NAT'ing
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• re: [RRG] map change due to a path failure?
  • From: Xu Xiaohu <xuxh@huawei.com>
• [RRG] Trying to find a path forwards
  • From: Randall Atkinson <rja@extremenetworks.com>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] What does incremental deployment mean
  • From: HeinerHummel@aol.com
• Re: [RRG] map change due to a path failure?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] map change due to a path failure?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: Re: [RRG] map change due to a path failure?
  • From: "Hongbin Luo" <hbluo@bjtu.edu.cn>
• Re: [RRG] map change due to a path failure?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] map change due to a path failure?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] map change due to a path failure?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] What does incremental deployment mean
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] map change due to a path failure?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] map change due to a path failure?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Re: Knee jerking
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Mitigating the Downsides of NAT'ing
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Consensus check: mapping granularity
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Re: Knee jerking
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Knee jerking
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] What does incremental deployment mean
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] What does incremental deployment mean
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] What does incremental deployment mean
  • From: Dino Farinacci <dino@cisco.com>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] What does incremental deployment mean
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Consensus check: mapping granularity
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] What does incremental deployment mean
  • From: Dino Farinacci <dino@cisco.com>
• re: [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] What does incremental deployment mean
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] What does incremental deployment mean
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• re: [RRG] Consensus check: mapping granularity
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Re: map change due to a path failure?
  • From: "William Herrin" <bill@herrin.us>
• re: [RRG] map change due to a path failure?
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] map change due to a path failure?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Re: map change due to a path failure?
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• [RRG] Dynamis of the mapping function
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Mitigating the Downsides of NAT'ing
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Mark Prior <mrp@mrp.net>
• Re: [RRG] Re: map change due to a path failure?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• [RRG] Re:
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Re: map change due to a path failure?
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Lightweight multihoming with TTRs, DSL, HFC, WiMax etc.
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Re: map change due to a path failure?
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Concerns about the RRG process ... & how not to design an airliner
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Re: map change due to a path failure?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] map change due to a path failure?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Concerns about the RRG process ... & how not to design an airliner
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Concerns about the RRG process ... & how not to design an airliner
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Concerns about the RRG process ... & how not to design an airliner
  • From: Eliot Lear <lear@cisco.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
• Re: [RRG] Hosts, DFZ, purity & incremental deployment
  • From: HeinerHummel@aol.com
• Re: [RRG] Hosts, DFZ, purity & incremental deployment
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Concerns about the RRG process ... & how not to design an airliner
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus check: mapping granularity
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• Re: [RRG] What does incremental deployment mean
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• Re: [RRG] Hosts, DFZ, purity & incremental deployment
  • From: "Stephen Sprunk" <stephen@sprunk.org>
• [RRG] Dynamics of the mapping function
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG]
  • From: "William Herrin" <bill@herrin.us>
• [RRG]
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] What does incremental deployment mean??
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] What does incremental deployment mean - 2 questions
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Consensus check: mapping granularity
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] What does incremental deployment mean - 2 questions
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Text proposal: mapping granularity
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Consensus check: mapping granularity
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Consensus check: mapping granularity
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Consensus check: mapping granularity
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Text proposal: mapping granularity
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Text proposal: mapping granularity
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Text proposal: mapping granularity
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Text proposal: mapping granularity
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Consensus check: mapping granularity
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Consensus check: mapping granularity
  • From: HeinerHummel@aol.com
• Re: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Mitigating the Downsides of NAT'ing
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Mobility, update rates & charging per update
  • From: David R Oran <oran@cisco.com>
• RE: [RRG] What does incremental deployment mean - 2 questions
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] What does incremental deployment mean - 2 questions
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Text proposal: mapping granularity
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Text proposal: mapping granularity
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• [RRG] Characterizing incremental deployments
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] What does incremental deployment mean - 2 questions
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Ivip's "Open ITRs in the DFZ" (OITRDs), formerly "Anycast ITRs in the core"
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Text proposal: mapping granularity
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Text proposal: mapping granularity
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] What does incremental deployment mean - 2 questions
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Text proposal: mapping granularity
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Consensus check: mapping granularity
  • From: Sheng Jiang <shengjiang@huawei.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] What does incremental deployment mean - 2 questions
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Text proposal: mapping granularity
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] on draft-meyer-lisp-eid-block-00.txt
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Consensus check: mapping granularity
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] on draft-meyer-lisp-eid-block-00.txt
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: HeinerHummel@aol.com
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Consensus check: mapping granularity
  • From: HeinerHummel@aol.com
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Assumptions and mapping tools
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] on draft-meyer-lisp-eid-block-00.txt
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] on draft-meyer-lisp-eid-block-00.txt
  • From: Dino Farinacci <dino@cisco.com>
• RE: [RRG] Consensus check: mapping granularity
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] on draft-meyer-lisp-eid-block-00.txt
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: David Meyer <dmm@1-4-5.net>
• RE: [RRG] What does incremental deployment mean - 2 questions
  • From: <philip.eardley@bt.com>
• Re: [RRG] Assumptions and mapping tools
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] Consensus check: mapping granularity
  • From: Scott Brim <swb@employees.org>
• [RRG] Assumptions and mapping tools
  • From: <hannu.flinck@nsn.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Consensus check: mapping granularity
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] Consensus check: mapping granularity
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] Consensus check: mapping granularity
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Consensus check: mapping granularity
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Consensus check: mapping granularity
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Consensus check: mapping granularity
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Consensus check: mapping granularity
  • From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
• re: [RRG] Consensus check: mapping granularity
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Consensus check: mapping granularity
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• re: [RRG] Consensus check: mapping granularity
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Consensus check: mapping granularity
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: <hannu.flinck@nsn.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Consensus check: mapping granularity
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Consensus check: mapping granularity
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] RRG shouldn't try to directly address mobility, including qualifying mobility attributes
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Hosts, DFZ, purity & incremental deployment
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] mapping "issues" list from this morning
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] RRG shouldn't try to directly address mobility, including qualifying mobility attributes
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] RRG shouldn't try to directly address mobility, including qualifying mobility attributes
  • From: "Fleischman, Eric" <eric.fleischman@boeing.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Mobility, update rates & charging per update
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] Meeting Minutes from March 11 and 14
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: [RRG] Mobility, update rates & charging per update
  • From: Randall Atkinson <rja@extremenetworks.com>
• re: [RRG] Mobility, update rates & charging per update
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] Which Side to Control Ingress Link Selection?
  • From: <hannu.flinck@nsn.com>
• Re: [RRG] mapping "issues" list from this morning
  • From: dimitri papadimitriou <dpapadimitriou@psg.com>
• RE: [RRG] On "jack-down" models
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] LISP next steps
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Mobility, update rates & charging per update
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] LISP next steps
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] mapping "issues" list from this morning
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Mobility, update rates & charging per update
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] On "jack-down" models
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Pierre Francois <pierre.francois@uclouvain.be>
• Re: [RRG] On "jack-down" models - independent namespaces
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] What does incremental deployment mean - 2 questions
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Why delaying initial packets matters
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Re: DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Re: DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Six/One Implementation
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] What does incremental deployment mean - 2 questions
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] On "jack-down" models
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] On "jack-down" models
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] What does incremental deployment mean
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Mobility, update rates & charging per update
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] On "jack-down" models - independent namespaces
  • From: HeinerHummel@aol.com
• RE: [RRG] On "jack-down" models - independent namespaces
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] What does incremental deployment mean
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] On "jack-down" models
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] What does incremental deployment mean
  • From: HeinerHummel@aol.com
• Re: [RRG] LISP next steps
  • From: Vince Fuller <vaf@cisco.com>
• Re: [RRG] LISP next steps
  • From: Vince Fuller <vaf@cisco.com>
• Re: [RRG] Mobility, update rates & charging per update
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Mobility, update rates & charging per update
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• [RRG] Mobility, update rates & charging per update
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] What does incremental deployment mean
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] re: Some concern about the flat label as identifier
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] On "jack-down" models - independent namespaces
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Reactivating the RAM list?
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Hosts, DFZ, purity & incremental deployment
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Reactivating the RAM list?
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Hosts, DFZ, purity & incremental deployment
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] LISP next steps
  • From: Randall Atkinson <rja@extremenetworks.com>
• [RRG] Node Identity, PKIs, and bindings between the two
  • From: Randall Atkinson <rja@extremenetworks.com>
• [RRG] re: Some concern about the flat label as identifier
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Reactivating the RAM list?
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] Re: Some concern about the flat label as identifier
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [RRG] Some concern about the flat label as identifier
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] On "jack-down" models
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] On "jack-down" models
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Hosts, DFZ, purity & incremental deployment
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Reactivating the RAM list?
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] LISP next steps
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] On "jack-down" models
  • From: Pekka Nikander <pekka.nikander@nomadiclab.com>
• [RRG] Hosts, DFZ, purity & incremental deployment
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] On "jack-down" models
  • From: Scott Brim <swb@employees.org>
• [RRG] Reactivating the RAM list?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] LISP next steps
  • From: Vince Fuller <vaf@cisco.com>
• Re: [RRG] On "jack-down" models
  • From: Pekka Nikander <pekka.nikander@nomadiclab.com>
• RE: [RRG] On "jack-down" models
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] On "jack-down" models
  • From: David R Oran <oran@cisco.com>
• Re: [RRG] On "jack-down" models
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] LISP next steps
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] On "jack-down" models
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] LISP next steps
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] LISP next steps
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] On "jack-down" models
  • From: "Victor Grishchenko" <victor.grishchenko@gmail.com>
• Re: [RRG] LISP next steps
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] On "jack-down" models
  • From: HeinerHummel@aol.com
• Re: [RRG] On "jack-down" models
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] LISP next steps
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] On "jack-down" models
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] LISP next steps
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] mapping "issues" list from this morning
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] LISP next steps
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] LISP next steps
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] mapping "issues" list from this morning
  • From: dimitri papadimitriou <dpapadimitriou@psg.com>
• Re: [RRG] LISP next steps
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] LISP next steps
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: HeinerHummel@aol.com
• [RRG] Newbies: Unofficial guide to LISP
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] LISP next steps
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Six/One Implementation
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] LISP next steps
  • From: David Meyer <dmm@1-4-5.net>
• [RRG] Six/One Implementation
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: [RRG] Point about EID prefixes as transition indication
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] Point about EID prefixes as transition indication
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] Slides IETF-71
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] Slides IETF-71
  • From: Roland Bless <bless@tm.uka.de>
• Re: [RRG] Generic requirements on mapping mechanisms
  • From: Lars Westberg <Lars.westberg@ericsson.com>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility - easy explanation
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Generic requirements on mapping mechanisms
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Re: Supposed impossibility of scaling for mobility - easy explanation
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: Scott Brim <swb@employees.org>
• [RRG] Re: Supposed impossibility of scaling for mobility - easy explanation
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Re: Supposed impossibility of scaling for mobility
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: <hannu.flinck@nsn.com>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] clarification of locators, IDs, IP addresses
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: <louise.burness@bt.com>
• RE: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: <louise.burness@bt.com>
• RE: [RRG] clarification of locators, IDs, IP addresses
  • From: "Lars Westberg" <lars.westberg@ericsson.com>
• [RRG] Notify = "proactive" updates; flexible placement of full db ITRs & query servers
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Supposed impossibility of scaling for mobility
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Generic requirements on mapping mechanisms
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: <hannu.flinck@nsn.com>
• [RRG] Anyone want to co-author & present an Ivip paper at ACM MobiArch, Seattle, in August?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Supposed impossibility of scaling for mobility
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] APT security and other matters
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "Tony Li" <tony.li@tony.li>
• Re: Cache size [Re: [RRG] Happiness; lack thereof]
  • From: Luigi Iannone <Luigi.Iannone@uclouvain.be>
• [RRG] APT security and other matters
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: Supposed impossibility of scaling for mobility
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• Re: [RRG] APT: no need for islands?
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Xu Xiaohu <xuxh@huawei.com>
• [RRG] Supposed impossibility of scaling for mobility
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Robin Whittle <rw@firstpr.com.au>
• What is the big-O picture? (was: [RRG] Happiness; lack thereof)
  • From: "Victor Grishchenko" <victor.grishchenko@gmail.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Cache size [Re: [RRG] Happiness; lack thereof]
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] APT: no need for islands?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Ricardo Oliveira <rveloso@CS.UCLA.EDU>
• RE: [RRG] Generic requirements on mapping mechanisms
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Generic requirements on mapping mechanisms
  • From: Scott Brim <swb@employees.org>
• [RRG] mapping "issues" list from this morning
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Generic requirements on mapping mechanisms
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Generic requirements on mapping mechanisms
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Generic requirements on mapping mechanisms
  • From: Scott Brim <swb@employees.org>
• [RRG]
  • From: "Tony Li" <tony.li@tony.li>
• [RRG] clarification of locators, IDs, IP addresses
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Generic requirements on mapping mechanisms
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• RE: [RRG] Re: LISP PMTU & fragmentation problems
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Re: LISP PMTU & fragmentation problems
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Xu Xiaohu <xuxh@huawei.com>
• RE: [RRG] yetAnotherProposal: AS-number forwarding
  • From: "Lars Westberg" <lars.westberg@ericsson.com>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: "Juan Jose Adan" <juanjose.adan@gmail.com>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Ricardo Oliveira <rveloso@cs.ucla.edu>
• [RRG] DEADLINE EXTENDED to March 31: MobiArch'08 - ACM SIGCOMM 2008 workshop
  • From: Xiaoming Fu <fu@cs.uni-goettingen.de>
• re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Peter Sherbin <pesherb@yahoo.com>
• RE: [RRG] Re: LISP PMTU & fragmentation problems
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Re: LISP PMTU & fragmentation problems
  • From: Scott Brim <swb@employees.org>
• re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Xu Xiaohu <xuxh@huawei.com>
• [RRG] RE: LISP PMTU & fragmentation problems
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] Re: LISP PMTU & fragmentation problems
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] Mapping model discussion - push, pull, hybrids and notify
  • From: Robin Whittle <rw@firstpr.com.au>
• re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Geoff Huston <gih@apnic.net>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: "Juan Jose Adan" <juanjose.adan@gmail.com>
• RE: [RRG] yetAnotherProposal: AS-number forwarding
  • From: "Lars Westberg" <lars.westberg@ericsson.com>
• re: [RRG] Happiness; lack thereof
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] yetAnotherProposal: AS-number forwarding
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Using a DHT to map identifiers onto locators
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] yetAnotherProposal: AS-number forwarding
  • From: "Lars Westberg" <lars.westberg@ericsson.com>
• [RRG] Re: LISP gleaning looks insecure and therefore unusable
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: LISP PMTU & fragmentation problems
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: LISP PMTU & fragmentation problems
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Re: LISP PMTU & fragmentation problems
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Re: LISP PMTU & fragmentation problems
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [RRG] Re: DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [RRG] Re: LISP PMTU & fragmentation problems
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Re: LISP gleaning looks insecure and therefore unusable
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Happiness; lack thereof
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Are we solving the wrong problem?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Happiness; lack thereof
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] comments on IVIP Conceptual Summary and Analysis documents
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Agenda
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Happiness; lack thereof
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Happiness; lack thereof
  • From: "William Herrin" <bill@herrin.us>
• [RRG] LISP PMTU & fragmentation problems
  • From: Robin Whittle <rw@firstpr.com.au>
• re: [RRG] Happiness; lack thereof
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] LISP gleaning looks insecure and therefore unusable
  • From: Robin Whittle <rw@firstpr.com.au>
• re: [RRG] LISP gleaning looks insecure and therefore unusable
  • From: Xu Xiaohu <xuxh@huawei.com>
• [RRG] LISP gleaning looks insecure and therefore unusable
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] 答复: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Bengt Ahlgren <bengta@sics.se>
• [RRG] 答复: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Happiness; lack thereof
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• [RRG] APT summary update on RRG wiki
  • From: Dan Jen <jenster@cs.ucla.edu>
• RE: [RRG] Comments on draft-lewis-lisp-interworking
  • From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Happiness; lack thereof
  • From: "Victor Grishchenko" <victor.grishchenko@gmail.com>
• Re: [RRG] Happiness; lack thereof
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] a backwards compatible FIB scaling approach
  • From: Paul Francis <francis@cs.cornell.edu>
• Re: [RRG] Happiness; lack thereof
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] comments on IVIP Conceptual Summary and Analysis documents
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Happiness; lack thereof
  • From: Michael Meisel <meisel@cs.ucla.edu>
• [RRG] Happiness; lack thereof
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] a backwards compatible FIB scaling approach
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Are we solving the wrong problem?
  • From: Scott Brim <swb@employees.org>
• [RRG] Browsing Proposal Summaries
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: <philip.eardley@bt.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] comments on IVIP Conceptual Summary and Analysis documents
  • From: <philip.eardley@bt.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Are we solving the wrong problem?
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] a backwards compatible FIB scaling approach
  • From: Paul Francis <francis@cs.cornell.edu>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Bengt Ahlgren <bengta@sics.se>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Which Side to Control Ingress Link Selection?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Are we solving the wrong problem?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] Which Side to Control Ingress Link Selection?
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• [RRG] Request for presentation slot: APT incremental deployment
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] Are we solving the wrong problem?
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• [RRG] Policy routing
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Are we solving the wrong problem?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Are we solving the wrong problem?
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• Re: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Comments on draft-lewis-lisp-interworking
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Are we solving the wrong problem?
  • From: Pekka Nikander <pekka.nikander@nomadiclab.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: Pekka Nikander <pekka.nikander@nomadiclab.com>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] For Newbies: ITR, ETR, DFZ, TE, ITRD & other terms explained
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Process proposal: Conceptual Summary and Analysis documents
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Are we solving the wrong problem?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Are we solving the wrong problem?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Are we solving the wrong problem?
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: <philip.eardley@bt.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
• [RRG] Inherit some benefits from GIRO into HRA
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: Marshall Eubanks <tme@multicasttech.com>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Are we solving the wrong problem?
  • From: Pekka Nikander <pekka.nikander@nomadiclab.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Process proposal: Conceptual Summary and Analysis documents
  • From: "Tony Li" <tony.li@tony.li>
• RE: [RRG] Are we solving the wrong problem?
  • From: "Tony Li" <tony.li@tony.li>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: Scott Brim <swb@employees.org>
• [RRG] Comments on draft-lewis-lisp-interworking
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Why delaying initial packets matters
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Process proposal: Conceptual Summary and Analysis documents
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] V6DH - IPv6 Dual-Homing
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] V6DH - IPv6 Dual-Homing
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• [RRG] V6DH - IPv6 Dual-Homing
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Are we solving the wrong problem?
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• Re: [RRG] Are we solving the wrong problem?
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• Re: [RRG] Are we solving the wrong problem?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Scott Brim <swb@employees.org>
• re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Are we solving the wrong problem?
  • From: Jari Arkko <jari.arkko@piuha.net>
• RE: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: <philip.eardley@bt.com>
• [RRG] Loc/id split using the data link layer
  • From: "Victor Grishchenko" <victor.grishchenko@gmail.com>
• Re: [RRG] Traffic engineering
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Reminder: Conceptual Summary and Analysis documents due tomorrow
  • From: Brian Dickson <briand@ca.afilias.info>
• [RRG] Traffic engineering
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• RE: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] Reminder: Conceptual Summary and Analysis documents due tomorrow
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] On guaranteeing that route/map state changes propagate
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] NTP and various proposals.
  • From: Markus Stenberg <mstenber@cisco.com>
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] How to Incrementally Deploy APT
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] How to Incrementally Deploy APT
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] NTP and various proposals.
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] NTP and various proposals.
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] NTP and various proposals.
  • From: "William Herrin" <bill@herrin.us>
• [RRG] ID draft-farinacci-lisp-06.txt available
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] NTP and various proposals.
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] NTP and various proposals.
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] Using a DHT to map identifiers onto locators
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] getting rid of longest match
  • From: Per Heldal <heldal@eml.cc>
• Re: [RRG] NTP and various proposals.
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] NTP and various proposals.
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Push vs pull vs hybrid, was: Re: [RRG] Mobility considerations in proposal evaluation
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Re: TRRP's micronet length specification?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] NTP and various proposals.
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: "William Herrin" <bill@herrin.us>
• Push vs pull vs hybrid, was: Re: [RRG] Mobility considerations in proposal evaluation
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Scaling, Mobility & 228 mapping changes a second
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] Scaling, Mobility & 228 mapping changes a second
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: TRRP's micronet length specification?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Scaling: ad-hoc to unified or unified from the start?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] getting rid of longest match
  • From: sandy@tislabs.com (Sandy Murphy)
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] getting rid of longest match
  • From: Jason Schiller <schiller@uu.net>
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Why delaying initial packets matters
  • From: "William Herrin" <bill@herrin.us>
• [RRG] ILNP Concept of Operations
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Deadline in 3 weeks - MobiArch'08 - ACM SIGCOMM workshop
  • From: Eggert Lars (Nokia-NRC/Helsinki) <lars.eggert@nokia.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• [RRG] DNS Map: Mapping Resolution Combining Pull/Push Advantages
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Mobility considerations in proposal evaluation
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] NTP and various proposals.
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] NTP and various proposals.
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] NTP and various proposals.
  • From: Tony Li <tli@cisco.com>
• [RRG] Re: TRRP Waypoint Routers
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] getting rid of longest match
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] NTP and various proposals.
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] getting rid of longest match
  • From: Danny McPherson <danny@arbor.net>
• Re: [RRG] getting rid of longest match
  • From: Tony Li <tony.li@tony.li>
• Re: [RRG] getting rid of longest match
  • From: Danny McPherson <danny@arbor.net>
• Re: [RRG] Process proposal: Conceptual Summary and Analysis documents
  • From: Tony Li <tony.li@tony.li>
• [RRG] NTP and various proposals.
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Why delaying initial packets matters
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Re: Security of TRRP mapping replies
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Process proposal: Conceptual Summary and Analysis documents
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] getting rid of longest match
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] Re: Security of TRRP mapping replies
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] getting rid of longest match
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] getting rid of longest match
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] getting rid of longest match
  • From: Tony Li <tli@cisco.com>
• [RRG] getting rid of longest match
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Process proposal: Conceptual Summary and Analysis documents
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• [RRG] Re: TRRP's micronet length specification?
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Re: Delays inherent in TRRP's DNS-like lookup?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Future mapping DB size, small micronets/EIDs
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] TRRP's micronet length specification?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Security of TRRP mapping replies
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Re: TRRP Waypoint Routers
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Future mapping DB size, small micronets/EIDs
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Re: Delays inherent in TRRP's DNS-like lookup?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] How to Incrementally Deploy APT
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] How to Incrementally Deploy APT
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] How to Incrementally Deploy APT
  • From: Dan Jen <jenster@CS.UCLA.EDU>
• Re: [RRG] How to Incrementally Deploy APT
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] DNS down vs Network down
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] How to Incrementally Deploy APT
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] How to Incrementally Deploy APT
  • From: Michael Meisel <meisel@cs.ucla.edu>
• Re: [RRG] DNS down vs Network down
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Re: Delays inherent in TRRP's DNS-like lookup?
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Re: TRRP Waypoint Routers
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] DNS down vs Network down
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] DNS down vs Network down
  • From: Randall Atkinson <rja@extremenetworks.com>
• [RRG] TRRP Waypoint Routers
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Delays inherent in TRRP's DNS-like lookup?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Mobile robustness via layer 7, or multiple tunnels to TTRs
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] How to Incrementally Deploy APT
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] How to Incrementally Deploy APT
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Re: The Map-Encap "third party" problem
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Re: TRRP implementation path concerns
  • From: "William Herrin" <bill@herrin.us>
• [RRG] How to Incrementally Deploy APT
  • From: Dan Jen <jenster@CS.UCLA.EDU>
• [RRG] Re: transport relying on DNS
  • From: "William Herrin" <bill@herrin.us>
• re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Brian Dickson <briand@ca.afilias.info>
• [RRG] The Map-Encap "third party" problem
  • From: Brian Dickson <briand@ca.afilias.info>
• [RRG] TRRP implementation path concerns
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Future mapping DB size, small micronets/EIDs
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] transport relying on DNS
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Mobility frequency
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Future mapping DB size, small micronets/EIDs
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] Re: Delays inherent in TRRP's DNS-like lookup?
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Map-encap space only for small end-users? PI space prices
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Mobility frequency
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Hosts modified so DNS lookup also gives mapping to ITR?
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Mobility frequency
  • From: <hannu.flinck@nsn.com>
• [RRG] Delays inherent in TRRP's DNS-like lookup?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: David Meyer <dmm@1-4-5.net>
• [RRG] Mobility considerations in proposal evaluation
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Mobility frequency
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "Simon Schuetz" <Simon.Schuetz@nw.neclab.eu>
• RE: [RRG] Mobility frequency
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Mobility frequency
  • From: Eliot Lear <lear@cisco.com>
• [RRG] Mobility frequency
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: Pekka Nikander <pekka.nikander@nomadiclab.com>
• Re: [RRG] Traffic Engineering scenarios
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• re: [RRG] Re: Why not take address depletion issue into account
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: "William Herrin" <bill@herrin.us>
• re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Authentication of authority to control mapping
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Authentication of authority to control mapping
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Future mapping DB size, small micronets/EIDs
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Authentication of authority to control mapping
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Traffic Engineering scenarios
  • From: Jason Schiller <schiller@uu.net>
• Re: [RRG] Path Hash proposal
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Re: Map-encap space for "server" vs. "client" end-users?
  • From: "William Herrin" <bill@herrin.us>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Evolutionary Possibilities - host MH/portability, IPv4 address depletion
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Randall Atkinson <rja@extremenetworks.com>
• [RRG] Re: Why not take address depletion issue into account
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Re: Map-encap space for "server" vs. "client" end-users?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Sheng Jiang <shengjiang@huawei.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: "Victor Grishchenko" <victor.grishchenko@gmail.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
• Re: [RRG] Evolutionary Possibilities
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Evolutionary Possibilities
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Path Hash proposal
  • From: Elwyn Davies <elwynd@dial.pipex.com>
• Re: [RRG] Benchmark scenario for modeling
  • From: "K. Sriram" <ksriram@nist.gov>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Path Hash proposal
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• RE: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
• RE: [RRG] Path Hash proposal
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Traffic Engineering scenarios
  • From: Randall Atkinson <rja@extremenetworks.com>
• [RRG] New draft on LISP implementation
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Path Hash proposal
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Traffic Engineering scenarios
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• RE: [RRG] Prototyping systems
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Path Hash proposal
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Why delaying initial packets matters
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Why delaying initial packets matters
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Are we solving the wrong problem?
  • From: Dow Street <dow.street@linquest.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: Elwyn Davies <elwynd@dial.pipex.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Traffic Engineering scenarios
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Are we solving the wrong problem?
  • From: Randall Atkinson <rja@extremenetworks.com>
• [RRG] Are host-stack modifications allowed or disallowed ?
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Why delaying initial packets matters
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Why delaying initial packets matters
  • From: Randall Atkinson <rja@extremenetworks.com>
• RE: [RRG] Are we solving the wrong problem?
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Why delaying initial packets matters - complex web pages & real-time P2P
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Are we solving the wrong problem?
  • From: David Williamson <dlw+rrg@tellme.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
• [RRG] Ivip Fast Push ID & 8 page Conceptual Summary and Analysis
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Are we solving the wrong problem?
  • From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
• Re: [RRG] Why delaying initial packets matters
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Why delaying initial packets matters
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Are we solving the wrong problem?
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: Geoff Huston <gih@apnic.net>
• re: [RRG] Why not take address depletion issue into account
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Why not take address depletion issue into account
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Lars Eggert <lars.eggert@nokia.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Benchmark scenario for modeling
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Are we solving the wrong problem?
  • From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
• Re: [RRG] Are we solving the wrong problem?
  • From: Brian Dickson <briand@ca.afilias.info>
• [RRG] Are we solving the wrong problem?
  • From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
• [RRG] Benchmark scenario for modeling
  • From: ksriram@nist.gov
• re: [RRG] Why not take address depletion issue into account
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Evolutionary Possibilities
  • From: Jari Arkko <jari.arkko@piuha.net>
• [RRG] New routing and addressing proposal added to the RRG wiki
  • From: "Anders Eriksson E" <anders.e.eriksson@ericsson.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Lars Eggert <lars.eggert@nokia.com>
• [RRG] new draft
  • From: <louise.burness@bt.com>
• Re: [RRG] Evolutionary Possibilities
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Why not take address depletion issue into account
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Why not take address depletion issue into account
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Stig Venaas <stig.venaas@uninett.no>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Evolutionary Possibilities - host MH/portability, IPv4 address depletion
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Evolutionary Possibilities
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Evolutionary Possibilities
  • From: Tony Li <tli@cisco.com>
• RE: [RRG] Evolutionary Possibilities
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Evolutionary Possibilities
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Re: Map-encap space for "server" vs. "client" end-users?
  • From: "William Herrin" <bill@herrin.us>
• [RRG] Map-encap space for "server" vs. "client" end-users?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Why delaying initial packets matters - complex web pages & real-time P2P
  • From: "William Herrin" <bill@herrin.us>
• Re: [RRG] Why delaying initial packets matters - complex web pages & real-time P2P
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Why delaying initial packets matters
  • From: Stig Venaas <stig.venaas@uninett.no>
• Re: [RRG] Why delaying initial packets matters
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Why delaying initial packets matters
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Why delaying initial packets matters
  • From: Lars Eggert <lars.eggert@nokia.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Stig Venaas <stig.venaas@uninett.no>
• Re: [RRG] Why delaying initial packets matters
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Evolutionary Possibilities
  • From: Randall Atkinson <rja@extremenetworks.com>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Why delaying initial packets matters
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Why delaying initial packets matters
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Why delaying initial packets matters
  • From: Lars Eggert <lars.eggert@nokia.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Host changes & user costs of adopting map-encap addresses
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Host changes & user costs of adopting map-encap addresses
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] Why delaying initial packets matters
  • From: Lars Eggert <lars.eggert@nokia.com>
• [RRG] Host changes & user costs of adopting map-encap addresses
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Subnetwork Encapsulation and Adaptation Layer (SEAL)
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Why delaying initial packets matters
  • From: HeinerHummel@aol.com
• Re: [RRG] Why delaying initial packets matters
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Why delaying initial packets matters
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] Why delaying initial packets matters
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Why delaying initial packets matters
  • From: Lars Eggert <lars.eggert@nokia.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Stig Venaas <stig.venaas@uninett.no>
• Re: [RRG] Why delaying initial packets matters
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: [RRG] Subnetwork Encapsulation and Adaptation Layer (SEAL)
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: Lars Eggert <lars.eggert@nokia.com>
• [RRG] Subnetwork Encapsulation and Adaptation Layer (SEAL)
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] Why delaying initial packets matters
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Lars Eggert <lars.eggert@nokia.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Stig Venaas <stig.venaas@uninett.no>
• [RRG] Agenda items?
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Marshall Eubanks <tme@multicasttech.com>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: Aggregation Implies Provider Dependence // Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] RRG session schedule at IETF 71
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: Aggregation Implies Provider Dependence // Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Why delaying initial packets matters
  • From: Marshall Eubanks <tme@multicasttech.com>
• [RRG] Meeting in Philly
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] Re: Aggregation Implies Provider Dependence (LISP-ALT) & Ivip dependencies too
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Why delaying initial packets matters
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• RE: [RRG] Why delaying initial packets matters
  • From: <louise.burness@bt.com>
• [RRG] Re: Aggregation Implies Provider Dependence (LISP-ALT) & Ivip dependencies too
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Why delaying initial packets matters
  • From: Tony Li <tli@cisco.com>
• Re: Aggregation Implies Provider Dependence // Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: "Joel M. Halpern" <jmh@joelhalpern.com>
• RE: [RRG] Why delaying initial packets matters
  • From: <hannu.flinck@nsn.com>
• Re: Aggregation Implies Provider Dependence // Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] Why delaying initial packets matters
  • From: Stig Venaas <stig.venaas@uninett.no>
• Re: [RRG] Why delaying initial packets matters
  • From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
• Re: [RRG] Why delaying initial packets matters
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Large companies with PI, small with map-encap space?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Why delaying initial packets matters
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Why delaying initial packets matters
  • From: Kevin Loch <kloch@kl.net>
• [RRG] Why delaying initial packets matters
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] MPLS with different types of mapping
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] MPLS with different types of mapping
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] Re: Aggregation Implies Provider Dependence (LISP-ALT) & Ivip dependencies too
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] MPLS with different types of mapping
  • From: Robert Raszuk <raszuk@juniper.net>
• [RRG] MPLS with different types of mapping
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• [RRG] Re: Aggregation Implies Provider Dependence (LISP-ALT) & Ivip dependencies too
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Tradeoff between anycast and tree-hierarchy
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Response from the LISP-ALT team soon?
  • From: Robin Whittle <rw@firstpr.com.au>
• RE: Aggregation Implies Provider Dependence // Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: <hannu.flinck@nsn.com>
• [RRG] FW: [manet] SEAL (was: DPD for IPv4 MANETs)
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: Aggregation Implies Provider Dependence // Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: Aggregation Implies Provider Dependence // Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Eliot Lear <lear@cisco.com>
• Aggregation Implies Provider Dependence // Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Xu Xiaohu <xuxh@huawei.com>
• [RRG] Tradeoff between anycast and tree-hierarchy
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Messages not getting to the List?
  • From: Tony Li <tli@cisco.com>
• [RRG] Messages not getting to the List?
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Single Host Granularity (SHG) with full database ITRs & Query Servers
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: ksriram@nist.gov
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: "K. Sriram" <ksriram@nist.gov>
• re: [RRG] draft-fuller-lisp-alt-01.txt
  • From: Xu Xiaohu <xuxh@huawei.com>
• re: [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] draft-fuller-lisp-alt-01.txt
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] ALT's strong aggregation often leads to *very* long paths
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] draft-fuller-lisp-alt-01.txt
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Re: Granularity & number of ETRs for multihoming
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Tony Li <tli@cisco.com>
• [RRG] draft-fuller-lisp-alt-01.txt
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] Fresh subject lines
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: David Conrad <drc@virtualized.org>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Tony Li <tli@cisco.com>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Peter Sherbin <pesherb@yahoo.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• [RRG] draft-lear-lisp-nerd-03.txt
  • From: Eliot Lear <lear@cisco.com>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Eliot Lear <lear@cisco.com>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: David Conrad <drc@virtualized.org>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian Dickson <briand@ca.afilias.info>
• Granularity (was Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip)
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: David Meyer <dmm@1-4-5.net>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Scott Brim <swb@employees.org>
• Re: [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Dino Farinacci <dino@cisco.com>
• [RRG] ALT + NERD is inelegant & inefficient, compared to APT or Ivip
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Properties of mapping solutions
  • From: briand@ca.afilias.info
• Re: [RRG] Properties of mapping solutions
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Replacement for BGP-TCP-MD5
  • From: Tony Li <tli@cisco.com>
• [RRG] Replacement for BGP-TCP-MD5
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Properties of mapping solutions
  • From: Brian Dickson <briand@ca.afilias.info>
• RE: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: Dependency on mapping [Re: [RRG] Tunnel fragmentation/reassembly for RRG ...
  • From: Tony Li <tli@cisco.com>
• Re: Dependency on mapping [Re: [RRG] Tunnel fragmentation/reassembly for RRG ...
  • From: HeinerHummel@aol.com
• Re: Dependency on mapping [Re: [RRG] Tunnel fragmentation/reassembly for RRG ...
  • From: Luigi Iannone <Luigi.Iannone@uclouvain.be>
• Re: Dependency on mapping [Re: [RRG] Tunnel fragmentation/reassembly for RRG ...
  • From: HeinerHummel@aol.com
• Re: Dependency on mapping [Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures]
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Markus Stenberg <mstenber@cisco.com>
• Re: Dependency on mapping [Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures]
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: sandy@tislabs.com (Sandy Murphy)
• Re: Dependency on mapping [Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures]
  • From: Tony Li <tli@cisco.com>
• Dependency on mapping [Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures]
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Markus Stenberg <mstenber@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: David Conrad <drc@virtualized.org>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Christian Vogt <christian.vogt@nomadiclab.com>
• re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Xu Xiaohu <xuxh@huawei.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• [RRG] RRG Program Committee
  • From: Tony Li <tli@cisco.com>
• Fwd: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Fwd: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Luigi Iannone <luigi.iannone@uclouvain.be>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Properties of mapping solutions
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Properties of mapping solutions
  • From: Eliot Lear <lear@cisco.com>
• [RRG] Provider Changes Under APT
  • From: Dan Jen <jenster@CS.UCLA.EDU>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Properties of mapping solutions
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• [RRG] Properties of mapping solutions
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• [RRG] Comparing BGP with map-encap schemes
  • From: Robin Whittle <rw@firstpr.com.au>
• [RRG] Comparing BGP with map-encap shemes
  • From: Robin Whittle <rw@firstpr.com.au>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• [RRG] BGP issues
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Fwd: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dan Jen <jenster@CS.UCLA.EDU>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• RE: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Iljitsch van Beijnum <iljitsch@muada.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Eliot Lear <lear@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• [RRG] Re: map-and-map (vs map-and-encaps) - further thoughts
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] map-and-map (vs map-and-encaps) - further thoughts
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] map-and-map (vs map-and-encaps) - further thoughts
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Robert Raszuk <raszuk@juniper.net>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Yakov Rekhter <yakov@juniper.net>
• Re: [RRG] map-and-map (vs map-and-encaps) - further thoughts
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] map-and-map (vs map-and-encaps) - further thoughts
  • From: Brian E Carpenter <brian.e.carpenter@gmail.com>
• RE: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] map-and-map (vs map-and-encaps) - further thoughts
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] MTU/fragmentation AGAIN
  • From: Brian Dickson <briand@ca.afilias.info>
• RE: [RRG] MTU/fragmentation AGAIN
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] MTU/fragmentation AGAIN
  • From: Brian Dickson <briand@ca.afilias.info>
• RE: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] MTU/fragmentation AGAIN
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] MTU/fragmentation AGAIN
  • From: Scott Brim <swb@employees.org>
• RE: [RRG] MTU/fragmentation AGAIN
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• [RRG] updated RRG Vancouver meeting minutes
  • From: Lixia Zhang <lixia@CS.UCLA.EDU>
• Re: [RRG] MTU/fragmentation AGAIN
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] MTU/fragmentation AGAIN
  • From: Brian Dickson <briand@ca.afilias.info>
• RE: [RRG] MTU/fragmentation AGAIN
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• RE: [RRG] MTU/fragmentation AGAIN
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] MTU/fragmentation AGAIN
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Tony Li <tli@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Dino Farinacci <dino@cisco.com>
• Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: Brian Dickson <briand@ca.afilias.info>
• RE: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures
  • From: "Templin, Fred L" <Fred.L.Templin@boeing.com>