From rtgwg-bounces@ietf.org  Fri Apr  8 18:08:40 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16239
	for <rtgwg-web-archive@ietf.org>; Fri, 8 Apr 2005 18:08:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DK1nS-0000uK-Oi
	for rtgwg-web-archive@ietf.org; Fri, 08 Apr 2005 18:17:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DK1eC-0007BL-GG; Fri, 08 Apr 2005 18:08:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DK1e5-00071U-HN
	for rtgwg@megatron.ietf.org; Fri, 08 Apr 2005 18:08:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16156
	for <rtgwg@ietf.org>; Fri, 8 Apr 2005 18:08:07 -0400 (EDT)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DK1mv-0000th-7n
	for rtgwg@ietf.org; Fri, 08 Apr 2005 18:17:18 -0400
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1DK1e3-000ANU-J7
	for rtgwg@ietf.org; Fri, 08 Apr 2005 22:08:07 +0000
Date: Fri, 8 Apr 2005 15:08:07 -0700
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1646537713.20050408150807@psg.com>
To: rtgwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 4ec3642ae9025e273a4a263d640f3300
Content-Transfer-Encoding: 7bit
Subject: IETF-62 RTGWG Minutes
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 563af5038a5e1dade28c8affc0fff375
Content-Transfer-Encoding: 7bit

Folks-

 Meeting minutes below. Thanks to Don for taking the notes!
 Corrections are welcome till Apr 22.

-- 
Alex
http://www.psg.com/~zinin

IETF-62 RTGWG Meeting Minutes.

THURSDAY, March 10, 2005
1300-1500 Afternoon Sessions I
Chairs: Alex Zinin and Bill Fenner

Alex Zinin started the discussion with a WG status update (see slides).

- GTSM document will be LC'ed before Paris IETF, Alex to send comments
- Basic IP FRR updated.
- Draft MIB move to WG doc.

Alia Atlas Gave a presentation on the status up the Loop Free Alternates
draft (draft-ietf-rtgwg-ipfrr-spec-base) (See Slides for details).

  Alia gave a run down to the Changes to Draft including:
  Updates to the draft.
  There are some issues with various topologies in OSPF:
  - Multi areas: Can get paths back and forth across Area boundaries. Can
  cause the LFA to loop.
  - Virtual links: Different router than the back bone topology.
  - Alternate ABRs:
  - Multiarea ABRs:
  - AS External Routes:

  Recommend we do not support Virtual links or Alternate ABR
  If ASBR is in multiple non-backbone areas, then no other ABR is also in more
  than one of those non-backbone areas.
  AS External Route of specific type (1 or 2) must not be announced with a
  forwarding addresses from multiple non-backbone areas IF those non-backbone
  areas share at least one ABR.

  Future changes:
  Added Other applicability and Strict Downstream Alternates.
  Strict Downstream Alternates guarantees loop freedom but Cannot guarantee
  SRLG protections.
  Alia: Would like opinions to the list please.
  Alia: Applicability was for OSPF.
  Alex: Comments?

  Ted Seely: Was it Inter AS you were talking about?
  Alia: Yes, it was AS-external
  Ted : Any operators would use this for inter-AS?
       Isn't it easier to solve the intra-AS problem first?
  Alia: these are external routes, but the discussion is about
        behavior within a single AS

  Dave Ward: Regarding your applicability statement note, are you planning on
             having the protocol automatically figure out what's supported and what's not
             or have it as a user burden?
  Alia: It is a User burden today.
  Dave: Many problematic situations can be discovered automatically, may want to
        converge on some protocol mechanisms for that, rather than rely solely on the
        user.
  Alia: OK, we can discuss this

Next Alex discussed :Micro-loop prevention DT update \
Reference: http://psg.com/~zinin/ietf/rtgwg/neverloop/
>         draft-bryant-shand-lf-conv-frmwk-00.txt
>         draft-zinin-microloop-analysis-00.txt

  Alex described a summary of the Micro loop design team summary which was
  on the RTGWG list. So far the team has eliminated:
  
  -Incremental cost change, due to multiple convergence cycles and long
   convergence
  -Synched FIB installation, due to reqs for tight sync'ing, strong
   implementation constrains, service dependency on NTP, operational
   constrains

  Brian Habberman: Is it only service dependency or an architectural problem?
  Alex: No architectural problem, since general routing still doesn't depend on NTP,
        only the FRR piece that would depend on it

  Alex went through the various options currently under consideration by the design
  team.  <See Slides for details>

  DT: PLSN

   Pros:
     -Easy to understand
     -Constant delay
     -Covers all topo changes
     -Allows SRLGs
     -About 90% of the loops
     -Changing topology is likely to improve coverage
     -Can be used as a basic method with further extensions
   Cons:
    - Less than 100 %
    - Loop traffic may congest loop free.
    - Asymmetric link costs require stricter safety condition (DS BF
      instead of LFA)

  Order FIB Install
   Pros:
     - 100% coverage [for micro-loops]
     - Asym costs covered
     - SRLGs covered at a cost
   Cons:
     - Distributed
     - Longer convergence (can be improved using explicit signaling)

  Tunnels:
   Pros:
    -Cover 100%
    -Const Convergence time (shorter than the ordered FIB)
    -Can handle SRLGs
   Cons
    -Requires "Covert announcements" in PRs
    -With Basic FRR requires additional an data-plane mechanisms
    -Tunnels have different operational and security operations
    -Distributed version involves increased complexity

  The next step for the Design Team is to come up with the recommendations for
  WG. So far Path Locking Safe Neighbors for basic FRR is a high runner. Hoping
  the design team will make recommendation in, one month?
  Questions?
  Alex: Will summarize considerations and send this to the ML and move the
        discussion there.

  Dave Ward: How did the DT come to a conclusion that Less than 100% coverage is good enough?
  Alex: Generally, there's no clear cut here--reaching 100% coverage comes at a
        high cost. Basic IP FRR doesn't give us 100% coverage, and PLSN's
        coverage is very similar to that.
  
  Dave: OK, do envision using PLSN as the base method and use something else for
        advanced?

  Alex: Both basic FRR and PLSN address local failures and micro-loops using
        redundancy in physical network topology. As we move towards better
        coverage, the physical-topology method may be augmented with advanced
        methods like tunnels. Use PLSN where possible, use advanced on top of
        that for the rest.

  Russ White: What is parts of topology not covered?

  Alex: Mike did simulations, that show that places where PLSN doesn't cover
        microloops are almost the same as the places where IP FRR wouldn't cover
        local failures.

  Mike: Most of the places where you can't repair you also can't prevent loops.
        There are some cases where loops and failures do not collocate, of
        course.

  [? Not sure if this was still Russ] I think IPFRR and PLSN May be valid

  Alex: The physical meaning is that since both basic IPFRR and PLSN use similar
        constructs for defining nbrs that can be used for local failure repair
        and micro-loop prevention, so if you have a problem protecting against
        a local failure, it's likely you'll have loops there too.
  
  Mike Shand: There are certain typical topologies that have problems:
       Rigorous Hub and spoke; some rings. If you have a well constructed mesh,
       it will play much better.

  Thomas Eriksson[sp?]:If you play with metrics it does not add much.
  Stewart: You might come up with poor topologies.
  You can reduce coverage with metrics or asymmetric link metrics.

  This line of questioning went too fast for the scribe:
  [?]Asymmetric link metrics occur as intentional or accidental?
  [Dave Ward?] How do I set up my metrics for traffic and repair.
  [?]Useful if more people with operations experiences could comment.

  IGP metric-based TE and IP FRR coverage will probably work against each
  other. Not going to solve it here and now. Tools should take this into
  account.

  Stewart asked for feedback on whether we're getting sufficient coverage given
  the restrictions.

  Alex: there was a Panel at NANOG: Message that Alex took from there, as well
  as from conversations with other SPs is operators are concerned about
  complexity and would rather see 80-90% coverage with simple methods they can
  understand and deploy.
  
  Stewart: did they say if they want to pick the traffic that is covered [by the 80-90%]?

  Alex: telling you what I heard.
  Alex: my position: basic IP FRR and advanced FRR will have different applicability
  compared to each other and MPLS FRR. There will be networks where they won't make
  any sense because of the topology, and networks where the fit nicely. All about
  trade-offs.
  
Stewart Bryant presented a New Method called NotVia. This is an improvement on the tunnels
method. (See Slides for details)

  IP Fast reroute via NotVia

  Advantages of NotVia:
    - Repairs all non-partitioning failures. When repair delivers traffic
      NotVia paths.
    - Two guardian routers deliver the traffic NotVia paths.
    - NotVia addresses are created per interface.
    - Stewart used some Diagrams illustrating NotVia
    - Some Sample results using NotVia:
    - Incremental SPF with early terminations in networks with 40-400 nodes
      equivalent of 5-13 full SPFs per node.
    - Really a very cheap [computationally] algorithm.

  More Advantages:
    - Works with MPLS LDP. Just push the label for an intermediate to get to P.
      Labels needed by S source.
    - Encapsulation (any IP encapsulation will work).
    - One tunnel does the job.
    - Not just Pt-pt unicast.
    - NotVia Covers LANs.
    - When You have a LAN Don't know whether the LAN or a component failed. Can
      diagnose what is going on. Simple case must assume LAN failed. - Can
      discover via the not via repair to test the P failure.  Powerful technique.
    - NotVia Works for Multicast. Although this is a hard problem.
    - Loop Free alternates can be used with NotVia. Can use NotVia as an
      acceleration for LFA.
    - Multicast needs an encapsulation but works [claimed by Stewart and Mike].
    - ECMP can be used with NotVia.
    - NotVia supports Incremental Deployment. [via capabilities]
    - You can Exclude routers that are not NotVia capable.

  Stewart explained the Routing extensions for NotVia:
  - Need to advertise NotVia address.
  - Must advertise protected component SRG

  Stewart explained Link Failure for NotVia.
  S (a source router in the diagram) can give any packet to any router.  S can
  optimize which router is best.
  NotVia provides for diagnosis of faults in LANs by correlating NotVia paths.

  Loops don't form[?]

  Stewart explains it supports Multi-homed prefixes with two strategies.

  Joel Halpern: <referring to diagram> Node  B [source Node] must have
  detected the failure already to use the [NotVia path].
  Stewart: Yes
  Joel: B sends to P if P cannot forward P drops [and does not loop]?
  [Yes]

  Thomas Eriksson [sp?]. How would this work with MPLS?
  Some fast discussion and debate whether all the cases are covered by several
  people.
  Stewart: Does not change the problem--B needs to know about the failure
  quickly enough.

  Summary of NotVia by Stewart:
  - Solves the problem at an Intuitive level.
  - Works with asymmetric links.
  - Uses MPLS FRR hardware
  - Single-level encapsulation
  - Repair time is bounded.

  Alex: How many NotVia addresses?
  Stewart: One per link [in network]
  Joel: Isn't it one per neighbor?
  Stewart: yes, one per neighbor
  Joel: Except for SRLG ?

  Alex: Assumption B [referring to diagram] will detect the failure soon
  enough that it is not dropped on the floor.

  Stewart: Standard failure detection applies to every problem and every
  solution here. Same response characteristics here as with basic IP FRR.

  <some more discussion on this>

  [Dave?]BFD time is comparable with all neighbors.  Part of all solution in
  all problem scenarios.

  Alia: This is Different than Loop Free Alternates.
  Might not be able to do the repair.
  Stewart: Exactly the same [problem as LFA].
  Mike: [Agrees] Does not make a difference.  If BFD time is different that is
  the least of the problems.

  George Swallow: Works for Any packet?
  {scribe missed response Affirmative I believe.}

  Joel: What about Transients? Do you Assume the path is available?
  Alex: The network is going under changes
  Stewart: NotVia is Never worse than one detection time.
  Alex and Stewart: Read the draft. It is available publicly.
  Thanks. Read send comments.

  More Discussion on NotVia:
  Alia: If the link between S and P is a broadcast link I don't think it
  works.
  Stewart: If a broadcast link it is like the pseudo node.
  Joel: Made a comment, and subsequently withdrew it.

Next Mike Shand Presented Summary of agreements from DT and non agreements
between Alia, Mike and Stewart. <See Slides for details>

  All agree: There are four advanced methods.
  - U-turn
  - IP-TE
  - PQ-Tunnels
  - NotVia

  Less agreement: What value do you assign? [To complexity etc] It is a Value
  judgment.

  Issue: Failure scenarios

  All agree Methods Must do:
  -Link failure,
  -node failure,
  -broadcast link failure,
  -local SRLG failure
  Some agreement Maybe :
  - SRLG failure
  - IP unicast failure
  - MPLS LDP failure
  - IP multicast failure?

  Questions On Complexity of the encapsulation.

  Tunneling:
  Use IP or LDP for encapsulation?
  Some traffic types probably need tunneling.
  All Tunneling requires label acquisition.

  On Computation complexity (least agreement in DT)
  More SPFs how many is too many?
  Final computation time?
  How long it take to prepare for the next failure?
  Not all SPFs are equal?

  Network is vulnerable during the [preparation] time.

  Delay convergence is provided. So you might get the computation done in
  time.

  Mike presented a number of SPF calculations table: See slides

  Notable:
  U-turn - 20 node ~ 10 SPFs
  NotVia - 15 equivalent SPFs
  Mike also presented comments on Routing extensions, Forwarding extensions,
  Coverage. See slides

  What cost completeness, what cost lack of it?

Alex:  Are we Done?

Andy Smith:
Are the Methods nodal base or link based? What if the node is congested? 
Joel: This is about failures not congestion management. 
Andy: Do you have a delay mechanism for Link Flapping, e.g. link flap dampening.
Stewart: Absolutely.

Andy: Is it Nodal based or link based?  Does the algorithm delay announcements
for each link or for the node as a whole?
Alex: We're building on the existing IGP behavior. What you're asking is how IGP will
      react to a flapping link. Different vendors have different optimizations.
      There was a draft on that, which didn't survive. Might be useful to reconsider that.
      Assume the IGP can handle this.
Andy: These are all good ideas, but DOS attacks etc.
Alex: If a router is overloaded and starts dropping hellos, it will be detected
      as a failure
Joel: Congestion better dealt with by other aspects.
Alex: Agree with Joel, this is a general problem for IGPs, IP FRR, MPLS FRR, and
      should not be solved here. Valid problem, but IPFRR is not the right place.
Don Fedyk: Do we need to allow an option to Bail out?
Some Discussion for Don to clarify his comment. 
Alex: Not required.

? [Does this mean there are] Not a lot of nodal failures. 
Ted:  How do you tell? Common failure situation is many links.  
Stewart: Do you mean SRLGs?  
Ted: Yes. 
Andy: SRLGs on a nodal basis or across an network 
Alia: Yes.  Both  local SRLGs and general SRLGs.  
[?]If we have a meshy network.  Would not change anything if it is.
Determinism. 
Ted: When something happens in the night how do you adjust?  
[Dave?]Pagers are for that. 
Dave Ward:  IP FRR is not for that. 

[?]What is the path coming to a conclusion on those things? 

Alex: Need to finnish the base Spec first. Then Do the Mibs, applicability statement.
      The framework could be applicability statement. Will need Implementation reports.

Chris Hopps[sp?]  Do you want [basic] implementations? 

Alex: Basic implementations [first yes]. 

Stewart: Concerned about Basic IPFFR; believes it is an accidental approach.
It may turn out not what we want. If it turns out to not be what we
want, if so the RFC will legitimize it. We may not be able to deploy other
better solutions. It's not entirely clear if Basic is the right
intermediate step. Look at it as more of a facilitator. May mean we miss the
Real solution for the real [situations].

Alex: talked to a few service providers. Believes the Basic FRR is still valid
and useful, more operationally feasible. The decision made while chartering
the WG--to produce basic first--is still valid, and shouldn't be revisited
it now.

Thomas Erricson: Agree keep down complexity.
Alex: exactly why the basic first.

Alex: Thanks, read drafts send comments. 

WG meeting concluded.



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg


From rtgwg-bounces@ietf.org  Tue Apr 12 11:41:26 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09208
	for <rtgwg-web-archive@ietf.org>; Tue, 12 Apr 2005 11:41:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLNfg-0004Q3-BP
	for rtgwg-web-archive@ietf.org; Tue, 12 Apr 2005 11:51:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLNQ5-0003qf-Js; Tue, 12 Apr 2005 11:35:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLNQ3-0003pd-IY
	for rtgwg@megatron.ietf.org; Tue, 12 Apr 2005 11:35:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08737
	for <rtgwg@ietf.org>; Tue, 12 Apr 2005 11:35:03 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLNZU-0004Dx-8R
	for rtgwg@ietf.org; Tue, 12 Apr 2005 11:45:02 -0400
Received: from aatlas-lt.avici.com (aatlas-lt.avici.com [10.2.20.92])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3CFYd7l002281
	for <rtgwg@ietf.org>; Tue, 12 Apr 2005 11:34:39 -0400
Message-Id: <5.1.0.14.2.20050412112542.01fb44d0@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 12 Apr 2005 11:34:39 -0400
To: rtgwg@ietf.org
From: Alia Atlas <aatlas@avici.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: Ordered FIB approach & broadcast links
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

In the design team discussion, a question with the Ordered FIBs approach to 
micro-loop prevention was whether it could handle both "positive" and 
"negative" news in the same set of topology changes.  In general, this was 
seen as a nice to have.

I believe that the broadcast link case may make this necessary.  The 
scenario I am thinking of is where the interface from the DR on a broadcast 
link fails.  As a result, the backup DR will start announcing the router 
LSA needed for the pseudo-node.  This will look like a pseudo-node has 
failed & as if a new pseudo-node has appeared with all of its links.

What do others think?

I know that the DT decided on PLSN for the basic approach - but there's the 
possibility that a different advanced method might become desirable.

Alia


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg


From rtgwg-bounces@ietf.org  Wed Apr 13 04:37:22 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05767
	for <rtgwg-web-archive@ietf.org>; Wed, 13 Apr 2005 04:37:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLdWz-0008D4-5u
	for rtgwg-web-archive@ietf.org; Wed, 13 Apr 2005 04:47:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLdKL-0000H2-MY; Wed, 13 Apr 2005 04:34:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLdKF-0000FW-GG
	for rtgwg@megatron.ietf.org; Wed, 13 Apr 2005 04:34:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05516
	for <rtgwg@ietf.org>; Wed, 13 Apr 2005 04:34:09 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLdTr-000899-5o
	for rtgwg@ietf.org; Wed, 13 Apr 2005 04:44:16 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 13 Apr 2005 10:34:01 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3D8Xtvm000372; 
	Wed, 13 Apr 2005 10:33:56 +0200 (MEST)
Received: from mshand-w2k02.cisco.com (ams-clip-vpn-dhcp429.cisco.com
	[10.61.65.173])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id JAA24923;
	Wed, 13 Apr 2005 09:33:55 +0100 (BST)
Message-Id: <4.3.2.7.2.20050413092727.02d3ac90@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 13 Apr 2005 09:33:53 +0100
To: Alia Atlas <aatlas@avici.com>
From: mike shand <mshand@cisco.com>
In-Reply-To: <5.1.0.14.2.20050412112542.01fb44d0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: rtgwg@ietf.org
Subject: Re: Ordered FIB approach & broadcast links
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

At 11:34 12/04/2005 -0400, Alia Atlas wrote:
>In the design team discussion, a question with the Ordered FIBs approach 
>to micro-loop prevention was whether it could handle both "positive" and 
>"negative" news in the same set of topology changes.  In general, this was 
>seen as a nice to have.
>
>I believe that the broadcast link case may make this necessary.  The 
>scenario I am thinking of is where the interface from the DR on a 
>broadcast link fails.  As a result, the backup DR will start announcing 
>the router LSA needed for the pseudo-node.  This will look like a 
>pseudo-node has failed & as if a new pseudo-node has appeared with all of 
>its links.

Alia,

Yes, good point. That is certainly true, and looks like it could get rather 
messy:-(

I'm wondering whether it might be possible to deal with this at a higher 
level. i.e. rather than consider the pseudonode represented topology which 
has been severely shaken about by the DR changeover, is there some way we 
can consider the "real" topology which has simply lost a node. This might 
involve some special case processing of pseudonodes, but it might avoid the 
other complication.

Haven't had a chance to think seriously about this. I just throw it out as 
a possibility for further thought.

         Mike



>What do others think?
>
>I know that the DT decided on PLSN for the basic approach - but there's 
>the possibility that a different advanced method might become desirable.
>
>Alia
>
>
>_______________________________________________
>Rtgwg mailing list
>Rtgwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/rtgwg

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg


From rtgwg-bounces@ietf.org  Wed Apr 13 06:23:47 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12220
	for <rtgwg-web-archive@ietf.org>; Wed, 13 Apr 2005 06:23:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLfBz-0002K4-47
	for rtgwg-web-archive@ietf.org; Wed, 13 Apr 2005 06:33:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLey3-0003OJ-NO; Wed, 13 Apr 2005 06:19:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLey2-0003LV-67
	for rtgwg@megatron.ietf.org; Wed, 13 Apr 2005 06:19:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11925
	for <rtgwg@ietf.org>; Wed, 13 Apr 2005 06:19:27 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLf7m-0002Ds-OS
	for rtgwg@ietf.org; Wed, 13 Apr 2005 06:29:36 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 13 Apr 2005 12:19:20 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3DAJEvm002239; 
	Wed, 13 Apr 2005 12:19:15 +0200 (MEST)
Received: from mshand-w2k02.cisco.com (ams-clip-vpn-dhcp225.cisco.com
	[10.61.64.225])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA06320;
	Wed, 13 Apr 2005 11:19:12 +0100 (BST)
Message-Id: <4.3.2.7.2.20050413111556.04604b28@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 13 Apr 2005 11:19:11 +0100
To: Alia Atlas <aatlas@avici.com>
From: mike shand <mshand@cisco.com>
In-Reply-To: <4.3.2.7.2.20050413092727.02d3ac90@jaws.cisco.com>
References: <5.1.0.14.2.20050412112542.01fb44d0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: rtgwg@ietf.org
Subject: Re: Ordered FIB approach & broadcast links
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135

Alia,
         Thinking about this just a tiny bit more, when we have a failure 
of a DR, if we compare the old topology and the new topology, apart from 
the actual node itself going away, the only difference is that the NAME of 
the pseudonode has changed. All the links and costs to it and from it must 
be the same as they were before (except for the links to and from the 
physically failed node of course).

         So if there were some way we could recognize this, we could just 
ignore the problem.

         Mike

At 09:33 13/04/2005 +0100, mike shand wrote:
>At 11:34 12/04/2005 -0400, Alia Atlas wrote:
>>In the design team discussion, a question with the Ordered FIBs approach 
>>to micro-loop prevention was whether it could handle both "positive" and 
>>"negative" news in the same set of topology changes.  In general, this 
>>was seen as a nice to have.
>>
>>I believe that the broadcast link case may make this necessary.  The 
>>scenario I am thinking of is where the interface from the DR on a 
>>broadcast link fails.  As a result, the backup DR will start announcing 
>>the router LSA needed for the pseudo-node.  This will look like a 
>>pseudo-node has failed & as if a new pseudo-node has appeared with all of 
>>its links.
>
>Alia,
>
>Yes, good point. That is certainly true, and looks like it could get 
>rather messy:-(
>
>I'm wondering whether it might be possible to deal with this at a higher 
>level. i.e. rather than consider the pseudonode represented topology which 
>has been severely shaken about by the DR changeover, is there some way we 
>can consider the "real" topology which has simply lost a node. This might 
>involve some special case processing of pseudonodes, but it might avoid 
>the other complication.
>
>Haven't had a chance to think seriously about this. I just throw it out as 
>a possibility for further thought.
>
>         Mike
>
>
>
>>What do others think?
>>
>>I know that the DT decided on PLSN for the basic approach - but there's 
>>the possibility that a different advanced method might become desirable.
>>
>>Alia
>>
>>
>>_______________________________________________
>>Rtgwg mailing list
>>Rtgwg@ietf.org
>>https://www1.ietf.org/mailman/listinfo/rtgwg
>
>_______________________________________________
>Rtgwg mailing list
>Rtgwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/rtgwg

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg


From rtgwg-bounces@ietf.org  Wed Apr 13 10:25:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00597
	for <rtgwg-web-archive@ietf.org>; Wed, 13 Apr 2005 10:25:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLixr-0000F1-Jt
	for rtgwg-web-archive@ietf.org; Wed, 13 Apr 2005 10:35:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLinE-0002wa-OX; Wed, 13 Apr 2005 10:24:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLinD-0002vz-A8
	for rtgwg@megatron.ietf.org; Wed, 13 Apr 2005 10:24:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00538
	for <rtgwg@ietf.org>; Wed, 13 Apr 2005 10:24:25 -0400 (EDT)
Received: from [208.246.215.5] (helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLiwq-0000Dg-V2
	for rtgwg@ietf.org; Wed, 13 Apr 2005 10:34:35 -0400
Received: from aatlas-lt.avici.com (b2-pc240.avici.com [10.2.100.240])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3DEOC7l014905;
	Wed, 13 Apr 2005 10:24:12 -0400
Message-Id: <5.1.0.14.2.20050413101332.01ea3830@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 13 Apr 2005 10:24:10 -0400
To: mike shand <mshand@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <4.3.2.7.2.20050413111556.04604b28@jaws.cisco.com>
References: <4.3.2.7.2.20050413092727.02d3ac90@jaws.cisco.com>
	<5.1.0.14.2.20050412112542.01fb44d0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: rtgwg@ietf.org
Subject: Re: Ordered FIB approach & broadcast links
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6

Mike,

I agree that recognizing the pseudo-node has changed its name would remove 
this additional concern for handling "good news" and "bad news" 
simultaneously.

Alia

At 06:19 AM 4/13/2005, mike shand wrote:
>Alia,
>         Thinking about this just a tiny bit more, when we have a failure 
> of a DR, if we compare the old topology and the new topology, apart from 
> the actual node itself going away, the only difference is that the NAME 
> of the pseudonode has changed. All the links and costs to it and from it 
> must be the same as they were before (except for the links to and from 
> the physically failed node of course).
>
>         So if there were some way we could recognize this, we could just 
> ignore the problem.
>
>         Mike
>
>At 09:33 13/04/2005 +0100, mike shand wrote:
>>At 11:34 12/04/2005 -0400, Alia Atlas wrote:
>>>In the design team discussion, a question with the Ordered FIBs approach 
>>>to micro-loop prevention was whether it could handle both "positive" and 
>>>"negative" news in the same set of topology changes.  In general, this 
>>>was seen as a nice to have.
>>>
>>>I believe that the broadcast link case may make this necessary.  The 
>>>scenario I am thinking of is where the interface from the DR on a 
>>>broadcast link fails.  As a result, the backup DR will start announcing 
>>>the router LSA needed for the pseudo-node.  This will look like a 
>>>pseudo-node has failed & as if a new pseudo-node has appeared with all 
>>>of its links.
>>
>>Alia,
>>
>>Yes, good point. That is certainly true, and looks like it could get 
>>rather messy:-(
>>
>>I'm wondering whether it might be possible to deal with this at a higher 
>>level. i.e. rather than consider the pseudonode represented topology 
>>which has been severely shaken about by the DR changeover, is there some 
>>way we can consider the "real" topology which has simply lost a node. 
>>This might involve some special case processing of pseudonodes, but it 
>>might avoid the other complication.
>>
>>Haven't had a chance to think seriously about this. I just throw it out 
>>as a possibility for further thought.
>>
>>         Mike
>>
>>
>>
>>>What do others think?
>>>
>>>I know that the DT decided on PLSN for the basic approach - but there's 
>>>the possibility that a different advanced method might become desirable.
>>>
>>>Alia
>>>
>>>
>>>_______________________________________________
>>>Rtgwg mailing list
>>>Rtgwg@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/rtgwg
>>
>>_______________________________________________
>>Rtgwg mailing list
>>Rtgwg@ietf.org
>>https://www1.ietf.org/mailman/listinfo/rtgwg
>
>_______________________________________________
>Rtgwg mailing list
>Rtgwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/rtgwg



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg


From rtgwg-bounces@ietf.org  Thu Apr 14 17:05:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27854
	for <rtgwg-web-archive@ietf.org>; Thu, 14 Apr 2005 17:05:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMBh2-0002uC-8o
	for rtgwg-web-archive@ietf.org; Thu, 14 Apr 2005 17:16:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMAIe-0007u7-7u; Thu, 14 Apr 2005 15:46:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMAIV-0007sj-MM; Thu, 14 Apr 2005 15:46:43 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16559;
	Thu, 14 Apr 2005 15:46:41 -0400 (EDT)
Message-Id: <200504141946.PAA16559@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 14 Apr 2005 15:46:41 -0400
Cc: rtgwg@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-05.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group Working Group of the IETF.

	Title		: The Generalized TTL Security Mechanism (GTSM)
	Author(s)	: V. Gill, et al.
	Filename	: draft-ietf-rtgwg-rfc3682bis-05.txt
	Pages		: 16
	Date		: 2005-4-14
	
The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6)
   to protect a protocol stack from CPU-utilization based attacks has
   been proposed in many settings (see for example, RFC 2461). This
   document generalizes these techniques for use by other protocols such
   as BGP (RFC 1771), Multicast Source Discovery Protocol (MSDP),
   Bidirectional Forwarding Detection, and Label Distribution Protocol
   (LDP) (RFC 3036). While the Generalized TTL Security Mechanism (GTSM)
   is most effective in protecting directly connected protocol peers, it
   can also provide a lower level of protection to multi-hop sessions.
   GTSM is not directly applicable to protocols employing flooding
   mechanisms (e.g., multicast), and use of multi-hop GTSM should be
   considered on a case-by-case basis.  This document obsoletes RFC
   3682.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-rfc3682bis-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rtgwg-rfc3682bis-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-14161844.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-05.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-rtgwg-rfc3682bis-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-14161844.I-D@ietf.org>


--OtherAccess--

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

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

--NextPart--





From rtgwg-bounces@ietf.org Tue Apr 26 10:35:30 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQR9u-0005U0-LB; Tue, 26 Apr 2005 10:35:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQR9q-0005Tq-Sp
	for rtgwg@megatron.ietf.org; Tue, 26 Apr 2005 10:35:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13291
	for <rtgwg@ietf.org>; Tue, 26 Apr 2005 10:35:25 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQRMG-0005ms-VW
	for rtgwg@ietf.org; Tue, 26 Apr 2005 10:48:20 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 26 Apr 2005 16:35:15 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3QEZB54003627; 
	Tue, 26 Apr 2005 16:35:12 +0200 (MEST)
Received: from mshand-w2k02.cisco.com (dhcp-rea-gp250-64-103-64-184.cisco.com
	[64.103.64.184])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA02166;
	Tue, 26 Apr 2005 15:35:08 +0100 (BST)
Message-Id: <4.3.2.7.2.20050426141038.021f1a90@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 26 Apr 2005 15:35:00 +0100
To: Alia Atlas <aatlas@avici.com>
From: mike shand <mshand@cisco.com>
In-Reply-To: <5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5216aa5b0df24d46eaed76d4f65aa31
Cc: rtgwg@ietf.org
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

At 15:07 25/03/2005 -0500, Alia Atlas wrote:

>Second is the list of downsides with the approach.  The main concern is 
>that the mechanism becomes too complex such that the trade-off between its 
>complexity and the full coverage is not desirable.
>1.      This requires a large number of additional IP addresses in the 
>IGP.  The same number of additional FECs is required to support LDP.

Yes, it does. In the simplest case of link and node protection, and 
ignoring LANs it requires 2 addresses per protected link. It is expected 
that these would come out of a "private" address space, and hence wouldn't 
consume real addresses. Indeed for security reasons it is preferable that 
they are private addresses.

I don't think this number is "too many". The question is how does this 
number increase when we add LANs and SRLGs.

>2.      Explicit tunnels are needed, which means that targeted LDP 
>sessions are necessary to have this support LDP traffic.

Yes. In the case of node protection we could also using Naiming's scheme of 
next-next hop LDP advertisement.

>  This is a particular concern for multi-homed prefixes; I'll describe my 
> concerns on this later.

Yes. This is a concern for LDP. I don't like the idea of targeted LDP 
sessions. Two possibilities come to mind

a) each node with an attached MHP distributes an additional label for that 
prefix which has the semantics that when you pop that address you MUST 
forward the underlying IP packet "directly".

b) an alternative which doesn't require additional labels, but DOES require 
a new "well known" label with the above semantics.

Neither are very attractive, but perhaps more attractive than the directed 
LDP sessions.

>3.      Substantial IGP changes are required to handle the additional 
>Notvia addresses.

Substantial is perhaps a bit strong. We need to advertise the not-via 
address and its association. For IS-IS its pretty straightforward. OSPF, by 
its very nature, may be a little more tricky.



>4.      A more complex algorithm is required to make the computation feasible.

Yes.

>5.      The management of the Notvia addresses & of the tunnels can create 
>longer time periods where protection isn't available for a part of the 
>network (the new link or node, etc.).

I don't think the tunnels add to the time at all. They are after all just 
FIB entries. Distributing the notvia addresses for a new node/link will 
occur at the same time as distributing the information about the link/node 
in the first place. I don't think it significantly increases the delay.

There is of course the time it takes to recompute notvia routes, but we 
think this will be well under a second.

These aspects certainly need thinking about, but they don't seem to pose 
insurmountable issues.


>Third, there are a number of issues that I feel need considerable 
>discussion to try and resolve.  I will try to go through each in turn and 
>explain what I think the various aspects of each are.  Each of these 
>issues has the possibility to resolve in such a way that the Notvia 
>Addresses approach becomes overly complex.

Yes. That is a temptation we need to resist!

>1.      Notvia Addresses:  The first issue is how the Notvia addresses are 
>allocated, distributed and withdrawn.  An initial idea of Stewart & Mike 
>is that these addresses are not global addresses (i.e. are 10.x.x.x or 
>such) and are configured in blocks on each router so that the router can 
>manage the bindings itself.

That seems the most reasonable thing to do.

>a.      The routing extensions to the IGP will have to associate a network 
>resource (node or link) that an address should be Notvia.  This is 
>probably straightforward.

Yes, As I said above.

>b.      It is desirable to have some dampening on the withdrawal of Notvia 
>addresses to minimize thrashing.

The allocation of notvia addresses to links certainly shouldn't be changed 
as a result of not "needing" the notvia address when the object with which 
it is associated goes away. It should also get back the same notvia address 
when it comes back. But I don't think there are any particular issues 
associated with them disappearing and reappearing in the LSPs.

Do you have any specific issues in mind?

>c.      If configured in blocks, it would be extremely desirable to have 
>the same Notvia address mean the same thing through multiple reboots, 
>etc.  It'd be good to have some means of consistent association.  This is 
>for easy manageability.

Yes, definitely.


>d.      When a new link or neighbor comes up, there will be a longer 
>period of time when an alternate isn't available because the Notvia 
>address hasn't been advertised yet.  These periods without protection need 
>to be clearly understood and minimized.

Yes. I'm not convinced there is a particular problem here, but it does need 
thinking through carefully.

>e.      There may be scalability concerns based on the number of Notvia 
>addresses and LDP FECs required.  For instance, as described in the draft, 
>it is basically the number of uni-directional links in the topology.  This 
>is ignoring the extras for broadcast links.  To fully & certainly provide 
>SRLG protection if at all feasible, would require that each router 
>advertise a Notvia address for every uni-directional link into every 
>neighbor of that router.  This would result in K*L additional addresses, 
>where K is the average number of neighbors & L is the number of 
>uni-directional links in the topology.

Yes. This is a major concern, and we need to devise ways of solving SRLGs 
etc. which minimize the potential proliferation of addresses.
We need to get the right tradeoff here between optimal solutions and 
complexity.

>2.      Insufficiently diverse topology:  It is possible that a network 
>topology cannot provide an alternate that suffices for link, node and SRLG 
>protection.  It isn't clear to me how to compute a "best-available" 
>alternate using this approach.  For instance, if one can get link 
>protection, but not node protection, how would that be determined, 
>computed and assigned?  This becomes much more of a concern for SRLG 
>protection & for topologies where failures have already occurred and the 
>network has converged for those & needs protection in the event of an 
>additional failure.

Clearly it is always possible to create a topology which contains single 
points of failure and is inherently irreparable. This is part of the 
tradeoff we need to address when thinking about SRLGs, since taking a 
simple but pessimistic approach to SRLG can result in this sort of failure. 
This seems to be a property of the problem rather than any particular solution.


>3.      Failure Diagnosis versus Pessimism:  As written, the draft 
>discusses the idea of doing failure diagnosis using BFD.  As Stewart, Mike 
>& I have discussed, this isn't possible for SRLG failures, although it is 
>possible for broadcast links.

Yes, and this relates to (2) above.

>a.      I am concerned about adding the failure diagnosis.  This is yet 
>another level of complexity for implementation.  It also has ramifications 
>for the forwarding plane, because of the need to store multiple alternates 
>to use & have multiple states to check to decide what to use.

Yes. It would be nice not to have to do it, but that is back to the 
tradeoff above.

>b.      An example of a concern with the BFD diagnosis is that all 
>interfaces on a node that has failed are not certain to fail exactly 
>simultaneously or even within a sub-50ms bounded window.  It is entirely 
>possible that BFD sessions are terminated on different line-cards, that 
>detect the router failure at slightly different times and stop forwarding 
>traffic, therefore, at slightly different times.

Yes. There is the possibility of misdiagnosis in this case if the second 
failure occurs too long after the first. I suppose this then looks like two 
separate failures. Clearly an unreliable diagnosis is probably worse than 
no diagnosis at all. We need to get some handle on how realistic or not 
this scenario is.


>c.      The other approach is to pessimistically eliminate all routers 
>connected to the broadcast link as well as the broadcast link; this may 
>not provide an alternate.

Yes. While simple, it runs into the problem of being a single (albeit 
large) point of failure. Its the same trade-off as above.

>   It also needs to be thought through what issues might exist if the 
> topologies used for the SPF vary slightly for each router that is on the 
> broadcast link, since each will, as described, not prune itself out when 
> doing the computation; of course, there could be an approach where the 
> same topology can be used everywhere.

I'm not really sure what you mean here.

>  It isn't clear to me what Notvia addresses would be needed to express 
> "don't go through this pseudo-node or any nodes attached to it"; I don't 
> think that it is simply the Notvia address for avoiding a particular node.

No, it would need a specific notvia address bound to the LAN interface.

>4.      Multi-homed Prefixes:  I am quite concerned about the mechanisms 
>suggested in the draft.
>a.      First, I really do not like the idea of having separate forwarding 
>for "local" prefixes that come out of a tunnel.  What is a local 
>prefix?  For instance, does this mean that an ABR has to forward traffic 
>different depending on which area traffic from the tunnel has come 
>from?  I am concerned about how this would scale; maybe only 2 FIBs are 
>needed (one for backbone & one for other), but it may be worse to handle 
>AS external routes.  I know that Stewart, Mike, Joel, Albert and I had 
>discussed/agreed to put this idea out of scope  at least for the moment.

Clearly the problem needs solving, especially since prefixes which are 
multihomed are frequently the most important prefixes (which is WHY they 
are multihomed in the first place).

>b.      I am quite concerned about having tunnels to the advertisers of 
>the prefixes.
>i.      There needs to be a mechanism to determine whether the advertiser 
>of a prefix will forward the packet in a loop-free fashion to avoid the 
>failure point.  The separate forwarding for "local" prefixes avoided the 
>need for this determination, but at more substantial cost.

There seem to be two aspects to this.

a) we need the ability to get the packet to the "second-best" attachment 
point for the prefix without it being "sucked back" to the failure. This in 
general requires a tunnel, except for the cases where a neighbor of the 
node detecting the failure has an LFA to the second best attachment point. 
Clearly this could be used in preference to a tunnel where available, but 
at the expense of additional complexity. However this is really just an 
extension of the general principle that we should use "basic" (i.e. LFA) 
repair to cream off traffic which doesn't NEED to be tunnelled.

b) we need (in a very limited number of cases), the ability to force the 
packet to the locally attached prefix. This only occurs where the local 
cost is high compared to the cost back to the failed attachment point. But 
when we DO need it, the use of a tunnel is a convenient means of signalling 
this. I'm not sure how else to do it, other than using a label.

Of course ONE "solution" would be to REQUIRE the costs to be set sensibly :-)


>ii.     To support LDP, every tunnel requires a targeted LDP session.  If 
>multi-homed prefixes are common, then this becomes a full mesh for 
>LDP.  That isn't acceptable.

Agreed.

>  Of course, multi-homed prefixes may be much more infrequent for LDP than 
> for IP; for example, there is no reason to advertise a separate FEC for 
> the subnet of a link.  However, multi-homed prefixes are a concern for 
> LDP for at least the inter-area, AS External, and BGP routes.
>iii.    If traffic is encapsulated to a node's regular address, because 
>that traffic is destined to a prefix advertised by the node, how does the 
>receiving node know to remove the encapsulation and forward the packet 
>inside  all in the fast path?  Is this a just a question of different 
>handling based on the header type inside the outer encapsulation (for GRE)?

Yes.

>iv.     Perhaps these issues could be handled by determining a 
>next-next-hop that avoids the failure to reach an appropriate 
>advertiser.   Of course, this is a different set/type of computation.

Could you explain that suggestion please?

>5.      SRLGs and Broadcast Links:  There seem to be a number of possible 
>ways to handle SRLGs and broadcast links, each of which provides a 
>different trade-off in terms of  coverage, computation, and extra Notvia 
>addresses.

Yes.

>   There are basically 4 approaches at this point.
>a.      First, In order to compute a notvia alternate that avoids a link, 
>the primary neighbor, and all SRLGs that the link is part of, it is 
>necessary to have a separate topology and associated SPF computation for 
>each link that is a member of an SRLG or a broadcast link.   This requires 
>also a substantially larger number of Notvia addresses and the 
>corresponding mechanisms to determine how and when to allocate and 
>de-allocate them.

.. and could potentially result in a combinatorial explosion if we weren't 
very careful.

>b.      Second, one could use a topology that removed the primary neighbor 
>and see whether SRLG protection can be obtained either along S's path or 
>along any path of a neighbor of S that is also loop-free.

Could you explain that a bit more please?

>c.      Third, when a Notvia address indicates to avoid a node, one could 
>remove not merely the node & the uni-directional links to and from that 
>node, but also any other links that are in a common SRLG with any of the 
>links to or from the removed node.  This is pessimistic  but allows some 
>SRLG protection without increased computation or Notvia addresses.

Yes. This is nice and simple, but as you have pointed out above, could 
easily result in an inability to find a viable repair.

>d.      Fourth, one could simply track the SRLGs encountered along the 
>Notvia path; this just reports whether the alternate provides SRLG 
>protection without any effort to obtain it.

Yes. Interesting. I wonder how useful this would be.

>6.      Implementability:  Clearly, the draft describes the basic idea for 
>Notvia addresses, but there are a fair number of implementation/protocol 
>decisions that need to be made before this can become anything more than 
>an interesting idea.

Sure. There are quite a few design decisions and tradeoffs as indicated 
above that need tieing down.

>7.      There is a definite need to describe the convergence case 
>better.   This is how the transition from using the alternate to the 
>network being converged happens, such that the alternate remains functional.
>a.      For instance, if the node E fails, then the Notvia address E_!S 
>will no longer be advertised.  If S was getting link protection (because 
>that was all that was possible, for instance) by tunneling traffic to 
>E_!S, it is important that this traffic be properly discarded when E's 
>addresses go away.   This implies that there needs to be a default 
>blackhole for Notvia addresses.

I don't quite understand your concern here. If E goes away and S is sending 
to E_!S, then the neighbors of E will drop the packets because we don't 
repair a notvia address.

Or are you concerned that after convergence, there will be nodes which 
don't even have a forwarding entry for E_!S. By this time I don't think 
that S (or anyone else) should still be using that address, but even if it 
were, the absence of a forwarding entry would (SHOULD) cause the packet to 
be dropped. Is this all you are saying?


>b.      Another example is when node E fails, the next-next-hop B must 
>continue to advertise the Notvia address B_!E until the network converges 
>so that S can continue to tunnel traffic to B_!E as the alternate.

Yes. Our view was that no changes would be made to notvia advertisement or 
more specifically notvia FIB entries until after convergence is over. Of 
course there is an issue as to how you tell when that has happened, but the 
timers associated with loop free convergence probably give a good indication.

>c.      It is possible to get a micro-forwarding loop affecting a Notvia 
>address as a result of a less severe failure than anticipated.  For 
>instance, consider the following topology.
>              [D]
>               |
>           1   |
>      [E]-----[F]-\
>       |       |   \ 10
>     1 |R    1 |R   \
>       |   5   |     \
>      [S]-----[H]----[I]
>                  2
>
>      Link S->E and Link H->F are in SRLG R
>
>When node E fails, if I converges before H, there will be a loop affecting 
>the Notvia address being used to reach F without going through any of Link 
>S->E, E or SRLG R.

We discussed this privately, and I still don't see how loops could arrise 
even if the notvia FIB were recomputed before normal convergence is 
complete. But I think it is better to delay the notvia FIB changes anyway.

>d.      How do exceptions work?  Particularly in regards to an IP-in-IP 
>encapsulation such as GRE, it doesn't seem like MTU exceeded cases can be 
>handled cleanly  either by use of DF or by doing IP fragmentation and then 
>the reassembly at the end of the tunnel.  This seems like a problem for 
>all ICMP packets; how could a source understand the header inside for a 
>TTL expired, for instance.

I'll leave this for Stewart (tunnel) Bryant!

>e.      For IP-in-IP tunnels, another concern is flow diversity.  The IP 
>source and destination addresses are used to determine a flow; this flow 
>identification may then be used for a variety of purposes, including 
>ECMP.  By putting all the traffic to a variety of destinations inside the 
>same header, the ability to take advantage of flow diversity appears to 
>have disappeared.   This could possibly be solved by putting the original 
>source address into the encapsulating header?  Are there other approaches?

and this.

>Hopefully, this will spark some discussion on the issues.

Let's hope so

         Mike


>Alia
>
>
>
>_______________________________________________
>Rtgwg mailing list
>Rtgwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/rtgwg

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Tue Apr 26 22:56:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQcjR-0006X6-Sd; Tue, 26 Apr 2005 22:56:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQcjQ-0006X1-J3
	for rtgwg@megatron.ietf.org; Tue, 26 Apr 2005 22:56:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17887
	for <rtgwg@ietf.org>; Tue, 26 Apr 2005 22:56:54 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQcvy-0007X6-3m
	for rtgwg@ietf.org; Tue, 26 Apr 2005 23:09:56 -0400
Received: from aatlas-lt.avici.com (b2-pc102.avici.com [10.2.100.102])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3R2ub7l009827;
	Tue, 26 Apr 2005 22:56:37 -0400
Message-Id: <5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 26 Apr 2005 22:56:32 -0400
To: mike shand <mshand@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <4.3.2.7.2.20050426141038.021f1a90@jaws.cisco.com>
References: <5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c4a3535d1556ada67f8703d3d31591
Cc: rtgwg@ietf.org
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

Mike,

At 10:35 AM 4/26/2005, mike shand wrote:
>At 15:07 25/03/2005 -0500, Alia Atlas wrote:
>
>>Second is the list of downsides with the approach.  The main concern is 
>>that the mechanism becomes too complex such that the trade-off between 
>>its complexity and the full coverage is not desirable.
>>1.      This requires a large number of additional IP addresses in the 
>>IGP.  The same number of additional FECs is required to support LDP.
>
>Yes, it does. In the simplest case of link and node protection, and 
>ignoring LANs it requires 2 addresses per protected link. It is expected 
>that these would come out of a "private" address space, and hence wouldn't 
>consume real addresses. Indeed for security reasons it is preferable that 
>they are private addresses.
>
>I don't think this number is "too many". The question is how does this 
>number increase when we add LANs and SRLGs.

It would be useful to hear some additional opinions on the impact of adding 
a large number of addresses.  The other question is what is the boundary 
when it becomes a serious concern.

>>2.      Explicit tunnels are needed, which means that targeted LDP 
>>sessions are necessary to have this support LDP traffic.
>
>Yes. In the case of node protection we could also using Naiming's scheme 
>of next-next hop LDP advertisement.

True - but I'd want to think about the implications in terms of additional 
communication & periods of instability/inaccuracy of knowledge.    It also 
doesn't handle the multi-homed prefix case for the case when the path isn't 
via the next-next-hop.


>>  This is a particular concern for multi-homed prefixes; I'll describe my 
>> concerns on this later.
>
>Yes. This is a concern for LDP. I don't like the idea of targeted LDP 
>sessions. Two possibilities come to mind
>
>a) each node with an attached MHP distributes an additional label for that 
>prefix which has the semantics that when you pop that address you MUST 
>forward the underlying IP packet "directly".
>
>b) an alternative which doesn't require additional labels, but DOES 
>require a new "well known" label with the above semantics.
>
>Neither are very attractive, but perhaps more attractive than the directed 
>LDP sessions.

Both of these presume the ability to route based on the nested addresses of 
the packet.  In general, I don't think that this is a valid 
assumption.  Consider, for instance, the case of a BGP-free core.  Traffic 
is directed towards an ASBR in a different area (that is multi-homed to the 
one being considered).  In that case, the ABR may not have the BGP routes 
to be able to correctly forward the packet based on its IP address.  There 
are also a number of scenarios where what is underneath the top LDP label 
is another MPLs label & not routable at all.

>>3.      Substantial IGP changes are required to handle the additional 
>>Notvia addresses.
>
>Substantial is perhaps a bit strong. We need to advertise the not-via 
>address and its association. For IS-IS its pretty straightforward. OSPF, 
>by its very nature, may be a little more tricky.

More substantial than a few bits :-)  The main issue here is just the 
interop and migration concerns.

>>5.      The management of the Notvia addresses & of the tunnels can 
>>create longer time periods where protection isn't available for a part of 
>>the network (the new link or node, etc.).
>
>I don't think the tunnels add to the time at all. They are after all just 
>FIB entries. Distributing the notvia addresses for a new node/link will 
>occur at the same time as distributing the information about the link/node 
>in the first place. I don't think it significantly increases the delay.
>
>There is of course the time it takes to recompute notvia routes, but we 
>think this will be well under a second.
>
>These aspects certainly need thinking about, but they don't seem to pose 
>insurmountable issues.

I agree that they're not insurmountable - but just require consideration.

>>Third, there are a number of issues that I feel need considerable 
>>discussion to try and resolve.  I will try to go through each in turn and 
>>explain what I think the various aspects of each are.  Each of these 
>>issues has the possibility to resolve in such a way that the Notvia 
>>Addresses approach becomes overly complex.
>
>Yes. That is a temptation we need to resist!

It's frequently a coverage versus complexity trade-off, where each decision 
is along the slippery slope - alas!

>>b.      It is desirable to have some dampening on the withdrawal of 
>>Notvia addresses to minimize thrashing.
>
>The allocation of notvia addresses to links certainly shouldn't be changed 
>as a result of not "needing" the notvia address when the object with which 
>it is associated goes away. It should also get back the same notvia 
>address when it comes back. But I don't think there are any particular 
>issues associated with them disappearing and reappearing in the LSPs.
>
>Do you have any specific issues in mind?

Only keeping the notvia addresses around until after the network has 
converged...  If the notvia address is withdrawn with the link that's 
failed, then traffic may still be using that alternate.

>>c.      If configured in blocks, it would be extremely desirable to have 
>>the same Notvia address mean the same thing through multiple reboots, 
>>etc.  It'd be good to have some means of consistent association.  This is 
>>for easy manageability.
>
>Yes, definitely.

For the case where the notvia address is for a neighbor, it's not always 
that straightforward - unless one ends up advertising multiple notvia 
addresses for the same neighbor, depending on the number of parallel 
links.  This is mostly engineering, I think.

>>d.      When a new link or neighbor comes up, there will be a longer 
>>period of time when an alternate isn't available because the Notvia 
>>address hasn't been advertised yet.  These periods without protection 
>>need to be clearly understood and minimized.
>
>Yes. I'm not convinced there is a particular problem here, but it does 
>need thinking through carefully.

Agreed.


>>e.      There may be scalability concerns based on the number of Notvia 
>>addresses and LDP FECs required.  For instance, as described in the 
>>draft, it is basically the number of uni-directional links in the 
>>topology.  This is ignoring the extras for broadcast links.  To fully & 
>>certainly provide SRLG protection if at all feasible, would require that 
>>each router advertise a Notvia address for every uni-directional link 
>>into every neighbor of that router.  This would result in K*L additional 
>>addresses, where K is the average number of neighbors & L is the number 
>>of uni-directional links in the topology.
>
>Yes. This is a major concern, and we need to devise ways of solving SRLGs 
>etc. which minimize the potential proliferation of addresses.
>We need to get the right tradeoff here between optimal solutions and 
>complexity.

Agreed.  We need to understand the impact of additional addresses to know 
the complexity cost of that versus the reduced coverage of selecting a less 
complete approach to broadcast link and SRLG protection.

>>2.      Insufficiently diverse topology:  It is possible that a network 
>>topology cannot provide an alternate that suffices for link, node and 
>>SRLG protection.  It isn't clear to me how to compute a "best-available" 
>>alternate using this approach.  For instance, if one can get link 
>>protection, but not node protection, how would that be determined, 
>>computed and assigned?  This becomes much more of a concern for SRLG 
>>protection & for topologies where failures have already occurred and the 
>>network has converged for those & needs protection in the event of an 
>>additional failure.
>
>Clearly it is always possible to create a topology which contains single 
>points of failure and is inherently irreparable. This is part of the 
>tradeoff we need to address when thinking about SRLGs, since taking a 
>simple but pessimistic approach to SRLG can result in this sort of 
>failure. This seems to be a property of the problem rather than any 
>particular solution.

Let me try to explain this a bit better.  Say there's a topology that, for 
a particular next-hop & next-next-hop, can only provide an alternate that 
gives link and node protection but not SRLG protection.  Now, how does the 
notvia addresses method compute an alternate?  If the method is pruning the 
topology of the relevant link, node & SRLGs, no alternate will be 
found.  However, it was possible to compute & use an alternate that gives 
the link & node protection.  The similar case can easily occur with link & 
node protection.  Say S has two parallel links to E; if the first fails, S 
could use the other to get link protection  - but there is no 
node-protecting alternate.  How does S determine this?  What is the 
fall-back strategy in the case that no "full-protection" alternate is 
available?


>>3.      Failure Diagnosis versus Pessimism:  As written, the draft 
>>discusses the idea of doing failure diagnosis using BFD.  As Stewart, 
>>Mike & I have discussed, this isn't possible for SRLG failures, although 
>>it is possible for broadcast links.
>
>Yes, and this relates to (2) above.
>
>>a.      I am concerned about adding the failure diagnosis.  This is yet 
>>another level of complexity for implementation.  It also has 
>>ramifications for the forwarding plane, because of the need to store 
>>multiple alternates to use & have multiple states to check to decide what 
>>to use.
>
>Yes. It would be nice not to have to do it, but that is back to the 
>tradeoff above.

Complexity vs. coverage?  I'm very fond, unsurprisingly, of options that 
don't require hardware changes... so I judge that the complexity is rather 
high to support this one - as well as more error-prone (see comment on 
unreliable diagnosis).

>>b.      An example of a concern with the BFD diagnosis is that all 
>>interfaces on a node that has failed are not certain to fail exactly 
>>simultaneously or even within a sub-50ms bounded window.  It is entirely 
>>possible that BFD sessions are terminated on different line-cards, that 
>>detect the router failure at slightly different times and stop forwarding 
>>traffic, therefore, at slightly different times.
>
>Yes. There is the possibility of misdiagnosis in this case if the second 
>failure occurs too long after the first. I suppose this then looks like 
>two separate failures. Clearly an unreliable diagnosis is probably worse 
>than no diagnosis at all. We need to get some handle on how realistic or 
>not this scenario is.

Well, I think it is exceedingly realistic :-)
For a non-power related failure, routers with separate forwarding & control 
planes may take varying amounts of time for the line-cards to all realize 
that the route controller is down.

>>c.      The other approach is to pessimistically eliminate all routers 
>>connected to the broadcast link as well as the broadcast link; this may 
>>not provide an alternate.
>
>Yes. While simple, it runs into the problem of being a single (albeit 
>large) point of failure. Its the same trade-off as above.

Don't they all reduce to that?

>>   It also needs to be thought through what issues might exist if the 
>> topologies used for the SPF vary slightly for each router that is on the 
>> broadcast link, since each will, as described, not prune itself out when 
>> doing the computation; of course, there could be an approach where the 
>> same topology can be used everywhere.
>
>I'm not really sure what you mean here.

Let me try and explain it a bit.  Perhaps I'm missing something.   In the 
case where a notvia topology results in pruning the router doing the 
computation, what forms the root of the SPT?   Say routers A, B and C are 
all connected to a broadcast link X and want to compute a notvia X address 
as described in (c) by pruning the pseudo-node related to X as well as A, 
B, and C.   Now, router A prunes the pseudo-node, A, B and C from the 
topology; what does A use as the root?  IF A only prunes the pseudo-node, B 
and C to compute notvia X, B only prunes the pseudo-node, A, and C, and C 
only prunes the pseudo-node, A and B,  and all other routers prune the 
pseudo-node, A, B, and C, can there be any issues with a consistently 
computed & non-looping path for notvia X?

I think it may not be an issue - b/c once the traffic leaves A, B or C, it 
will never return - but it at least needs some thought, since this is a bit 
different from what's traditionally been done.

>>  It isn't clear to me what Notvia addresses would be needed to express 
>> "don't go through this pseudo-node or any nodes attached to it"; I don't 
>> think that it is simply the Notvia address for avoiding a particular node.
>
>No, it would need a specific notvia address bound to the LAN interface.

Agree

>>4.      Multi-homed Prefixes:  I am quite concerned about the mechanisms 
>>suggested in the draft.
>>a.      First, I really do not like the idea of having separate 
>>forwarding for "local" prefixes that come out of a tunnel.  What is a 
>>local prefix?  For instance, does this mean that an ABR has to forward 
>>traffic different depending on which area traffic from the tunnel has 
>>come from?  I am concerned about how this would scale; maybe only 2 FIBs 
>>are needed (one for backbone & one for other), but it may be worse to 
>>handle AS external routes.  I know that Stewart, Mike, Joel, Albert and I 
>>had discussed/agreed to put this idea out of scope  at least for the moment.
>
>Clearly the problem needs solving, especially since prefixes which are 
>multihomed are frequently the most important prefixes (which is WHY they 
>are multihomed in the first place).

inconvenient that!

>>b.      I am quite concerned about having tunnels to the advertisers of 
>>the prefixes.
>>i.      There needs to be a mechanism to determine whether the advertiser 
>>of a prefix will forward the packet in a loop-free fashion to avoid the 
>>failure point.  The separate forwarding for "local" prefixes avoided the 
>>need for this determination, but at more substantial cost.
>
>There seem to be two aspects to this.
>
>a) we need the ability to get the packet to the "second-best" attachment 
>point for the prefix without it being "sucked back" to the failure. This 
>in general requires a tunnel, except for the cases where a neighbor of the 
>node detecting the failure has an LFA to the second best attachment point. 
>Clearly this could be used in preference to a tunnel where available, but 
>at the expense of additional complexity. However this is really just an 
>extension of the general principle that we should use "basic" (i.e. LFA) 
>repair to cream off traffic which doesn't NEED to be tunnelled.

Yes - though the tunnels bring out the LDP issues with targeted sessions - 
of course.

>b) we need (in a very limited number of cases), the ability to force the 
>packet to the locally attached prefix. This only occurs where the local 
>cost is high compared to the cost back to the failed attachment point. But 
>when we DO need it, the use of a tunnel is a convenient means of 
>signalling this. I'm not sure how else to do it, other than using a label.
>
>Of course ONE "solution" would be to REQUIRE the costs to be set sensibly :-)

I like that one :-)  but you knew I would!  We may need to define what that 
means better or have a way of determining that it is the case.

>>ii.     To support LDP, every tunnel requires a targeted LDP session.  If 
>>multi-homed prefixes are common, then this becomes a full mesh for 
>>LDP.  That isn't acceptable.
>
>Agreed.
>
>>  Of course, multi-homed prefixes may be much more infrequent for LDP 
>> than for IP; for example, there is no reason to advertise a separate FEC 
>> for the subnet of a link.  However, multi-homed prefixes are a concern 
>> for LDP for at least the inter-area, AS External, and BGP routes.
>>iii.    If traffic is encapsulated to a node's regular address, because 
>>that traffic is destined to a prefix advertised by the node, how does the 
>>receiving node know to remove the encapsulation and forward the packet 
>>inside  all in the fast path?  Is this a just a question of different 
>>handling based on the header type inside the outer encapsulation (for GRE)?
>
>Yes.

OK.  The traffic wouldn't be directed up to the control plane because it 
was GRE encapsulated??  And had a special header type for this 
purpose?  Certainly I can see something like this working with an LDP LSP, 
b/c the label would just get it to that router & then be popped & the 
packet forwarded based on what's underneath.

>>iv.     Perhaps these issues could be handled by determining a 
>>next-next-hop that avoids the failure to reach an appropriate 
>>advertiser.   Of course, this is a different set/type of computation.
>
>Could you explain that suggestion please?

Well, if there is a neighbor's neighbor whose path to the multi-homed 
prefix doesn't go through the failure & this can be determined, then the 
traffic could be tunneled to that neighbor's neighbor & then normally 
forwarded from there.

Basically, if one knows the SPT from each neighbor's neighbor & can reach 
all of those neighbor's neighbors without going through the failure, then 
it might provide an alternate.  The issue there is first that the path to a 
neighbor's neighbor might go via the failed element & not have an 
appropriate notvia  & second the effort of computing and considering the 
different SPTs.

Does that make more sense?

>>5.      SRLGs and Broadcast Links:  There seem to be a number of possible 
>>ways to handle SRLGs and broadcast links, each of which provides a 
>>different trade-off in terms of  coverage, computation, and extra Notvia 
>>addresses.
>
>Yes.
>
>>   There are basically 4 approaches at this point.
>>a.      First, In order to compute a notvia alternate that avoids a link, 
>>the primary neighbor, and all SRLGs that the link is part of, it is 
>>necessary to have a separate topology and associated SPF computation for 
>>each link that is a member of an SRLG or a broadcast link.   This 
>>requires also a substantially larger number of Notvia addresses and the 
>>corresponding mechanisms to determine how and when to allocate and 
>>de-allocate them.
>
>.. and could potentially result in a combinatorial explosion if we weren't 
>very careful.

I do think of this as having the highest potential to be the "too 
complicated & run-away" scenario.

>>b.      Second, one could use a topology that removed the primary 
>>neighbor and see whether SRLG protection can be obtained either along S's 
>>path or along any path of a neighbor of S that is also loop-free.
>
>Could you explain that a bit more please?

This is the concept of looking for a loop-free neighbor to the notvia 
address whose path there happens to give SRLG protection.  We'd discussed 
this one the last day at IETF.

>>c.      Third, when a Notvia address indicates to avoid a node, one could 
>>remove not merely the node & the uni-directional links to and from that 
>>node, but also any other links that are in a common SRLG with any of the 
>>links to or from the removed node.  This is pessimistic  but allows some 
>>SRLG protection without increased computation or Notvia addresses.
>
>Yes. This is nice and simple, but as you have pointed out above, could 
>easily result in an inability to find a viable repair.

At the risk of additional complication, one could have it configurable as 
to the specific handling of SRLGs.  For instance, most link/node/SRLG would 
be handled with a single notvia per node  - and then there could be 
configured specific links that required their own notvia.   Of course, that 
adds substantial extra complexity.  Is it necessary?

>>d.      Fourth, one could simply track the SRLGs encountered along the 
>>Notvia path; this just reports whether the alternate provides SRLG 
>>protection without any effort to obtain it.
>
>Yes. Interesting. I wonder how useful this would be.

Well, it could feedback to a network design at least - to give an 
indication of coverage.  Also, not all SRLGs have the same likelihood to 
fail.  So, if avoiding all doesn't work, perhaps one can avoid the most 
risky ones - and then report the protection against the failures of the 
others.

This is part of my concern/question about what notvia alternate is computed 
if the best protection isn't possible.

>>6.      Implementability:  Clearly, the draft describes the basic idea 
>>for Notvia addresses, but there are a fair number of 
>>implementation/protocol decisions that need to be made before this can 
>>become anything more than an interesting idea.
>
>Sure. There are quite a few design decisions and tradeoffs as indicated 
>above that need tieing down.
>
>>7.      There is a definite need to describe the convergence case 
>>better.   This is how the transition from using the alternate to the 
>>network being converged happens, such that the alternate remains functional.
>>a.      For instance, if the node E fails, then the Notvia address E_!S 
>>will no longer be advertised.  If S was getting link protection (because 
>>that was all that was possible, for instance) by tunneling traffic to 
>>E_!S, it is important that this traffic be properly discarded when E's 
>>addresses go away.   This implies that there needs to be a default 
>>blackhole for Notvia addresses.
>
>I don't quite understand your concern here. If E goes away and S is 
>sending to E_!S, then the neighbors of E will drop the packets because we 
>don't repair a notvia address.

I'm thinking of this as the more specific prefix goes away.   Without a 
specific blackhole for the group of prefixes, why wouldn't the packets take 
that instead?  I.e., if the notvia address is 10.1.1.1 and there's a 
default route for 10.1/16  (or for 0.0.0.0/0), then the packet would pick 
up the latter when the notvia address is removed.

>Or are you concerned that after convergence, there will be nodes which 
>don't even have a forwarding entry forE_!S. By this time I don't think 
>that S (or anyone else) should still be using that address, but even if it 
>were, the absence of a forwarding entry would (SHOULD) cause the packet to 
>be dropped. Is this all you are saying?

I was also worrying about the above in reference to the notvia 
addresses.  While it is possible to say that changes to notvia 
addresses  shouldn't be installed until after the network has otherwise 
converged, that sort of detail needs to be clarified.

>>b.      Another example is when node E fails, the next-next-hop B must 
>>continue to advertise the Notvia address B_!E until the network converges 
>>so that S can continue to tunnel traffic to B_!E as the alternate.
>
>Yes. Our view was that no changes would be made to notvia advertisement or 
>more specifically notvia FIB entries until after convergence is over. Of 
>course there is an issue as to how you tell when that has happened, but 
>the timers associated with loop free convergence probably give a good 
>indication.

Conceptually, I agree.  Having a primary topology to forward the traffic on 
while the backup one reconverges helps.

>>c.      It is possible to get a micro-forwarding loop affecting a Notvia 
>>address as a result of a less severe failure than anticipated.  For 
>>instance, consider the following topology.
>>              [D]
>>               |
>>           1   |
>>      [E]-----[F]-\
>>       |       |   \ 10
>>     1 |R    1 |R   \
>>       |   5   |     \
>>      [S]-----[H]----[I]
>>                  2
>>
>>      Link S->E and Link H->F are in SRLG R
>>
>>When node E fails, if I converges before H, there will be a loop 
>>affecting the Notvia address being used to reach F without going through 
>>any of Link S->E, E or SRLG R.
>
>We discussed this privately, and I still don't see how loops could arrise 
>even if the notvia FIB were recomputed before normal convergence is 
>complete. But I think it is better to delay the notvia FIB changes anyway.

Just for clarity (hopefully),  before the failure, H computes the path for 
F_!E, the address of F's that is notvia E, to go via I and then to 
F.  After the failure of E, if H installs the changed notvia address F_!E 
the path is directly to F, b/c node E no longer has SRLG R associated with 
any of E's up links.

>>d.      How do exceptions work?  Particularly in regards to an IP-in-IP 
>>encapsulation such as GRE, it doesn't seem like MTU exceeded cases can be 
>>handled cleanly  either by use of DF or by doing IP fragmentation and 
>>then the reassembly at the end of the tunnel.  This seems like a problem 
>>for all ICMP packets; how could a source understand the header inside for 
>>a TTL expired, for instance.
>
>I'll leave this for Stewart (tunnel) Bryant!

For LDP, there are mechanisms (layer violations though they are) to handle 
exceptions generating ICMP packets.

>>e.      For IP-in-IP tunnels, another concern is flow diversity.  The IP 
>>source and destination addresses are used to determine a flow; this flow 
>>identification may then be used for a variety of purposes, including 
>>ECMP.  By putting all the traffic to a variety of destinations inside the 
>>same header, the ability to take advantage of flow diversity appears to 
>>have disappeared.   This could possibly be solved by putting the original 
>>source address into the encapsulating header?  Are there other approaches?
>
>and this.

Again, for an LDP tunnel, many routers can look under the label and 
consider the IP packet inside for flow identification.

Alia


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Wed Apr 27 05:48:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQj9a-0005p8-Ab; Wed, 27 Apr 2005 05:48:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQj9V-0005kb-Cb
	for rtgwg@megatron.ietf.org; Wed, 27 Apr 2005 05:48:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19100
	for <rtgwg@ietf.org>; Wed, 27 Apr 2005 05:48:15 -0400 (EDT)
Received: from weird-brew.cisco.com ([144.254.15.118]
	helo=av-tac-bru.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DQjM6-0006di-Ft
	for rtgwg@ietf.org; Wed, 27 Apr 2005 06:01:20 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j3R9llY19283; Wed, 27 Apr 2005 11:47:47 +0200 (CEST)
Received: from [144.254.14.128] (dhcp-peg2-vl21-144-254-14-128.cisco.com
	[144.254.14.128])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j3R9lkK11171; Wed, 27 Apr 2005 11:47:46 +0200 (CEST)
In-Reply-To: <5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
References: <5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0a929cce554b7ce3f7b5e942f2690e11@cisco.com>
Content-Transfer-Encoding: 7bit
From: stefano previdi <sprevidi@cisco.com>
Date: Wed, 27 Apr 2005 11:49:27 +0200
To: Alia Atlas <aatlas@avici.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

Alia, Mike,

just one comment on not-via addresses...

On Apr 27, 2005, at 4:56 AM, Alia Atlas wrote:

> Mike,
>
> At 10:35 AM 4/26/2005, mike shand wrote:
>> At 15:07 25/03/2005 -0500, Alia Atlas wrote:
>>
>>> Second is the list of downsides with the approach.  The main concern 
>>> is that the mechanism becomes too complex such that the trade-off 
>>> between its complexity and the full coverage is not desirable.
>>> 1.      This requires a large number of additional IP addresses in 
>>> the IGP.  The same number of additional FECs is required to support 
>>> LDP.
>>
>> Yes, it does. In the simplest case of link and node protection, and 
>> ignoring LANs it requires 2 addresses per protected link. It is 
>> expected that these would come out of a "private" address space, and 
>> hence wouldn't consume real addresses. Indeed for security reasons it 
>> is preferable that they are private addresses.
>>
>> I don't think this number is "too many". The question is how does 
>> this number increase when we add LANs and SRLGs.
>
> It would be useful to hear some additional opinions on the impact of 
> adding a large number of addresses.  The other question is what is the 
> boundary when it becomes a serious concern.

I believe there are ways of implicitly advertise these
addresses (i.e.: the router advertises a kind of a summary
from which the interface not-via addresses are derived).
For example, a router receiving an LSP/LSA will do:

- check if the originator has ipfrr enabled on one
   or more interfaces (capability TLV ?)
- the originator advertised a summary not-via address
   (new not-via summary address TLV ?)
- check what are the originator neighbors for which
   protection has been enabled and derive which not-via
   address has to be used for which neighbor (neighbor
   subTLV with a few bits identifier correlated to the
   not-via address to use)

In this case the igp won't suffer much from these
additional addresses and I believe we have most of the
bits we need to do that...

s.


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Wed Apr 27 10:52:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQntR-0003go-1t; Wed, 27 Apr 2005 10:52:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQntN-0003cU-Li
	for rtgwg@megatron.ietf.org; Wed, 27 Apr 2005 10:51:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21742
	for <rtgwg@ietf.org>; Wed, 27 Apr 2005 10:51:55 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQo5z-0006RL-4W
	for rtgwg@ietf.org; Wed, 27 Apr 2005 11:05:03 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 27 Apr 2005 16:51:43 +0200
Received: from cisco.com (dhcp-rea-gp250-64-103-65-209.cisco.com
	[64.103.65.209])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3REpZ54017192; 
	Wed, 27 Apr 2005 16:51:35 +0200 (MEST)
Message-ID: <426FA6E7.5050903@cisco.com>
Date: Wed, 27 Apr 2005 15:51:19 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alia Atlas <aatlas@avici.com>
References: <5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
In-Reply-To: <5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 12866e56e287fcb9ed724727fee710b4
Content-Transfer-Encoding: 7bit
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

First of all I largely agree with Mike's email,
but then that's not going to surprise anyone :)

Alia Atlas wrote:

> Mike,
> 
> At 10:35 AM 4/26/2005, mike shand wrote:
> 
>> At 15:07 25/03/2005 -0500, Alia Atlas wrote:
>>
>>> Second is the list of downsides with the approach.  The main concern 
>>> is that the mechanism becomes too complex such that the trade-off 
>>> between its complexity and the full coverage is not desirable.
>>> 1.      This requires a large number of additional IP addresses in 
>>> the IGP.  The same number of additional FECs is required to support LDP.
>>
>>
>> Yes, it does. In the simplest case of link and node protection, and 
>> ignoring LANs it requires 2 addresses per protected link. It is 
>> expected that these would come out of a "private" address space, and 
>> hence wouldn't consume real addresses. Indeed for security reasons it 
>> is preferable that they are private addresses.
>>
>> I don't think this number is "too many". The question is how does this 
>> number increase when we add LANs and SRLGs.
> 
> 
> It would be useful to hear some additional opinions on the impact of 
> adding a large number of addresses.  The other question is what is the 
> boundary when it becomes a serious concern.

Also to understand whether the issue is the number of addresses per se
or the inflation of the routing protocol message size.


> 
>>> 2.      Explicit tunnels are needed, which means that targeted LDP 
>>> sessions are necessary to have this support LDP traffic.
>>
>>
>> Yes. In the case of node protection we could also using Naiming's 
>> scheme of next-next hop LDP advertisement.
> 
> 
> True - but I'd want to think about the implications in terms of 
> additional communication & periods of instability/inaccuracy of 
> knowledge.    It also doesn't handle the multi-homed prefix case for the 
> case when the path isn't via the next-next-hop.
> 

OK. I think that we need to work on some state transition description
to make sure that all the bases are covered, and that we have
a common view of the states.

The complexity of MHP is really the complexity of MHP per se, rather
than the complexity of NV.

We have four options:

1) Restrict the reach of the repair to max two hops and
maybe use Naiming's LDP extension.
2) Tunnel the packet (using NV, PQ or whatever) and learn the label
at the far end.
3) Tunnel the packet and then strip all labels and do an IP lookup.
4) Figure out some other method of delivering the packet n hops away
in the base topology (such as n-hop u-turn).

Each of these approaches seems to have it's issues, and it's
a question of picking the least unpalatable.

> 
>>>  This is a particular concern for multi-homed prefixes; I'll describe 
>>> my concerns on this later.
>>
>>
>> Yes. This is a concern for LDP. I don't like the idea of targeted LDP 
>> sessions. Two possibilities come to mind
>>
>> a) each node with an attached MHP distributes an additional label for 
>> that prefix which has the semantics that when you pop that address you 
>> MUST forward the underlying IP packet "directly".
>>
>> b) an alternative which doesn't require additional labels, but DOES 
>> require a new "well known" label with the above semantics.
>>
>> Neither are very attractive, but perhaps more attractive than the 
>> directed LDP sessions.
> 
> 
> Both of these presume the ability to route based on the nested addresses 
> of the packet.  In general, I don't think that this is a valid 
> assumption.  Consider, for instance, the case of a BGP-free core.  
> Traffic is directed towards an ASBR in a different area (that is 
> multi-homed to the one being considered).  In that case, the ABR may not 
> have the BGP routes to be able to correctly forward the packet based on 
> its IP address.  There are also a number of scenarios where what is 
> underneath the top LDP label is another MPLs label & not routable at all.

In which case we either have to:

a) Run the directed LDP session
b) Give up
c) Think of something else.

A for else might be domain wide labels, but I remember the last
time that was proposed in MPLS WG:)

Are there any other for-else's that are better?


> 
>>> 3.      Substantial IGP changes are required to handle the additional 
>>> Notvia addresses.
>>
>>
>> Substantial is perhaps a bit strong. We need to advertise the not-via 
>> address and its association. For IS-IS its pretty straightforward. 
>> OSPF, by its very nature, may be a little more tricky.
> 
> 
> More substantial than a few bits :-)  The main issue here is just the 
> interop and migration concerns.

I don't understand. The IGP will flood the TLV's we have in mind.
Non-NV routers will be excluded from base. Could you expand?

> 
>>> 5.      The management of the Notvia addresses & of the tunnels can 
>>> create longer time periods where protection isn't available for a 
>>> part of the network (the new link or node, etc.).
>>
>>
>> I don't think the tunnels add to the time at all. They are after all 
>> just FIB entries. Distributing the notvia addresses for a new 
>> node/link will occur at the same time as distributing the information 
>> about the link/node in the first place. I don't think it significantly 
>> increases the delay.
>>
>> There is of course the time it takes to recompute notvia routes, but 
>> we think this will be well under a second.
>>
>> These aspects certainly need thinking about, but they don't seem to 
>> pose insurmountable issues.
> 
> 
> I agree that they're not insurmountable - but just require consideration.
> 
>>> Third, there are a number of issues that I feel need considerable 
>>> discussion to try and resolve.  I will try to go through each in turn 
>>> and explain what I think the various aspects of each are.  Each of 
>>> these issues has the possibility to resolve in such a way that the 
>>> Notvia Addresses approach becomes overly complex.
>>
>>
>> Yes. That is a temptation we need to resist!
> 
> 
> It's frequently a coverage versus complexity trade-off, where each 
> decision is along the slippery slope - alas!
> 
>>> b.      It is desirable to have some dampening on the withdrawal of 
>>> Notvia addresses to minimize thrashing.
>>
>>
>> The allocation of notvia addresses to links certainly shouldn't be 
>> changed as a result of not "needing" the notvia address when the 
>> object with which it is associated goes away. It should also get back 
>> the same notvia address when it comes back. But I don't think there 
>> are any particular issues associated with them disappearing and 
>> reappearing in the LSPs.
>>
>> Do you have any specific issues in mind?
> 
> 
> Only keeping the notvia addresses around until after the network has 
> converged...  If the notvia address is withdrawn with the link that's 
> failed, then traffic may still be using that alternate.

Since we are going to use controlled rather than uncontrolled
convergence we can include managing the NV entries in the FIB.
You are right to point out that we have not described how to do this.

> 
>>> c.      If configured in blocks, it would be extremely desirable to 
>>> have the same Notvia address mean the same thing through multiple 
>>> reboots, etc.  It'd be good to have some means of consistent 
>>> association.  This is for easy manageability.
>>
>>
>> Yes, definitely.
> 
> 
> For the case where the notvia address is for a neighbor, it's not always 
> that straightforward - unless one ends up advertising multiple notvia 
> addresses for the same neighbor, depending on the number of parallel 
> links.  This is mostly engineering, I think.
> 
>>> d.      When a new link or neighbor comes up, there will be a longer 
>>> period of time when an alternate isn't available because the Notvia 
>>> address hasn't been advertised yet.  These periods without protection 
>>> need to be clearly understood and minimized.
>>
>>
>> Yes. I'm not convinced there is a particular problem here, but it does 
>> need thinking through carefully.
> 
> 
> Agreed.
> 
> 
>>> e.      There may be scalability concerns based on the number of 
>>> Notvia addresses and LDP FECs required.  For instance, as described 
>>> in the draft, it is basically the number of uni-directional links in 
>>> the topology.  This is ignoring the extras for broadcast links.  To 
>>> fully & certainly provide SRLG protection if at all feasible, would 
>>> require that each router advertise a Notvia address for every 
>>> uni-directional link into every neighbor of that router.  This would 
>>> result in K*L additional addresses, where K is the average number of 
>>> neighbors & L is the number of uni-directional links in the topology.
>>
>>
>> Yes. This is a major concern, and we need to devise ways of solving 
>> SRLGs etc. which minimize the potential proliferation of addresses.
>> We need to get the right tradeoff here between optimal solutions and 
>> complexity.
> 
> 
> Agreed.  We need to understand the impact of additional addresses to 
> know the complexity cost of that versus the reduced coverage of 
> selecting a less complete approach to broadcast link and SRLG protection.
> 
>>> 2.      Insufficiently diverse topology:  It is possible that a 
>>> network topology cannot provide an alternate that suffices for link, 
>>> node and SRLG protection.  It isn't clear to me how to compute a 
>>> "best-available" alternate using this approach.  For instance, if one 
>>> can get link protection, but not node protection, how would that be 
>>> determined, computed and assigned?  This becomes much more of a 
>>> concern for SRLG protection & for topologies where failures have 
>>> already occurred and the network has converged for those & needs 
>>> protection in the event of an additional failure.
>>
>>
>> Clearly it is always possible to create a topology which contains 
>> single points of failure and is inherently irreparable. This is part 
>> of the tradeoff we need to address when thinking about SRLGs, since 
>> taking a simple but pessimistic approach to SRLG can result in this 
>> sort of failure. This seems to be a property of the problem rather 
>> than any particular solution.
> 
> 
> Let me try to explain this a bit better.  Say there's a topology that, 
> for a particular next-hop & next-next-hop, can only provide an alternate 
> that gives link and node protection but not SRLG protection.  Now, how 
> does the notvia addresses method compute an alternate?  If the method is 
> pruning the topology of the relevant link, node & SRLGs, no alternate 
> will be found.  However, it was possible to compute & use an alternate 
> that gives the link & node protection.  

I need to think about this.

> The similar case can easily 
> occur with link & node protection.  Say S has two parallel links to E; 
> if the first fails, S could use the other to get link protection  - but 
> there is no node-protecting alternate.  How does S determine this?  What 
> is the fall-back strategy in the case that no "full-protection" 
> alternate is available?

In this case

S fails E, and computes the NV paths to its neighbors.
If any or all of these are unreachable it uses a link
repair to E_!S to reach them as described in Section 4.2
of the draft. If E_!S does not exist as in the case above,
S then looks to see if the parallel link exists.

Of course in the absence of SRLG, this topology contains
a SPF for node protection and will always be expected to have
limited repair coverage.

You are correct that this all needs describing in detail.

> 
> 
>>> 3.      Failure Diagnosis versus Pessimism:  As written, the draft 
>>> discusses the idea of doing failure diagnosis using BFD.  As Stewart, 
>>> Mike & I have discussed, this isn't possible for SRLG failures, 
>>> although it is possible for broadcast links.
>>
>>
>> Yes, and this relates to (2) above.
>>
>>> a.      I am concerned about adding the failure diagnosis.  This is 
>>> yet another level of complexity for implementation.  It also has 
>>> ramifications for the forwarding plane, because of the need to store 
>>> multiple alternates to use & have multiple states to check to decide 
>>> what to use.
>>
>>
>> Yes. It would be nice not to have to do it, but that is back to the 
>> tradeoff above.
> 
> 
> Complexity vs. coverage?  I'm very fond, unsurprisingly, of options that 
> don't require hardware changes... so I judge that the complexity is 
> rather high to support this one - as well as more error-prone (see 
> comment on unreliable diagnosis).
> 
>>> b.      An example of a concern with the BFD diagnosis is that all 
>>> interfaces on a node that has failed are not certain to fail exactly 
>>> simultaneously or even within a sub-50ms bounded window.  It is 
>>> entirely possible that BFD sessions are terminated on different 
>>> line-cards, that detect the router failure at slightly different 
>>> times and stop forwarding traffic, therefore, at slightly different 
>>> times.
>>
>>
>> Yes. There is the possibility of misdiagnosis in this case if the 
>> second failure occurs too long after the first. I suppose this then 
>> looks like two separate failures. Clearly an unreliable diagnosis is 
>> probably worse than no diagnosis at all. We need to get some handle on 
>> how realistic or not this scenario is.
> 
> 
> Well, I think it is exceedingly realistic :-)
> For a non-power related failure, routers with separate forwarding & 
> control planes may take varying amounts of time for the line-cards to 
> all realize that the route controller is down.

Well maybe for power-failures as well :)

The pathology of this sort of failure is highly implementation dependent.
Say BFD was running on the LC, but the switch fabric was down.
You could end up with the neighbors thinking that the router was still
up, but it was non-functional. Eventually routing would notice the
absence of routing hellos, unless of course, these had also been
delegated :) Perhaps we need to run BFD to the neighbor's neighbors
on the direct path?

The problem is that we rapidly get on a complexity spiral that
becomes intractable.

We clearly to write down a set of project scoping rules for the
types of failure that we will and will not deal with.

> 
>>> c.      The other approach is to pessimistically eliminate all 
>>> routers connected to the broadcast link as well as the broadcast 
>>> link; this may not provide an alternate.
>>
>>
>> Yes. While simple, it runs into the problem of being a single (albeit 
>> large) point of failure. Its the same trade-off as above.
> 
> 
> Don't they all reduce to that?
> 
>>>   It also needs to be thought through what issues might exist if the 
>>> topologies used for the SPF vary slightly for each router that is on 
>>> the broadcast link, since each will, as described, not prune itself 
>>> out when doing the computation; of course, there could be an approach 
>>> where the same topology can be used everywhere.
>>
>>
>> I'm not really sure what you mean here.
> 
> 
> Let me try and explain it a bit.  Perhaps I'm missing something.   In 
> the case where a notvia topology results in pruning the router doing the 
> computation, what forms the root of the SPT?   Say routers A, B and C 
> are all connected to a broadcast link X and want to compute a notvia X 
> address as described in (c) by pruning the pseudo-node related to X as 
> well as A, B, and C.   Now, router A prunes the pseudo-node, A, B and C 
> from the topology; what does A use as the root?  IF A only prunes the 
> pseudo-node, B and C to compute notvia X, B only prunes the pseudo-node, 
> A, and C, and C only prunes the pseudo-node, A and B,  and all other 
> routers prune the pseudo-node, A, B, and C, can there be any issues with 
> a consistently computed & non-looping path for notvia X?
> 
> I think it may not be an issue - b/c once the traffic leaves A, B or C, 
> it will never return - but it at least needs some thought, since this is 
> a bit different from what's traditionally been done.

Agreed, we need to write down the algorithm and subject it to review.
> 
>>>  It isn't clear to me what Notvia addresses would be needed to 
>>> express "don't go through this pseudo-node or any nodes attached to 
>>> it"; I don't think that it is simply the Notvia address for avoiding 
>>> a particular node.
>>
>>
>> No, it would need a specific notvia address bound to the LAN interface.
> 
> 
> Agree
> 
>>> 4.      Multi-homed Prefixes:  I am quite concerned about the 
>>> mechanisms suggested in the draft.
>>> a.      First, I really do not like the idea of having separate 
>>> forwarding for "local" prefixes that come out of a tunnel.  What is a 
>>> local prefix?  For instance, does this mean that an ABR has to 
>>> forward traffic different depending on which area traffic from the 
>>> tunnel has come from?  I am concerned about how this would scale; 
>>> maybe only 2 FIBs are needed (one for backbone & one for other), but 
>>> it may be worse to handle AS external routes.  I know that Stewart, 
>>> Mike, Joel, Albert and I had discussed/agreed to put this idea out of 
>>> scope  at least for the moment.
>>
>>
>> Clearly the problem needs solving, especially since prefixes which are 
>> multihomed are frequently the most important prefixes (which is WHY 
>> they are multihomed in the first place).
> 
> 
> inconvenient that!
> 
>>> b.      I am quite concerned about having tunnels to the advertisers 
>>> of the prefixes.
>>> i.      There needs to be a mechanism to determine whether the 
>>> advertiser of a prefix will forward the packet in a loop-free fashion 
>>> to avoid the failure point.  The separate forwarding for "local" 
>>> prefixes avoided the need for this determination, but at more 
>>> substantial cost.
>>
>>
>> There seem to be two aspects to this.
>>
>> a) we need the ability to get the packet to the "second-best" 
>> attachment point for the prefix without it being "sucked back" to the 
>> failure. This in general requires a tunnel, except for the cases where 
>> a neighbor of the node detecting the failure has an LFA to the second 
>> best attachment point. Clearly this could be used in preference to a 
>> tunnel where available, but at the expense of additional complexity. 
>> However this is really just an extension of the general principle that 
>> we should use "basic" (i.e. LFA) repair to cream off traffic which 
>> doesn't NEED to be tunnelled.
> 
> 
> Yes - though the tunnels bring out the LDP issues with targeted sessions 
> - of course.
> 
>> b) we need (in a very limited number of cases), the ability to force 
>> the packet to the locally attached prefix. This only occurs where the 
>> local cost is high compared to the cost back to the failed attachment 
>> point. But when we DO need it, the use of a tunnel is a convenient 
>> means of signalling this. I'm not sure how else to do it, other than 
>> using a label.
>>
>> Of course ONE "solution" would be to REQUIRE the costs to be set 
>> sensibly :-)
> 
> 
> I like that one :-)  but you knew I would!  We may need to define what 
> that means better or have a way of determining that it is the case.
> 
>>> ii.     To support LDP, every tunnel requires a targeted LDP 
>>> session.  If multi-homed prefixes are common, then this becomes a 
>>> full mesh for LDP.  That isn't acceptable.
>>
>>
>> Agreed.
>>
>>>  Of course, multi-homed prefixes may be much more infrequent for LDP 
>>> than for IP; for example, there is no reason to advertise a separate 
>>> FEC for the subnet of a link.  However, multi-homed prefixes are a 
>>> concern for LDP for at least the inter-area, AS External, and BGP 
>>> routes.
>>> iii.    If traffic is encapsulated to a node's regular address, 
>>> because that traffic is destined to a prefix advertised by the node, 
>>> how does the receiving node know to remove the encapsulation and 
>>> forward the packet inside  all in the fast path?  Is this a just a 
>>> question of different handling based on the header type inside the 
>>> outer encapsulation (for GRE)?
>>
>>
>> Yes.
> 
> 
> OK.  The traffic wouldn't be directed up to the control plane because it 
> was GRE encapsulated??  

GRE always pops the header at the tunnel endpoint. That is how it
works!

> And had a special header type for this purpose?  
> Certainly I can see something like this working with an LDP LSP, b/c the 
> label would just get it to that router & then be popped & the packet 
> forwarded based on what's underneath.
> 

Perhaps an MPLS label of some sort the way we thought of doing directed
forwarding and the way that Mark Townsley proposed doing IP VPN?

>>> iv.     Perhaps these issues could be handled by determining a 
>>> next-next-hop that avoids the failure to reach an appropriate 
>>> advertiser.   Of course, this is a different set/type of computation.
>>
>>
>> Could you explain that suggestion please?
> 
> 
> Well, if there is a neighbor's neighbor whose path to the multi-homed 
> prefix doesn't go through the failure & this can be determined, then the 
> traffic could be tunneled to that neighbor's neighbor & then normally 
> forwarded from there.

Yes, but you only get two hop reachability. Perhaps you do this,
and then do directed LDP for the remaining (perhaps 2%) of cases.
The problem I have with this is the added complexity.

> 
> Basically, if one knows the SPT from each neighbor's neighbor & can 
> reach all of those neighbor's neighbors without going through the 
> failure, then it might provide an alternate.  The issue there is first 
> that the path to a neighbor's neighbor might go via the failed element & 
> not have an appropriate notvia  & second the effort of computing and 
> considering the different SPTs.
> 
> Does that make more sense?

Yes.

> 
>>> 5.      SRLGs and Broadcast Links:  There seem to be a number of 
>>> possible ways to handle SRLGs and broadcast links, each of which 
>>> provides a different trade-off in terms of  coverage, computation, 
>>> and extra Notvia addresses.
>>
>>
>> Yes.
>>
>>>   There are basically 4 approaches at this point.
>>> a.      First, In order to compute a notvia alternate that avoids a 
>>> link, the primary neighbor, and all SRLGs that the link is part of, 
>>> it is necessary to have a separate topology and associated SPF 
>>> computation for each link that is a member of an SRLG or a broadcast 
>>> link.   This requires also a substantially larger number of Notvia 
>>> addresses and the corresponding mechanisms to determine how and when 
>>> to allocate and de-allocate them.
>>
>>
>> .. and could potentially result in a combinatorial explosion if we 
>> weren't very careful.
> 
> 
> I do think of this as having the highest potential to be the "too 
> complicated & run-away" scenario.
> 
>>> b.      Second, one could use a topology that removed the primary 
>>> neighbor and see whether SRLG protection can be obtained either along 
>>> S's path or along any path of a neighbor of S that is also loop-free.
>>
>>
>> Could you explain that a bit more please?
> 
> 
> This is the concept of looking for a loop-free neighbor to the notvia 
> address whose path there happens to give SRLG protection.  We'd 
> discussed this one the last day at IETF.
> 
>>> c.      Third, when a Notvia address indicates to avoid a node, one 
>>> could remove not merely the node & the uni-directional links to and 
>>> from that node, but also any other links that are in a common SRLG 
>>> with any of the links to or from the removed node.  This is 
>>> pessimistic  but allows some SRLG protection without increased 
>>> computation or Notvia addresses.
>>
>>
>> Yes. This is nice and simple, but as you have pointed out above, could 
>> easily result in an inability to find a viable repair.
> 
> 
> At the risk of additional complication, one could have it configurable 
> as to the specific handling of SRLGs.  For instance, most link/node/SRLG 
> would be handled with a single notvia per node  - and then there could 
> be configured specific links that required their own notvia.   Of 
> course, that adds substantial extra complexity.  Is it necessary?
> 
>>> d.      Fourth, one could simply track the SRLGs encountered along 
>>> the Notvia path; this just reports whether the alternate provides 
>>> SRLG protection without any effort to obtain it.
>>
>>
>> Yes. Interesting. I wonder how useful this would be.
> 
> 
> Well, it could feedback to a network design at least - to give an 
> indication of coverage.  Also, not all SRLGs have the same likelihood to 
> fail.  So, if avoiding all doesn't work, perhaps one can avoid the most 
> risky ones - and then report the protection against the failures of the 
> others.
> 
> This is part of my concern/question about what notvia alternate is 
> computed if the best protection isn't possible.
> 
>>> 6.      Implementability:  Clearly, the draft describes the basic 
>>> idea for Notvia addresses, but there are a fair number of 
>>> implementation/protocol decisions that need to be made before this 
>>> can become anything more than an interesting idea.
>>
>>
>> Sure. There are quite a few design decisions and tradeoffs as 
>> indicated above that need tieing down.
>>
>>> 7.      There is a definite need to describe the convergence case 
>>> better.   This is how the transition from using the alternate to the 
>>> network being converged happens, such that the alternate remains 
>>> functional.
>>> a.      For instance, if the node E fails, then the Notvia address 
>>> E_!S will no longer be advertised.  If S was getting link protection 
>>> (because that was all that was possible, for instance) by tunneling 
>>> traffic to E_!S, it is important that this traffic be properly 
>>> discarded when E's addresses go away.   This implies that there needs 
>>> to be a default blackhole for Notvia addresses.
>>
>>
>> I don't quite understand your concern here. If E goes away and S is 
>> sending to E_!S, then the neighbors of E will drop the packets because 
>> we don't repair a notvia address.
> 
> 
> I'm thinking of this as the more specific prefix goes away.   Without a 
> specific blackhole for the group of prefixes, why wouldn't the packets 
> take that instead?  I.e., if the notvia address is 10.1.1.1 and there's 
> a default route for 10.1/16  (or for 0.0.0.0/0), then the packet would 
> pick up the latter when the notvia address is removed.

Yes, you are quite right. We need a NV black hole.

> 
>> Or are you concerned that after convergence, there will be nodes which 
>> don't even have a forwarding entry forE_!S. By this time I don't think 
>> that S (or anyone else) should still be using that address, but even 
>> if it were, the absence of a forwarding entry would (SHOULD) cause the 
>> packet to be dropped. Is this all you are saying?
> 
> 
> I was also worrying about the above in reference to the notvia 
> addresses.  While it is possible to say that changes to notvia 
> addresses  shouldn't be installed until after the network has otherwise 
> converged, that sort of detail needs to be clarified.
> 
>>> b.      Another example is when node E fails, the next-next-hop B 
>>> must continue to advertise the Notvia address B_!E until the network 
>>> converges so that S can continue to tunnel traffic to B_!E as the 
>>> alternate.
>>
>>
>> Yes. Our view was that no changes would be made to notvia 
>> advertisement or more specifically notvia FIB entries until after 
>> convergence is over. Of course there is an issue as to how you tell 
>> when that has happened, but the timers associated with loop free 
>> convergence probably give a good indication.
> 
> 
> Conceptually, I agree.  Having a primary topology to forward the traffic 
> on while the backup one reconverges helps.
> 
>>> c.      It is possible to get a micro-forwarding loop affecting a 
>>> Notvia address as a result of a less severe failure than 
>>> anticipated.  For instance, consider the following topology.
>>>              [D]
>>>               |
>>>           1   |
>>>      [E]-----[F]-\
>>>       |       |   \ 10
>>>     1 |R    1 |R   \
>>>       |   5   |     \
>>>      [S]-----[H]----[I]
>>>                  2
>>>
>>>      Link S->E and Link H->F are in SRLG R
>>>
>>> When node E fails, if I converges before H, there will be a loop 
>>> affecting the Notvia address being used to reach F without going 
>>> through any of Link S->E, E or SRLG R.
>>
>>
>> We discussed this privately, and I still don't see how loops could 
>> arrise even if the notvia FIB were recomputed before normal 
>> convergence is complete. But I think it is better to delay the notvia 
>> FIB changes anyway.
> 
> 
> Just for clarity (hopefully),  before the failure, H computes the path 
> for F_!E, the address of F's that is notvia E, to go via I and then to 
> F.  After the failure of E, if H installs the changed notvia address 
> F_!E the path is directly to F, b/c node E no longer has SRLG R 
> associated with any of E's up links.
> 

I think that the core issue here is the case of a failure during the
reconvergence of the repair topology. Is that in scope?

>>> d.      How do exceptions work?  Particularly in regards to an 
>>> IP-in-IP encapsulation such as GRE, it doesn't seem like MTU exceeded 
>>> cases can be handled cleanly  either by use of DF or by doing IP 
>>> fragmentation and then the reassembly at the end of the tunnel.  This 
>>> seems like a problem for all ICMP packets; how could a source 
>>> understand the header inside for a TTL expired, for instance.
>>
>>
>> I'll leave this for Stewart (tunnel) Bryant!
> 
> 
> For LDP, there are mechanisms (layer violations though they are) to 
> handle exceptions generating ICMP packets.

The interesting question is who needs to know of the MTU problem?

If you tell the host, then by the time it adjusts it's MTU the
network will likely have reconverged anyway.

However if you tell repairing router (which is what will happen
with a tunnels packet), it can alarm and let the network
administrators know that there is problem with IPFRR config.

For this to work, the MTU at the edges needs to be lower than the
MTU in the core.

> 
>>> e.      For IP-in-IP tunnels, another concern is flow diversity.  The 
>>> IP source and destination addresses are used to determine a flow; 
>>> this flow identification may then be used for a variety of purposes, 
>>> including ECMP.  By putting all the traffic to a variety of 
>>> destinations inside the same header, the ability to take advantage of 
>>> flow diversity appears to have disappeared.   This could possibly be 
>>> solved by putting the original source address into the encapsulating 
>>> header?  Are there other approaches?
>>
>>
>> and this.
> 
> 
> Again, for an LDP tunnel, many routers can look under the label and 
> consider the IP packet inside for flow identification.

I was going to say:

Given that basic cuts in before NV, I think that the only case where
this is a problem is when you have a router with max ECMP = say 2 which
selects two from more than two, and the next hop on one of them fails.
This is surely a corner case?

Then Mike pointed out that we had said that we would use ECMP in the
draft, and yes there is a problem. Again we need to think about the
implications, because it's not clear what we should do.

- Stewart


> Alia
> 
> 
> _______________________________________________
> Rtgwg mailing list
> Rtgwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/rtgwg
> 
> 

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Wed Apr 27 11:00:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQo26-0005dL-Pl; Wed, 27 Apr 2005 11:00:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQo25-0005dD-BK
	for rtgwg@megatron.ietf.org; Wed, 27 Apr 2005 11:00:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22508
	for <rtgwg@ietf.org>; Wed, 27 Apr 2005 11:00:55 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQoEi-0006fZ-9K
	for rtgwg@ietf.org; Wed, 27 Apr 2005 11:14:03 -0400
Received: from aatlas-lt.avici.com (aatlas-lt.avici.com [10.2.20.92])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3RF0W7l013636;
	Wed, 27 Apr 2005 11:00:32 -0400
Message-Id: <5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 27 Apr 2005 11:00:28 -0400
To: stefano previdi <sprevidi@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <0a929cce554b7ce3f7b5e942f2690e11@cisco.com>
References: <5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: mike shand <mshand@cisco.com>, rtgwg@ietf.org
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

Stefano,

If I understand correctly, you are suggesting that the advertising of the 
addresses could be a starting address (for the block) and then each 
neighbor sub-TLV could give an index within that block?  Of course, that 
introduces the constraint that the notvia addresses given by a particular 
router have to be contiguous - and brings up issues when the block size 
needs to increase.  It sounds a lot like the label distribution mechanism 
used in RFC 2547.

Another question (somewhat related) would be how to handle a neighbor 
connected by multiple parallel links.   Logically, one only needs a single 
notvia address for the neighbor - but one doesn't want the one used to be 
dependent on which of the parallel links came up first.  This argues that 
there may be multiple notvia addresses advertised for a particular neighbor 
- for the parallel links case.

Any extensions would want to handle this as well, I think.

Alia

At 05:49 AM 4/27/2005, stefano previdi wrote:
>Alia, Mike,
>
>just one comment on not-via addresses...
>
>On Apr 27, 2005, at 4:56 AM, Alia Atlas wrote:
>
>>Mike,
>>
>>At 10:35 AM 4/26/2005, mike shand wrote:
>>>At 15:07 25/03/2005 -0500, Alia Atlas wrote:
>>>
>>>>Second is the list of downsides with the approach.  The main concern is 
>>>>that the mechanism becomes too complex such that the trade-off between 
>>>>its complexity and the full coverage is not desirable.
>>>>1.      This requires a large number of additional IP addresses in the 
>>>>IGP.  The same number of additional FECs is required to support LDP.
>>>
>>>Yes, it does. In the simplest case of link and node protection, and 
>>>ignoring LANs it requires 2 addresses per protected link. It is expected 
>>>that these would come out of a "private" address space, and hence 
>>>wouldn't consume real addresses. Indeed for security reasons it is 
>>>preferable that they are private addresses.
>>>
>>>I don't think this number is "too many". The question is how does this 
>>>number increase when we add LANs and SRLGs.
>>
>>It would be useful to hear some additional opinions on the impact of 
>>adding a large number of addresses.  The other question is what is the 
>>boundary when it becomes a serious concern.
>
>I believe there are ways of implicitly advertise these
>addresses (i.e.: the router advertises a kind of a summary
>from which the interface not-via addresses are derived).
>For example, a router receiving an LSP/LSA will do:
>
>- check if the originator has ipfrr enabled on one
>   or more interfaces (capability TLV ?)
>- the originator advertised a summary not-via address
>   (new not-via summary address TLV ?)
>- check what are the originator neighbors for which
>   protection has been enabled and derive which not-via
>   address has to be used for which neighbor (neighbor
>   subTLV with a few bits identifier correlated to the
>   not-via address to use)
>
>In this case the igp won't suffer much from these
>additional addresses and I believe we have most of the
>bits we need to do that...
>
>s.
>
>
>_______________________________________________
>Rtgwg mailing list
>Rtgwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/rtgwg



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Wed Apr 27 12:03:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQp0y-0007zQ-Ij; Wed, 27 Apr 2005 12:03:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQp0x-0007zK-F2
	for rtgwg@megatron.ietf.org; Wed, 27 Apr 2005 12:03:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27338
	for <rtgwg@ietf.org>; Wed, 27 Apr 2005 12:03:49 -0400 (EDT)
Received: from weird-brew.cisco.com ([144.254.15.118]
	helo=av-tac-bru.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DQpDc-00082G-Qm
	for rtgwg@ietf.org; Wed, 27 Apr 2005 12:16:58 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j3RG3G518277; Wed, 27 Apr 2005 18:03:16 +0200 (CEST)
Received: from [192.168.1.112] (ams-clip-vpn-dhcp4588.cisco.com [10.61.81.235])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j3RG3DK25776; Wed, 27 Apr 2005 18:03:13 +0200 (CEST)
In-Reply-To: <5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
References: <5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9d78dabc1de6ed06ca7b3bd993e54158@cisco.com>
Content-Transfer-Encoding: 7bit
From: stefano previdi <sprevidi@cisco.com>
Date: Wed, 27 Apr 2005 18:04:51 +0200
To: Alia Atlas <aatlas@avici.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Content-Transfer-Encoding: 7bit
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

Alia,

On Apr 27, 2005, at 5:00 PM, Alia Atlas wrote:

> Stefano,
>
> If I understand correctly, you are suggesting that the advertising of 
> the addresses could be a starting address (for the block) and then 
> each neighbor sub-TLV could give an index within that block?

Not exactly. I was suggesting that each router will
advertise a kind of not-via summary address in addition
to the host part of it on its neighbor TLVs.

Example: Router X advertises 10.1.1/24 as the summary
not-via address and then, for each of its neighbor on its
LSP, router X will add following subTLVs:

	neighbor A, not-via-host-address: 1
	neighbor B, not-via-host-address: 5
	neighbor C, not-via-host-address: 20
	...

so, any other router in the area, when receiving router X
LSP, can derive that router X not-via addresses will be:

	Neighbor-A: 10.1.1.1/32
	Neighbor-B: 10.1.1.5/32
	Neighbor-C: 10.1.1.20/32

And nothing prevents router Y to advertise the _same_
summary but with different host addresses.

>  Of course, that introduces the constraint that the notvia addresses 
> given by a particular router have to be contiguous

I don't think so.

>  - and brings up issues when the block size needs to increase.  It 
> sounds a lot like the label distribution mechanism used in RFC 2547.

I still believe these addresses will likely be taken from
the private address space so the issue is more how to
reduce the effective information you advertise rather than
the address space you're going to use (10/8 will just work
fine).

> Another question (somewhat related) would be how to handle a neighbor 
> connected by multiple parallel links.   Logically, one only needs a 
> single notvia address for the neighbor - but one doesn't want the one 
> used to be dependent on which of the parallel links came up first.  
> This argues that there may be multiple notvia addresses advertised for 
> a particular neighbor - for the parallel links case.

in this case I believe the router will do ipfrr among ECMP
members so we need an address in case both link fails.

s.

>
> Any extensions would want to handle this as well, I think.
>
> Alia
>
> At 05:49 AM 4/27/2005, stefano previdi wrote:
>> Alia, Mike,
>>
>> just one comment on not-via addresses...
>>
>> On Apr 27, 2005, at 4:56 AM, Alia Atlas wrote:
>>
>>> Mike,
>>>
>>> At 10:35 AM 4/26/2005, mike shand wrote:
>>>> At 15:07 25/03/2005 -0500, Alia Atlas wrote:
>>>>
>>>>> Second is the list of downsides with the approach.  The main 
>>>>> concern is that the mechanism becomes too complex such that the 
>>>>> trade-off between its complexity and the full coverage is not 
>>>>> desirable.
>>>>> 1.      This requires a large number of additional IP addresses in 
>>>>> the IGP.  The same number of additional FECs is required to 
>>>>> support LDP.
>>>>
>>>> Yes, it does. In the simplest case of link and node protection, and 
>>>> ignoring LANs it requires 2 addresses per protected link. It is 
>>>> expected that these would come out of a "private" address space, 
>>>> and hence wouldn't consume real addresses. Indeed for security 
>>>> reasons it is preferable that they are private addresses.
>>>>
>>>> I don't think this number is "too many". The question is how does 
>>>> this number increase when we add LANs and SRLGs.
>>>
>>> It would be useful to hear some additional opinions on the impact of 
>>> adding a large number of addresses.  The other question is what is 
>>> the boundary when it becomes a serious concern.
>>
>> I believe there are ways of implicitly advertise these
>> addresses (i.e.: the router advertises a kind of a summary
>> from which the interface not-via addresses are derived).
>> For example, a router receiving an LSP/LSA will do:
>>
>> - check if the originator has ipfrr enabled on one
>>   or more interfaces (capability TLV ?)
>> - the originator advertised a summary not-via address
>>   (new not-via summary address TLV ?)
>> - check what are the originator neighbors for which
>>   protection has been enabled and derive which not-via
>>   address has to be used for which neighbor (neighbor
>>   subTLV with a few bits identifier correlated to the
>>   not-via address to use)
>>
>> In this case the igp won't suffer much from these
>> additional addresses and I believe we have most of the
>> bits we need to do that...
>>
>> s.
>>
>>
>> _______________________________________________
>> Rtgwg mailing list
>> Rtgwg@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rtgwg
>


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Wed Apr 27 13:56:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQqm2-00071G-E8; Wed, 27 Apr 2005 13:56:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQqly-000718-VY
	for rtgwg@megatron.ietf.org; Wed, 27 Apr 2005 13:56:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06837
	for <rtgwg@ietf.org>; Wed, 27 Apr 2005 13:56:29 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQqyc-00022w-Jx
	for rtgwg@ietf.org; Wed, 27 Apr 2005 14:09:38 -0400
Received: from aatlas-lt.avici.com (aatlas-lt.avici.com [10.2.20.92])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3RHtW7l016493;
	Wed, 27 Apr 2005 13:55:32 -0400
Message-Id: <5.1.0.14.2.20050427122250.020483f8@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 27 Apr 2005 13:55:25 -0400
To: Stewart Bryant <stbryant@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <426FA6E7.5050903@cisco.com>
References: <5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7c7a0f28a102b9cb6317697abf1cf76
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

At 10:51 AM 4/27/2005, Stewart Bryant wrote:
>First of all I largely agree with Mike's email,
>but then that's not going to surprise anyone :)

Simply shocking :-)

>Alia Atlas wrote:
>
>>Mike,
>>At 10:35 AM 4/26/2005, mike shand wrote:
>>
>>>At 15:07 25/03/2005 -0500, Alia Atlas wrote:
>>>
>>>>Second is the list of downsides with the approach.  The main concern is 
>>>>that the mechanism becomes too complex such that the trade-off between 
>>>>its complexity and the full coverage is not desirable.
>>>>1.      This requires a large number of additional IP addresses in the 
>>>>IGP.  The same number of additional FECs is required to support LDP.
>>>
>>>
>>>Yes, it does. In the simplest case of link and node protection, and 
>>>ignoring LANs it requires 2 addresses per protected link. It is expected 
>>>that these would come out of a "private" address space, and hence 
>>>wouldn't consume real addresses. Indeed for security reasons it is 
>>>preferable that they are private addresses.
>>>
>>>I don't think this number is "too many". The question is how does this 
>>>number increase when we add LANs and SRLGs.
>>
>>It would be useful to hear some additional opinions on the impact of 
>>adding a large number of addresses.  The other question is what is the 
>>boundary when it becomes a serious concern.
>
>Also to understand whether the issue is the number of addresses per se
>or the inflation of the routing protocol message size.

Sure.  We need to understand clearly the potential issues causing the 
constraints.

>>>>2.      Explicit tunnels are needed, which means that targeted LDP 
>>>>sessions are necessary to have this support LDP traffic.
>>>
>>>Yes. In the case of node protection we could also using Naiming's scheme 
>>>of next-next hop LDP advertisement.
>>
>>True - but I'd want to think about the implications in terms of 
>>additional communication & periods of instability/inaccuracy of 
>>knowledge.    It also doesn't handle the multi-homed prefix case for the 
>>case when the path isn't via the next-next-hop.
>
>OK. I think that we need to work on some state transition description
>to make sure that all the bases are covered, and that we have
>a common view of the states.
>
>The complexity of MHP is really the complexity of MHP per se, rather
>than the complexity of NV.
>
>We have four options:
>
>1) Restrict the reach of the repair to max two hops and
>maybe use Naiming's LDP extension.

yes - maybe it's good enough?  It'd be good to get the multi-homed prefixes 
considered in the network topology & simulations so we can see.

>2) Tunnel the packet (using NV, PQ or whatever) and learn the label
>at the far end.

In the general worst-case, doesn't scale.  How realistic that worst-case 
isn't as clear.

>3) Tunnel the packet and then strip all labels and do an IP lookup.

Not really an option - assuming we want to have things like pseudo-wires 
running under the LDP :-)

>4) Figure out some other method of delivering the packet n hops away
>in the base topology (such as n-hop u-turn).

Possible, but it does get uglier to compute.

>Each of these approaches seems to have it's issues, and it's
>a question of picking the least unpalatable.

Agree

>>>>  This is a particular concern for multi-homed prefixes; I'll describe 
>>>> my concerns on this later.
>>>
>>>
>>>Yes. This is a concern for LDP. I don't like the idea of targeted LDP 
>>>sessions. Two possibilities come to mind
>>>
>>>a) each node with an attached MHP distributes an additional label for 
>>>that prefix which has the semantics that when you pop that address you 
>>>MUST forward the underlying IP packet "directly".
>>>
>>>b) an alternative which doesn't require additional labels, but DOES 
>>>require a new "well known" label with the above semantics.
>>>
>>>Neither are very attractive, but perhaps more attractive than the 
>>>directed LDP sessions.
>>
>>Both of these presume the ability to route based on the nested addresses 
>>of the packet.  In general, I don't think that this is a valid 
>>assumption.  Consider, for instance, the case of a BGP-free core.
>>Traffic is directed towards an ASBR in a different area (that is 
>>multi-homed to the one being considered).  In that case, the ABR may not 
>>have the BGP routes to be able to correctly forward the packet based on 
>>its IP address.  There are also a number of scenarios where what is 
>>underneath the top LDP label is another MPLs label & not routable at all.
>
>In which case we either have to:
>
>a) Run the directed LDP session

See above for my thoughts on the options.

>b) Give up

nope - too stubborn :-)

>c) Think of something else.
>
>A for else might be domain wide labels, but I remember the last
>time that was proposed in MPLS WG:)

sure, but we're seeing upstream label distribution being proposed again too :-)
It is true that anything else seems likely to require some change/addition 
to the MPLS semantics - and that would be more challenging to consider.

>Are there any other for-else's that are better?

>>>>3.      Substantial IGP changes are required to handle the additional 
>>>>Notvia addresses.
>>>
>>>
>>>Substantial is perhaps a bit strong. We need to advertise the not-via 
>>>address and its association. For IS-IS its pretty straightforward. OSPF, 
>>>by its very nature, may be a little more tricky.
>>
>>More substantial than a few bits :-)  The main issue here is just the 
>>interop and migration concerns.
>
>I don't understand. The IGP will flood the TLV's we have in mind.
>Non-NV routers will be excluded from base. Could you expand?

Oh, this is just the more general worry of getting interoperability without 
very clear specification.  I've nothing specific here yet - just a 
background concern that it be thought about.

I do agree that excluding those routers that don't advertise the capability 
takes care of a large section of the issues.

>>>>b.      It is desirable to have some dampening on the withdrawal of 
>>>>Notvia addresses to minimize thrashing.
>>>
>>>The allocation of notvia addresses to links certainly shouldn't be 
>>>changed as a result of not "needing" the notvia address when the object 
>>>with which it is associated goes away. It should also get back the same 
>>>notvia address when it comes back. But I don't think there are any 
>>>particular issues associated with them disappearing and reappearing in 
>>>the LSPs.
>>>
>>>Do you have any specific issues in mind?
>>
>>Only keeping the notvia addresses around until after the network has 
>>converged...  If the notvia address is withdrawn with the link that's 
>>failed, then traffic may still be using that alternate.
>
>Since we are going to use controlled rather than uncontrolled
>convergence we can include managing the NV entries in the FIB.
>You are right to point out that we have not described how to do this.

What are you defining as controlled convergence?  Is this the wait until 
the network's done otherwise & then do the notvia addresses?  That'll work 
- but it's a bit different from the general controlled convergence for the 
primary topology.

>>>>2.      Insufficiently diverse topology:  It is possible that a network 
>>>>topology cannot provide an alternate that suffices for link, node and 
>>>>SRLG protection.  It isn't clear to me how to compute a 
>>>>"best-available" alternate using this approach.  For instance, if one 
>>>>can get link protection, but not node protection, how would that be 
>>>>determined, computed and assigned?  This becomes much more of a concern 
>>>>for SRLG protection & for topologies where failures have already 
>>>>occurred and the network has converged for those & needs protection in 
>>>>the event of an additional failure.
>>>
>>>
>>>Clearly it is always possible to create a topology which contains single 
>>>points of failure and is inherently irreparable. This is part of the 
>>>tradeoff we need to address when thinking about SRLGs, since taking a 
>>>simple but pessimistic approach to SRLG can result in this sort of 
>>>failure. This seems to be a property of the problem rather than any 
>>>particular solution.
>>
>>Let me try to explain this a bit better.  Say there's a topology that, 
>>for a particular next-hop & next-next-hop, can only provide an alternate 
>>that gives link and node protection but not SRLG protection.  Now, how 
>>does the notvia addresses method compute an alternate?  If the method is 
>>pruning the topology of the relevant link, node & SRLGs, no alternate 
>>will be found.  However, it was possible to compute & use an alternate 
>>that gives the link & node protection.
>
>I need to think about this.
>
>>The similar case can easily occur with link & node protection.  Say S has 
>>two parallel links to E; if the first fails, S could use the other to get 
>>link protection  - but there is no node-protecting alternate.  How does S 
>>determine this?  What is the fall-back strategy in the case that no 
>>"full-protection" alternate is available?
>
>In this case
>
>S fails E, and computes the NV paths to its neighbors.
>If any or all of these are unreachable it uses a link
>repair to E_!S to reach them as described in Section 4.2
>of the draft. If E_!S does not exist as in the case above,
>S then looks to see if the parallel link exists.
>
>Of course in the absence of SRLG, this topology contains
>a SPF for node protection and will always be expected to have
>limited repair coverage.

Thanks.  This helps clarify the behavior when the link is pt-to-pt.

For the broadcast link case, I can see  greater difficulties - because it 
looks like a local SRLG  to a large extent.  Any thoughts there?

>You are correct that this all needs describing in detail.

That's what revisions are for :-)

>>>>b.      An example of a concern with the BFD diagnosis is that all 
>>>>interfaces on a node that has failed are not certain to fail exactly 
>>>>simultaneously or even within a sub-50ms bounded window.  It is 
>>>>entirely possible that BFD sessions are terminated on different 
>>>>line-cards, that detect the router failure at slightly different times 
>>>>and stop forwarding traffic, therefore, at slightly different times.
>>>
>>>
>>>Yes. There is the possibility of misdiagnosis in this case if the second 
>>>failure occurs too long after the first. I suppose this then looks like 
>>>two separate failures. Clearly an unreliable diagnosis is probably worse 
>>>than no diagnosis at all. We need to get some handle on how realistic or 
>>>not this scenario is.
>>
>>Well, I think it is exceedingly realistic :-)
>>For a non-power related failure, routers with separate forwarding & 
>>control planes may take varying amounts of time for the line-cards to all 
>>realize that the route controller is down.
>
>Well maybe for power-failures as well :)
>
>The pathology of this sort of failure is highly implementation dependent.
>Say BFD was running on the LC, but the switch fabric was down.
>You could end up with the neighbors thinking that the router was still
>up, but it was non-functional. Eventually routing would notice the
>absence of routing hellos, unless of course, these had also been
>delegated :) Perhaps we need to run BFD to the neighbor's neighbors
>on the direct path?

This is a large part of what I see to be the problem with thinking of BFD 
as being a mechanism for detecting router failure.  Perhaps there are those 
with more BFD experience who can point out how it could work?

To my mind, either the BFD session is running on the line-card, in which 
case one can possibly imagine it being implemented in a scalable way such 
that packets are sent out at least every 5-10ms, such that a failure could 
be detected within 20ms & then repaired in the remaining 30ms, or the BFD 
session isn't running on the line-card, in which case generating packets 
every 5-10ms per interface reliably seems a bit of a stretch.

It seems to me to get the desired speed for failure detection that BFD 
would need to be done on the line-card & preferably in hardware.  This 
makes BFD good for detecting link failures, but not so much for detecting 
router failures.

As for the line-card being up, but the switch fabric down, I'd hope that 
the router internals would have a way of detecting that & bringing the 
line-card down when appropriate.  That's internal implementation anyhow.

BFD to neighbor's neighbor would at least validate the forwarding path all 
the way to that neighbor's neighbor - but it gives a larger number of BFD 
sessions & there is also the difficulty of interpreting the failure back to 
the affected routes.  For instance, what about the case where the 
downstream neighbor may (or may not?) ECMP to two of its neighbors.  If the 
BFD session to one of those goes down, does S do repair?

>The problem is that we rapidly get on a complexity spiral that
>becomes intractable.

This is why I really do not like the idea of trying to do failure diagnosis 
via BFD.  I don't think it is realistic to believe that router failure can 
be identified as such by BFD within 20-30ms.

>We clearly to write down a set of project scoping rules for the
>types of failure that we will and will not deal with.

I don't think the issue here is the type of failure that is being handled - 
that is determined by the avoidance of the alternate.  The question here is 
the ability to diagnosis failure types on the fly.

>>>>   It also needs to be thought through what issues might exist if the 
>>>> topologies used for the SPF vary slightly for each router that is on 
>>>> the broadcast link, since each will, as described, not prune itself 
>>>> out when doing the computation; of course, there could be an approach 
>>>> where the same topology can be used everywhere.
>>>
>>>
>>>I'm not really sure what you mean here.
>>
>>Let me try and explain it a bit.  Perhaps I'm missing something.   In the 
>>case where a notvia topology results in pruning the router doing the 
>>computation, what forms the root of the SPT?   Say routers A, B and C are 
>>all connected to a broadcast link X and want to compute a notvia X 
>>address as described in (c) by pruning the pseudo-node related to X as 
>>well as A, B, and C.   Now, router A prunes the pseudo-node, A, B and C 
>>from the topology; what does A use as the root?  IF A only prunes the 
>>pseudo-node, B and C to compute notvia X, B only prunes the pseudo-node, 
>>A, and C, and C only prunes the pseudo-node, A and B,  and all other 
>>routers prune the pseudo-node, A, B, and C, can there be any issues with 
>>a consistently computed & non-looping path for notvia X?
>>I think it may not be an issue - b/c once the traffic leaves A, B or C, 
>>it will never return - but it at least needs some thought, since this is 
>>a bit different from what's traditionally been done.
>
>Agreed, we need to write down the algorithm and subject it to review.

The more I think about it, the more comfortable I am - but as we've agreed, 
it needs clear description & thought about the differences & their 
implications.

>>>>  Of course, multi-homed prefixes may be much more infrequent for LDP 
>>>> than for IP; for example, there is no reason to advertise a separate 
>>>> FEC for the subnet of a link.  However, multi-homed prefixes are a 
>>>> concern for LDP for at least the inter-area, AS External, and BGP routes.
>>>>iii.    If traffic is encapsulated to a node's regular address, because 
>>>>that traffic is destined to a prefix advertised by the node, how does 
>>>>the receiving node know to remove the encapsulation and forward the 
>>>>packet inside  all in the fast path?  Is this a just a question of 
>>>>different handling based on the header type inside the outer 
>>>>encapsulation (for GRE)?
>>>
>>>
>>>Yes.
>>
>>OK.  The traffic wouldn't be directed up to the control plane because it 
>>was GRE encapsulated??
>
>GRE always pops the header at the tunnel endpoint. That is how it
>works!

OK.  Thanks.  I'm (obviously) not that familiar with GRE.

>>And had a special header type for this purpose?
>>Certainly I can see something like this working with an LDP LSP, b/c the 
>>label would just get it to that router & then be popped & the packet 
>>forwarded based on what's underneath.
>
>Perhaps an MPLS label of some sort the way we thought of doing directed
>forwarding and the way that Mark Townsley proposed doing IP VPN?

Could you explain more?  I'm not sure what you're picturing the label being 
used for.

>>>>iv.     Perhaps these issues could be handled by determining a 
>>>>next-next-hop that avoids the failure to reach an appropriate 
>>>>advertiser.   Of course, this is a different set/type of computation.
>>>
>>>
>>>Could you explain that suggestion please?
>>
>>Well, if there is a neighbor's neighbor whose path to the multi-homed 
>>prefix doesn't go through the failure & this can be determined, then the 
>>traffic could be tunneled to that neighbor's neighbor & then normally 
>>forwarded from there.
>
>Yes, but you only get two hop reachability. Perhaps you do this,
>and then do directed LDP for the remaining (perhaps 2%) of cases.
>The problem I have with this is the added complexity.

Yes, it would require additional computation & anytime you have two ways to 
do something, it gets more complicated.   On the other hand, a 
(potentially) full mesh of LDP sessions isn't simple either!

If the frequency of multi-homed prefixes that can't be protected via this 
is small - and the network design to gain protection isn't too complicated 
to understand, then it'd help.  For, say, the inter-area case, a typical 
cross-hatch connection probably works fine.

>>>>7.      There is a definite need to describe the convergence case 
>>>>better.   This is how the transition from using the alternate to the 
>>>>network being converged happens, such that the alternate remains functional.
>>>>a.      For instance, if the node E fails, then the Notvia address E_!S 
>>>>will no longer be advertised.  If S was getting link protection 
>>>>(because that was all that was possible, for instance) by tunneling 
>>>>traffic to E_!S, it is important that this traffic be properly 
>>>>discarded when E's addresses go away.   This implies that there needs 
>>>>to be a default blackhole for Notvia addresses.
>>>
>>>
>>>I don't quite understand your concern here. If E goes away and S is 
>>>sending to E_!S, then the neighbors of E will drop the packets because 
>>>we don't repair a notvia address.
>>
>>I'm thinking of this as the more specific prefix goes away.   Without a 
>>specific blackhole for the group of prefixes, why wouldn't the packets 
>>take that instead?  I.e., if the notvia address is 10.1.1.1 and there's a 
>>default route for 10.1/16  (or for 0.0.0.0/0), then the packet would pick 
>>up the latter when the notvia address is removed.
>
>Yes, you are quite right. We need a NV black hole.

I think this is just a detail to be written down then.

>>>>c.      It is possible to get a micro-forwarding loop affecting a 
>>>>Notvia address as a result of a less severe failure than 
>>>>anticipated.  For instance, consider the following topology.
>>>>              [D]
>>>>               |
>>>>           1   |
>>>>      [E]-----[F]-\
>>>>       |       |   \ 10
>>>>     1 |R    1 |R   \
>>>>       |   5   |     \
>>>>      [S]-----[H]----[I]
>>>>                  2
>>>>
>>>>      Link S->E and Link H->F are in SRLG R
>>>>
>>>>When node E fails, if I converges before H, there will be a loop 
>>>>affecting the Notvia address being used to reach F without going 
>>>>through any of Link S->E, E or SRLG R.
>>>
>>>
>>>We discussed this privately, and I still don't see how loops could 
>>>arrise even if the notvia FIB were recomputed before normal convergence 
>>>is complete. But I think it is better to delay the notvia FIB changes anyway.
>>
>>Just for clarity (hopefully),  before the failure, H computes the path 
>>for F_!E, the address of F's that is notvia E, to go via I and then to 
>>F.  After the failure of E, if H installs the changed notvia address F_!E 
>>the path is directly to F, b/c node E no longer has SRLG R associated 
>>with any of E's up links.
>
>I think that the core issue here is the case of a failure during the
>reconvergence of the repair topology. Is that in scope?

??  No, I think this is the issue of whether the repair topology 
reconverges at the same time as the primary topology or it is delayed.  If 
it is at the same time, the problem above happens.  I think we're all 
agreed that delaying the repair topology convergence until the primary 
topology convergence is complete is the way to go.

>>>>d.      How do exceptions work?  Particularly in regards to an IP-in-IP 
>>>>encapsulation such as GRE, it doesn't seem like MTU exceeded cases can 
>>>>be handled cleanly  either by use of DF or by doing IP fragmentation 
>>>>and then the reassembly at the end of the tunnel.  This seems like a 
>>>>problem for all ICMP packets; how could a source understand the header 
>>>>inside for a TTL expired, for instance.
>>>
>>>
>>>I'll leave this for Stewart (tunnel) Bryant!
>>
>>For LDP, there are mechanisms (layer violations though they are) to 
>>handle exceptions generating ICMP packets.
>
>The interesting question is who needs to know of the MTU problem?
>
>If you tell the host, then by the time it adjusts it's MTU the
>network will likely have reconverged anyway.

It depends on how long the network is taking to get off the 
alternates.   That could be 10s or so - so there's a chance the host will 
be able to adjust its MTU usefully.

>However if you tell repairing router (which is what will happen
>with a tunnels packet), it can alarm and let the network
>administrators know that there is problem with IPFRR config.

But why does the ICMP packet need to travel back to the repairing 
router?  Why couldn't the router which sees an MTU exceeded addressed to a 
notvia address let the network administrators know?

>For this to work, the MTU at the edges needs to be lower than the
>MTU in the core.

Sure.  My  concern isn't so much for the MTU exceeded case as for the TTL 
expired case.  That's a common network debugging tool - and we'd want it to 
continue to work during repair.

>>>>e.      For IP-in-IP tunnels, another concern is flow diversity.  The 
>>>>IP source and destination addresses are used to determine a flow; this 
>>>>flow identification may then be used for a variety of purposes, 
>>>>including ECMP.  By putting all the traffic to a variety of 
>>>>destinations inside the same header, the ability to take advantage of 
>>>>flow diversity appears to have disappeared.   This could possibly be 
>>>>solved by putting the original source address into the encapsulating 
>>>>header?  Are there other approaches?
>>>
>>>
>>>and this.
>>
>>Again, for an LDP tunnel, many routers can look under the label and 
>>consider the IP packet inside for flow identification.
>
>I was going to say:
>
>Given that basic cuts in before NV, I think that the only case where
>this is a problem is when you have a router with max ECMP = say 2 which
>selects two from more than two, and the next hop on one of them fails.
>This is surely a corner case?
>
>Then Mike pointed out that we had said that we would use ECMP in the
>draft, and yes there is a problem. Again we need to think about the
>implications, because it's not clear what we should do.

If the paths for notvia addresses can be ECMP, then it becomes a 
concern.   Now, maybe it isn't necessary for those to be ECMP - or that 
likely.  But maybe it could be solved by pulling the real source IP address 
in the encapsulating packet header?

Alia



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Wed Apr 27 16:53:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQtX4-0003ov-Md; Wed, 27 Apr 2005 16:53:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQtX1-0003oq-N5
	for rtgwg@megatron.ietf.org; Wed, 27 Apr 2005 16:53:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05807
	for <rtgwg@ietf.org>; Wed, 27 Apr 2005 16:53:13 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQtjj-0001le-L2
	for rtgwg@ietf.org; Wed, 27 Apr 2005 17:06:25 -0400
Received: from aatlas-lt.avici.com (aatlas-lt.avici.com [10.2.20.92])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3RKqw7l018717;
	Wed, 27 Apr 2005 16:52:58 -0400
Message-Id: <5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 27 Apr 2005 16:52:58 -0400
To: stefano previdi <sprevidi@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <9d78dabc1de6ed06ca7b3bd993e54158@cisco.com>
References: <5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

Stefano,

At 12:04 PM 4/27/2005, stefano previdi wrote:
>On Apr 27, 2005, at 5:00 PM, Alia Atlas wrote:
>
>>Stefano,
>>
>>If I understand correctly, you are suggesting that the advertising of the 
>>addresses could be a starting address (for the block) and then each 
>>neighbor sub-TLV could give an index within that block?
>
>Not exactly. I was suggesting that each router will
>advertise a kind of not-via summary address in addition
>to the host part of it on its neighbor TLVs.
>
>Example: Router X advertises 10.1.1/24 as the summary
>not-via address and then, for each of its neighbor on its
>LSP, router X will add following subTLVs:
>
>         neighbor A, not-via-host-address: 1
>         neighbor B, not-via-host-address: 5
>         neighbor C, not-via-host-address: 20
>         ...
>
>so, any other router in the area, when receiving router X
>LSP, can derive that router X not-via addresses will be:
>
>         Neighbor-A: 10.1.1.1/32
>         Neighbor-B: 10.1.1.5/32
>         Neighbor-C: 10.1.1.20/32
>
>And nothing prevents router Y to advertise the _same_
>summary but with different host addresses.


OK.  This seems like it could be a useful way of reducing the actual bits 
advertised.  It does seem to me that it might be useful/desirable for a 
router to be able to advertise multiple summary addresses.

>>  Of course, that introduces the constraint that the notvia addresses 
>> given by a particular router have to be contiguous
>
>I don't think so.
>
>>  - and brings up issues when the block size needs to increase.  It 
>> sounds a lot like the label distribution mechanism used in RFC 2547.
>
>I still believe these addresses will likely be taken from
>the private address space so the issue is more how to
>reduce the effective information you advertise rather than
>the address space you're going to use (10/8 will just work
>fine).

True, but needing to use 10/8 would dictate the effective information 
required.  The ability to use multiple summaries could be useful to reduce 
this further.

I guess a question is whether this is the point of concern with the 
additional quantity of notvia addresses, such that it deserves substantial 
optimization.

>>Another question (somewhat related) would be how to handle a neighbor 
>>connected by multiple parallel links.   Logically, one only needs a 
>>single notvia address for the neighbor - but one doesn't want the one 
>>used to be dependent on which of the parallel links came up first.
>>This argues that there may be multiple notvia addresses advertised for a 
>>particular neighbor - for the parallel links case.
>
>in this case I believe the router will do ipfrr among ECMP
>members so we need an address in case both link fails.

I don't think so.  Consider that S is connected to E via a link & E is 
connected to F via two links.  Now, F will advertise at least one F_!E 
notvia address that S can use if its link to E fails (for traffic whose 
next-next-hop is F).  The question is how does F decide what address to use 
to mean F_!E.  It doesn't seem desirable (to me) to have the specific 
address used to vary - based on which link to E came up first or 
such.  Therefore, I'd assume that there could be multiple notvia addresses 
that mean F_!E.

Do you see a cleaner way to do this & still ensure consistent use of 
addresses through reboots, link state changes, etc?

Alia


>s.
>
>>
>>Any extensions would want to handle this as well, I think.
>>
>>Alia
>>
>>At 05:49 AM 4/27/2005, stefano previdi wrote:
>>>Alia, Mike,
>>>
>>>just one comment on not-via addresses...
>>>
>>>On Apr 27, 2005, at 4:56 AM, Alia Atlas wrote:
>>>
>>>>Mike,
>>>>
>>>>At 10:35 AM 4/26/2005, mike shand wrote:
>>>>>At 15:07 25/03/2005 -0500, Alia Atlas wrote:
>>>>>
>>>>>>Second is the list of downsides with the approach.  The main concern 
>>>>>>is that the mechanism becomes too complex such that the trade-off 
>>>>>>between its complexity and the full coverage is not desirable.
>>>>>>1.      This requires a large number of additional IP addresses in 
>>>>>>the IGP.  The same number of additional FECs is required to support LDP.
>>>>>
>>>>>Yes, it does. In the simplest case of link and node protection, and 
>>>>>ignoring LANs it requires 2 addresses per protected link. It is 
>>>>>expected that these would come out of a "private" address space, and 
>>>>>hence wouldn't consume real addresses. Indeed for security reasons it 
>>>>>is preferable that they are private addresses.
>>>>>
>>>>>I don't think this number is "too many". The question is how does this 
>>>>>number increase when we add LANs and SRLGs.
>>>>
>>>>It would be useful to hear some additional opinions on the impact of 
>>>>adding a large number of addresses.  The other question is what is the 
>>>>boundary when it becomes a serious concern.
>>>
>>>I believe there are ways of implicitly advertise these
>>>addresses (i.e.: the router advertises a kind of a summary
>>>from which the interface not-via addresses are derived).
>>>For example, a router receiving an LSP/LSA will do:
>>>
>>>- check if the originator has ipfrr enabled on one
>>>   or more interfaces (capability TLV ?)
>>>- the originator advertised a summary not-via address
>>>   (new not-via summary address TLV ?)
>>>- check what are the originator neighbors for which
>>>   protection has been enabled and derive which not-via
>>>   address has to be used for which neighbor (neighbor
>>>   subTLV with a few bits identifier correlated to the
>>>   not-via address to use)
>>>
>>>In this case the igp won't suffer much from these
>>>additional addresses and I believe we have most of the
>>>bits we need to do that...
>>>
>>>s.
>>>
>>>
>>>_______________________________________________
>>>Rtgwg mailing list
>>>Rtgwg@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/rtgwg



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Apr 28 06:24:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DR6Bi-0007c3-TT; Thu, 28 Apr 2005 06:24:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D5TFr-0000gB-Ml; Sun, 27 Feb 2005 13:34:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20381;
	Sun, 27 Feb 2005 13:34:56 -0500 (EST)
Received: from zmamail05.zma.compaq.com ([161.114.64.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D5TGP-0002wM-J9; Sun, 27 Feb 2005 13:35:35 -0500
Received: from tayexg12.americas.cpqcorp.net (tayexg12.americas.cpqcorp.net
	[16.103.130.127])
	by zmamail05.zma.compaq.com (Postfix) with ESMTP id 99237BAF2;
	Sun, 27 Feb 2005 13:34:46 -0500 (EST)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by
	tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 27 Feb 2005 13:34:46 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C51CFB.03194768"
Date: Sun, 27 Feb 2005 13:34:57 -0500
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B087EE13D@tayexc13.americas.cpqcorp.net>
X-MS-Has-Attach: yes
Thread-Topic: 6LSA IETF Drafts
Thread-Index: AcUa47LTX00DC0a+T8eCXKZuA1LeuwACWG8AAFdABJAAAMfkMA==
From: "Bound, Jim" <jim.bound@hp.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 27 Feb 2005 18:34:46.0455 (UTC)
	FILETIME=[031D5470:01C51CFB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0076290b21c69318492534f4e4dfda6a
X-Mailman-Approved-At: Thu, 28 Apr 2005 06:24:03 -0400
Cc: rtgwg@ietf.org
Subject: 6LSA IETF Drafts
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C51CFB.03194768
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

See below draft and two attached that will be available after the IETF.
It provides a solution for IPv6 Label Switch Architecture that does not
compete with MPLS or QOS work in progress in the industry at ITU, etc.

http://ietf.org/internet-drafts/draft-chakravorty-6lsa-01.txt=20

If some of you would do me a favor and review and send comments to Sham
Chakravorty schakra@mitre.org, Jim.Bound@nav6tf.org, and Kevin Zhang
kzhang@mitre.org I would appreciate it.  We will have a BOF most likely
on 6LSA at the Paris meeting to see if this would be its own working
group.  We will set up industry list for technical persons to work on it
until then if we get enough responses. I am pretty sure we should do
this here in the IETF not go to the ITU.  Also we will be at the
Minneapolis IETF so if you have in person comments that is appreciate
too.

Thanks
/jim


------_=_NextPart_001_01C51CFB.03194768
Content-Type: text/plain;
	name="draft-chakravorty-bcc-FEC-00.txt"
Content-Description: draft-chakravorty-bcc-FEC-00.txt
Content-Disposition: attachment;
	filename="draft-chakravorty-bcc-FEC-00.txt"
Content-Transfer-Encoding: base64

DQoNCkludGVybmV0IEVuZ2luZWVyaW5nIFRhc2sgRm9yY2UgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBKLiBCb3VuZA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTkF2NlRGDQpFeHBpcmVzOiBBdWd1c3QgMjEs
IDIwMDUgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUy4gQ2hha3Jhdm9ydHkNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEQu
IENoaXJpZWxlaXNvbg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgVGhlIE1JVFJFIENvcnBvcmF0aW9uDQogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRmVicnVhcnkgMjAsIDIwMDUNCg0KDQogICAg
ICAgICAgICAgICAgICAgIEJpbmRpbmcgUGFja2V0cyB0byBGRUNzIGluIDZMU0ENCiAgICAgICAg
ICAgICAgICAgICAgICBkcmFmdC1jaGFrcmF2b3J0eS1iY2MtZmVjLTAwDQoNClN0YXR1cyBvZiB0
aGlzIE1lbW8NCg0KICAgVGhpcyBkb2N1bWVudCBpcyBhbiBJbnRlcm5ldC1EcmFmdCBhbmQgaXMg
c3ViamVjdCB0byBhbGwgcHJvdmlzaW9ucw0KICAgb2Ygc2VjdGlvbiAzIG9mIFJGQyAzNjY3LiAg
Qnkgc3VibWl0dGluZyB0aGlzIEludGVybmV0LURyYWZ0LCBlYWNoDQogICBhdXRob3IgcmVwcmVz
ZW50cyB0aGF0IGFueSBhcHBsaWNhYmxlIHBhdGVudCBvciBvdGhlciBJUFIgY2xhaW1zIG9mDQog
ICB3aGljaCBoZSBvciBzaGUgaXMgYXdhcmUgaGF2ZSBiZWVuIG9yIHdpbGwgYmUgZGlzY2xvc2Vk
LCBhbmQgYW55IG9mDQogICB3aGljaCBoZSBvciBzaGUgYmVjb21lIGF3YXJlIHdpbGwgYmUgZGlz
Y2xvc2VkLCBpbiBhY2NvcmRhbmNlIHdpdGgNCiAgIFJGQyAzNjY4Lg0KDQogICBJbnRlcm5ldC1E
cmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0K
ICAgVGFzayBGb3JjZSAoSUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4g
IE5vdGUgdGhhdA0KICAgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUgd29ya2luZyBk
b2N1bWVudHMgYXMNCiAgIEludGVybmV0LURyYWZ0cy4NCg0KICAgSW50ZXJuZXQtRHJhZnRzIGFy
ZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzDQogICBh
bmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1l
bnRzIGF0IGFueQ0KICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0
LURyYWZ0cyBhcyByZWZlcmVuY2UNCiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0
aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiINCg0KICAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRl
cm5ldC1EcmFmdHMgY2FuIGJlIGFjY2Vzc2VkIGF0DQogICBodHRwOi8vd3d3LmlldGYub3JnL2ll
dGYvMWlkLWFic3RyYWN0cy50eHQuDQoNCiAgIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNo
YWRvdyBEaXJlY3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQNCiAgIGh0dHA6Ly93d3cuaWV0Zi5v
cmcvc2hhZG93Lmh0bWwuDQoNCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUgb24g
QXVndXN0IDIxLCAyMDA1Lg0KDQpDb3B5cmlnaHQgTm90aWNlDQoNCiAgIENvcHlyaWdodCAoQykg
VGhlIEludGVybmV0IFNvY2lldHkgKDIwMDUpLg0KDQpBYnN0cmFjdA0KDQogICBJRVRGIEludGVy
bmV0IERyYWZ0ICJJUHY2IExhYmVsIFN3aXRjaGluZyBBcmNoaXRlY3R1cmUgKDZMU0EpIiBbNkxT
QV0NCiAgIFsyXSBwcm9wb3NlcyB1c2luZyB0aGUgSVB2NiBGbG93IExhYmVsIGZpZWxkIHRvIHN3
aXRjaCBwYWNrZXRzDQogICB0aHJvdWdoIGFuIElQdjYgc3VibmV0d29yay4gIFRoZSB1c2Ugb2Yg
dGhlc2UgSVB2NiBMYWJlbCBTd2l0Y2hlZA0KICAgUGF0aHMgKDZMU1BzKSBjYW4gcHJvdmlkZSBt
ZWFucyBmb3IgdHJhZmZpYyBlbmdpbmVlcmluZyBhbmQNCiAgIHBvdGVudGlhbGx5IGluY3JlYXNl
IHRoZSBzcGVlZCBvZiBwYWNrZXRzIHRyYXZlcnNpbmcgYSByb3V0ZWQgbmV0d29yaw0KDQoNCg0K
Qm91bmQsIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjEsIDIwMDUgICAgICAgICAg
ICAgICAgIFtQYWdlIDFdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgIEJpbmRpbmcgUGFja2V0cyB0
byBGRUNzIGluIDZMU0EgICAgICAgIEZlYnJ1YXJ5IDIwMDUNCg0KDQogICB3aXRoIG5vIGluY3Jl
YXNlIGluIGJhbmR3aWR0aC4gIFRoZSA2TFNBIGRyYWZ0IGRlZmluZXMgdHdvIHByb2Nlc3NlczoN
CiAgIDEpIGdyb3VwaW5nIHBhY2tldHMgd2l0aCBpZGVudGljYWwgZm9yd2FyZGluZyBiZWhhdmlv
ciBpbnRvIGENCiAgIEZvcndhcmRpbmcgRXF1aXZhbGVuY2UgQ2xhc3MgKEZFQyksIDIpIGZvcndh
cmRpbmcgYWxsIHBhY2tldHMNCiAgIGJlbG9uZ2luZyB0byBhbiBGRUMgYWxvbmcgdGhlIHNhbWUg
cGF0aC4gIFRoZSBhc3NpZ25tZW50IG9mIHBhY2tldHMNCiAgIHRvIGFuIEZFQyBpcyBjYWxsZWQg
YmluZGluZy4gIFRoZSBwdXJwb3NlIG9mIHRoaXMgZG9jdW1lbnQgaXMgdG8NCiAgIGV4cGFuZCBv
biB0aGVzZSB0d28gcHJvY2Vzc2VzLCBkaXNjdXNzaW5nIHNwZWNpZmljIG1ldGhvZHMgb2YNCiAg
IHBlcmZvcm1pbmcgdGhlIHJlcXVpcmVkIGZ1bmN0aW9ucy4NCg0KVGFibGUgb2YgQ29udGVudHMN
Cg0KICAgMS4gIEludHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICAzDQogICAyLiAgVGVybWlub2xvZ3kgIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDMNCiAgIDMuICBCYWNrZ3JvdW5kIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNA0KICAg
NC4gIEZFQyBDb25zdHJ1Y3Rpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICA2DQogICAgIDQuMSAgIE1hbnVhbCBDb25maWd1cmF0aW9uIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDcNCiAgICAgNC4yICAgTmV0d29yayBNYW5hZ2Vt
ZW50IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNw0KICAgICA0LjMg
ICBQc2V1ZG9mbG93IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICA4DQogICAgIDQuNCAgIExhYmVsIERpc3RyaWJ1dGlvbiBQcm90b2NvbCAgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDkNCiAgIDUuICBCaW5kaW5nIElQdjYgUGFja2V0cyB0byBh
biBGRUMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgOQ0KICAgICA1LjEgICBNYW51
YWwgQ29uZmlndXJhdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEw
DQogICAgIDUuMiAgIEFsZ29yaXRobWljIEJpbmRpbmcgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gMTENCiAgICAgNS4zICAgRkVDIEJpbmRpbmcgdXNpbmcgU05NUCAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMg0KICAgNi4gIFNlY3VyaXR5IENvbnNp
ZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEyDQogICAg
IDYuMSAgIFVzZSBvZiBTTk1QICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gMTINCiAgICAgNi4yICAgVXNlIG9mIExhYmVsIERpc3RyaWJ1dGlvbiBQcm90b2Nv
bHMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMw0KICAgNy4gIFJlZmVyZW5jZXMgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEzDQogICA4LiAgQWNr
bm93bGVnZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gMTQNCiAgIDkuICBEaXNjbGFpbWVyIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAxNA0KICAgICAgIEF1dGhvcnMnIEFkZHJlc3NlcyAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE0DQogICAgICAgSW50ZWxsZWN0
dWFsIFByb3BlcnR5IGFuZCBDb3B5cmlnaHQgU3RhdGVtZW50cyAuIC4gLiAuIC4gLiAuIC4gMTUN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkJvdW5kLCBldCBhbC4g
ICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDIxLCAyMDA1ICAgICAgICAgICAgICAgICBbUGFnZSAy
XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICBCaW5kaW5nIFBhY2tldHMgdG8gRkVDcyBpbiA2TFNB
ICAgICAgICBGZWJydWFyeSAyMDA1DQoNCg0KMS4gIEludHJvZHVjdGlvbg0KDQogICBUaGUgSUVU
RiBJbnRlcm5ldCBEcmFmdCAiSVB2NiBMYWJlbCBTd2l0Y2hpbmcgQXJjaGl0ZWN0dXJlICg2TFNB
KSINCiAgIFs2TFNBXSBbMl0gcHJvcG9zZXMgdXNpbmcgdGhlIElQdjYgRmxvdyBMYWJlbCBmaWVs
ZCB0byBzd2l0Y2ggcGFja2V0cw0KICAgdGhyb3VnaCBhbiBJUHY2IHN1Ym5ldHdvcmsuICBUaGUg
dXNlIG9mIHRoZXNlIElQdjYgTGFiZWwgU3dpdGNoZWQNCiAgIFBhdGhzICg2TFNQcykgY2FuIHBy
b3ZpZGUgbWVhbnMgZm9yIHRyYWZmaWMgZW5naW5lZXJpbmcgYW5kDQogICBwb3RlbnRpYWxseSBp
bmNyZWFzZSB0aGUgc3BlZWQgb2YgcGFja2V0cyB0cmF2ZXJzaW5nIGEgcm91dGVkIG5ldHdvcmsN
CiAgIHdpdGggbm8gaW5jcmVhc2UgaW4gbmVlZGVkIGJhbmR3aWR0aC4NCg0KICAgTGFiZWwgc3dp
dGNoaW5nIGluIDZMU0EsIGFzIGluIE1QTFMsIGVuYWJsZXMgc2V0dGluZyB1cCBvZiBsYWJlbGVk
DQogICBwYXRocyB0aGF0IGNhbiByZXByZXNlbnQgZGlmZmVyZW50IHNlcnZpY2UgY2xhc3NlcyBh
bmQgZW5zdXJlIHRoYXQNCiAgIHRyYWZmaWMgb2YgZGlmZmVyZW50IHN1Y2ggY2xhc3NlcyBmbG93
cyBvdmVyIHRoZXNlIHBhdGhzLiAgTGFiZWwNCiAgIHN3aXRjaGluZyBtYXkgaGF2ZSBzcGVlZCBh
ZHZhbnRhZ2VzIG92ZXIgdHJhZGl0aW9uYWwgcm91dGluZy4gIFRoaXMNCiAgIGFkdmFudGFnZSB3
aWxsIGxpa2VseSBiZSBncmVhdGVyIGluIElQdjYgc2luY2UgaXRzIGFkZHJlc3MgZmllbGRzIGFy
ZQ0KICAgMTI4IGJpdHMgbG9uZy4gIE5leHQtaG9wIGRldGVybWluYXRpb24gdXNpbmcgdGhlIDIw
IGJpdCBsYWJlbA0KICAgcHJvcG9zZWQgaW4gNkxTQSBzaG91bGQgYmUgY29uc2lkZXJhYmx5IG1v
cmUgZWZmaWNpZW50IHRoYW4gYSAxMjggYml0DQogICByb3V0aW5nIHRhYmxlIGxvb2t1cC4NCg0K
ICAgVGhlIGJhc2ljIDZMU0EgZHJhZnQgZGVmaW5lcyB0d28gcHJvY2Vzc2VzOiAxKSBncm91cGlu
ZyBwYWNrZXRzIHdpdGgNCiAgIGlkZW50aWNhbCBmb3J3YXJkaW5nIGJlaGF2aW9yIGludG8gYSBG
b3J3YXJkaW5nIEVxdWl2YWxlbmNlIENsYXNzDQogICAoRkVDKSwgMikgZm9yd2FyZGluZyBhbGwg
cGFja2V0cyBiZWxvbmdpbmcgdG8gYW4gRkVDIGFsb25nIHRoZSBzYW1lDQogICBwYXRoLiAgVGhl
IGFzc2lnbm1lbnQgb2YgcGFja2V0cyB0byBhbiBGRUMgaXMgY2FsbGVkIGJpbmRpbmcuICBUaGUN
CiAgIHB1cnBvc2Ugb2YgdGhpcyBkb2N1bWVudCBpcyB0byBleHBhbmQgb24gdGhlc2UgdHdvIHBy
b2Nlc3NlcywNCiAgIGRpc2N1c3Npbmcgc3BlY2lmaWMgbWV0aG9kcyBvZiBwZXJmb3JtaW5nIHRo
ZSByZXF1aXJlZCBmdW5jdGlvbnMuDQoNCiAgIFRlcm1pbm9sb2d5IGFzIGludHJvZHVjZWQgaW4g
dGhlIDZMU0EgZHJhZnQgaXMgcmV2aWV3ZWQgaW4gU2VjdGlvbiAyDQogICBiZWxvdy4gIFNlY3Rp
b24gMyBwcmVzZW50cyBzb21lIGJhY2tncm91bmQgaW5mb3JtYXRpb24gb24gdGhlIDZMU0ENCiAg
IGRlc2lnbi4gIFNlY3Rpb24gNCBkaXNjdXNzZXMgd2F5cyB0byBjb25zdHJ1Y3QgRkVDcy4gIFNl
Y3Rpb24gNQ0KICAgZGVzY3JpYmVzIGhvdyBwYWNrZXRzIG1pZ2h0IGJlIGJvdW5kIHRvIGEgY2Vy
dGFpbiBGRUMuICBTZWN0aW9uIDYNCiAgIGNvdmVycyBzZWN1cml0eSBjb25zaWRlcmF0aW9ucy4N
Cg0KMi4gIFRlcm1pbm9sb2d5DQoNCiAgIEl0IGlzIGludGVuZGVkIHRoYXQgdGhpcyBkb2N1bWVu
dCB1c2UgdGhlIHNhbWUgdGVybWlub2xvZ3kgYXMgdGhlDQogICA2TFNBIGRyYWZ0IFsyXS4gIFRo
aXMgc2VjdGlvbiByZXBlYXRzIHRoZSByZWxldmFudCBkZWZpbml0aW9ucyBmcm9tDQogICB0aGF0
IGRvY3VtZW50Lg0KDQoNCg0KICAgCTZMU0EgZG9tYWluICAgICAgICAgICAgIGEgY29udGlndW91
cyBzZXQgb2Ygbm9kZXMgdGhhdCBwZXJmb3JtDQogICAJICAgICAgICAgICAgICAgICAgICAgICAg
NkxTQSByb3V0aW5nIGFuZCBmb3J3YXJkaW5nIG9wZXJhdGlvbnMNCiAgIAkgICAgICAgICAgICAg
ICAgICAgICAgICBhbmQgYXJlIGluIG9uZSByb3V0aW5nIG9yIGFkbWluIGRvbWFpbg0KDQogICAJ
NkxTQSBlZ3Jlc3Mgbm9kZSAgICAgICAgYSA2TFNBIGVkZ2Ugbm9kZSBpbiBpdHMgcm9sZSBvZiBo
YW5kbGluZw0KICAgCSAgICAgICAgICAgICAgICAgICAgICAgIHRyYWZmaWMgYXMgdGhlIHRyYWZm
aWMgbGVhdmVzIDZMU0EgZG9tYWluDQoNCiAgIAk2TFNBIGluZ3Jlc3Mgbm9kZSAgICAgICBhIDZM
U0EgZWRnZSBub2RlIGluIGl0cyByb2xlIG9mIGhhbmRsaW5nDQogICAJICAgICAgICAgICAgICAg
ICAgICAgICAgdHJhZmZpYyBhcyB0aGUgdHJhZmZpYyBlbnRlcnMgYSA2TFNBIGRvbWFpbg0KDQoN
Cg0KQm91bmQsIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjEsIDIwMDUgICAgICAg
ICAgICAgICAgIFtQYWdlIDNdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgIEJpbmRpbmcgUGFja2V0
cyB0byBGRUNzIGluIDZMU0EgICAgICAgIEZlYnJ1YXJ5IDIwMDUNCg0KDQogICAJNkxTUCAgICAg
ICAgICAgICAgICAgICAgYSBsYWJlbCBzd2l0Y2hlZCBwYXRoIHRocm91Z2ggYSBwYWlyIG9yDQog
ICAJICAgICAgICAgICAgICAgICAgICAgICAgbW9yZSA2TFNScw0KDQogICAJNkxTUiAgICAgICAg
ICAgICAgICAgICAJSVB2NiBsYWJlbCBzd2l0Y2hpbmcgcm91dGVyIHRoYXQgaXMgY2FwYWJsZQ0K
ICAgCSAgICAgICAgICAgICAgICAgICAgICAgIG9mIGZvcndhcmRpbmcgSVB2NiBwYWNrZXRzIGJh
c2VkIG9uIGNlcnRhaW4NCiAgIAkgICAgICAgICAgICAgICAgICAgICAgICBGRUMgYXR0cmlidXRl
cw0KDQogICAJbGFiZWwJICAgICAgICAgICAgICAgIHRoZSBJUHY2IEZsb3cgTGFiZWwgd2hpY2gg
aXMgY2FycmllZCBpbg0KICAgCSAgICAgICAgICAgICAgICAgICAgICAgIHRoZSBJUHY2IHBhY2tl
dCBoZWFkZXIgYW5kIG1heSByZXByZXNlbnQNCiAgIAkgICAgICAgICAgICAgICAgICAgICAgICB0
aGUgcGFja2V0J3MgRkVDDQoNCiAgIAlGbG93IExhYmVsICAgICAgICAgICAgICB0aGUgMjAtYml0
IGxhYmVsIGluIHRoZSBJUHY2IGhlYWRlciB1c2VkDQogICAJICAgICAgICAgICAgICAgICAgICAg
ICAgZm9yIGlkZW50aWZ5aW5nIGZsb3dzDQoNCiAgIAlsYWJlbCBzd2l0Y2hpbmcgICAJYSBmYXN0
IGZvcndhcmRpbmcgb3BlcmF0aW9uIGFsbG93aW5nDQogICAJICAgICAgICAgICAgICAgICAgICAg
ICAgc3RyZWFtbGluZWQgZm9yd2FyZGluZyBvZiBwYWNrZXRzIGJ5DQogICAJCQkJdXNpbmcgbGFi
ZWxzIHRvIGlkZW50aWZ5IGNsYXNzZXMgb2YNCiAgIAkJCQlkYXRhIHBhY2tldHMgd2hpY2ggYXJl
IHRyZWF0ZWQNCiAgIAkJCQlpbmRpc3Rpbmd1aXNoYWJseSB3aGVuIGZvcndhcmRpbmcNCg0KICAg
CWxhYmVsIHN3aXRjaGVkIGhvcCAgICAJdGhlIGhvcCBiZXR3ZWVuIHR3byA2TFNBIG5vZGVzLCBv
biB3aGljaA0KICAgCSAgICAgICAgICAgICAgICAgICAgICAgIGZvcndhcmRpbmcgaXMgZG9uZSB1
c2luZyBsYWJlbHMNCg0KICAgCWxhYmVsIHN3aXRjaGVkIHBhdGgJYSB2aXJ0dWFsIHBhdGggdGhy
b3VnaCB3aGljaCBhbGwgcGFja2V0cw0KICAgCSAgICAgICAgICAgICAgICAgICAgICAgIGluIGEg
ZmxvdyBhcmUgcm91dGVkIGFjcm9zcyBhIHJvdXRpbmcgb3INCiAgIAkJCQlhZG1pbmlzdHJhdGl2
ZSBkb21haW4NCg0KDQozLiAgQmFja2dyb3VuZA0KDQogICBQYWNrZXRzIHJlY2VpdmluZyBpZGVu
dGljYWwgZm9yd2FyZGluZyB0cmVhdG1lbnQgYXJlIHNhaWQgdG8gYmVsb25nDQogICB0byB0aGUg
c2FtZSBGRUMuICBGb3IgZXhhbXBsZSwgd2l0aGluIGEgZ2l2ZW4gcm91dGVyLCBwYWNrZXRzIHRo
YXQNCiAgIGFyZSBzZW50IHRvIHRoZSBzYW1lIG5leHQtaG9wIG92ZXIgdGhlIHNhbWUgbGluayB3
aXRoIHRoZSBzYW1lDQogICBxdWFsaXR5LW9mLXNlcnZpY2UgKFFvUykgd291bGQgYmVsb25nIHRv
IHRoZSBzYW1lIEZFQyBiZWNhdXNlIHRoZQ0KICAgcm91dGVyIHRyZWF0cyBlYWNoIHBhY2tldCBp
biBleGFjdGx5IHRoZSBzYW1lIG1hbm5lci4gIEFuIEZFQyBjb3VsZA0KICAgYmUgaWRlbnRpZmll
ZCBieSBhIHRhZyBvciBsYWJlbC4gIFRodXMgaWYgYW4gaW5jb21pbmcgcGFja2V0IGlzDQogICBs
YWJlbGVkIGFzIGJlbG9uZ2luZyB0byBhIGNlcnRhaW4gRkVDLCBhIGZvcndhcmRpbmcgZGVjaXNp
b24gY2FuIGJlDQogICBtYWRlIHdpdGhvdXQgcmVmZXJlbmNlIHRvIHRoZSBwYWNrZXQncyBkZXN0
aW5hdGlvbiBvciB0byB0aGUgcm91dGluZw0KICAgdGFibGUuICBJbiBNUExTLCBhIHNoaW0gaGVh
ZGVyIGlzIG5lZWRlZCBmb3IgdGhlIG5ldHdvcmsgbGF5ZXIgaGVhZGVyDQogICB0byBjYXJyeSB0
aGlzIGxhYmVsLiAgQSBzaGltIGhlYWRlciBpcyBub3QgcmVxdWlyZWQgaW4gNkxTQTsgdGhlIEZs
b3cNCiAgIExhYmVsIGlzIHRoZSBsYWJlbC4gIEVhY2ggcm91dGVyIG11c3QgaW5mb3JtIGl0cyAo
dXBzdHJlYW0pIG5laWdoYm9yDQogICBvZiB0aGUgbGFiZWwgdmFsdWUgdG8gdXNlIHRvIHJlcHJl
c2VudCBlYWNoIEZFQy4gIEluIE1QTFMsIFRoZQ0KICAgbGFiZWwtdG8tRkVDIG1hcHBpbmcgaXMg
cGFzc2VkIGJ5IG1lYW5zIG9mIGEgbGFiZWwgZGlzdHJpYnV0aW9uDQogICBwcm90b2NvbCBzdWNo
IGFzIExEUCBbUkZDIDMwMzZdIG9yIFJTVlAtVEVbUkZDIDMyMDldLg0KDQogICBPbmNlIGxhYmVs
LXRvLUZFQyBtYXBwaW5ncyBoYXZlIGJlZW4gZXN0YWJsaXNoZWQgZm9yIGVhY2ggaG9wIGFsb25n
IGENCiAgIGdpdmVuIHBhdGgsIHVubGFiZWxlZCBwYWNrZXRzIGFycml2aW5nIGF0IHRoZSBmaXJz
dC1ob3AgKGluZ3Jlc3MpDQogICA2TFNSIGFyZSBjbGFzc2lmaWVkIG9yIGJvdW5kIHRvIGFuIEZF
Qy4gIFRoaXMgY2xhc3NpZmljYXRpb24gY2FuIGJlDQoNCg0KDQpCb3VuZCwgZXQgYWwuICAgICAg
ICAgICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAgICAgW1BhZ2UgNF0NCgwN
CkludGVybmV0LURyYWZ0ICAgICAgQmluZGluZyBQYWNrZXRzIHRvIEZFQ3MgaW4gNkxTQSAgICAg
ICAgRmVicnVhcnkgMjAwNQ0KDQoNCiAgIGJhc2VkIG9uIGEgdmFyaWV0eSBvZiBjaGFyYWN0ZXJp
c3RpY3MgaW5jbHVkaW5nIGRlc3RpbmF0aW9uIGFkZHJlc3MsDQogICBzb3VyY2UgYWRkcmVzcywg
VHJhZmZpYyBDbGFzcywgVENQL1VEUCBwb3J0LCBldGMuICBBdCBlYWNoIHN1YnNlcXVlbnQNCiAg
IGhvcCwgdGhlIGZvcndhcmRpbmcgZGVjaXNpb24gY2FuIGJlIG1hZGUgc29sZWx5IGJ5IGV4YW1p
bmluZyB0aGUNCiAgIGluY29taW5nIGxhYmVsIHdpdGhvdXQgZnVydGhlciByZWZlcmVuY2UgdG8g
dGhlIHBhY2tldCdzIGhlYWRlciBvcg0KICAgY29udGVudHMuDQoNCiAgIFRoZSA2TFNBIHVzZXMg
dGhlIEZsb3cgTGFiZWwgZmllbGQgaW4gdGhlIElQdjYgaGVhZGVyIHRvIHJlcHJlc2VudA0KICAg
dGhlIEZFQyBvZiB0aGUgcGFja2V0LiAgQ29uc3RyYWludHMgb24gdXNpbmcgdGhlIElQdjYgRmxv
dyBMYWJlbA0KICAgZmllbGQgYXJlIGRlc2NyaWJlZCBpbiBSRkMgMzY5NywgSVB2NiBGbG93IExh
YmVsIFNwZWNpZmljYXRpb24gW1JGQw0KICAgMzY5N10uICBBbW9uZyBvdGhlciBjb25zaWRlcmF0
aW9ucywgdGhpcyBkb2N1bWVudCByZXF1aXJlcyB0aGF0IHRoZQ0KICAgRmxvdyBMYWJlbCBiZSBw
YXNzZWQgdW5jaGFuZ2VkIGZyb20gc291cmNlIHRvIGRlc3RpbmF0aW9uLiAgVGhlIDZMU0ENCiAg
IExhYmVsIFN3aXRjaGluZyBSb3V0ZXJzICg2TFNScyksIGhvd2V2ZXIsIHNob3VsZCBiZSBmcmVl
IHRvIG1ha2UgdXNlDQogICBvZiB0aGlzIGZpZWxkLiAgSWYgdGhlIHNvdXJjZSBob3N0IGhhcyBs
ZWZ0IHRoZSBmaWVsZCBzZXQgdG8gemVybywgYW4NCiAgIGVncmVzcyA2TFNSLCB3aGVuIGl0IGZv
cndhcmRzIGEgcGFja2V0IHRvIGEgbm9uLTZMU0Egcm91dGVyLCBjYW4gc2V0DQogICB0aGUgRmxv
dyBMYWJlbCBiYWNrIHRvIHplcm8gdGh1cyByZXN0b3JpbmcgaXQgdG8gaXRzIG9yaWdpbmFsIHN0
YXRlLg0KDQogICBJbiB0aGUgNkxTQSBhcmNoaXRlY3R1cmUsIGVhY2ggcG9ydCBvbiBhIDZMU1Ig
d291bGQgYmUgY29uZmlndXJlZCBhcw0KICAgYW4gImVkZ2UiIChpbmdyZXNzL2VncmVzcykgcG9y
dCBvciBhICJuZXR3b3JrIiBwb3J0LiAgVGhlc2Ugcm91dGVycw0KICAgY291bGQgaW5jbHVkZSBu
b24tNkxTUiBwb3J0cyBhcyB3ZWxsLCBidXQgc3VjaCBjb25maWd1cmF0aW9ucyBhcmUNCiAgIGJl
eW9uZCB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudC4NCg0KICAgUGFja2V0cyBlbGlnaWJsZSBm
b3IgNkxTQSB0cmVhdG1lbnQgdGhhdCBhcnJpdmUgYXQgYW4gZWRnZSBwb3J0IG9mIGENCiAgIDZM
U1IgYXJlIGJvdW5kIHRvIGFuIEZFQy4gIFRoZSBGRUMgaXMgcmVwcmVzZW50ZWQgYnkgYSBub24t
emVybyB2YWx1ZQ0KICAgaW5zZXJ0ZWQgaW4gdGhlIElQdjYgSGVhZGVyIEZsb3cgTGFiZWwgZmll
bGQuICBPZiBjb3Vyc2UgaWYgYSBwYWNrZXQNCiAgIGFycml2aW5nIGF0IGEgNkxTUiBpbmdyZXNz
IHBvcnQgaXMgdG8gYmUgZm9yd2FyZGVkIG91dCBhbm90aGVyIGVkZ2UNCiAgIChlZ3Jlc3MpIHBv
cnQgb24gdGhlIHNhbWUgNkxTUiwgdGhlIEZsb3cgTGFiZWwgZmllbGQgbmVlZCBub3QgYmUNCiAg
IGNoYW5nZWQuICBUaGVyZWZvcmUgdGhlIDZMU0Egc3dpdGNoaW5nIHRlY2huaXF1ZSBhcHBsaWVz
IG9ubHkgdG8NCiAgIHBhY2tldHMgYmVpbmcgZm9yd2FyZGVkIG91dCBuZXR3b3JrIHBvcnRzIG9u
IHRoZSA2TFNSLiAgVGhpcyBhbHNvDQogICBwcm92aWRlcyB0aGUgZmxleGliaWxpdHkgb2YgSVAg
cm91dGluZyBhcyB3ZWxsIGFzIGxhYmVsIHN3aXRjaGluZyBvZg0KICAgcGFja2V0cy4NCg0KICAg
QmVjYXVzZSBvZiB0aGUgcmVxdWlyZW1lbnQgdG8gbWFpbnRhaW4gdGhlIGludGVncml0eSBvZiB0
aGUgRmxvdw0KICAgTGFiZWwgZmllbGQsIHRoZSA2TFNBIHN3aXRjaGluZyB0ZWNobmlxdWUgY2Fu
IG9ubHkgYmUgYXBwbGllZCB0bw0KICAgcGFja2V0cyBhcnJpdmluZyBhdCBhbiBlZGdlIHBvcnQg
d2l0aCB0aGVpciBGbG93IExhYmVsIGZpZWxkIHNldCB0bw0KICAgemVyby4gIEluIGZ1dHVyZSB3
b3JrIG9uIDZMU0EsIG1vcmUgZ2VuZXJhbGl6ZWQgdHJlYXRtZW50IG9mIHBhY2tldHMNCiAgIHRo
YXQgYXJyaXZlIHdpdGggbm9uLXplcm8gRmxvdyBMYWJlbCB3aWxsIGJlIHByZXNlbnRlZC4gIElu
IHRoZQ0KICAgc2ltcGxlc3QgZGVzaWduLCB3ZSBhc3N1bWUgdGhhdCB0aGUgbmV0d29yayBjYW4g
YmUgY29uZmlndXJlZCBzbyB0aGF0DQogICBvbmx5IHRoZSBmb3JtZXIgcGFja2V0cyB3aXRoIHpl
cm8gbGFiZWwgYXJyaXZlIGF0IDZMU1IgZWRnZSBwb3J0cy4NCiAgIE1vcmUgaW52b2x2ZWQgdGVj
aG5pcXVlcyBmb3Igc2VwYXJhdGluZyBhbmQgbWFya2luZyA2TFNBLWVsaWdpYmxlDQogICBwYWNr
ZXRzIGFycml2aW5nIGF0IGVkZ2UgcG9ydHMgYXJlIGRpc2N1c3NlZCBpbiBTZWN0aW9uIDUuDQoN
CiAgIEEgcGFja2V0IGFycml2aW5nIGF0IGEgbmV0d29yayBwb3J0IG9uIGEgNkxTUiBtdXN0IGVp
dGhlciBoYXZlIGEgMA0KICAgRmxvdyBMYWJlbCBmaWVsZCAoaW5kaWNhdGluZyB0aGUgZmlyc3Qg
cGFja2V0IGluIGEgbmV3IGZsb3cpLCBoYXZlDQogICBpdHMgRmxvdyBMYWJlbCBmaWVsZCBzZXQg
YnkgdGhlIHVwc3RyZWFtIChwcmV2aW91cy1ob3ApIHJvdXRlciBhcyBhbg0KICAgaW5kaWNhdGlv
biBvZiB0aGUgcGFja2V0J3MgRkVDIChmb3IgdGhlIGN1cnJlbnQgcm91dGVyKSwgb3IgYmUgbWFy
a2VkDQogICBpbiBzb21lIHdheSBhcyBpbmVsaWdpYmxlIGZvciA2TFNBLXRyZWF0bWVudC4gIElm
IHRoZSBwYWNrZXQgaXMNCiAgIGVsaWdpYmxlIGZvciA2TFNBIHRyZWF0bWVudCBhbmQgaXMgYmVp
bmcgZm9yd2FyZGVkIG91dCBhbiBlZGdlDQogICAoZWdyZXNzKSBwb3J0LCB0aGUgRmxvdyBMYWJl
bCBpcyBzZXQgdG8gemVyby4gIElmIGFuIGVsaWdpYmxlIHBhY2tldA0KDQoNCg0KQm91bmQsIGV0
IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjEsIDIwMDUgICAgICAgICAgICAgICAgIFtQ
YWdlIDVdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgIEJpbmRpbmcgUGFja2V0cyB0byBGRUNzIGlu
IDZMU0EgICAgICAgIEZlYnJ1YXJ5IDIwMDUNCg0KDQogICBpcyBiZWluZyBmb3J3YXJkZWQgb3V0
IGEgbmV0d29yayBwb3J0LCB0aGUgRmxvdyBMYWJlbCBmaWVsZCBpcw0KICAgdW5jaGFuZ2VkIGlm
IGl0IGlzIHplcm8gKGluZGljYXRpbmcgYSBuZXcgZmxvdyB0byB0aGUgbmV4dC1ob3ApIG9yDQog
ICBzZXQgdG8gdGhlIHZhbHVlIGNvcnJlc3BvbmRpbmcgdG8gdGhlIHBhY2tldCdzIEZFQyBhdCB0
aGUgbmV4dC1ob3ANCiAgIExTUi4NCg0KICAgVGhlIHJlbWFpbmRlciBvZiB0aGlzIGRvY3VtZW50
IHdpbGwgZm9jdXMgb24gdHdvIHF1ZXN0aW9uczoNCg0KICAgCTEpIEhvdyBkb2VzIGEgNkxTUiBj
b25zdHJ1Y3QgRkVDcz8NCg0KICAgCTIpIEhvdyBkb2VzIGEgNkxTUiBiaW5kIHBhY2tldHMgdG8g
YW4gRkVDPw0KDQoNCjQuICBGRUMgQ29uc3RydWN0aW9uDQoNCiAgIEZvciB0aGUgcHVycG9zZXMg
b2YgdGhpcyBkaXNjdXNzaW9uLCBhbiBGRUMgaXMgdmlld2VkIGFzIGEgbGlzdCBvZg0KICAgb25l
IG9yIG1vcmUgYWRkcmVzc2VzIG9yIHByZWZpeGVzIHdpdGggdGhlaXIgYXNzb2NpYXRlZCBUcmFm
ZmljIENsYXNzDQogICB2YWx1ZSBmb3IgUW9TIG9yIHByZWNlZGVuY2UuICBQYWNrZXRzIGRlc3Rp
bmVkIGZvciBhbnkgb2YgdGhlDQogICBhZGRyZXNzZXMvcHJlZml4ZXMgaW4gdGhlIGxpc3QgKHdp
dGggdGhlIHNwZWNpZmllZCBRb1MgaWYgYXBwbGljYWJsZSkNCiAgIHdpbGwgYmUgZm9yd2FyZGVk
IGluIGV4YWN0bHkgdGhlIHNhbWUgd2F5LCBlLmcuLCB0aGV5IHdpbGwgYmUgc2VudA0KICAgb3V0
IHRoZSBzYW1lIHBvcnQgd2l0aCB0aGUgc2FtZSBkYXRhIGxpbmsgZW5jYXBzdWxhdGlvbiwgYW5k
IHRoZSBzYW1lDQogICBvdXRnb2luZyBsYWJlbC4gIFRoZSBzaW1wbGVzdCBpbnN0YW5jZSBvZiBh
biBGRUMgaXMgYSBzaW5nbGUgSVB2Ng0KICAgYWRkcmVzcyB3aXRoIGRlZmF1bHQgZm9yd2FyZGlu
ZyBwcmVjZWRlbmNlLiAgQSBzaWduaWZpY2FudGx5IG1vcmUNCiAgIGNvbXBsaWNhdGVkIEZFQyBt
aWdodCBiZSBhIGxpc3Qgb2YgYWxsIHJvdXRpbmcgdGFibGUgZW50cmllcyB3aXRoIHRoZQ0KICAg
c2FtZSBuZXh0LWhvcC4gIFRoZSBmb3J3YXJkaW5nIHRyZWF0bWVudCBmb3IgYSBzZXQgb2YgcGFj
a2V0cyBpcw0KICAgcmVwcmVzZW50ZWQgYnkgYSBmb3J3YXJkaW5nIGRhdGEgc3RydWN0dXJlLiAg
VGhpcyBzdHJ1Y3R1cmUgY29udGFpbnMNCiAgIHRoZSByZXF1aXJlZCBmb3J3YXJkaW5nIGluZm9y
bWF0aW9uIGluY2x1ZGluZzoNCg0KDQogICAJMSkgUGFja2V0knMgbmV4dC1ob3ANCg0KICAgCTIp
IE91dGdvaW5nIGludGVyZmFjZQ0KDQogICAJMykgT3V0Z29pbmcgbGFiZWwNCg0KICAgCTQpIERh
dGEgbGluayBlbmNhcHN1bGF0aW9uDQoNCiAgIAk1KSBQcmVjZWRlbmNlIG9yIG91dGJvdW5kIHF1
ZXVpbmcgaW5mb3JtYXRpb24uDQoNCiAgIEluIGdlbmVyYWwsIElQdjYgcGFja2V0cyB3aWxsIGFy
cml2ZSBhdCBhIDZMU1IgbmV0d29yayBwb3J0IHdpdGggYQ0KICAgbm9uLXplcm8gbGFiZWwgaW4g
dGhlIGhlYWRlciAodW5sZXNzIGl0IGlzIHRoZSBmaXJzdCBwYWNrZXQgaW4gdGhlDQogICBmbG93
KS4gIEluIG9yZGVyIHRvIGRldGVybWluZSB0aGUgcHJvcGVyIGZvcndhcmRpbmcgdHJlYXRtZW50
IGZvciB0aGUNCiAgIHBhY2tldCB0aGUgNkxTUiB3aWxsIGNvbnN1bHQgYSBzd2l0Y2hpbmcgdGFi
bGUgd2hpY2ggbWFwcyBpbmJvdW5kDQogICBsYWJlbHMgdG8gdGhlIGFwcHJvcHJpYXRlIGZvcndh
cmRpbmcgZGF0YSBzdHJ1Y3R1cmUuICBUaGUgZm9yd2FyZGluZw0KICAgc3RydWN0dXJlIHdpbGwg
ZGVmaW5lIGhvdyB0byBzZW5kIHRoZSBwYWNrZXQgdG8gaXRzIG5leHQgaG9wDQogICBpbmNsdWRp
bmcgd2hhdCBvdXRib3VuZCBsYWJlbCB0byB1c2UgaWYgdGhlIG91dGdvaW5nIHBvcnQgaXMgbm90
IGFuDQogICBlZGdlIHBvcnQuICBNdWx0aXBsZSBzd2l0Y2hpbmcgdGFibGUgZW50cmllcyBjYW4g
cmVmZXIgdG8gdGhlIHNhbWUNCiAgIGZvcndhcmRpbmcgZGF0YSBzdHJ1Y3R1cmUuICBTaW1pbGFy
bHksIGEgc2luZ2xlIGluY29taW5nIGxhYmVsIGNhbg0KICAgbWFwIHRvIG11bHRpcGxlIGZvcndh
cmRpbmcgZW50cmllcyB0byBwZXJtaXQgbG9hZCBiYWxhbmNpbmcuDQoNCg0KDQpCb3VuZCwgZXQg
YWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAgICAgW1Bh
Z2UgNl0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgQmluZGluZyBQYWNrZXRzIHRvIEZFQ3MgaW4g
NkxTQSAgICAgICAgRmVicnVhcnkgMjAwNQ0KDQoNCiAgIFRoZXJlIGFyZSBzZXZlcmFsIG1ldGhv
ZHMgdGhhdCBtaWdodCBiZSB1c2VkIHRvIHBvcHVsYXRlIHRoZQ0KICAgZm9yd2FyZGluZyBkYXRh
IHN0cnVjdHVyZSBsaXN0IGFuZCBzd2l0Y2hpbmcgdGFibGUuICBUaG9zZSB0aGF0IHdpbGwNCiAg
IGJlIGRpc2N1c3NlZCBoZXJlIGFyZToNCg0KDQogICAJMSkgTWFudWFsIGNvbmZpZ3VyYXRpb24N
Cg0KICAgCTIpIE5ldHdvcmsgbWFuYWdlbWVudCAoU05NUCkNCg0KICAgCTMpIEluZmVyZW5jZSBm
cm9tIGluY29taW5nIHBhY2tldHMNCg0KICAgCTQpIExhYmVsIGRpc3RyaWJ1dGlvbiBwcm90b2Nv
bA0KDQoNCjQuMSAgTWFudWFsIENvbmZpZ3VyYXRpb24NCg0KICAgRml4ZWQgcGF0aHMgdGhyb3Vn
aCBhIDZMU0EgZG9tYWluICh0dW5uZWxzKSBjYW4gYmUgcHJlLWNvbXB1dGVkIGFuZA0KICAgbG9h
ZGVkIGludG8gYSA2TFNSIGJ5IG1hbnVhbCBvciBzZW1pLWF1dG9tYXRpYyBtZWFucy4gIEZvciBl
eGFtcGxlLCBhDQogICBjb25maWd1cmF0aW9uIGZpbGUgY29udGFpbmluZyB0aGUgc3dpdGNoaW5n
IHRhYmxlIGNvdWxkIGJlIGRvd25sb2FkZWQNCiAgIGludG8gYSBkZXZpY2UgZnJvbSBhIGNlbnRy
YWwgZGlzdHJpYnV0aW9uIHBvaW50LiAgV2hpbGUgbm90IHZlcnkNCiAgIHByYWN0aWNhbCBmb3Ig
bGFyZ2Ugc3lzdGVtcyBpbiBsYXJnZSBuZXR3b3JrcywgdGhpcyBhcHByb2FjaCBtaWdodCBiZQ0K
ICAgdXNlZnVsIGluIGNlcnRhaW4gY2FzZXMuICBUaGUgc3ludGF4IG9mIHRoZSBjb21tYW5kcyBu
ZWVkZWQgdG8NCiAgIGNvbmZpZ3VyZSB0aGUgZGV2aWNlIGFyZSBvZiBjb3Vyc2UgaW1wbGVtZW50
YXRpb24gZGVwZW5kZW50IGFuZCBoYXZlDQogICB0byBiZSBjb25zaXN0ZW50IHdpdGggdGhlIG92
ZXJhbGwgY29tbWFuZCBzdHJ1Y3R1cmUgb2YgdGhlIGRldmljZS4NCg0KNC4yICBOZXR3b3JrIE1h
bmFnZW1lbnQNCg0KICAgV2l0aCB0aGUgZGVmaW5pdGlvbiBvZiBhcHByb3ByaWF0ZSBNSUJzLCBT
Tk1QIGNvdWxkIGJlIHVzZWQgdG8gc2V0IHVwDQogICB0aGUgZm9yd2FyZGluZyBkYXRhIHN0cnVj
dHVyZXMgYW5kIHRoZSBzd2l0Y2hpbmcgdGFibGUgZm9yIGEgNkxTUi4NCiAgIEFnYWluLCB0aGlz
IHRlY2huaXF1ZSB3b3VsZCBiZSBtb3N0IHVzZWZ1bCBmb3Igc2V0dGluZyB1cCB0dW5uZWxzDQog
ICB0aHJvdWdoIGEgNkxTQSBkb21haW4gd2l0aCBmYWlybHkgc3RhdGljIGxpbmtzLiAgVGhlIGlu
Zm9ybWF0aW9uIHRoYXQNCiAgIHdvdWxkIGhhdmUgdG8gYmUgc3VwcGxpZWQgdG8gdGhlIHJvdXRl
ciB3b3VsZCBpbmNsdWRlIHRoZSBjb250ZW50cyBvZg0KICAgdGhlIGZvcndhcmRpbmcgZGF0YSBz
dHJ1Y3R1cmUgZm9yIGVhY2ggRkVDIGJlaW5nIGNvbmZpZ3VyZWQgdXNpbmcgdGhlDQogICBNSUIg
YXMgd2VsbCBhcyBvbmUgb3IgbW9yZSBzd2l0Y2hpbmcgdGFibGUgZW50cmllcyBtYXBwaW5nIGFu
DQogICBpbmNvbWluZyBsYWJlbCB0byB0aGF0IGRhdGEgc3RydWN0dXJlLiAgSW5mb3JtYXRpb24g
Y29udGFpbmVkIGluIHRoZQ0KICAgZm9yd2FyZGluZyBkYXRhIHN0cnVjdHVyZSB3b3VsZCBoYXZl
IHRvIGJlIHN1ZmZpY2llbnQgdG8gYWNjb21wbGlzaA0KICAgZm9yd2FyZGluZyB0byB0aGUgbmV4
dC1ob3AgNkxTUi4gIFRoaXMgd291bGQgaW5jbHVkZSBvdXRnb2luZyBwb3J0LA0KICAgb3V0Z29p
bmcgbGFiZWwgYW5kIGRhdGEgbGluayBlbmNhcHN1bGF0aW9uIGlmIHJlcXVpcmVkLiAgRWFjaCBv
Zg0KICAgdGhlc2UgZGF0YSBzdHJ1Y3R1cmUgZWxlbWVudHMgY291bGQgYmUgZGVmaW5lZCBieSBh
biBlbnRyeSBpbiBhIE1JQg0KICAgdGFibGUuICBMaWtld2lzZSwgdGhlIGNvbnRlbnRzIG9mIHRo
ZSBzd2l0Y2hpbmcgdGFibGUgY291bGQgYmUNCiAgIHNwZWNpZmllZCBieSBlbnRyaWVzIGluIGEg
c2Vjb25kIE1JQiB0YWJsZS4NCg0KICAgQW4gZXhhbXBsZSBvZiBhIE1JQiBmb3IgY29uZmlndXJp
bmcgTVBMUyBMU1BzIGlzIHByZXNlbnRlZCBpbg0KICAgk011bHRpcHJvdG9jb2wgTGFiZWwgU3dp
dGNoaW5nIChNUExTKSBMYWJlbCBTd2l0Y2hpbmcgUm91dGVyIChMU1IpDQogICBNYW5hZ2VtZW50
IEluZm9ybWF0aW9uIEJhc2WUIChSRkMgMzgxMykuICBUaGUgTUlCKHMpIG5lY2Vzc2FyeSB0bw0K
ICAgaW1wbGVtZW50IHRoaXMgYXBwcm9hY2ggaW4gdGhlIDZMU0Egd2lsbCBiZSBkZWZpbmVkIGlu
IGEgc2VwYXJhdGUNCiAgIGRvY3VtZW50Lg0KDQoNCg0KDQpCb3VuZCwgZXQgYWwuICAgICAgICAg
ICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAgICAgW1BhZ2UgN10NCgwNCklu
dGVybmV0LURyYWZ0ICAgICAgQmluZGluZyBQYWNrZXRzIHRvIEZFQ3MgaW4gNkxTQSAgICAgICAg
RmVicnVhcnkgMjAwNQ0KDQoNCjQuMyAgUHNldWRvZmxvdw0KDQogICBJZiB0aGUgRkVDcyBhcmUg
bGltaXRlZCB0byBhIHNpbmdsZSBlbGVtZW50IGNvbnNpc3Rpbmcgb2Ygb25lDQogICBhZGRyZXNz
LCB0aGUgaW5jb21pbmcgbGFiZWwgY2FuIGJlIGRpc3RyaWJ1dGVkIHBpZ2d5LWJhY2tlZCBvbnRv
IGENCiAgIGRhdGEgcGFja2V0LiAgV2l0aCB0aGlzIGFwcHJvYWNoLCBhIDZMU1IgZm9yd2FyZGlu
ZyBwYWNrZXRzIG91dCBhDQogICBuZXR3b3JrIHBvcnQgc2VsZWN0cyBhbiB1bnVzZWQgbGFiZWwg
ZnJvbSBpdHMgb3duIGxhYmVsIHNwYWNlLiAgVGhlDQogICBsYWJlbCBzcGFjZSBjYW4gYmUgcGVy
LXBsYXRmb3JtIG9yIHBlci1wb3J0IChpZiB0aGUgbmV4dC1ob3Agcm91dGVyDQogICBjYW4gdW5h
bWJpZ3VvdXNseSBkZXRlcm1pbmUgdGhlIGxhYmVsIHNwYWNlIG9mIHRoZSBwYWNrZXQgaXQNCiAg
IHJlY2VpdmVzLCBlLmcuLCBvbiBhIHBvaW50LXRvLXBvaW50IGxpbmspLiAgVGhlIGNob3NlbiBs
YWJlbCBpcyBhZGRlZA0KICAgdG8gdGhlIGZvcndhcmRpbmcgZGF0YSBzdHJ1Y3R1cmUgYXMgdGhl
IG91dGdvaW5nIGxhYmVsIGZvciB0aGUgRkVDDQogICBhbmQgaXMgYWxzbyBpbnNlcnRlZCBpbnRv
IHRoZSBGbG93IExhYmVsIGZpZWxkIG9mIHRoZSBvdXRnb2luZw0KICAgcGFja2V0LiAgVGhlIHBh
Y2tldCBpcyB0aGVuIGZvcndhcmRlZCBwZXIgdGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZA0KICAg
aW4gdGhlIGZvcndhcmRpbmcgZGF0YSBzdHJ1Y3R1cmUsIGkuZS4sIGFsb25nIHRoZSByb3V0ZWQg
cGF0aC4gIFdoZW4NCiAgIHRoZSBwYWNrZXQgaXMgcmVjZWl2ZWQgYXQgdGhlIG5leHQtaG9wIHJv
dXRlciwgdGhhdCA2TFNSIGNhbiBsb2NhdGUNCiAgIGl0cyBvd24gZm9yd2FyZGluZyBkYXRhIHN0
cnVjdHVyZSBmb3IgdGhlIHBhY2tldCBieSBtZWFucyBvZiB0aGUNCiAgIHBhY2tldJJzIGRlc3Rp
bmF0aW9uIGFkZHJlc3MuICBUaGUgbGFiZWwgaW4gdGhlIGluY29taW5nIHBhY2tldCBpcw0KICAg
dXNlZCB0byBjcmVhdGUgdGhlIHN3aXRjaGluZyB0YWJsZSBlbnRyeSBhc3NvY2lhdGluZyB0aGF0
IGxhYmVsIHdpdGgNCiAgIHRoZSBmb3J3YXJkaW5nIGRhdGEgc3RydWN0dXJlLiAgVGhlIGZvcndh
cmRpbmcgdHJlYXRtZW50IGZvcg0KICAgc3VjY2VlZGluZyBwYWNrZXRzIGNhbiB0aGVuIGJlIGRl
dGVybWluZWQgZGlyZWN0bHkgdGhyb3VnaCBhIHRhYmxlDQogICBsb29rdXAgdXNpbmcgdGhlIGlu
Y29taW5nIGxhYmVsIGFzIGFuIGluZGV4LiAgKEluIGZ1dHVyZSB3b3JrIG9uDQogICA2TFNBLCBp
dCB3aWxsIGJlIHNob3duIGhvdyBvbmx5IHRoZSBsYWJlbCBjYW4gYmUgdXNlZCBmb3IgZm9yd2Fy
ZGluZw0KICAgcGFja2V0cyBpbnN0ZWFkIG9mIHRoZSB3aG9sZSBJUCBIZWFkZXIgd2l0aCBlYWNo
IHBhY2tldC4pDQoNCiAgIFNpbWlsYXJseSwgaWYgdGhlIEZFQyBpcyBsaW1pdGVkIHRvIHNwZWNp
ZmljIFRyYWZmaWMgQ2xhc3MgdmFsdWVzLA0KICAgdGhlIGluY29taW5nIGxhYmVscyBvciBvbmUg
Z2VuZXJhdGVkIGxvY2FsbHkgaW4gdGhlIHJvdXRlciBjb3VsZCBiZQ0KICAgbWFwcGVkIHRvIHRo
ZSBUcmFmZmljIENsYXNzLiAgT3RoZXIgd2F5cyB0byBpbmZlciB0aGUgRkVDcyB3b3VsZCBiZQ0K
ICAgZnJvbSB0aGUgdmFsdWVzIGluIHNwZWNpZmljIEV4dGVuc2lvbiBIZWFkZXIgZmllbGRzLiAg
RGV0YWlscyBvZiBzdWNoDQogICBtZXRob2RzIHdpbGwgYmUgcHJlc2VudGVkIGluIGZ1dHVyZSB3
b3JrLg0KDQogICBBcyBleHBsYWluZWQgaW4gdGhlIDZMU0EgZHJhZnQsIHRoZSByZWNlaXZpbmcg
cm91dGVyIHdvdWxkIHR5cGljYWxseQ0KICAgc2V0IHVwIGEgZm9yd2FyZGluZyBkYXRhIHN0cnVj
dHVyZSB3aGVuIHRoZSBsZWFkIHBhY2tldCBmb3IgdGhlIGZsb3cNCiAgIHRvIGEgcGFydGljdWxh
ciBkZXN0aW5hdGlvbiBmaXJzdCBhcHBlYXJzLiAgQWNjb3JkaW5nIHRvIHRoZQ0KICAgc3BlY2lm
aWNhdGlvbiwgdGhlIGxlYWQgcGFja2V0IGZvciB0aGUgZmxvdyBzaG91bGQgYXJyaXZlIGF0IGEg
NkxTUg0KICAgcG9ydCB3aXRoIGEgemVybyBsYWJlbC4gIFRoZSB6ZXJvIGxhYmVsIGlzIGluIGdl
bmVyYWwgYSBzaWduYWwgdGhhdCBhDQogICBuZXcgZmxvdyBoYXMgYXJyaXZlZC4gIElmLCBob3dl
dmVyLCB0aGUgbGVhZCBwYWNrZXQgaXMgbG9zdCBhbmQgdGhlDQogICBmaXJzdCBwYWNrZXQgdG8g
YXJyaXZlIGhhcyBhIGxhYmVsLCB0aGUgcm91dGVyIGNhbiBzZXQgdXAgdGhlDQogICBmb3J3YXJk
aW5nIGVudHJ5IGZvciB0aGUgZmxvdyBhdCB0aGF0IHRpbWUgdXNpbmcgdGhlIGFjY29tcGFueWlu
Zw0KICAgRmxvdyBMYWJlbC4NCg0KICAgV2l0aCB0aGUgYXJyaXZhbCBvZiB0aGUgZmlyc3QgbGFi
ZWxlZCBwYWNrZXQgZm9yIHRoZSBmbG93LCB0aGUgNkxTUg0KICAgY2FuIHNldCB1cCB0aGUgdGFi
bGUgZW50cnkgYXNzb2NpYXRpbmcgdGhlIGlucHV0IGxhYmVsIHdpdGggdGhlDQogICBmb3J3YXJk
aW5nIGRhdGEgc3RydWN0dXJlLiAgVGhlIHJlYXNvbiB0aGF0IHRoZSBGRUMgaXMgaW4gZ2VuZXJh
bA0KICAgbGltaXRlZCB0byBhIHNpbmdsZSBhZGRyZXNzIGlzIHRoYXQgdGhlIHVwc3RyZWFtIDZM
U1Igd2hpY2ggYXNzaWducw0KICAgdGhlIGxhYmVsIGhhcyBubyBrbm93bGVkZ2Ugb2YgaG93IHRo
ZSBuZXh0LWhvcCA2TFNSIHdpbGwgZm9yd2FyZCB0aGUNCiAgIHBhY2tldC4gIEZvciBleGFtcGxl
LCBpZiB0aGUgdXBzdHJlYW0gNkxTUiB3ZXJlIHRvIGFzc2lnbiB0aGUgc2FtZQ0KICAgbGFiZWwg
dG8gYWxsIHBhY2tldHMgZGVzdGluZWQgZm9yIGEgcGFydGljdWxhciBwcmVmaXgsIHRoZSBuZXh0
LWhvcA0KICAgNkxTUiB3b3VsZCBoYXZlIHRvIGNoZWNrIHRoZSByb3V0aW5nIHRhYmxlIGVhY2gg
dGltZSBpdCByZWNlaXZlcyBhDQogICBwYWNrZXQgd2l0aCB0aGF0IGxhYmVsIGluIG9yZGVyIHRv
IGFzc3VyZSB0aGF0IHRoZSBmb3J3YXJkaW5nIHJ1bGVzDQoNCg0KDQpCb3VuZCwgZXQgYWwuICAg
ICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAgICAgW1BhZ2UgOF0N
CgwNCkludGVybmV0LURyYWZ0ICAgICAgQmluZGluZyBQYWNrZXRzIHRvIEZFQ3MgaW4gNkxTQSAg
ICAgICAgRmVicnVhcnkgMjAwNQ0KDQoNCiAgIGZvciB0aGUgZW50aXJlIHByZWZpeCBhcmUgaWRl
bnRpY2FsLg0KDQo0LjQgIExhYmVsIERpc3RyaWJ1dGlvbiBQcm90b2NvbA0KDQogICBUaGlzIGlz
IHRoZSBhcHByb2FjaCB0YWtlbiBpbml0aWFsbHkgYnkgTVBMUy4gIFNldmVyYWwgc3BlY2lhbA0K
ICAgcHJvdG9jb2xzIGhhdmUgYmVlbiBkZWZpbmVkIHRvIGRpc3RyaWJ1dGUgTVBMUyBsYWJlbHMg
aW5jbHVkaW5nIExEUCwNCiAgIENvbnN0cmFpbmVkIFJvdXRpbmcgTERQIFtSRkMgMzIxMl0sIGFu
ZCBSU1ZQLVRFLg0KDQogICBSZWdhcmRsZXNzIG9mIHRoZSBwcm9jZXNzIHVzZWQgdG8gc2V0IHVw
IHRoZSA2TFNBIHN3aXRjaGluZyB0YWJsZSwNCiAgIGFueSB0d28gYWRqYWNlbnQgNkxTUnMgbXVz
dCBhZ3JlZSBvbiB0aGUgbWVhbmluZyBvZiB0aGUgbGFiZWxzIHRoZXkNCiAgIGV4Y2hhbmdlLiAg
SW4gcGFydGljdWxhciwgdGhlIGxhYmVsIG9uIGFuIGluY29taW5nIHBhY2tldCBtdXN0DQogICB1
bmFtYmlndW91c2x5IGRlZmluZSB0aGUgZm9yd2FyZGluZyBiZWhhdmlvciBmb3IgdGhlIHJlY2lw
aWVudCBvZiB0aGUNCiAgIHBhY2tldC4gIFRoZSBsb2NhbCBjb25maWd1cmF0aW9uIGFuZCBuZXR3
b3JrIG1hbmFnZW1lbnQgYXBwcm9hY2hlcw0KICAgbWVudGlvbmVkIGFib3ZlIHVzZSBhbiBleHRl
cm5hbCBhZ2VuY3kgdG8gbWFrZSBhZGphY2VudCByb3V0ZXJzIGF3YXJlDQogICBvZiB0aGUgbGFi
ZWxzJyBtZWFuaW5nLiAgVGhlIGxhYmVsIGRpc3RyaWJ1dGlvbiBwcm90b2NvbCBhcHByb2FjaA0K
ICAgYWxsb3dzIG9uZSByb3V0ZXIgdG8gc2ltcGx5IGluZm9ybSBpdHMgbmVpZ2hib3Igd2hhdCBh
IGxhYmVsIG1lYW5zLg0KDQogICBJbiBMRFAsIGZvciBleGFtcGxlLCB0d28gTVBMUyByb3V0ZXJz
IGVzdGFibGlzaCBhIHNlc3Npb24gYmV0d2Vlbg0KICAgdGhlbXNlbHZlcy4gIE9uZSBvZiB0aGUg
cm91dGVycyBjYW4gdGhlbiBzZW5kIGEgTGFiZWwgTWFwcGluZyBtZXNzYWdlDQogICB0byBpdHMg
cGVlciBpbmZvcm1pbmcgdGhlIHBlZXIgb2YgdGhlIGluY29taW5nIGxhYmVsIHRoYXQgd2lsbCBt
YXAgdG8NCiAgIG9uZSBvZiB0aGUgc2VuZGluZyByb3V0ZXIncyBGRUNzLiAgVGhpcyBtZXNzYWdl
IHdvdWxkIGNvcnJlc3BvbmQgdG8NCiAgIG9uZSBlbnRyeSBpbiB0aGUgSW5jb21pbmcgTGFiZWwg
TWFwIChJTE0pIHNpbmNlIGl0IHJlbGF0ZXMgYW4NCiAgIGluY29taW5nIGxhYmVsIHRvIHRoZSBO
ZXh0IEhvcCBMYWJlbCBGb3J3YXJkaW5nIEVudHJ5IChOSExGRSkgdGhhdA0KICAgZGVmaW5lcyB0
aGUgZm9yd2FyZGluZyBiZWhhdmlvciBmb3IgdGhlIEZFQy4NCg0KICAgT25lIG9mIHRoZSBleGlz
dGluZyBsYWJlbCBkaXN0cmlidXRpb24gcHJvdG9jb2xzIGNvdWxkIGJlIHVzZWQNCiAgIGJldHdl
ZW4gdHdvIDZMU1JzIHdpdGggYSBtaW5pbXVtIG9mIG1vZGlmaWNhdGlvbiB0byB0aGUgcHJvdG9j
b2wuDQogICBUaGlzIHNwZWNpZmljYXRpb24gYWxsb3dzIHVzZSBvZiBvbmUgb3IgbW9yZSBsYWJl
bCBkaXN0cmlidXRpb24NCiAgIHByb3RvY29scyB0byBwcm92aWRlIEZFQyB2YWx1ZXMgdG8gdGhl
IDZMU1IgZG9tYWluLg0KDQo1LiAgQmluZGluZyBJUHY2IFBhY2tldHMgdG8gYW4gRkVDDQoNCiAg
IFRoZSBwcm9jZXNzIG9mIGJpbmRpbmcgSVB2NiBwYWNrZXRzIHRvIEZFQ3MgaW52b2x2ZXMgZXhh
bWluYXRpb24gb2YNCiAgIHRoZSBwYWNrZXQgaGVhZGVyIGFuZC9vciBjb250ZW50cyBmb3IgdGhl
IGNoYXJhY3RlcmlzdGljcyB0aGF0DQogICBkZXRlcm1pbmUgbWVtYmVyc2hpcCBpbiBhIGNlcnRh
aW4gRkVDLiAgSW4gZ2VuZXJhbCwgdGhhdCByZXF1aXJlcw0KICAgc3BlY2lmaWNhdGlvbiBvZiBh
IHNldCBvZiBydWxlcyB0aGF0IGRldGVybWluZSB0aGUgYXBwcm9wcmlhdGUgRkVDDQogICBhc3Np
Z25tZW50IGZvciB2YXJpb3VzIHR5cGVzIG9mIHBhY2tldHMuDQoNCiAgIFBhY2tldHMgc2hvdWxk
IGJlIGJvdW5kIHRvIGFuIEZFQyBhdCA2TFNSIGVkZ2UgKGluZ3Jlc3MpIHBvcnRzLg0KICAgVGhl
cmUgbWF5IGJlIHNldmVyYWwgYXBwcm9hY2hlcyB0byB0aGUgZXN0YWJsaXNobWVudCBvZiB0aGUg
YmluZGluZw0KICAgcnVsZXMuICBUaHJlZSBhcmUgZGlzY3Vzc2VkIGhlcmU6DQoNCg0KDQoNCg0K
DQoNCg0KDQoNCkJvdW5kLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDIxLCAyMDA1
ICAgICAgICAgICAgICAgICBbUGFnZSA5XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICBCaW5kaW5n
IFBhY2tldHMgdG8gRkVDcyBpbiA2TFNBICAgICAgICBGZWJydWFyeSAyMDA1DQoNCg0KICAgMSkJ
TWFudWFsIENvbmZpZ3VyYXRpb24NCg0KICAgMikJQWxnb3JpdGhtaWMgQmluZGluZw0KDQogICAz
KQlOZXR3b3JrIE1hbmFnZW1lbnQNCg0KNS4xICBNYW51YWwgQ29uZmlndXJhdGlvbg0KDQogICBC
aW5kaW5nIHJ1bGVzIGNhbiBiZSBlc3RhYmxpc2hlZCBieSBtYW51YWwgbWVhbnMgZWl0aGVyIHRo
cm91Z2ggYQ0KICAgQ29tbWFuZCBMaW5lIEludGVyZmFjZSAoQ0xJKSBvciBieSB1c2luZyBhbiBl
eHRlcm5hbGx5IGdlbmVyYXRlZA0KICAgY29uZmlndXJhdGlvbiBmaWxlLiAgVGhlIHN5bnRheCBv
ZiB0aGUgRkVDIGJpbmRpbmcgcG9ydGlvbiBvZiB0aGUgQ0xJDQogICBvciBjb25maWd1cmF0aW9u
IGZpbGUgd291bGQgaGF2ZSB0byBiZSBpbXBsZW1lbnRhdGlvbi1kZXBlbmRlbnQgaW4NCiAgIG9y
ZGVyIHRvIGJlIGNvbnNpc3RlbnQgd2l0aCB0aGUgb3RoZXIgcm91dGVyIGZ1bmN0aW9ucy4NCg0K
ICAgQXMgYW4gZXhhbXBsZSwgY29uc2lkZXIgYSB2ZXJ5IHNpbXBsZSBwYWNrZXQgY2xhc3NpZmlj
YXRpb24gc2NoZW1lLg0KICAgVGhlcmUgYXJlIHR3byBsZXZlbHMgb2Ygc2VydmljZSwgcHJpb3Jp
dHkgYW5kIHN0YW5kYXJkLiAgUGFja2V0cw0KICAgb3JpZ2luYXRpbmcgZnJvbSBhIHByZS1jb25m
aWd1cmVkIHNldCBvZiBhZGRyZXNzZXMgYXJlIGdpdmVuIHByaW9yaXR5DQogICBzZXJ2aWNlLiAg
QWxsIG90aGVycyByZWNlaXZlIHN0YW5kYXJkIHNlcnZpY2UuICBBbHNvIGFzc3VtZSBhIHZlcnkN
CiAgIHNpbXBsZSBwb2xpY2luZyBmdW5jdGlvbiwgZS5nLiwgbm8gbW9yZSB0aGFuIDEwJSBvZiBp
bmNvbWluZyBwYWNrZXRzDQogICAob3ZlciBzb21lIHByZS1kZWZpbmVkIHRpbWUgcGVyaW9kKSBt
YXkgYmUgZ2l2ZW4gcHJpb3JpdHkgc2VydmljZS4NCiAgIFBhY2tldHMgZXhjZWVkaW5nIHRoaXMg
bGltaXQgYXJlIGdpdmVuIHN0YW5kYXJkIHNlcnZpY2UuDQoNCiAgIFRoZSBwYWNrZXQgY2xhc3Np
ZmljYXRpb24gYW5kIHRyYWZmaWMgY29uZGl0aW9uaW5nIG9wZXJhdGlvbnMNCiAgIGRlc2NyaWJl
ZCBhYm92ZSBhcmUgcGVyZm9ybWVkIGF0IGEgNkxTUiBlZGdlIHBvcnQuICBGb3IgaW5jb21pbmcN
CiAgIHBhY2tldHMgdG8gYmUgZWxpZ2libGUgZm9yIDZMU0EgZm9yd2FyZGluZywgdGhlIElQdjYg
RmxvdyBMYWJlbCBmaWVsZA0KICAgaW4gcGFja2V0cyBhcHBlYXJpbmcgYXQgYSA2TFNSIGVkZ2Ug
cG9ydCBtYXkgYmUgc2V0IHRvIHplcm8uICBQYWNrZXRzDQogICB3aXRoIG5vbi16ZXJvIEZsb3cg
TGFiZWxzIG1heSBiZSBnaXZlbiBkZWZhdWx0IHRyZWF0bWVudC4gIFRodXMsIGF0DQogICB0aGUg
ZWRnZSBwb3J0LCBwYWNrZXRzIGFyZSBkaXZpZGVkIGludG8gMyBncm91cHM6DQoNCg0KICAgCTEp
IFByaW9yaXR5IDZMU0EgcGFja2V0cw0KDQogICAJMikgU3RhbmRhcmQgNkxTQSBwYWNrZXRzDQoN
CiAgIAkzKSBOb24tNkxTQSBwYWNrZXRzDQoNCiAgIEluIHRoaXMgZXhhbXBsZSwgYSA2TFNBIG5l
dHdvcmsgaXMgY29uc2lkZXJlZCB0byBiZSBhIJNEaWZmZXJlbnRpYXRlZA0KICAgU2VydmljZXMg
RG9tYWlulCBpbiB0aGUgc2Vuc2Ugb2YgdGhlIGFwcGxpY2FibGUgUkZDIJNEZWZpbml0aW9uIG9m
DQogICB0aGUgRGlmZmVyZW50aWF0ZWQgU2VyaWVzIEZpZWxkIChEUyBGaWVsZCkgaW4gdGhlIElQ
djQgYW5kIElQdjYNCiAgIEhlYWRlcnOUW1JGQyAyNDc0XS4gIEluIHRoaXMgc3BlY2lmaWNhdGlv
biwgYSBEaWZmZXJlbnRpYXRlZCBTZXJ2aWNlcw0KICAgRG9tYWluIGlzIGRlZmluZWQgYXMgk2Eg
Y29udGlndW91cyBwb3J0aW9uIG9mIHRoZSBJbnRlcm5ldCBvdmVyIHdoaWNoDQogICBhIGNvbnNp
c3RlbnQgc2V0IG9mIGRpZmZlcmVudGlhdGVkIHNlcnZpY2VzIHBvbGljaWVzIGFyZSBhZG1pbmlz
dGVyZWQNCiAgIGluIGEgY29vcmRpbmF0ZWQgZmFzaGlvbpQuICBQYWNrZXRzIG11c3QgZW50ZXIg
YW5kIGV4aXQgdGhlIGRvbWFpbg0KICAgdGhyb3VnaCBhIDZMU1IgZWRnZSBwb3J0LiAgV2l0aGlu
IHRoZSBkb21haW4sIHBhY2tldHMgYXJlIGZvcndhcmRlZA0KICAgYmV0d2VlbiCTbmV0d29ya5Qg
cG9ydHMgb2YgNkxTUnMuDQoNCiAgIE9uY2UgYSBwYWNrZXQgaXMgY2xhc3NpZmllZCwgdGhlIGVk
Z2UgcG9ydCBjYW4gZXhlcmNpc2UgaXRzDQogICBEaWZmZXJlbnRpYXRlZCBTZXJ2aWNlcyAoRFMp
IG1hcmtpbmcgZnVuY3Rpb24gYnkgc2V0dGluZyB0aGUgVHJhZmZpYw0KDQoNCg0KQm91bmQsIGV0
IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjEsIDIwMDUgICAgICAgICAgICAgICAgW1Bh
Z2UgMTBdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgIEJpbmRpbmcgUGFja2V0cyB0byBGRUNzIGlu
IDZMU0EgICAgICAgIEZlYnJ1YXJ5IDIwMDUNCg0KDQogICBDbGFzcyBieXRlIChEUyBGaWVsZCkg
dG8gdGhlIGFwcHJvcHJpYXRlIHZhbHVlLiAgT25jZSBhIHBhY2tldCBpcw0KICAgbWFya2VkLCBk
b3duc3RyZWFtIDZMU1JzIHdpbGwga25vdyB0aGUgY29ycmVjdCBmb3J3YXJkaW5nIGJlaGF2aW9y
DQogICB3aXRoIHJlc3BlY3QgdG8gcHJlY2VkZW5jZS4gIEFsc28sIGRvd25zdHJlYW0gNkxTUnMg
d2lsbCBrbm93IHRvDQogICBsZWF2ZSB0aGUgRmxvdyBMYWJlbHMgb2Ygbm9uLTZMU0EgcGFja2V0
cyB1bmNoYW5nZWQuICBGb3IgUHJpb3JpdHkNCiAgIGFuZCBTdGFuZGFyZCBjbGFzcyA2TFNBIHBh
Y2tldHMsIHRoZSBlZGdlIHJvdXRlciBjYW4gYXNzaWduIGFuDQogICBvdXRnb2luZyBsYWJlbCBi
YXNlZCBvbiBkZXN0aW5hdGlvbiBhbmQgcHJlY2VkZW5jZS4NCg0KICAgQXMgdGhlIG1hcmtlZCBw
YWNrZXRzIGFycml2ZSBhdCBzdWNjZXNzaXZlIDZMU1IgbmV0d29yayBwb3J0cywgdGhlaXINCiAg
IGZvcndhcmRpbmcgY2xhc3MgY2FuIGJlIG9idGFpbmVkIGZyb20gdGhlIFRyYWZmaWMgQ2xhc3Mg
Ynl0ZSBpbiB0aGUNCiAgIGhlYWRlci4gIFRoZSBvdXRnb2luZyBsYWJlbCAoZm9yIG91dGJvdW5k
IG5ldHdvcmsgcG9ydHMpIGlzIGFzc2lnbmVkDQogICBiYXNlZCBvbiBkZXN0aW5hdGlvbiBhbmQg
VHJhZmZpYyBDbGFzcyBzby4gIFRoaXMgYWNoaWV2ZXMgdGhlIGdvYWwgb2YNCiAgIGhhdmluZyBm
b3J3YXJkaW5nIGJlaGF2aW9yIHNvbGVseSBkZWZpbmVkIGJ5IGluY29taW5nIGxhYmVsLg0KDQog
ICBUaGUgQ0xJIG9yIGNvbmZpZ3VyYXRpb24gZmlsZSBjb21tYW5kIHN5bnRheCBtdXN0IGJlIGFk
ZXF1YXRlIHRvDQogICBzcGVjaWZ5IGEgdmFyaWV0eSBvZiBwYXJhbWV0ZXJzIGluY2x1ZGluZyBi
dXQgbm90IGxpbWl0ZWQgdG86DQoNCg0KICAgCTEpIE51bWJlciBvZiBRb1MvcHJlY2VkZW5jZSBs
ZXZlbHMNCg0KICAgCTIpIERpZmZlcmVudGlhdGVkIFNlcnZpY2VzIENvZGUgUG9pbnQgKERTQ1Ap
IG9yIFRyYWZmaWMgQ2xhc3MgZm9yIGVhY2ggc2VydmljZSBsZXZlbA0KDQogICAJMykgVHJhZmZp
YyBwb2xpY2luZyBwYXJhbWV0ZXJzDQoNCiAgIAk0KSBMYWJlbCBhc3NpZ25tZW50IGNyaXRlcmlh
DQoNCjUuMiAgQWxnb3JpdGhtaWMgQmluZGluZw0KDQogICBUaGUgYWxnb3JpdGhtKHMpIGZvciBh
c3NpZ25pbmcgcGFja2V0cyB0byBGRUNzIGNhbiBiZSBjb2RlZCBpbnRvIHRoZQ0KICAgNkxTUiBl
ZGdlIHBvcnQgcGFja2V0IGhhbmRsaW5nIHNvZnR3YXJlIGF0IHRoZSB0aW1lIGl0IGlzIGRlc2ln
bmVkLg0KICAgVGhpcyBjb2RlIHNlZ21lbnQgbWlnaHQgY29uc2lzdCBvZiBvbmUgb3IgbW9yZSBm
aWx0ZXJzIHRoYXQgZXhhbWluZQ0KICAgaW5jb21pbmcgcGFja2V0cyBmb3IgY2VydGFpbiBjaGFy
YWN0ZXJpc3RpY3MsIGUuZy4sIFRDUC9VRFAgcG9ydA0KICAgbnVtYmVyLiAgVGhlIHByZXNlbmNl
IG9yIGFic2VuY2Ugb2YgdGhlc2UgY2hhcmFjdGVyaXN0aWNzIHdvdWxkDQogICByZXN1bHQgaW4g
dGhlIHBhY2tldCBiZWluZyBhc3NpZ25lZCB0byBjZXJ0YWluIHByZWRldGVybWluZWQgRkVDcy4N
Cg0KICAgQSBzaW1wbGUgZXhhbXBsZSB3b3VsZCBiZSB0aGUgY2FzZSB3aGVyZSBGRUNzIGNvbnNp
c3Qgb2Ygc2luZ2xlDQogICBkZXN0aW5hdGlvbiBhZGRyZXNzZXMuICBFZGdlIHBvcnQgYmVoYXZp
b3IgY291bGQgYmUgY29kZWQgc3VjaCB0aGF0DQogICBlYWNoIHRpbWUgYSBwYWNrZXQgYXJyaXZl
cyBmb3IgYSBuZXcgZGVzdGluYXRpb24sIGEgbmV3IEZFQyBpcw0KICAgY3JlYXRlZC4gIEFuIHVu
dXNlZCBsYWJlbCBpcyBjaG9zZW4gdG8gcmVwcmVzZW50IHRoaXMgRkVDIGFuZCB0aGUNCiAgIHBh
Y2tldCBpcyBmb3J3YXJkZWQuDQoNCiAgIFRoZSBvYnZpb3VzIGRpc2FkdmFudGFnZSBvZiB0aGlz
IGFwcHJvYWNoIGlzIGl0cyBpbmZsZXhpYmlsaXR5Lg0KICAgTmV0d29yayBtYW5hZ2VycyB3b3Vs
ZCBub3QgYmUgYWJsZSB0byBjaGFuZ2UgdGhlIGFzc2lnbm1lbnQgb2YNCiAgIHBhY2tldHMgdG8g
RkVDcy4gIEluIHNvbWUgY2FzZXMsIGhvd2V2ZXIsIHRoZSBhZGRlZCBvdmVyaGVhZCBhbmQNCiAg
IGNvbXBsZXhpdHkgb2YgcHJvdmlkaW5nIGEgbW9yZSBmbGV4aWJsZSBhcHByb2FjaCBtaWdodCBu
b3QgYmUNCiAgIGp1c3RpZmllZC4NCg0KDQoNCg0KDQoNCkJvdW5kLCBldCBhbC4gICAgICAgICAg
IEV4cGlyZXMgQXVndXN0IDIxLCAyMDA1ICAgICAgICAgICAgICAgIFtQYWdlIDExXQ0KDA0KSW50
ZXJuZXQtRHJhZnQgICAgICBCaW5kaW5nIFBhY2tldHMgdG8gRkVDcyBpbiA2TFNBICAgICAgICBG
ZWJydWFyeSAyMDA1DQoNCg0KNS4zICBGRUMgQmluZGluZyB1c2luZyBTTk1QDQoNCiAgIFRoZSBh
bGdvcml0aG0ocykgZm9yIGFzc2lnbmluZyBwYWNrZXRzIHRvIEZFQ3MgY2FuIGJlIGNvZGVkIGlu
dG8gdGhlDQogICA2TFNSIGVkZ2UgcG9ydCBwYWNrZXQgaGFuZGxpbmcgc29mdHdhcmUgYXQgdGhl
IHRpbWUgaXQgaXMgZGVzaWduZWQuDQogICBUaGlzIGNvZGUgc2VnbWVudCBtaWdodCBjb25zaXN0
IG9mIG9uZSBvciBtb3JlIGZpbHRlcnMgdGhhdCBleGFtaW5lDQogICBpbmNvbWluZyBwYWNrZXRz
IGZvciBjZXJ0YWluIGNoYXJhY3RlcmlzdGljcywgZS5nLiwgVENQL1VEUCBwb3J0DQogICBudW1i
ZXIuICBUaGUgcHJlc2VuY2Ugb3IgYWJzZW5jZSBvZiB0aGVzZSBjaGFyYWN0ZXJpc3RpY3Mgd291
bGQNCiAgIHJlc3VsdCBpbiB0aGUgcGFja2V0IGJlaW5nIGFzc2lnbmVkIHRvIGNlcnRhaW4gcHJl
ZGV0ZXJtaW5lZCBGRUNzLg0KDQogICBBIHNpbXBsZSBleGFtcGxlIHdvdWxkIGJlIHRoZSBjYXNl
IHdoZXJlIEZFQ3MgY29uc2lzdCBvZiBzaW5nbGUNCiAgIGRlc3RpbmF0aW9uIGFkZHJlc3Nlcy4g
IEVkZ2UgcG9ydCBiZWhhdmlvciBjb3VsZCBiZSBjb2RlZCBzdWNoIHRoYXQNCiAgIGVhY2ggdGlt
ZSBhIHBhY2tldCBhcnJpdmVzIGZvciBhIG5ldyBkZXN0aW5hdGlvbiwgYSBuZXcgRkVDIGlzDQog
ICBjcmVhdGVkLiAgQW4gdW51c2VkIGxhYmVsIGlzIGNob3NlbiB0byByZXByZXNlbnQgdGhpcyBG
RUMgYW5kIHRoZQ0KICAgcGFja2V0IGlzIGZvcndhcmRlZC4NCg0KICAgVGhlIG9idmlvdXMgZGlz
YWR2YW50YWdlIG9mIHRoaXMgYXBwcm9hY2ggaXMgaXRzIGluZmxleGliaWxpdHkuDQogICBOZXR3
b3JrIG1hbmFnZXJzIHdvdWxkIG5vdCBiZSBhYmxlIHRvIGNoYW5nZSB0aGUgYXNzaWdubWVudCBv
Zg0KICAgcGFja2V0cyB0byBGRUNzLiAgSW4gc29tZSBjYXNlcywgaG93ZXZlciwgdGhlIGFkZGVk
IG92ZXJoZWFkIGFuZA0KICAgY29tcGxleGl0eSBvZiBwcm92aWRpbmcgYSBtb3JlIGZsZXhpYmxl
IGFwcHJvYWNoIG1pZ2h0IG5vdCBiZQ0KICAganVzdGlmaWVkLg0KDQo2LiAgU2VjdXJpdHkgQ29u
c2lkZXJhdGlvbnMNCg0KICAgU2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgZm9yIHRoZSB1c2Ugb2Yg
dGhlIEZsb3cgTGFiZWwgc3dpdGNoaW5nDQogICBtZXRob2QgaXRzZWxmIGFyZSBkaXNjdXNzZWQg
aW4gdGhlIGFyY2hpdGVjdHVyZSBkb2N1bWVudCBbNkxTQV0uICBUbw0KICAgc3VtbWFyaXplLCBm
b3IgU2VjdXJpdHkgQXNzb2NpYXRpb25zIG9wZXJhdGluZyBpbiB0aGUgdHJhbnNwb3J0IG1vZGUs
DQogICBvbmx5IHRoZSBwYWNrZXQgcGF5bG9hZCBpcyBlbmNyeXB0ZWQgYW5kIGhlbmNlIGZpZWxk
cyBpbiB0aGUgSVB2Ng0KICAgaGVhZGVyLCBpLmUuLCB0aGUgRmxvdyBMYWJlbCBmaWVsZCwgYXJl
IG5vdCBhZmZlY3RlZC4gIEluIHRoZSB0dW5uZWwNCiAgIG1vZGUsIHRoZSBJUHY2IHBhY2tldCBp
cyBlbmNhcHN1bGF0ZWQgaW4gYW4gb3V0ZXIgcGFja2V0IHdoaWNoDQogICBpbmNsdWRlcyBhIG5l
dyBoZWFkZXIuICBJbiB0aGlzIGNhc2UsIHRoZSBGbG93IExhYmVsIGlzIG5vdCBhY2Nlc3NlZA0K
ICAgdW50aWwgdGhlIHBhY2tldCByZWFjaGVzIHRoZSBlbmQgcG9pbnQgb2YgdGhlIFNlY3VyaXR5
IEFzc29jaWF0aW9uDQogICBhbmQgaXMgdW53cmFwcGVkLiAgSGVuY2UgdGhlIDZMU0EgaGFzIG5v
IGltcGFjdCBvbiBzZWN1cml0eSBpbiB0aGlzDQogICBtb2RlIGVpdGhlci4NCg0KICAgVGVjaG5p
cXVlcyBmb3Igc2V0dGluZyB1cCBmb3J3YXJkaW5nIGVudHJpZXMgYW5kIEZFQyBiaW5kaW5ncyBo
YXZlDQogICBiZWVuIGRlc2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50LiAgVGhvc2UgdGVjaG5pcXVl
cyBpbnZvbHZpbmcgbmV0d29yaw0KICAgcHJvdG9jb2xzIGhhdmUgdGhlIHNhbWUgc2VjdXJpdHkg
Y29uc2lkZXJhdGlvbnMgYXMgdGhlIHByb3RvY29scw0KICAgdGhlbXNlbHZlcy4gIFNwZWNpZmlj
IGNhc2VzIGFyZSBvdXRsaW5lZCBiZWxvdy4NCg0KNi4xICBVc2Ugb2YgU05NUA0KDQogICBTTk1Q
IGhhcyBiZWVuIGRpc2N1c3NlZCBhcyBhIHBvc3NpYmxlIGFwcHJvYWNoIHRvIGRlZmluaW5nIEZF
Q3MgYW5kDQogICBGRUMgYmluZGluZ3MuICBJZiB0aGlzIHRlY2huaXF1ZSBpcyB1c2VkLCB0aGUg
TUlCcyAoeWV0IHRvIGJlDQogICBkZWZpbmVkKSBjb3VsZCBiZSB1c2VkIHRvIHNldCB1cCA2TFNQ
cyB0aGF0IGRlbGl2ZXIgdHJhZmZpYyB0bw0KICAgaW1wcm9wZXIgZGVzdGluYXRpb25zLiAgVGhp
cyBzaXR1YXRpb24gaXMgZGlzY3Vzc2VkIGluIHRoZSBkb2N1bWVudA0KICAgdGhhdCBkZWZpbmVz
IHRoZSBGVE4gTUlCIFtSRkMgMzgxNF0uICBUaGUgYXV0aG9ycyBvZiB0aGlzIGRvY3VtZW50DQog
ICBlbmNvdXJhZ2UgdGhlIHVzZSBvZiBTTk1QdjMgd2hpY2ggaGFzIHNlY3VyaXR5IGZlYXR1cmVz
IGJ1aWx0IGluIHRvDQogICBhdm9pZCB1bmF1dGhvcml6ZWQgU2V0IG9wZXJhdGlvbnMgb24gTUlC
IHRhYmxlcy4NCg0KDQoNCkJvdW5kLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDIx
LCAyMDA1ICAgICAgICAgICAgICAgIFtQYWdlIDEyXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICBC
aW5kaW5nIFBhY2tldHMgdG8gRkVDcyBpbiA2TFNBICAgICAgICBGZWJydWFyeSAyMDA1DQoNCg0K
Ni4yICBVc2Ugb2YgTGFiZWwgRGlzdHJpYnV0aW9uIFByb3RvY29scw0KDQogICBUaGlzIGRvY3Vt
ZW50IGhhcyBkaXNjdXNzZWQgdGhlIHVzZSBvZiBhIGxhYmVsIGRpc3RyaWJ1dGlvbiBwcm90b2Nv
bA0KICAgZm9yIGRlZmluaW5nIGxhYmVsLXRvLUZFQyBtYXBwaW5ncyBpbiA2TFNScy4gIFNwZWNp
ZmljIHNlY3VyaXR5DQogICBjb25zaWRlcmF0aW9ucyB3b3VsZCBkZXBlbmQgb24gdGhlIGRldGFp
bHMgb2YgdGhlIHByb3RvY29sIHNlbGVjdGVkLg0KICAgQW4gZXhhbXBsZSBvZiB0aGUgc2VjdXJp
dHkgY29uc2VxdWVuY2VzIHJlc3VsdGluZyBmcm9tIHRoZSB1c2Ugb2YNCiAgIHN1Y2ggcHJvdG9j
b2xzIGNhbiBiZSBmb3VuZCBpbiB0aGUgTERQIHNwZWNpZmljYXRpb24gW1JGQyAzMDM2XS4NCiAg
IFRoaXMgZG9jdW1lbnQgcG9pbnRzIG91dCB0aGF0IHRoZSBzZWN1cml0eSByZXF1aXJlbWVudHMg
b2YgbGFiZWwNCiAgIGRpc3RyaWJ1dGlvbiBwcm90b2NvbHMgYXJlIHRoZSBzYW1lIGFzIHRob3Nl
IG9mIHJvdXRpbmcgcHJvdG9jb2xzLg0KICAgVGhlIExEUCBzcGVjaWZpY2F0aW9uIHN0YXRlcyBm
dXJ0aGVyIHRoYXQgIlRvIGF2b2lkIGxhYmVsIHNwb29maW5nDQogICBhdHRhY2tzLCBpdCBpcyBu
ZWNlc3NhcnkgdG8gZW5zdXJlIHRoYXQgbGFiZWxlZCBkYXRhIHBhY2tldHMgYXJlDQogICBsYWJl
bGVkIGJ5IHRydXN0ZWQgTFNScyBhbmQgdGhhdCB0aGUgbGFiZWxzIHBsYWNlZCBvbiB0aGUgcGFj
a2V0cyBhcmUNCiAgIHByb3Blcmx5IGxlYXJuZWQgYnkgdGhlIGxhYmVsaW5nIExTUnMuIg0KDQo3
LiAgUmVmZXJlbmNlcw0KDQogICAgMS4gQnJhZG5lciwgUy4sIEtleSB3b3JkcyBmb3IgdXNlIGlu
IFJGQ3MgdG8gSW5kaWNhdGUgUmVxdWlyZW1lbnQNCiAgIExldmVscywgQkNQIDE0LCBSRkMgMjEx
OSwgTWFyY2ggMTk5Nw0KDQogICAgMi4gWzZMU0FdIENoYWtyYXZvcnR5LCBTLiwgSVB2NiBMYWJl
bCBTd2l0Y2hpbmcgQXJjaGl0ZWN0dXJlICg2TFNBKSwNCiAgIGRyYWZ0LWNoYWtyYXZvcnR5LTZs
c2EtMDEudHh0LCBKYW51YXJ5IDIwMDUuDQoNCiAgICAzLiBbUkZDIDMwMzZdIEFuZGVyc3Nvbiwg
TC4sIERvb2xhbiwgUC4sIEZlbGRtYW4sIE4uLCBGcmVkZXR0ZSwgQS4sDQogICBhbmQgQi4gVGhv
bWFzLCBMRFAgU3BlY2lmaWNhdGlvbiwgUkZDIDMwMzYsIEphbnVhcnkgMjAwMS4NCg0KICAgIDQu
IFtSRkMgMzIwOV0gQXdkdWNoZSwgRC4sIEJlcmdlciwgTC4sIEdhbiwgRC4sIExpLCBULiwgU3Jp
bml2YXNhbiwNCiAgIFYuLCBhbmQgRy4gU3dhbGxvdywgUlNWUC1URTogRXh0ZW5zaW9ucyB0byBS
U1ZQIGZvciBMU1AgVHVubmVscywgUkZDDQogICAzMjA5LCBEZWNlbWJlciAyMDAxLg0KDQogICAg
IDUuIFtSRkMgMzY5N10gUmFqYWhhbG1lLCBKLiwgQ29udGEsIEEuLCBDYXJwZW50ZXIsIEIuLCBh
bmQgUy4NCiAgIERlZXJpbmcsIElQdjYgRmxvdyBMYWJlbCBTcGVjaWZpY2F0aW9uLCBSRkMgMzY5
NywgTWFyY2ggMjAwNC4NCg0KICAgIDYuIFtSRkMgMzIxMl0gSmFtb3Vzc2ksIEIuLCBldC4gYWws
IENvbnN0cmFpbnQtQmFzZWQgTFNQIFNldHVwIHVzaW5nDQogICBMRFAsIFJGQyAzMjEyLCBKYW51
YXJ5MiAwMDIuDQoNCiAgICA3LiBbUkZDIDI0NzRdIE5pY2hvbHMsIEsuLCBCbGFrZSwgUy4sIEJh
a2VyLCBGLiwgYW5kIEQuIEJsYWNrLA0KICAgRGVmaW5pdGlvbiBvZiB0aGUgRGlmZmVyZW50aWF0
ZWQgU2VydmljZXMgRmllbGQgKERTIEZpZWxkKSBpbiB0aGUNCiAgIElQdjQgYW5kIElQdjYgSGVh
ZGVycywgUkZDIDI0NzQsIERlY2VtYmVyIDE5OTguDQoNCiAgICA4LiBbUkZDIDM4MTRdIE5hZGVh
dSwgVC4sIFNyaW5pdmFzYW4sIEMuLCBhbmQgQS4gVmlzd2FuYXRoYW4sDQogICBNdWx0aXByb3Rv
Y29sIExhYmVsIFN3aXRjaGluZyAoTVBMUykgRm9yd2FyZGluZyBFcXVpdmFsZW5jZSBDbGFzcyBU
bw0KICAgTmV4dCBIb3AgTGFiZWwgRm9yd2FyZGluZyBFbnRyeSAoRkVDLVRvLU5ITEZFKSBNYW5h
Z2VtZW50IEluZm9ybWF0aW9uDQogICBCYXNlIChNSUIpLCBSRkMgMzgxNCwgSnVuZSAyMDA0Lg0K
DQogICAgOS4gW1JGQyAzODEzXSBTcmluaXZhc2FuLCBDLiwgVmlzd2FuYXRoYW4sIEEuLCBhbmQg
VC4gTmFkZWF1LA0KICAgTXVsdGlwcm90b2NvbCBMYWJlbCBTd2l0Y2hpbmcgKE1QTFMpIExhYmVs
IFN3aXRjaGluZyBSb3V0ZXIgKExTUikNCiAgIE1hbmFnZW1lbnQgSW5mb3JtYXRpb24gQmFzZSAo
TUlCKSwgUkZDIDM4MTMsIEp1bmUgMjAwNC4NCg0KDQoNCg0KQm91bmQsIGV0IGFsLiAgICAgICAg
ICAgRXhwaXJlcyBBdWd1c3QgMjEsIDIwMDUgICAgICAgICAgICAgICAgW1BhZ2UgMTNdDQoMDQpJ
bnRlcm5ldC1EcmFmdCAgICAgIEJpbmRpbmcgUGFja2V0cyB0byBGRUNzIGluIDZMU0EgICAgICAg
IEZlYnJ1YXJ5IDIwMDUNCg0KDQo4LiAgQWNrbm93bGVnZW1lbnRzDQoNCiAgIFRoZSBhdXRob3Jz
IGRlZXBseSBhcHByZWNpYXRlcyBNaXRyZSBtYW5hZ2VtZW50IHN1cHBvcnQgZm9yDQogICBpbXBs
ZW1lbnRhdGlvbiBvZiB0aGlzIHByb3RvY29sLg0KDQo5LiAgRGlzY2xhaW1lcg0KDQogICBUaGUg
YXV0aG9ycycgYWZmaWxpYXRpb24gd2l0aCBIUCBhbmQgdGhlIE1JVFJFIENvcnBvcmF0aW9uIGlz
DQogICBwcm92aWRlZCBmb3IgaWRlbnRpZmljYXRpb24gcHVycG9zZXMgb25seSwgYW5kIGlzIG5v
dCBpbnRlbmRlZCB0bw0KICAgY29udmV5IG9yIGltcGx5IGVpdGhlciBIUCdzIG9yIE1JVFJFknMg
Y29uY3VycmVuY2Ugd2l0aCwgb3Igc3VwcG9ydA0KICAgZm9yLCB0aGUgcG9zaXRpb25zLCBvcGlu
aW9ucyBvciB2aWV3cG9pbnRzIGV4cHJlc3NlZCBieSB0aGUgYXV0aG9ycy4NCg0KDQpBdXRob3Jz
JyBBZGRyZXNzZXMNCg0KICAgSmltIGJvdW5kDQogICBOQXY2VEYNCiAgIFAuTy4gQm94DQogICBI
b2xsaXMsIE5IICAyMjEwMg0KICAgVVNBDQoNCiAgIEVNYWlsOiBKaW0uYm91bmRAaHAuY29tDQoN
Cg0KICAgU2hhbSBDaGFrcmF2b3J0eQ0KICAgVGhlIE1JVFJFIENvcnBvcmF0aW9uDQogICAxNTc1
IENvbHNoaXJlIERyLg0KICAgTWNMZWFuLCBWQSAgMjIxMDINCiAgIFVTQQ0KDQogICBFTWFpbDog
c2NoYWtyYUBtaXRyZS5vcmcNCg0KDQogICBEb24gQ2hpcmllbGVpc29uDQogICBUaGUgTUlUUkUg
Q29ycG9yYXRpb24NCiAgIDc1MTUgQ29sc2hpcmUgRHIuDQogICBNY0xlYW4sIFZBICAyMjEwMg0K
ICAgVVNBDQoNCiAgIEVNYWlsOiBkb25jQG1pdHJlLm9yZw0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
CkJvdW5kLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDIxLCAyMDA1ICAgICAgICAg
ICAgICAgIFtQYWdlIDE0XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICBCaW5kaW5nIFBhY2tldHMg
dG8gRkVDcyBpbiA2TFNBICAgICAgICBGZWJydWFyeSAyMDA1DQoNCg0KSW50ZWxsZWN0dWFsIFBy
b3BlcnR5IFN0YXRlbWVudA0KDQogICBUaGUgSUVURiB0YWtlcyBubyBwb3NpdGlvbiByZWdhcmRp
bmcgdGhlIHZhbGlkaXR5IG9yIHNjb3BlIG9mIGFueQ0KICAgSW50ZWxsZWN0dWFsIFByb3BlcnR5
IFJpZ2h0cyBvciBvdGhlciByaWdodHMgdGhhdCBtaWdodCBiZSBjbGFpbWVkIHRvDQogICBwZXJ0
YWluIHRvIHRoZSBpbXBsZW1lbnRhdGlvbiBvciB1c2Ugb2YgdGhlIHRlY2hub2xvZ3kgZGVzY3Jp
YmVkIGluDQogICB0aGlzIGRvY3VtZW50IG9yIHRoZSBleHRlbnQgdG8gd2hpY2ggYW55IGxpY2Vu
c2UgdW5kZXIgc3VjaCByaWdodHMNCiAgIG1pZ2h0IG9yIG1pZ2h0IG5vdCBiZSBhdmFpbGFibGU7
IG5vciBkb2VzIGl0IHJlcHJlc2VudCB0aGF0IGl0IGhhcw0KICAgbWFkZSBhbnkgaW5kZXBlbmRl
bnQgZWZmb3J0IHRvIGlkZW50aWZ5IGFueSBzdWNoIHJpZ2h0cy4gIEluZm9ybWF0aW9uDQogICBv
biB0aGUgcHJvY2VkdXJlcyB3aXRoIHJlc3BlY3QgdG8gcmlnaHRzIGluIFJGQyBkb2N1bWVudHMg
Y2FuIGJlDQogICBmb3VuZCBpbiBCQ1AgNzggYW5kIEJDUCA3OS4NCg0KICAgQ29waWVzIG9mIElQ
UiBkaXNjbG9zdXJlcyBtYWRlIHRvIHRoZSBJRVRGIFNlY3JldGFyaWF0IGFuZCBhbnkNCiAgIGFz
c3VyYW5jZXMgb2YgbGljZW5zZXMgdG8gYmUgbWFkZSBhdmFpbGFibGUsIG9yIHRoZSByZXN1bHQg
b2YgYW4NCiAgIGF0dGVtcHQgbWFkZSB0byBvYnRhaW4gYSBnZW5lcmFsIGxpY2Vuc2Ugb3IgcGVy
bWlzc2lvbiBmb3IgdGhlIHVzZSBvZg0KICAgc3VjaCBwcm9wcmlldGFyeSByaWdodHMgYnkgaW1w
bGVtZW50ZXJzIG9yIHVzZXJzIG9mIHRoaXMNCiAgIHNwZWNpZmljYXRpb24gY2FuIGJlIG9idGFp
bmVkIGZyb20gdGhlIElFVEYgb24tbGluZSBJUFIgcmVwb3NpdG9yeSBhdA0KICAgaHR0cDovL3d3
dy5pZXRmLm9yZy9pcHIuDQoNCiAgIFRoZSBJRVRGIGludml0ZXMgYW55IGludGVyZXN0ZWQgcGFy
dHkgdG8gYnJpbmcgdG8gaXRzIGF0dGVudGlvbiBhbnkNCiAgIGNvcHlyaWdodHMsIHBhdGVudHMg
b3IgcGF0ZW50IGFwcGxpY2F0aW9ucywgb3Igb3RoZXIgcHJvcHJpZXRhcnkNCiAgIHJpZ2h0cyB0
aGF0IG1heSBjb3ZlciB0ZWNobm9sb2d5IHRoYXQgbWF5IGJlIHJlcXVpcmVkIHRvIGltcGxlbWVu
dA0KICAgdGhpcyBzdGFuZGFyZC4gIFBsZWFzZSBhZGRyZXNzIHRoZSBpbmZvcm1hdGlvbiB0byB0
aGUgSUVURiBhdA0KICAgaWV0Zi1pcHJAaWV0Zi5vcmcuDQoNCg0KRGlzY2xhaW1lciBvZiBWYWxp
ZGl0eQ0KDQogICBUaGlzIGRvY3VtZW50IGFuZCB0aGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGhl
cmVpbiBhcmUgcHJvdmlkZWQgb24gYW4NCiAgICJBUyBJUyIgYmFzaXMgYW5kIFRIRSBDT05UUklC
VVRPUiwgVEhFIE9SR0FOSVpBVElPTiBIRS9TSEUgUkVQUkVTRU5UUw0KICAgT1IgSVMgU1BPTlNP
UkVEIEJZIChJRiBBTlkpLCBUSEUgSU5URVJORVQgU09DSUVUWSBBTkQgVEhFIElOVEVSTkVUDQog
ICBFTkdJTkVFUklORyBUQVNLIEZPUkNFIERJU0NMQUlNIEFMTCBXQVJSQU5USUVTLCBFWFBSRVNT
IE9SIElNUExJRUQsDQogICBJTkNMVURJTkcgQlVUIE5PVCBMSU1JVEVEIFRPIEFOWSBXQVJSQU5U
WSBUSEFUIFRIRSBVU0UgT0YgVEhFDQogICBJTkZPUk1BVElPTiBIRVJFSU4gV0lMTCBOT1QgSU5G
UklOR0UgQU5ZIFJJR0hUUyBPUiBBTlkgSU1QTElFRA0KICAgV0FSUkFOVElFUyBPRiBNRVJDSEFO
VEFCSUxJVFkgT1IgRklUTkVTUyBGT1IgQSBQQVJUSUNVTEFSIFBVUlBPU0UuDQoNCg0KQ29weXJp
Z2h0IFN0YXRlbWVudA0KDQogICBDb3B5cmlnaHQgKEMpIFRoZSBJbnRlcm5ldCBTb2NpZXR5ICgy
MDA1KS4gIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdA0KICAgdG8gdGhlIHJpZ2h0cywgbGljZW5z
ZXMgYW5kIHJlc3RyaWN0aW9ucyBjb250YWluZWQgaW4gQkNQIDc4LCBhbmQNCiAgIGV4Y2VwdCBh
cyBzZXQgZm9ydGggdGhlcmVpbiwgdGhlIGF1dGhvcnMgcmV0YWluIGFsbCB0aGVpciByaWdodHMu
DQoNCg0KQWNrbm93bGVkZ21lbnQNCg0KICAgRnVuZGluZyBmb3IgdGhlIFJGQyBFZGl0b3IgZnVu
Y3Rpb24gaXMgY3VycmVudGx5IHByb3ZpZGVkIGJ5IHRoZQ0KICAgSW50ZXJuZXQgU29jaWV0eS4N
Cg0KDQoNCg0KQm91bmQsIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjEsIDIwMDUg
ICAgICAgICAgICAgICAgW1BhZ2UgMTVdDQoMDQo=

------_=_NextPart_001_01C51CFB.03194768
Content-Type: text/plain; name="draft-chakravorty-bcz-ipv6-flow-label-00.txt"
Content-Description: draft-chakravorty-bcz-ipv6-flow-label-00.txt
Content-Disposition: attachment;
	filename="draft-chakravorty-bcz-ipv6-flow-label-00.txt"
Content-Transfer-Encoding: base64

DQoNCk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBKLiBCb3VuZA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTkF2NlRGDQpFeHBpcmVzOiBBdWd1c3QgMjEs
IDIwMDUgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUy4gQ2hha3Jhdm9ydHkNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBLLiBaaGFuZw0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgVGhlIE1JVFJFIENvcnBvcmF0aW9uDQogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgRmVicnVhcnkgMjAsIDIwMDUNCg0KDQogICAg
ICAgICAgICAgICAgUHJvcG9zYWwgZm9yIGEgTmV3IEZsb3cgTGFiZWwgRGVmaW5pdGlvbg0KICAg
ICAgICAgICAgICAgICAgIGRyYWZ0LWNoYWtyYXZvcnR5LWJjYy1mbG93bGFiZWwtMDANCg0KU3Rh
dHVzIG9mIHRoaXMgTWVtbw0KDQogICBUaGlzIGRvY3VtZW50IGlzIGFuIEludGVybmV0LURyYWZ0
IGFuZCBpcyBzdWJqZWN0IHRvIGFsbCBwcm92aXNpb25zDQogICBvZiBzZWN0aW9uIDMgb2YgUkZD
IDM2NjcuICBCeSBzdWJtaXR0aW5nIHRoaXMgSW50ZXJuZXQtRHJhZnQsIGVhY2gNCiAgIGF1dGhv
ciByZXByZXNlbnRzIHRoYXQgYW55IGFwcGxpY2FibGUgcGF0ZW50IG9yIG90aGVyIElQUiBjbGFp
bXMgb2YNCiAgIHdoaWNoIGhlIG9yIHNoZSBpcyBhd2FyZSBoYXZlIGJlZW4gb3Igd2lsbCBiZSBk
aXNjbG9zZWQsIGFuZCBhbnkgb2YNCiAgIHdoaWNoIGhlIG9yIHNoZSBiZWNvbWUgYXdhcmUgd2ls
bCBiZSBkaXNjbG9zZWQsIGluIGFjY29yZGFuY2Ugd2l0aA0KICAgUkZDIDM2NjguDQoNCiAgIElu
dGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2lu
ZWVyaW5nDQogICBUYXNrIEZvcmNlIChJRVRGKSwgaXRzIGFyZWFzLCBhbmQgaXRzIHdvcmtpbmcg
Z3JvdXBzLiAgTm90ZSB0aGF0DQogICBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZSB3
b3JraW5nIGRvY3VtZW50cyBhcw0KICAgSW50ZXJuZXQtRHJhZnRzLg0KDQogICBJbnRlcm5ldC1E
cmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250
aHMNCiAgIGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhl
ciBkb2N1bWVudHMgYXQgYW55DQogICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2Ug
SW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZQ0KICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVt
IG90aGVyIHRoYW4gYXMgIndvcmsgaW4gcHJvZ3Jlc3MuIg0KDQogICBUaGUgbGlzdCBvZiBjdXJy
ZW50IEludGVybmV0LURyYWZ0cyBjYW4gYmUgYWNjZXNzZWQgYXQNCiAgIGh0dHA6Ly93d3cuaWV0
Zi5vcmcvaWV0Zi8xaWQtYWJzdHJhY3RzLnR4dC4NCg0KICAgVGhlIGxpc3Qgb2YgSW50ZXJuZXQt
RHJhZnQgU2hhZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nlc3NlZCBhdA0KICAgaHR0cDovL3d3
dy5pZXRmLm9yZy9zaGFkb3cuaHRtbC4NCg0KICAgVGhpcyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4
cGlyZSBvbiBBdWd1c3QgMjEsIDIwMDUuDQoNCkNvcHlyaWdodCBOb3RpY2UNCg0KICAgQ29weXJp
Z2h0IChDKSBUaGUgSW50ZXJuZXQgU29jaWV0eSAoMjAwNSkuDQoNCkFic3RyYWN0DQoNCiAgIFRo
ZSBJUHY2IGhlYWRlciBpbmNsdWRlcyBhIDIwLWJpdCBGbG93IExhYmVsIGZpZWxkLiAgUkZDIDM2
OTcsICJJUHY2DQogICBGbG93IExhYmVsIFNwZWNpZmljYXRpb24iIFsxXSBzcGVjaWZpZWQgdGhp
cyBmaWVsZCBhbmQgbWluaW11bQ0KICAgcmVxdWlyZW1lbnRzIGZvciB1c2luZyB0aGUgZmllbGQu
ICBUaGlzIGRvY3VtZW50IGZpcnN0IGlkZW50aWZpZXMNCiAgIHNldmVyYWwgaXNzdWVzIHJlbGF0
ZWQgdG8gdGhlIGN1cnJlbnQgRmxvdyBMYWJlbCBzcGVjaWZpY2F0aW9uOyB0aGVuDQogICBpdCBk
aXNjdXNzZXMgdGhlIGxpbWl0YXRpb25zIG9mIHRoZSBjdXJyZW50IHNwZWNpZmljYXRpb24gYW5k
IHRoZQ0KDQoNCg0KQm91bmQsIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjEsIDIw
MDUgICAgICAgICAgICAgICAgIFtQYWdlIDFdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICBQcm9wb3Nh
bCBmb3IgYSBOZXcgRmxvdyBMYWJlbCBEZWZpbml0aW9uIEZlYnJ1YXJ5IDIwMDUNCg0KDQogICBu
ZWVkIGZvciBleHRlbmRpbmcgdGhlIGRlZmluaXRpb24gdG8gYWNjb21tb2RhdGUgZW1lcmdpbmcN
CiAgIGFwcGxpY2F0aW9ucyBhbmQgcHJvdG9jb2xzOyBmaW5hbGx5LCBhIG5ldyBGbG93IExhYmVs
IHNwZWNpZmljYXRpb24NCiAgIGlzIHByb3Bvc2VkIHRoYXQgZW5hYmxlcyBtb3JlIGVmZmVjdGl2
ZSB1c2FnZSBvZiB0aGlzIGZpZWxkLg0KDQpUYWJsZSBvZiBDb250ZW50cw0KDQogICAxLiAgSW50
cm9kdWN0aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gIDMNCiAgIDIuICBCYWNrZ3JvdW5kIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgNA0KICAgMy4gIElzc3VlcyBDb25jZXJuaW5nIHRoZSBDdXJy
ZW50IEZsb3cgTGFiZWwgLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1DQogICA0LiAgTmV3IEZsb3cg
TGFiZWwgU3BlY2lmaWNhdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDcN
CiAgICAgNC4xICAgSW1wbGljYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAgOQ0KICAgNS4gIEFuIEVtZXJnaW5nIFVzYWdlIGZvciB0aGUgRmxvdyBM
YWJlbCBGaWVsZCAuIC4gLiAuIC4gLiAuIC4gLiAuICA5DQogICA2LiAgQmVuZWZpdHMgb2YgRmxl
eGlibGUgTGFiZWwgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTANCiAgIDcu
ICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAxMg0KICAgOC4gIEFja25vd2xlZ2VtZW50cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEzDQogICA5LiAgRGlzY2xhaW1lciAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTMNCiAgIDEwLiAgIFJl
ZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAxMw0KICAgICAgIEF1dGhvcnMnIEFkZHJlc3NlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIDE0DQogICAgICAgSW50ZWxsZWN0dWFsIFByb3BlcnR5IGFuZCBD
b3B5cmlnaHQgU3RhdGVtZW50cyAuIC4gLiAuIC4gLiAuIC4gMTUNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpCb3VuZCwgZXQg
YWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAgICAgW1Bh
Z2UgMl0NCgwNCkludGVybmV0LURyYWZ0ICAgIFByb3Bvc2FsIGZvciBhIE5ldyBGbG93IExhYmVs
IERlZmluaXRpb24gRmVicnVhcnkgMjAwNQ0KDQoNCjEuICBJbnRyb2R1Y3Rpb24NCg0KICAgVGhl
IElQdjYgaGVhZGVyIGluY2x1ZGVzIGEgMjAtYml0IEZsb3cgTGFiZWwgZmllbGQuICBSRkMgMzY5
NyBbMV0NCiAgIHNwZWNpZmllZCB0aGlzIGZpZWxkIGFuZCB0aGUgbWluaW11bSByZXF1aXJlbWVu
dHMgcmVxdWlyZWQgZm9yIHVzaW5nDQogICBpdC4gIFRoaXMgZG9jdW1lbnQgaWRlbnRpZmllcyBz
ZXZlcmFsIGlzc3VlcyByZWxhdGVkIHRvIHRoZSBjdXJyZW50DQogICBGbG93IExhYmVsIHNwZWNp
ZmljYXRpb24sIGl0IGFsc28gZGlzY3Vzc2VzIHRoZSBsaW1pdGF0aW9ucyBvZiB0aGUNCiAgIGN1
cnJlbnQgc3BlY2lmaWNhdGlvbiBhbmQgdGhlIG5lZWQgZm9yIGV4cGFuZGluZyB0aGUgZGVmaW5p
dGlvbiB0bw0KICAgYWNjb21tb2RhdGUgZW1lcmdpbmcgYXBwbGljYXRpb25zIGFuZCBwcm90b2Nv
bHMuICBBZGRpdGlvbmFsbHksIGEgbmV3DQogICBGbG93IExhYmVsIGRlZmluaXRpb24gaXMgcHJv
cG9zZWQgdGhhdCBlbmFibGVzIG1vcmUgZWZmZWN0aXZlIHVzZSBvZg0KICAgdGhpcyBmaWVsZC4N
Cg0KICAgQSBGbG93IExhYmVsIGlzIGRlZmluZWQgaW4gWzFdIHRvIGJlIJFhIHNlcXVlbmNlIG9m
IHBhY2tldHMgc2VudCBmcm9tDQogICBhIHBhcnRpY3VsYXIgc291cmNlIHRvIGEgcGFydGljdWxh
ciB1bmljYXN0LCBhbnljYXN0LCBvciBtdWx0aWNhc3QNCiAgIGRlc3RpbmF0aW9uIHRoYXQgdGhl
IHNvdXJjZSBkZXNpcmVzIHRvIGxhYmVsIGFzIGEgZmxvdy6SIEl0IG1heSBiZQ0KICAgdXNlZCBi
eSBhIHNvdXJjZSB0byBsYWJlbCBzZXF1ZW5jZXMgb2YgcGFja2V0cyBmb3Igd2hpY2ggaXQgcmVx
dWVzdHMNCiAgIHNwZWNpYWwgaGFuZGxpbmcgYnkgdGhlIElQdjYgcm91dGVycy4gIFN1Y2ggaGFu
ZGxpbmcgY291bGQgY29tcHJpc2UNCiAgIG5vbi1kZWZhdWx0IHF1YWxpdHkgb2Ygc2VydmljZSBv
ciCRcmVhbC10aW1lkiBzZXJ2aWNlLg0KDQogICBIb3cgdG8gaWRlbnRpZnkgYSBmbG93IGFuZCBh
c3NpZ24gbGFiZWxzIHRvIGZsb3dzIGFyZSBzcGVjaWZpZWQgaW4NCiAgIFJGQyAzNjk3WzFdIGFz
IGZvbGxvd3M6DQoNCiAgIAktIEEgZmxvdyBpcyB1bmlxdWVseSBpZGVudGlmaWVkIGJ5IHRoZSAz
LXR1cGxlIG9mIHNvdXJjZSBhZGRyZXNzLA0KICAgZGVzdGluYXRpb24gYWRkcmVzcyBhbmQgYSBu
b24temVybyBGbG93IExhYmVsLg0KDQogICAJLSBBbGwgcGFja2V0cyBiZWxvbmdpbmcgdG8gdGhl
IHNhbWUgZmxvdyBtdXN0IGJlIHNlbnQgd2l0aCB0aGUgc2FtZQ0KICAgc291cmNlIGFkZHJlc3Ms
IGRlc3RpbmF0aW9uIGFkZHJlc3MsIGFuZCBGbG93IExhYmVsLg0KDQogICAJLSBQYWNrZXRzIHRo
YXQgZG8gbm90IGJlbG9uZyB0byBhIGZsb3cgY2FycnkgYSBGbG93IExhYmVsIG9mIHplcm8uDQoN
CiAgIAktIE5ldyBGbG93IExhYmVscyBtdXN0IGJlIGNob3NlbiAocHNldWRvLSlyYW5kb21seSBh
bmQgdW5pZm9ybWx5DQogICBmcm9tIHRoZSByYW5nZSAxIHRvIEZGRkZGIGhleC4NCg0KICAgCS0g
VGhlIEZsb3cgTGFiZWwgdmFsdWUgc2V0IGJ5IHRoZSBzb3VyY2UgTVVTVCBiZSBkZWxpdmVyZWQg
dW5jaGFuZ2VkDQogICB0byB0aGUgZGVzdGluYXRpb24gbm9kZShzKS4NCg0KICAgCS0gTm9kZXMg
a2VlcGluZyBkeW5hbWljIGZsb3cgc3RhdGUgTVVTVCBOT1QgYXNzdW1lIHBhY2tldHMgYXJyaXZp
bmcNCiAgIDEyMCBzZWNvbmRzIG9yIG1vcmUgYWZ0ZXIgdGhlIHByZXZpb3VzIHBhY2tldCBvZiBh
IGZsb3cgc3RpbGwgYmVsb25nDQogICB0byB0aGUgc2FtZSBmbG93LCB1bmxlc3MgYSBmbG93IHN0
YXRlIGVzdGFibGlzaG1lbnQgbWV0aG9kIHN1cHBvcnRzDQogICBpdC4NCg0KICAgCS0gU291cmNl
IG5vZGVzIFNIT1VMRCBhc3NpZ24gZWFjaCB1bnJlbGF0ZWQgdHJhbnNwb3J0IGNvbm5lY3Rpb24g
YW5kDQogICBhcHBsaWNhdGlvbiBkYXRhIHN0cmVhbSB0byBhIG5ldyBmbG93LiBJdCBNVVNUIGVu
c3VyZSB0aGF0IGl0IGRvZXMNCiAgIG5vdCB1bmludGVudGlvbmFsbHkgcmV1c2UgRmxvdyBMYWJl
bCB2YWx1ZXMgaXQgaXMgY3VycmVudGx5IHVzaW5nIG9yDQogICBoYXMgcmVjZW50bHkgdXNlZCB3
aGVuIGNyZWF0aW5nIG5ldyBmbG93cy4NCg0KICAgCS0gVG8gdXNlIEZsb3cgTGFiZWxzIGZvciBj
bGFzc2lmeWluZyBhbmQgcHJvdmlkaW5nIHNwZWNpYWwgdHJlYXRtZW50DQogICBvZiB0cmFmZmlj
LCCRZmxvdyBzdGF0ZZIgbmVlZHMgdG8gYmUgZXN0YWJsaXNoZWQgb24gYWxsIG9yIGEgc3Vic2V0
DQogICBvZiBJUHY2IG5vZGVzIG9uIHRoZSBwYXRoIGZyb20gdGhlIHNvdXJjZSB0byB0aGUgZGVz
dGluYXRpb24ocykuIFRoZQ0KDQoNCg0KQm91bmQsIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBB
dWd1c3QgMjEsIDIwMDUgICAgICAgICAgICAgICAgIFtQYWdlIDNdDQoMDQpJbnRlcm5ldC1EcmFm
dCAgICBQcm9wb3NhbCBmb3IgYSBOZXcgRmxvdyBMYWJlbCBEZWZpbml0aW9uIEZlYnJ1YXJ5IDIw
MDUNCg0KDQogICCRZmxvdyBzdGF0ZZIgc2hvdWxkIGluY2x1ZGUgc3VmZmljaWVudCBpbmZvcm1h
dGlvbiBzbyB0aGF0IHBlcnRpbmVudA0KICAgSVB2NiBub2RlcyBjYW4gc3VwcG9ydCByZXF1aXJl
ZCBmbG93LWJhc2VkIHByb2Nlc3NpbmcuDQoNCiAgIEluIHRoaXMgZG9jdW1lbnQsIHdlIHByb3Bv
c2UgYSBtb2RpZmllZCB2ZXJzaW9uIG9mIHRoZSBhYm92ZQ0KICAgc3BlY2lmaWNhdGlvbiBmb3Ig
dGhlIElQdjYgRmxvdyBMYWJlbCB0byBhZGQgZmxleGliaWxpdHkgYW5kIGVhc2Ugb2YNCiAgIHVz
ZSBvZiB0aGUgRmxvdyBMYWJlbCBlc3BlY2lhbGx5IGZvciBRdWFsaXR5IG9mIFNlcnZpY2UgKFFv
UykNCiAgIGRlbGl2ZXJ5Lg0KDQogICBUaGlzIHNwZWNpZmljYXRpb24gYWxsb3dzIGZsb3dzIHRv
IGJlIGRlZmluZWQgYnkgb25seSB0aGUgRmxvdyBMYWJlbA0KICAgb25jZSB0aGUgdW5pcXVlbmVz
cyBvZiB0aGUgRmxvdyBMYWJlbCBoYXMgYmVlbiBhc2NlcnRhaW5lZCBmb3IgYQ0KICAgZ2l2ZW4g
ZmxvdyBiZXR3ZWVuIHR3byBvciBtb3JlIHBlZXJpbmcgcm91dGVycy4gIFN1Y2ggYXNzZXJ0aW9u
IGNhbg0KICAgYmUgbWFkZSBieSB0aGUgRmxvdyBMYWJlbCBhc3NvY2lhdGVkIHdpdGggdGhlIHNv
dXJjZSBhbmQgZGVzdGluYXRpb24NCiAgIGFkZHJlc3NlcywgaW5jb21pbmcgcG9ydCBvciBzb21l
IHN1Y2ggb3RoZXIgbWV0aG9kb2xvZ2llcyBhcw0KICAgZGVzY3JpYmVkIGluIFsyXS4NCg0KICAg
VGhlIEZsb3cgTGFiZWwgbmVlZCBub3QgYmUgc3RhdGljIG9yIGEgZml4ZWQgdmFsdWUgYmV0d2Vl
biB0aGUgc291cmNlDQogICBhbmQgZGVzdGluYXRpb24sIHRoYXQgaXMsIGl0IGNhbiBiZSBjaGFu
Z2VkIGVucm91dGUgcHJvdmlkZWQgdGhlDQogICBvcmlnaW5hbCBGbG93IExhYmVsIGlzIGRlbGl2
ZXJlZCBpbiB0aGUgcGFja2V0IGF0IHRoZSBkZXN0aW5hdGlvbi4NCg0KICAgQ2xhc3NpZnlpbmcg
b25lIG9yIG1vcmUgcGFja2V0cyBpbiBhIGZsb3cgaW50byBhIGNsYXNzIG9mIHBhY2tldHMsDQog
ICBjYWxsZWQgdGhlIEZvcndhcmRpbmcgRXF1aXZhbGVudCBDbGFzcyAoRkVDKSBbMl0sIG9mIGdp
dmVuDQogICBjaGFyYWN0ZXJpc3RpY3Mgb2YgUW9TLCBzZWN1cml0eSBvciBzb21lIG90aGVyIHBh
cmFtZXRlciBvciBhDQogICBjb21iaW5hdGlvbiBvZiBwYXJhbWV0ZXJzLCBpcyBhbGxvd2VkLiAg
VGhlIGZsb3cgc3RhdGUgY2FuIGJlDQogICBlc3RhYmxpc2hlZCBhdCB0aGUgc3RhcnQgb2YgYSBm
bG93IHJlcHJlc2VudGVkIGJ5IHRoZSBGbG93IExhYmVsIGFuZA0KICAgb25lIHRoYXQgY2FuIHJl
bGF0ZSB0byBhbiBGRUM7IHRoZSBjb3JyZXNwb25kaW5nIHNlcnZpY2UgY2FuIHRoZW4gYmUNCiAg
IGRlbGl2ZXJlZCBhcyBleHBlY3RlZCBmcm9tIHRoZSBmbG93LiAgT25jZSBhIGZsb3cgc3RhdGUg
aGFzIGJlZW4NCiAgIGVzdGFibGlzaGVkIGFuZCB0aGUgcGFja2V0IGlzIGJvdW5kIHRvIGFuIEZF
QywgcGFja2V0IGZvcndhcmRpbmcgY2FuDQogICB0aGVuIGJlIGJhc2VkIG9uIG9ubHkgdGhlIEZs
b3cgTGFiZWwsIHNlZSBbMl0uDQoNCiAgIFRoaXMgc3BlY2lmaWNhdGlvbiBvZiBGbG93IExhYmVs
IHRodXMgYWxsb3dzIGNoYW5naW5nIHRoZSBsYWJlbCB3aGlsZQ0KICAgdGhlIHBhY2tldCBpcyBl
bnJvdXRlIGZyb20gdGhlIHNvdXJjZSB0byB0aGUgZGVzdGluYXRpb24gYXMgbG9uZyBhcw0KICAg
dGhlIG9yaWdpbmFsIGxhYmVsIGlzIHJlc3RvcmVkIHByaW9yIHRvIGFycml2YWwgb2YgdGhlIHBh
Y2tldCBhdCB0aGUNCiAgIGRlc3RpbmF0aW9uLiAgVGhlIEZsb3cgTGFiZWwgdGh1cyBlbmFibGVz
IHByb2Nlc3Npbmcgb2YgZmxvd3MgYmFzZWQNCiAgIG9uIEZsb3cgTGFiZWwgb25seSBvbmNlIHRo
ZSBmbG93IGhhcyBiZWVuIHVuaXF1ZWx5IGlkZW50aWZpZWQgYnkgYQ0KICAgbGFiZWwgYW5kIGFs
c28gZW5hYmxlcyB0aGUgbm9kYWwgY2FwYWJpbGl0eSBmb3IgdXNpbmcgbGFiZWwgZm9yDQogICBw
YWNrZXQgY2xhc3NpZmljYXRpb24gYXMgd2VsbCBhcyBwYWNrZXQgZm9yd2FyZGluZy4NCg0KMi4g
IEJhY2tncm91bmQNCg0KICAgRHVyaW5nIHRoZSBwYXN0IGRlY2FkZSwgSW50ZXJuZXQgUW9TIGZy
YW1ld29yayBoYXMgYmVlbiBidWlsdCBhcm91bmQNCiAgIHRoZSBuZXR3b3JrIHRyYWZmaWMgY2xh
c3MgYmFzZWQgc2VydmljZSBkaWZmZXJlbnRpYXRpb24gYW5kIHRyYWZmaWMNCiAgIGVuZ2luZWVy
aW5nLiAgRGlmZlNlcnYgaGFzIGVtZXJnZWQgYXMgYSBwcmV2YWxlbnQgSW50ZXJuZXQgUW9TDQog
ICBmcmFtZXdvcmsgdGhhdCBmb2N1c2VzIG9uIHByb3ZpZGluZyBwZXJmb3JtYW5jZSBkaWZmZXJl
bnRpYXRpb24gdG8NCiAgIGRpZmZlcmVudCB0cmFmZmljIGNsYXNzZXMuICBXaXRoIHRoZSCRVHJh
ZmZpYyBDbGFzc5IgZmllbGQgaW4gdGhlDQogICBJUHY2IGhlYWRlciB0aGF0IG1hcHMgdG8gSVB2
NCBEaWZmU2VydiBDb2RlIFBvaW50cyAoRFNDUHMpLCBJUHY2IGNhbg0KICAgcmVhZGlseSBzdXBw
b3J0IHRoZSBRb1MgZnJhbWV3b3JrIHdpdGggdGhlIGhlbHAgb2YgdGhlIHNwZWNpZmljYXRpb24N
CiAgIG9mIGxhYmVsIHByb3ZpZGVkIGhlcmUuICBUaGlzIHN1cHBvcnRzIGNsYXNzL3ByaW9yaXR5
IGJhc2VkIHRyYWZmaWMNCiAgIHRyZWF0bWVudC4gIElQdjYgcHJvdG9jb2wgdGh1cyBwcm92aWRl
cyBzdXBwb3J0IGZvciBib3RoIGNsYXNzIGJhc2VkDQoNCg0KDQpCb3VuZCwgZXQgYWwuICAgICAg
ICAgICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAgICAgW1BhZ2UgNF0NCgwN
CkludGVybmV0LURyYWZ0ICAgIFByb3Bvc2FsIGZvciBhIE5ldyBGbG93IExhYmVsIERlZmluaXRp
b24gRmVicnVhcnkgMjAwNQ0KDQoNCiAgIG9yIGZsb3cgYmFzZWQgcGFja2V0IGNsYXNzaWZpY2F0
aW9ucyBhcyB3ZWxsIGFzIHNwZWNpZmljIHBhY2tldA0KICAgZm9yd2FyZGluZyB0cmVhdG1lbnQg
cmVsYXRlZCB0byBzdWNoIGNsYXNzaWZpY2F0aW9ucy4NCg0KICAgQXMgb2YgdG9kYXksIHRoZSBk
ZXBsb3ltZW50IG9mIHBlci1mbG93IGJhc2VkIHBhY2tldCBmb3J3YXJkaW5nDQogICB0cmVhdG1l
bnQgaXMgcmF0aGVyIGxpbWl0ZWQgaW4gYW4gSVB2NiBuZXR3b3JrLiAgVGhlIDIwLWJpdCBGbG93
DQogICBMYWJlbCBmaWVsZCAod2hldGhlciBzZXQgYnkgdGhlIGVuZCBhcHBsaWNhdGlvbnMgb3Ig
bm90KSBpcyBpZ25vcmVkDQogICBieSBtb3N0IG5ldHdvcmsgZGV2aWNlcy4gIFRoaXMgcHJlc2Vu
dHMgYSBzaWduaWZpY2FudCB3YXN0ZSBvZg0KICAgYnVpbHQtaW4gSVB2NiBjYXBhYmlsaXRpZXM7
IHRoZSBsYWJlbCBmaWVsZCBjb3VsZCBoYXZlIGJlZW4NCiAgIGVmZmVjdGl2ZWx5IHVzZWQgdG93
YXJkIGVuaGFuY2luZyB0aGUgb3ZlcmFsbCBJUHY2IHByb3RvY29sDQogICBmdW5jdGlvbmFsaXR5
IGlmIGNlcnRhaW4gbWVhc3VyZSBvZiBmbGV4aWJpbGl0eSB3ZXJlIGFsbG93ZWQgaW4gaXRzDQog
ICBkZWZpbml0aW9uIGFuZCB1c2FnZS4NCg0KICAgVGhlIHByaW1hcnkgYXBwbGljYXRpb24gb2Yg
SVB2NiBGbG93IExhYmVsIHdhcyB0byBmYWNpbGl0YXRlIHBlciBmbG93DQogICByZXNvdXJjZSBh
bGxvY2F0aW9uIGFuZC9vciBwYWNrZXQgdHJlYXRtZW50LCBzbyB0aGF0IGRlc2lyYWJsZSBRb1MN
CiAgIGNhbiBiZSBkZWxpdmVyZWQuICBBbiBJUHY2IGZsb3cgaXMgY3VycmVudGx5IGRlZmluZWQg
b24gYW4gZW5kLXRvLWVuZA0KICAgYmFzaXMgYmV0d2VlbiB0aGUgc291cmNlIGFuZCBkZXN0aW5h
dGlvbi4gIEl0IHdhcyBkZXNpZ25lZCBiYXNlZCBvbg0KICAgYW4gZW5kLXRvLWVuZCBmaXhlZCBs
YWJlbCBhc3NpZ25tZW50IHRoYXQgd291bGQgc2lnbmFsIHNwZWNpYWwNCiAgIHRyYWZmaWMgdHJl
YXRtZW50IGJ5IG5ldHdvcmsgZGV2aWNlcyBhdCB0aGUgZmxvdyBsZXZlbCBncmFudWxhcml0eS4N
CiAgIFRodXMsIHVzaW5nIEZsb3cgTGFiZWxzLCB0cmFmZmljIGNvdWxkIGJlIGNsYXNzaWZpZWQg
aW50byBwZXINCiAgIGFwcGxpY2F0aW9uIGZsb3dzLCBwb3NzaWJseSBldmVuIHRvIGEgZmluZXIg
bGV2ZWwsIGUuZy4sIGJhc2VkIG9uDQogICB0cmFuc2FjdGlvbnMgZm9yIGFuIGFwcGxpY2F0aW9u
Lg0KDQogICBUaGUgRmxvdyBMYWJlbCBmaWVsZCB3YXMgYWxsb3dlZCBmb3IgbWFwcGluZyB0byBr
bm93biBmbG93cyBzdWNoIGFzDQogICBUQ1AgY29ubmVjdGlvbnMsIGFwcGxpY2F0aW9uIHN0cmVh
bXMsIGV0Yy4sIGJ1dCBubyBzZXJ2aWNlIG1vZGVscyBvcg0KICAgbWVjaGFuaXNtcyB3ZXJlIHBy
b3ZpZGVkIFsxXS4NCg0KICAgVGhlIElQdjYgRmxvdyBMYWJlbCBmaWVsZCByZW1haW5lZCB1bnVz
ZWQgYW5kIGlnbm9yZWQgYnkgYWxsIGZvcg0KICAgbmVhcmx5IGEgZGVjYWRlIGFsdGhvdWdoIHVz
ZSBvZiBhIHNpbWlsYXIgMjAtYml0IGxhYmVsIGZpZWxkIGluDQogICBNdWx0aXByb3RvY29sIExh
YmVsIFN3aXRjaGluZyAoTVBMUykgcHJvdG9jb2wgZm9yIHNpbWlsYXIgcHVycG9zZXMNCiAgIHJl
Y2VpdmVkIHdpZGUgaW1wbGVtZW50YXRpb24gc3VwcG9ydCBkdXJpbmcgdGhlIHNhbWUgcGVyaW9k
Lg0KDQozLiAgSXNzdWVzIENvbmNlcm5pbmcgdGhlIEN1cnJlbnQgRmxvdyBMYWJlbA0KDQogICBX
aXRoIHRoZSBjdXJyZW50IEZsb3cgTGFiZWwgZGVmaW5pdGlvbiBbMV0sIHByb3ZpZGluZyBmb3Ig
cGVyLWZsb3cNCiAgIFFvUyBtYXkgYmUgYSBkaWZmaWN1bHQgcHJvY2Vzcy4gIFdlIGhpZ2hsaWdo
dCBzZXZlcmFsIGlzc3Vlcw0KICAgY29uY2VybmluZyBwZXItZmxvdyBRb1Mgc3VwcG9ydCB1c2lu
ZyB0aGUgRmxvdyBMYWJlbCBmaWVsZC4NCg0KICAgCS0gIFRoZSBzdGF0aWMgYWxsb2NhdGlvbiBv
ZiBGbG93IExhYmVscyBkZWZpbmluZyBmaXhlZCwgZW5kLXRvLWVuZA0KICAgZmxvd3MgaW4gbGFy
Z2UgbmV0d29ya3MgaXMgdW53aWVsZHkgYXQgYmVzdC4gSWYgdGhlIHNwZWNpZmljYXRpb24gaGFk
DQogICBhbGxvd2VkIGZvciBkeW5hbWljIGFsbG9jYXRpb24gb2YgRmxvdyBMYWJlbHMgYXMgZmxv
d3Mgd2VyZSBzZXQgdXANCiAgIGFuZCB0b3JuIGRvd24gKG9yIHByb2dyZXNzZWQgb3ZlciBtdWx0
aXBsZSBob3BzKSwgdGhlIG5ldHdvcmsNCiAgIGFkbWluaXN0cmF0b3JzIGFuZC9vciB1c2VycyB3
b3VsZCBoYXZlIGhhZCB0aGUgbGF0aXR1ZGUgdG8gdXNlIG9uZSBvcg0KICAgbW9yZSBsYWJlbHMg
KGluIHRoZSBzYW1lIGZsb3dzKSAtIGFzIGFuZCB3aGVuIG5lY2Vzc2FyeSBhbmQgZm9yDQogICBk
aWZmZXJlbnQgcHVycG9zZXMuIFRoZSBzdGF0aWMgY2hhcmFjdGVyaXN0aWMgb2YgdGhlIEZsb3cg
TGFiZWwNCiAgIGFsbG9jYXRpb24gZW5kLXRvLWVuZCBhbmQgaXRzIDMtdHVwbGUgYXNzb2NpYXRp
b24gd2l0aCBzb3VyY2UgYW5kDQogICBkZXN0aW5hdGlvbiBhZGRyZXNzZXMgKHdoaWNoIGFyZSBh
bHNvIHN0YXRpYyBlbmQtdG8tZW5kKSByZW5kZXJzIHRoZQ0KICAgdmlldyB0aGF0IHRoZSBGbG93
IExhYmVsIGlzIHRoZXJlIHRvIGV4dGVuZCB0aGUgYWRkcmVzcyBzcGFjZSBpbnRvDQogICB0aGUg
RmxvdyBMYWJlbCBmaWVsZC4gQ29udmVyc2VseSwgb25lIGNvdWxkIHVzZSB0aGUgc291cmNlIGFu
ZA0KDQoNCg0KQm91bmQsIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjEsIDIwMDUg
ICAgICAgICAgICAgICAgIFtQYWdlIDVdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICBQcm9wb3NhbCBm
b3IgYSBOZXcgRmxvdyBMYWJlbCBEZWZpbml0aW9uIEZlYnJ1YXJ5IDIwMDUNCg0KDQogICBkZXN0
aW5hdGlvbiBhZGRyZXNzZXMgaW4gY29uanVuY3Rpb24gd2l0aCB0aGUgVHJhZmZpYyBDbGFzcyBm
aWVsZCB0bw0KICAgcHJvdmlkZSB0aGUgc2FtZSBzZXJ2aWNlcyB3aXRob3V0IHVzaW5nIHRoZSBG
bG93IExhYmVsIGF0IGFsbC4gVGhlcmUNCiAgIGlzIG5vIG5lZWQgZm9yIGEgc2VwYXJhdGUgc3Rh
dGljIDIwLWJpdCBmaWVsZCwgdGhhdCBoYXMgdG8gYmUgdXNlZA0KICAgZW5kLXRvLWVuZCwgb24g
dG9wIG9mIHRoZSAyNTYgYml0cyBvZiBhZGRyZXNzIHNwYWNlIHRvIGlkZW50aWZ5IGENCiAgIGZs
b3cuDQoNCiAgIAktICBTcGVjaWZpYyBmbG93IHN0YXRlIGVzdGFibGlzaG1lbnQgbWV0aG9kcyBh
bmQgdGhlIHJlbGF0ZWQgc2VydmljZQ0KICAgbW9kZWxzIGFyZSBvdXQgb2Ygc2NvcGUgaW4gdGhl
IGN1cnJlbnQgbGFiZWwgc3BlY2lmaWNhdGlvbiBbMV0uDQogICBEZXZvaWQgb2YgYSBtZXRob2Rv
bG9neSBmb3IgZXN0YWJsaXNoaW5nIGEgZmxvdyBvciBmb3IgcHJvdmlzaW9uaW5nDQogICBzZXJ2
aWNlcyB1c2luZyBlc3RhYmxpc2hlZCBmbG93cyBtZWFudCB0aGUgRmxvdyBMYWJlbCBzcGVjaWZp
Y2F0aW9uDQogICBpcyBpbmNvbXBsZXRlIGFuZCBwb3NzaWJseSBpbmFkZXF1YXRlIHRvd2FyZCBw
cm92aWRpbmcgaW1wbGVtZW50YXRpb24NCiAgIGFuZCBkZXBsb3ltZW50IGRpcmVjdGlvbiBmb3Ig
ZWZmaWNpZW50IHVzZSBvZiB0aGUgbGFiZWwuDQoNCiAgIAktICBBcyB0aGUgRmxvdyBMYWJlbCBm
aWVsZCBjYXJyaWVzIGEgc3RhdGljLCBmaXhlZCBsYWJlbCBnZW5lcmF0ZWQNCiAgIGJ5IGEgc291
cmNlIGhvc3QsIGZvciBhIGZsb3cgdG8gcmVjZWl2ZSByZXF1ZXN0ZWQgdHJlYXRtZW50IGluIHRo
ZQ0KICAgbmV0d29yaywgYSBzaWduYWxpbmcgcHJvdG9jb2wgc3VjaCBhcyB0aGUgTGFiZWwgRGlz
dHJpYnV0aW9uIFByb3RvY29sDQogICAoTERQKSAodXNlZCBpbiBNUExTKSBvciBSZXNvdXJjZSBS
ZXNlcnZhdGlvbiBQcm90b2NvbCAoUlNWUCkgbXVzdCBiZQ0KICAgdXNlZCB0byBkaXN0cmlidXRl
IHRoZSBsYWJlbCBiaW5kaW5nIChwYWNrZXQgY2xhc3NpZmljYXRpb24pDQogICBpbmZvcm1hdGlv
biAoZm9yIHRoaXMgc291cmNlLWJhc2VkIHBhY2tldCBjbGFzc2lmaWNhdGlvbikgdG8gYWxsDQog
ICBvdGhlciBub2RlcyBpbiB0aGUgbmV0d29yay4gVGhlIGN1cnJlbnQgRmxvdyBMYWJlbCBzcGVj
aWZpY2F0aW9uIFsxXQ0KICAgZG9lcyBub3QgcHJvdmlkZSBhbnkgbWVjaGFuaXNtIGZvciBwcm9w
YWdhdGluZyBsYWJlbCBiaW5kaW5nDQogICBpbmZvcm1hdGlvbiBpbnRvIHRoZSBuZXR3b3JrIHdo
aWNoIG1ha2VzIHRoZSBjdXJyZW50IEZsb3cgTGFiZWwNCiAgIHNwZWNpZmljYXRpb24gZGlmZmlj
dWx0IHRvIGltcGxlbWVudC4NCg0KICAgCS0gIFRvIGVuc3VyZSB0aGF0IGZsb3dzIGNhbiBiZSBp
ZGVudGlmaWVkIHVuaXF1ZWx5IGluIHRoZSBuZXR3b3JrLA0KICAgdGhlIDMtdHVwbGUgb2YgRmxv
dyBMYWJlbCwgU291cmNlIGFuZCBEZXN0aW5hdGlvbiBhZGRyZXNzZXMgaXMgdXNlZA0KICAgdG8g
ZGVmaW5lIGEgZmxvdy4gR2l2ZW4gdGhlIGxhcmdlIGFkZHJlc3MgZmllbGQgdXNlZCBieSB0aGUg
SVB2Ng0KICAgcHJvdG9jb2wsIHRoZSBtZW1vcnkgcmVxdWlyZW1lbnRzIGZvciBtYWludGFpbmlu
ZyBhIGZsb3cgc3RhdGUgdGhhdA0KICAgaW5jbHVkZXMgdHdvIDEyOC1iaXQgYWRkcmVzc2VzIGFu
ZCBhIDIwLWJpdCBGbG93IExhYmVsIChmb3IgYSB0b3RhbA0KICAgb2YgMjc2IGJpdHMpIGNhbiBi
ZSBzaWduaWZpY2FudCB3aGVuIHRlbnMgb2YgdGhvdXNhbmRzIG9mIGZsb3dzIGFyZQ0KICAgaW4g
b3BlcmF0aW9uIGluIGEgbmV0d29yayBub2RlLiBNb3Jlb3ZlciwgdGhlIG9wZXJhdGlvbnMgdXNl
ZCBmb3INCiAgIGZsb3cgbG9vay11cHMgbWF5IGFsc28gYmUgcHJvY2Vzc2luZyBpbnRlbnNpdmUg
aW52b2x2aW5nIG11bHRpcGxlDQogICBtZW1vcnkgZmV0Y2hlcyBwZXIgZmxvdyBpbiAzMi1iaXQg
b3IgNjQtYml0IG1hY2hpbmVzLiBUaGlzIGlzIG5vdA0KICAgZGVzaXJhYmxlIGZvciBzbWFsbCBv
ciBwb3J0YWJsZSBkZXZpY2VzIHdpdGggbGltaXRlZCBtZW1vcnkgYW5kDQogICBwcm9jZXNzaW5n
IHBvd2VyLg0KDQogICAJLSAgSW4gSVB2NiBwYWNrZXRzIHRoYXQgbXVzdCB0cmF2ZXJzZSBlcnJv
cpdwcm9uZSBvciB1bnJlbGlhYmxlDQogICBsaW5rcywgZXJyb3JzIG1heSBpbmFkdmVydGVudGx5
IGNoYW5nZSB0aGUgRmxvdyBMYWJlbCBiaXRzLiBBcyB0aGUNCiAgIHN0YXRpYyBGbG93IExhYmVs
IGlzIHRvIGJlIHVzZWQgZW5kLXRvLWVuZCwgdGhlIGVycm9ycyBtYXkgcmVzdWx0IGluDQogICBm
bG93cyB0aGF0IGNhbiBub3QgYmUgbWF0Y2hlZCB0byBhbnkgZmxvdyAocGFja2V0KSB0cmVhdG1l
bnQgcHJvZmlsZS4NCiAgIFRoZSBjdXJyZW50IHNwZWNpZmljYXRpb24gb2YgRmxvdyBMYWJlbCBk
b2VzIG5vdCBhZGRyZXNzIGhvdyBlcnJvcmVkDQogICBwYWNrZXRzIG5lZWQgdG8gYmUgaGFuZGxl
ZCBvciBpZiB0aGV5IGNhbiBiZSBwcm9jZXNzZWQgYXQgYWxsIGluIHRoZQ0KICAgZXJyb3ItcHJv
bmUgbGlua3MuIEZ1cnRoZXJtb3JlLCBlcnJvcmVkIHBhY2tldHMgaW4gVENQIHN0cmVhbXMgd2ls
bA0KICAgZmFpbCBjaGVja3N1bXMgYXQgdGhlIGRlc3RpbmF0aW9uIGhvc3QgcmVzdWx0aW5nIGlu
IHVubmVjZXNzYXJ5DQogICByZXRyYW5zbWlzc2lvbnMgYW5kIHBvc3NpYmxlIGNvbmdlc3Rpb24u
IChPbiB0aGUgb3RoZXIgaGFuZCwgZmxleGlibGUNCiAgIEZsb3cgTGFiZWwgYXMgcHJvcG9zZWQg
aW4gdGhpcyBkb2N1bWVudCBvbmx5IGhhcyBsb2NhbCBzaWduaWZpY2FuY2UNCiAgIGFuZCBhcyBz
dWNoIGhhcyBsaW1pdGVkIHZ1bG5lcmFiaWxpdHkuKQ0KDQoNCg0KDQpCb3VuZCwgZXQgYWwuICAg
ICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAgICAgW1BhZ2UgNl0N
CgwNCkludGVybmV0LURyYWZ0ICAgIFByb3Bvc2FsIGZvciBhIE5ldyBGbG93IExhYmVsIERlZmlu
aXRpb24gRmVicnVhcnkgMjAwNQ0KDQoNCiAgIAktICBUaGUgZml4ZWQgbGFiZWwgTVVTVCBiZSBk
ZWxpdmVyZWQgdW5jaGFuZ2VkIHRvIHRoZSBkZXN0aW5hdGlvbg0KICAgbm9kZXM7IHRoaXMgZXZl
biBhcHBsaWVzIHRvIHRoZSB6ZXJvIEZsb3cgTGFiZWwgd2hpY2ggaXMgdXNlZCBmb3INCiAgIGxh
YmVsaW5nIHBhY2tldHMgdGhhdCBhcmUgbm90IHBhcnQgb2YgYW55IGZsb3cgKGZvciBub2RlcyB0
aGF0IGRvIG5vdA0KICAgc3VwcG9ydCBGbG93IExhYmVsIGJhc2VkIGZsb3dzKS4gSXQgaXMgbm90
IGNsZWFyIGhvdyB0aGlzIHJlcXVpcmVtZW50DQogICBjb250cmlidXRlcyBhbnkgdXNlZnVsIGZ1
bmN0aW9uYWxpdHkuIFRoaXMgY29uc3RpdHV0ZXMgYW4gaWRlYWwNCiAgIG1lY2hhbmlzbSBmb3Ig
bWFuLWluLXRoZS1taWRkbGUgYXR0YWNrcy4gV2hhdCBpcyBuZWVkZWQgdG8gZGVyYWlsIGFuDQog
ICBlbmQtdG8tZW5kIHN0YXRpY2FsbHkgZGVmaW5lZCBmbG93IGlzIHRvIHNpbXBseSBpbnNlcnQg
YWxsIHplcm9lcyBpbg0KICAgdGhlIEZsb3cgTGFiZWwgZmllbGQgdGh1cyBtYWtpbmcgdGhlIGZs
b3cgYSAnbm9uLWZsb3cnLiBUaGUgZmxvdw0KICAgbWVhbnQgZm9yIFFvUyBkZWxpdmVyeSBiZWNv
bWVzIG1lYW5pbmdsZXNzIGFuZCBjb3VsZCBwb3RlbnRpYWxseSBiZQ0KICAgaGFybWZ1bCB0byBh
IG1pc3Npb24uDQoNCiAgIAktICBTY2FsYWJpbGl0eSBpcyBhbm90aGVyIGlzc3VlIHdpdGggdGhl
IHN0YXRpYywgZml4ZWQgRmxvdyBMYWJlbA0KICAgYXNzaWdubWVudC4gU3RhdGljIGFzc2lnbm1l
bnRzIGFyZSBub3QgY29uc2lkZXJlZCBieSB0aGVpciB2ZXJ5DQogICBuYXR1cmUgc2NhbGFibGUu
IEZvciBpbnN0YW5jZSwgdGhlIHByb2plY3RlZCBkZXBsZXRpb24gb2YgdGhlIGZpeGVkDQogICBh
ZGRyZXNzIHNwYWNlIGluIElQdjQgaGFzIHJlc3VsdGVkIGluIHRoZSBhZG9wdGlvbiBvZiBJUHY2
IChmb3IgaXRzDQogICBodWdlIGFkZHJlc3Mgc3BhY2UpLiBGbGV4aWJpbGl0eSBpbiB0aGUgYXNz
aWdubWVudCBvZiB2YWx1ZXMgdG8gYSBiaXQNCiAgIGZpZWxkIGFzIGFuZCB3aGVuIG5lZWRlZCBp
cyBjb25zaWRlcmVkIGluIGdlbmVyYWwgYSBnb29kIGlkZWEuICBUaGlzDQogICBpcyB0cnVlIGZv
ciB0aGUgRmxvdyBMYWJlbCBhcyB3ZWxsLg0KDQogICBUbyBzdW1tYXJpemUsIHRoZSBjdXJyZW50
IElQdjYgRmxvdyBMYWJlbCBpcyBsaXR0bGUgdXNlZDsgaXRzIGN1cnJlbnQNCiAgIHNwZWNpZmlj
YXRpb24gaXMgY29uZnVzaW5nLiAgQWJzZW50IGFuIGFzc29jaWF0ZWQgbWVjaGFuaXNtIGZvciBs
YWJlbA0KICAgYmluZGluZyBkaXN0cmlidXRpb24sIHRoZSBzcGVjaWZpY2F0aW9uIHByb3ZpZGVz
IGxpdHRsZSBpbiB3YXkgb2YNCiAgIGZ1bmN0aW9uYWxpdGllcyBmb3IgdGhlIElQdjYgcHJvdG9j
b2wuICBJdHMgYXBwbGljYXRpb24gaW4gcHJvdmlkaW5nDQogICBmbG93IGJhc2VkIFFvUyBoYXMg
bm90IGJlZW4gZGVmaW5lZCwgaXRzIGltcGxlbWVudGF0aW9uIGJ5IG5ldHdvcmsNCiAgIGRldmlj
ZXMgbWF5IHByb3ZlIHRvIGJlIGV4cGVuc2l2ZSBhbmQgbWF5IGludHJvZHVjZSBpc3N1ZXMgY29u
Y2VybmluZw0KICAgcHJvcGVyIHVzZSBvZiB0aGUgYXZhaWxhYmxlIHJlc291cmNlcy4gIEl0cyB1
c2UgaW4gdGhlIGVycm9yLXByb25lDQogICBtZWRpYSBpcyBxdWVzdGlvbmFibGUuICBJdCBpcyB2
dWxuZXJhYmxlIHRvIHRoZSBtYW4taW4tdGhlLW1pZGRsZQ0KICAgYXR0YWNrcy4NCg0KICAgRmlu
YWxseSwgdGhlIGN1cnJlbnQgc3BlY2lmaWNhdGlvbiBpcyB0b28gcmVzdHJpY3RpdmUgdG8gYWxs
b3cgaXRzDQogICB3aWRlLXNwcmVhZCB1c2U7IHRoZSBzdGF0aWMgYWxsb2NhdGlvbiBvZiB0aGUg
RmxvdyBMYWJlbCByYWlzZXMNCiAgIHF1ZXN0aW9ucyByZWdhcmRpbmcgaXRzIHNjYWxhYmlsaXR5
LiAgSXQgaXMgc2FmZSB0byBhc3N1bWUgdGhhdA0KICAgZW1lcmdpbmcgYXBwbGljYXRpb25zIHdp
bGwgZmluZCBpdCBkaWZmaWN1bHQgdG8gdGFrZSBhZHZhbnRhZ2Ugb2YgdGhlDQogICBjdXJyZW50
IEZsb3cgTGFiZWwgc3BlY2lmaWNhdGlvbi4NCg0KNC4gIE5ldyBGbG93IExhYmVsIFNwZWNpZmlj
YXRpb24NCg0KICAgVGhpcyBkb2N1bWVudCBwcm9wb3NlcyBsaW1pdGVkIG1vZGlmaWNhdGlvbiB0
byB0aGUgY3VycmVudA0KICAgc3BlY2lmaWNhdGlvbiBvZiB0aGUgRmxvdyBMYWJlbC4NCg0KICAg
SW4gdGhpcyBuZXcgc3BlY2lmaWNhdGlvbiwgdGhlIDIwLWJpdCBGbG93IExhYmVsIGluIHRoZSBJ
UHY2IGhlYWRlcg0KICAgaXMgdXNlZCBieSBhIGhvc3Qgb3IgbmV0d29yayBub2RlIHRvIGxhYmVs
IG9uZSBvciBtb3JlIHBhY2tldHMgb2YgYQ0KICAgZmxvdy4gIEluIHRoaXMgY29uZmlndXJhdGlv
biB0aGUgbGFiZWwgc3RpbGwgY29tcHJpc2VzIDIwLWJpdHMgLSBzYW1lDQogICBhcyBpbiB0aGUg
b3JpZ2luYWwgc3BlY2lmaWNhdGlvbiBbMV0sIGhvd2V2ZXIsIGFuIGFsbC16ZXJvIGxhYmVsIGNh
bg0KICAgYmUgdXNlZCBmb3IgaWRlbnRpZnlpbmcgYSBzcGVjaWZpYyBmbG93IHN1Y2ggYXMgZm9y
IHRoZSBsZWFzdA0KICAgc2lnbmlmaWNhbnQsIGRlZmF1bHQgY2xhc3Mgb2Ygc2VydmljZSBpbiB0
aGUgZGlmZmVyZW50aWF0ZWQgc2VydmljZQ0KICAgYXJjaGl0ZWN0dXJlLg0KDQoNCg0KDQpCb3Vu
ZCwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAg
ICAgW1BhZ2UgN10NCgwNCkludGVybmV0LURyYWZ0ICAgIFByb3Bvc2FsIGZvciBhIE5ldyBGbG93
IExhYmVsIERlZmluaXRpb24gRmVicnVhcnkgMjAwNQ0KDQoNCiAgIFBhY2tldCBjbGFzc2lmaWNh
dGlvbiB1c2VzIG9ubHkgdGhlIEZsb3cgTGFiZWwgdG8gaWRlbnRpZnkgd2hpY2ggZmxvdw0KICAg
YSBwYXJ0aWN1bGFyIHBhY2tldCBiZWxvbmdzIHRvLiAgVGhlIHVzZSBvZiBvdGhlciBpbmZvcm1h
dGlvbiBpbiB0aGUNCiAgIHBhY2tldCBoZWFkZXIgb3IgbmV0d29yayBub2RlIGNhbiBhbHNvIGJl
IHVzZWQgd2hlbiBuZWNlc3NhcnkgdG8NCiAgIGlkZW50aWZ5IGEgZmxvdyBmb3IgcmVuZGVyaW5n
IGxhYmVsIGJpbmRpbmcgc2lnbmlmaWNhbmNlIHRvIGEgZmxvdy4NCiAgIEZvciBleGFtcGxlLCB0
aGUgc291cmNlIGFuZC9vciBkZXN0aW5hdGlvbiBhZGRyZXNzZXMgaW4gdGhlIGZvcm1lcg0KICAg
Y2FzZSBhbmQgcGh5c2ljYWwgcG9ydCBhZGRyZXNzIGluIHRoZSBsYXR0ZXIgd291bGQgYmUgZXhh
bXBsZXMgb2YNCiAgIHN1Y2ggaW5mb3JtYXRpb24uDQoNCiAgIFRoZSBGbG93IExhYmVsIGhhcyBs
b2NhbCBzaWduaWZpY2FuY2UgLSB0aGUgc2NvcGUgb2YgdGhpcyBjb3VsZCBiZQ0KICAgbGltaXRl
ZCB0byBhIHNpbmdsZSBob3Agb3IgZXh0ZW5kZWQgdG8gYSB3aG9sZSBuZXR3b3JrIGRvbWFpbi4g
IEENCiAgIGZsb3cgdXNpbmcgYSB1bmlxdWUgbGFiZWwgY2FuIGJlIGluaXRpYXRlZCBhdCBhIGhv
c3Qgb3IgYW55IG5vZGUgaW4gYQ0KICAgbmV0d29yay4gIFNpbWlsYXJseSwgYSBmbG93IGNhbiBi
ZSB0ZXJtaW5hdGVkIGF0IHRoZSBhZGphY2VudA0KICAgZG93bnN0cmVhbSBub2RlIGluIGNhc2Ug
b2YgYSBzaW5nbGUtaG9wIGZsb3cgb3IgY2FuIGNvbnRpbnVlIGZvcg0KICAgc2V2ZXJhbCBob3Bz
IGRlcGVuZGluZyBvbiB0aGUgZXh0ZW50IG9mIHVzZSBvZiB0aGUgb3JpZ2luYWwgbGFiZWwNCiAg
IGJpbmRpbmcuDQoNCiAgIFBhY2tldHMgaW4gYSBmbG93IGFyZSBwcm9jZXNzZWQgaW4gYSBmbG93
LXNwZWNpZmljIG1hbm5lciBieSB0aGUNCiAgIG5vZGVzIHRoYXQgaGF2ZSBiZWVuIHNldCB1cCB3
aXRoIGZsb3ctc3BlY2lmaWMgc3RhdGUuICBUaGUgRmxvdyBMYWJlbA0KICAgc2V0IGJ5IHRoZSBm
bG93IHNvdXJjZSBub2RlIE1VU1QgYmUgZGVsaXZlcmVkIHVuY2hhbmdlZCB0byB0aGUgZmxvdw0K
ICAgZGVzdGluYXRpb24gbm9kZShzKS4NCg0KICAgVGhlIHNvdXJjZSBub2RlIGNhbiBiZSBhIGhv
c3Qgb3IgYSBub2RlIHRoYXQgZ2VuZXJhdGVzIGEgZmxvdzsgdGhpcw0KICAgbm9kZSBjYW4gYmUg
ZGlmZmVyZW50IGZyb20gdGhlIHNvdXJjZSBob3N0IChhcyBpZGVudGlmaWVkIGJ5IHRoZQ0KICAg
c291cmNlIGFkZHJlc3MgaW4gdGhlIHBhY2tldCBoZWFkZXIpIGFuZCB0aGUgZGVzdGluYXRpb24g
bm9kZSBjYW4gYmUNCiAgIGEgaG9zdCBvciBub2RlIHRoYXQgdGVybWluYXRlcyBhIGZsb3cgYW5k
IGNhbiBiZSBkaWZmZXJlbnQgZnJvbSB0aGUNCiAgIGRlc3RpbmF0aW9uIGhvc3QgKGFzIGlkZW50
aWZpZWQgYnkgdGhlIGRlc3RpbmF0aW9uIGFkZHJlc3MgaW4gdGhlDQogICBwYWNrZXQgaGVhZGVy
KS4NCg0KICAgVGhpcyBzcGVjaWZpY2F0aW9uIGZvbGxvd3MgdGhlIG9yaWdpbmFsIHNwZWNpZmlj
YXRpb24gWzFdIGluIHRoYXQNCiAgIG5vZGVzIGtlZXBpbmcgZHluYW1pYyBmbG93IHN0YXRlIE1V
U1QgTk9UIGFzc3VtZSBwYWNrZXRzIGFycml2aW5nIDEyMA0KICAgc2Vjb25kcyBvciBtb3JlIGFm
dGVyIHRoZSBwcmV2aW91cyBwYWNrZXQgb2YgYSBmbG93IHN0aWxsIGJlbG9uZyB0bw0KICAgdGhl
IHNhbWUgZmxvdywgdW5sZXNzIGEgZmxvdyBzdGF0ZSBlc3RhYmxpc2htZW50IG1ldGhvZCBpbiB1
c2UNCiAgIGRlZmluZXMgYSBsb25nZXIgZmxvdyBzdGF0ZSBsaWZldGltZSBvciB0aGUgZmxvdyBz
dGF0ZSBoYXMgYmVlbg0KICAgZXhwbGljaXRseSByZWZyZXNoZWQgd2l0aGluIHRoZSBsaWZldGlt
ZSBkdXJhdGlvbi4NCg0KICAgVGhlIHVzZSBvZiB0aGUgRmxvdyBMYWJlbCBmaWVsZCBkb2VzIG5v
dCBuZWNlc3NhcmlseSBzaWduYWwgYW55DQogICByZXF1aXJlbWVudCBvbiBwYWNrZXQgcmVvcmRl
cmluZy4gIElmIGFuIElQdjYgbm9kZSBpcyBub3QgcHJvdmlkaW5nDQogICBmbG93LXNwZWNpZmlj
IHRyZWF0bWVudCwgaXQgTVVTVCBpZ25vcmUgdGhlIGZpZWxkIHdoZW4gcmVjZWl2aW5nIG9yDQog
ICBmb3J3YXJkaW5nIGEgcGFja2V0Lg0KDQogICBUbyBleHRlbmQgdGhlIGNhcGFiaWxpdGllcyBv
ZiB0aGUgRmxvdyBMYWJlbCwgaXQgaXMgcHJvcG9zZWQgdGhhdCBvbmUNCiAgIGJpdCwgdGhlIG1v
c3Qgc2lnbmlmaWNhbnQgYml0IChNU0IpIGJpdCwgYmUgc3BlY2lmaWVkIGFzIGZvbGxvd3MuICBJ
bg0KICAgdGhlIGZvbGxvd2luZyBmaWd1cmUsIHRoZSBNU0IgYml0IGNvbnNpc3RzIG9mIGEgTGFi
ZWwgVHlwZSAoTCkNCiAgIHN1YmZpZWxkLg0KDQogICBUaGUgZm9sbG93aW5nIHZhbHVlcyBhcmUg
ZGVmaW5lZCBmb3IgdGhpcyBzdWJmaWVsZCBmb3IgYSBub2RlDQogICByZWNlaXZpbmcgYSBwYWNr
ZXQgZnJvbSBhbiB1cHN0cmVhbSBub2RlIG9yIGhvc3Q6DQoNCg0KDQoNCkJvdW5kLCBldCBhbC4g
ICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDIxLCAyMDA1ICAgICAgICAgICAgICAgICBbUGFnZSA4
XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgUHJvcG9zYWwgZm9yIGEgTmV3IEZsb3cgTGFiZWwgRGVm
aW5pdGlvbiBGZWJydWFyeSAyMDA1DQoNCg0KICAgCS0gIDAgaGV4OiB0aGlzIHBhY2tldCBpcyB0
aGUgZmlyc3QgcGFja2V0IG9mIGEgbmV3IGZsb3cNCg0KICAgCS0gIDEgaGV4OiB0aGlzIHBhY2tl
dCBpcyBub3QgdGhlIGZpcnN0IHBhY2tldCBvZiBhIG5ldyBmbG93DQoNCg0KDQogICAgICAgICAJ
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCiAgICAgICAgIAl8THwg
ICAgICAgICAgICAgRmxvdyBMYWJlbCAgICAgICAgICAgICAgfA0KICAgICAgICAgCSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQoNCiAgICAgICAgICAgICAgICAgICAg
RmxvdyBMYWJlbCB3aXRoIHN1YmZpZWxkIChMKQ0KDQoNCg0KICAgVGhlIGJpbmFyeSB2YWx1ZSBv
ZiB0aGUgTVNCIHdpbGwgbWFrZSBmbG93IG1lcmdpbmcgZWFzaWVyIGluIDZMU0ENCiAgIG5ldHdv
cmsgWzJdLg0KDQogICBUbyBzdXBwb3J0IDZMU0EgZnJhbWV3b3JrIChkZXNjcmliZWQgYmVsb3cg
aW4gU2VjdGlvbiA1KSBhbmQgZm9yDQogICBncmVhdGVyIHNjYWxhYmlsaXR5IG9mIHVzYWdlLCB0
aGUgY3VycmVudCBmaXhlZCBGbG93IExhYmVsDQogICBzcGVjaWZpY2F0aW9uIGlzIGV4dGVuZGVk
IHRvIGFsbG93IGZsZXhpYmlsaXR5IGluIGxhYmVsaW5nIHBhY2tldHMuDQogICBMYWJlbHMgYXJl
IG5vdCBzdGF0aWMgZW5kLXRvLWVuZCBhcyBzdWNoIHRoZSBzcGVjaWZpY2F0aW9uDQogICBhY2Nv
bW1vZGF0ZXMgbGFiZWwgc3dhcHBpbmcgaW4gdGhlIG5ldHdvcmsgbm9kZXMuICBTdWNoIGEgbm9u
LXN0YXRpYw0KICAgbGFiZWwgaXMgaGVyZWFmdGVyIGNhbGxlZCCTZmxleGlibGUgbGFiZWyUIG9y
IGZsZXhpYmxlIGxhYmVsDQogICBhc3NpZ25tZW50LiAgSW4gdGhlIGZsZXhpYmxlIGxhYmVsIGFz
c2lnbm1lbnQsIGxhYmVscyBjYW4gYmUgc3dhcHBlZA0KICAgaW4gdGhlIG5ldHdvcmsgbm9kZXMg
b2YgYSBnaXZlbiBuZXR3b3JrIGluIGEgNkxTQSBkb21haW4gc28gbG9uZyBhcw0KICAgdGhlIG9y
aWdpbmFsIGxhYmVsIGlzIHJlaW5zZXJ0ZWQgYmVmb3JlIHRoZSBmbG93IGFycml2ZXMgYXQgdGhl
DQogICBkZXN0aW5hdGlvbi4NCg0KNC4xICBJbXBsaWNhdGlvbnMNCg0KICAgVGhlIHByb3Bvc2Vk
IG1vZGlmaWNhdGlvbiBvZiB0aGUgRmxvdyBMYWJlbCBmaWVsZCBpbiB0aGUgSVB2Ng0KICAgZGF0
YWdyYW0gaGVhZGVyIGhhcyBubyBpbXBhY3RzIG9uIGhvc3RzIGFuZCByb3V0ZXJzIHRoYXQgZG8g
bm90DQogICBjdXJyZW50bHkgc3VwcG9ydCBJUHY2IEZsb3cgTGFiZWwgcHJvY2Vzc2luZy4gIEZv
ciBvdGhlciBzeXN0ZW1zLA0KICAgdGhpcyBtb2RpZmljYXRpb24gcmVxdWlyZXMgdG8gcmVkdWNl
IHRoZSBsYWJlbCBzaXplIGZyb20gMjAgYml0cyB0bw0KICAgMTkgYml0cy4gIFRoaXMgcmVkdWNl
cyB0aGUgbnVtYmVyIG9mIGZsb3dzIGZyb20gYWJvdXQgYSBtaWxsaW9uIHRvDQogICBhYm91dCBo
YWxmIG9mIHRoYXQuICBIb3dldmVyLCBvbmUtaGFsZiBtaWxsaW9uIGZsb3dzIHNob3VsZCBiZQ0K
ICAgYWRlcXVhdGUgZm9yIHBlci1ob3AgUW9TIGRlbGl2ZXJ5IGluIGFueSBzaXplIG5ldHdvcmsu
DQoNCjUuICBBbiBFbWVyZ2luZyBVc2FnZSBmb3IgdGhlIEZsb3cgTGFiZWwgRmllbGQNCg0KICAg
QW4gYXJjaGl0ZWN0dXJhbCBmcmFtZXdvcmssIGNhbGxlZCBJUHY2IExhYmVsIFN3aXRjaGluZyBB
cmNoaXRlY3R1cmUNCiAgICg2TFNBKSBoYXMgYmVlbiBwcm9wb3NlZCBbMl0gdG8gZGVtb25zdHJh
dGUgaG93IHRoZSBzcGVjaWZpY2F0aW9uDQogICBwcmVzZW50ZWQgaW4gdGhpcyBkb2N1bWVudCBj
YW4gYmUgdXNlZC4gIFRoZSBhcmNoaXRlY3R1cmUgYWxsb3dzDQogICBuZXR3b3JrIG5vZGVzIHRv
IGdlbmVyYXRlIGxhYmVscyBsb2NhbGx5LiAgVGhlIGxhYmVsIGlzIHRoZW4gdXNlZCB0bw0KICAg
c3BlY2lmeSBmbG93cywgYmluZCB0aGVtIHRvIEZFQ3MgYW5kIGZvcndhcmQgcGFja2V0cyBhdCBo
aWdoIHNwZWVkDQogICBvdmVyIHRoZSBsYWJlbC1kZXJpdmVkIExTUHMuDQoNCiAgIFRoZSBhcmNo
aXRlY3R1cmUgaW5jbHVkZXMgc3dhcHBpbmcgb2YgbGFiZWxzIGluIGEgbmV0d29yayBub2RlLCB0
aGF0DQoNCg0KDQpCb3VuZCwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAyMSwgMjAw
NSAgICAgICAgICAgICAgICAgW1BhZ2UgOV0NCgwNCkludGVybmV0LURyYWZ0ICAgIFByb3Bvc2Fs
IGZvciBhIE5ldyBGbG93IExhYmVsIERlZmluaXRpb24gRmVicnVhcnkgMjAwNQ0KDQoNCiAgIGlz
LCB0aGUgb3V0Z29pbmcgbGFiZWwgcmVwbGFjZXMgdGhlIGluY29taW5nIGxhYmVsIGFzIHRoZSBw
YWNrZXQNCiAgIHRyYXZlcnNlcyBhIG5vZGUuICBUaGUgb3V0Z29pbmcgbGFiZWwgcmVwcmVzZW50
cyB0aGUgTFNQIGZyb20gdGhpcw0KICAgbm9kZSB0byB0aGUgZG93bnN0cmVhbSBub2RlLiAgVGhl
IG9yaWdpbmFsIGxhYmVsIGlzIHJlaW5zdGF0ZWQgaW4gdGhlDQogICBwYWNrZXQgaW4gdGhlIDZM
U0EgZWdyZXNzIHJvdXRlci4NCg0KICAgVGhpcyBhcmNoaXRlY3R1cmUgaXMgbWVhbnQgdG8gcHJv
dmlkZSBtZWFucyBmb3IgdHJhZmZpYyBlbmdpbmVlcmluZw0KICAgZm9yIFFvUyBkZWxpdmVyeS4g
IEluIHRoaXMgbW9kZWwsIEZsb3cgTGFiZWwgY2FuIGJlIGNoYW5nZWQgaW4gYQ0KICAgcGFja2V0
IHN0cmVhbS4gIEEgZmxvdywgY2FsbGVkIHBzZXVkby1mbG93ICh0byBhdm9pZCBjb25mbGljdCB3
aXRoDQogICB0aGUgY3VycmVudCBkZWZpbml0aW9uIFsxXSksIGdldHMgaWRlbnRpZmllZCB3aXRo
IGEgRmxvdyBMYWJlbCBhcyBpdA0KICAgaXMgY3JlYXRlZCBmb3IgZWFjaCBob3AsIHRoYXQgaXMs
IGZsb3dzIGhhdmUgaG9wLWJ5LWhvcCBzaWduaWZpY2FuY2UNCiAgIGZvciBhIGdpdmVuIHNlc3Np
b24gYW5kIHJlcXVpcmVkIFFvUy4NCg0KICAgVG8gc3VwcG9ydCBJUHY2IGJhc2VkIGxhYmVsIHN3
aXRjaGluZywgdGhhdCBpcywgc3dhcHBpbmcgb2YgaW5jb21pbmcNCiAgIGxhYmVsIHdpdGggdGhl
IG91dGdvaW5nIGxhYmVsICh0aGUgbGF0dGVyIG1hcHBlZCB0byBhIGdpdmVuIEZFQykgaW4NCiAg
IHRoZSBuZXR3b3JrIG5vZGUgaXMgYWxsb3dlZC4gIFRoZSBsYWJlbCBzd2l0Y2hpbmcgaXMgdXNl
ZCB0byBzZXQgdXANCiAgIGxhYmVsIHN3aXRjaGVkIHBhdGhzIChMU1BzKSBzaW1pbGFyIHRvIHRo
ZSBNUExTIExTUHMgb3ZlciB3aGljaA0KICAgcGFja2V0cyBhcmUgZm9yd2FyZGVkIGFmdGVyIHRo
ZXkgYXJlIGJvdW5kIHRvIGEgRm9yd2FyZGluZyBFcXVpdmFsZW50DQogICBDbGFzcyAoRkVDKS4N
Cg0KICAgQnkgdXNpbmcgdGhlIElQdjYgRmxvdyBMYWJlbCB2YWx1ZSBmb3IgcGFja2V0IGZvcndh
cmRpbmcgKGFuZA0KICAgY2xhc3NpZmljYXRpb24gYXMgbmVjZXNzYXJ5IGlmIG5vdCBwcm92aWRl
ZCBieSB0aGUgVHJhZmZpYyBDbGFzcyksDQogICB0aGlzIGFyY2hpdGVjdHVyZSBhdm9pZHMgdGhl
IGxpbmsgb3ZlcmhlYWQgYXNzb2NpYXRlZCB3aXRoIGxhYmVsDQogICBkaXN0cmlidXRpb24gdGhh
dCBpcyBuZWVkZWQgdG8gdGllIHRoZSBJUHY2IGFkZHJlc3MgdG8gYSBGbG93IExhYmVsLg0KICAg
VGhpcyBsYXllciAzIHVzZSBvZiBGbG93IExhYmVsIGZvciBwYWNrZXQgZm9yd2FyZGluZyBhbHNv
IGFsbG93cw0KICAgcm91dGVyIHBlZXJpbmcgaW4gbGF5ZXIgMyB1bmxpa2Ugb3RoZXIgY29udGVt
cG9yYXJ5IHZpcnR1YWwgY2lyY3VpdA0KICAgcHJvdG9jb2xzLg0KDQogICBUaGUgNkxTQSBmcmFt
ZXdvcmsgWzJdIGlzIGEgZ29vZCBleGFtcGxlIHRoYXQgaGlnaGxpZ2h0cyB0aGUgbmVlZHMgdG8N
CiAgIGJyb2FkZW4gdGhlIGN1cnJlbnQgZGVmaW5pdGlvbiBvZiB0aGUgSVB2NiBGbG93IExhYmVs
IGZpZWxkLiAgSXQgaXMNCiAgIHBvc3NpYmxlIHRoYXQgbW9yZSBhcHBsaWNhdGlvbnMgbGlrZSA2
TFNBIHdpbGwgZW1lcmdlIHRoYXQgY2FuIHRha2UNCiAgIGFkdmFudGFnZSBvZiB0aGUgZmllbGQu
DQoNCjYuICBCZW5lZml0cyBvZiBGbGV4aWJsZSBMYWJlbA0KDQogICBUaGUgZmxleGlibGUgbGFi
ZWwgaGFzIG1hbnkgYmVuZWZpdHMsIGFuIGFicmlkZ2VkIHZlcnNpb24gaXMgcHJvdmlkZWQNCiAg
IGhlcmUuICBUaGUgNkxTQSBleGFtcGxlIFsyXSBzaG93cyBob3cgdGhlc2UgYmVuZWZpdHMgY2Fu
IGJlIHJlYWxpemVkLg0KDQogICAJLSAgU3VwcG9ydGluZyBhIHBlci1ob3AgbGFiZWwgYXNzaWdu
bWVudCBtZWNoYW5pc20gZW5hYmxlcw0KICAgaGlnaC1zcGVlZCBwYWNrZXQgcHJvY2Vzc2luZyB0
aHJvdWdoIHNob3J0IDIwLWJpdCBsYWJlbCBzd2l0Y2hpbmcNCiAgIGluc3RlYWQgb2YgZXh0cmVt
ZWx5IGxhcmdlIDMtdHVwbGUsIDI3Ni1iaXQgZmxvdyAoaWRlbnRpZmllcikgb3INCiAgIDEyOC1i
aXQgYWRkcmVzcyBsb29rLXVwcy4gVGhpcyBjb3VsZCBzaWduZmljYW50bHkgcmVkdWNlIGRlbGF5
cyBmb3INCiAgIGFsbCBkZWxheS1zZW5zaXRpdmUgcmVhbC10aW1lIGFuZCBuZWFyLXJlYWwtdGlt
ZSB0cmFmZmljIHRoZXJlYnkNCiAgIGNvbnNpZGVyYWJseSBlbmhhbmNpbmcgUW9TIGRlbGl2ZXJ5
Lg0KDQogICAJLSAgSW4gbW9iaWxlIGFkLWhvYyBuZXR3b3Jrcywgc3VjaCBhcyBpbiB0aGUgbWls
aXRhcnkgbmV0d29ya3MsIHRoZQ0KICAgdXNlIG9mIGxhYmVsIGZvciBwYWNrZXQgZm9yd2FyZGlu
ZyBwcm92aWRlcyBmb3IgZmFzdCBhbmQgZmxleGlibGUNCiAgIG5ldHdvcmtpbmcgZm9yIG1vYmls
ZSBub2Rlcy4gT25jZSBhIGZsb3cgaGFzIGJlZW4gc2V0IHVwIHRocm91Z2ggYW55DQogICBvbmUg
b2Ygc2V2ZXJhbCBzZWxlY3RlZCBtZXRob2RzIHN1Y2ggYXMgdGhyb3VnaCBhc3NvY2lhdGlvbiBv
ZiB0aGUNCg0KDQoNCkJvdW5kLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDIxLCAy
MDA1ICAgICAgICAgICAgICAgIFtQYWdlIDEwXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgUHJvcG9z
YWwgZm9yIGEgTmV3IEZsb3cgTGFiZWwgRGVmaW5pdGlvbiBGZWJydWFyeSAyMDA1DQoNCg0KICAg
RmxvdyBMYWJlbCBpbiB0aGUgZmlyc3QgKGxlYWQpIHBhY2tldCB3aXRoIElQdjYgYWRkcmVzc2Vz
IG9yIHBoeXNpY2FsDQogICBwb3J0IG9yIHRocm91Z2ggc29tZSBvdGhlciBtZWFucywgYWxsIHN1
c2VxdWVudCBwYWNrZXRzIGluIHRoZSBmbG93DQogICBjYW4gYmUgZm9yd2FyZGVkIHVzaW5nIHRo
ZSBGbG93IExhYmVsLiBUaGlzIGhlbHBzIHBhY2tldCBmb3J3YXJkaW5nDQogICBiYXNlZCBzb2xl
eSBvbiB0aGUgRmxvdyBMYWJlbCBhbmQgaW4gc21hbGwsIGJhbmR3aWR0aCBjb25zdHJhaW5lZA0K
ICAgbmV0d29ya3MgdGhpcyBjb3VsZCBoZWxwIGVsaW1pbmF0ZSB0aGUgdHJhbnNtaXNzaW9uIG9m
IHRoZSBwYWNrZXQNCiAgIGhlYWRlciB3aXRoIGVhY2ggcGFja2V0IGJleW9uZCB0aGUgaW5ncmVz
cyBub2RlIGZvciBwYWNrZXRzIHRoYXQgYXJlDQogICBuZXh0LXRvLWxlYWQgcGFja2V0cyBbMl0u
IChUaGlzIGNvbmNlcHQgaXMgaW4gaXRzIGVhcmx5IHN0YWdlIG9mDQogICBldmFsdWF0aW9uIGF0
IHRoaXMgdGltZS4pIFRoZSBwcm9jZXNzIGlmIGFkb3B0ZWQgd2lsbCBzYXZlIGJhbmR3aWR0aA0K
ICAgY29uc2lkZXJhYmx5IGluIGFkLWhvYywgbW9iaWxlIGxpbmtzIGluIGFkZGl0aW9uIHRvIHBy
b3ZpZGluZw0KICAgY29uc2lkZXJhYmxlIHNhdmluZ3MgaW4gbWVtb3J5IChlbm9ybW91c2x5IHJl
ZHVjZWQgYml0IHNwYWNlKSwNCiAgIGJhbmR3aWR0aCAoc2lnbmlmaWNhbnRseSByZWR1Y2VkIHBh
Y2tldCBoZWFkZXIgb3ZlcmhlYWQpIGFuZA0KICAgcHJvY2Vzc2luZyAoZmV3ZXIgZmV0Y2hlcyBh
bmQgc21hbGxlciBiaXQgZmllbGQpLg0KDQogICAJLSAgTGFiZWxzIGRlbWFyY2F0ZSBwZXIgaG9w
IGxhYmVsIHN3aXRjaGVkIHBhdGhzLiBQZXItaG9wIGxhYmVsDQogICBhc3NpZ25tZW50IGlzIG1v
cmUgcm9idXN0IHRoYW4gZW5kLXRvLWVuZCBiZWNhdXNlIHRoZSBGbG93IExhYmVscyBhcmUNCiAg
IGFzc2lnbmVkIGhvcC1ieS1ob3Agd2hpY2ggaGVscHMgcHJldmVudCBlcnJvcnMgZnJvbSBwcm9w
YWdhdGluZyBhbG9uZw0KICAgdGhlIGNvbW11bmljYXRpb25zIHBhdGguDQoNCiAgIAktICBQZXIg
aG9wIGxhYmVsIGFzc2lnbm1lbnQgYWxsb3dzIGZvciB1c2luZyBkYXRhZ3JhbSB0cmFuc21pc3Np
b24NCiAgIHdoZXJlIFFvUyByZXF1aXJlbWVudHMgY2FuIGJlIHJlbGF4ZWQgb3IgY2Fubm90IGJl
IGVuZm9yY2VkIGZvcg0KICAgdmFyaW91cyByZWFzb25zLiBUaGlzIGFkZHMgYW5vdGhlciBkaW1l
bnNpb24gdG8gdGhlIHVzZSBvZiBmbGV4aWJsZQ0KICAgbGFiZWwuIFRoZSBwYWNrZXRzIGNhbiBz
dGlsbCBjYXJyeSB0aGUgbGFiZWxzIGJ1dCBwcm9jZXNzc2luZyBvZg0KICAgcGFja2V0cyB3aWxs
IG5vdCBiZSBsYWJlbCBiYXNlZCBidXQgb24gY29udmVudGlvbmFsIHJvdXRpbmcNCiAgIGFsZ29y
aXRobXMuIFRoaXMgY291bGQgYmUgZW1wbG95ZWQgb24gb25lIG9yIG1vcmUgaG9wcyBieSBhcHJp
b3JpDQogICBkZXNpZ24sIHNpZ25hbGluZyBvciBhZC1ob2MgY29uZmlndXJhdGlvbiBjb250cm9s
IHVzaW5nIG5ldHdvcmsNCiAgIG1hbmFnbWVudCB0b29scy4NCg0KICAgCS0gIFRoZSBmbGV4aWJs
ZSBsYWJlbCBhbGxvd3MgcmVhZHkgaW50ZWdyYXRpb24gb2YgZmxvd3Mgd2l0aCBhIGxvY2FsDQog
ICBRb1MgbWVjaGFuaXNtIGFzIGF2YWlsYWJsZSBpbiBhIG5vZGUgdGhhdCBjYW4gbWFrZSB1c2Ug
b2YgdGhlIGxhYmVsIC0NCiAgIGEgbm9kZSBpcyBub3QgZGVwZW5kZW50IG9uIGEgY2VudHJhbGx5
IGFkbWluaXN0ZXJlZCBsYWJlbCBiaW5kaW5nIG9yDQogICBwYWNrZXQgY2xhc3NpZmljYXRpb24g
bWVjaGFuaXNtIC0gdGhpcyBpcyBnb29kIGZvciBzY2FsYWJpbGl0eS4NCiAgIFR5cGljYWxseSwg
aW5lbGFzdGljIG9yIHByZWZlcnJlZCBlbGFzdGljIGNsYXNzIG9mIHNlcnZpY2UgcndxdWlyZXMN
CiAgIGluZGl2aWR1YWwgZmxvd3MgdG8gcmVjZWl2ZSBwcmVmZXJyZWQgdHJlYXRtZW50LiAgT25l
IHdhdCB0byBhY2hpZXZlDQogICB0aGlzIHByZWZlcnJlZCB0cmVhdCBtZW50IGNvdWxkIHRocm91
Z2ggaW5kaXZpZHVhbCBUcmFmZmljIENsYXNzDQogICBtYXJraW5ncyBhbmQgZmxvdy1sYWJlbCBi
YXNlZCBmb3J3YXJkaW5nIHRyZWFtZW50IG9mIHN1Y2ggbWFya2VkDQogICBwYWNrZXRzIHRocm91
Z2ggbWFuYWdlZCBjb250cmwgb2YgYXZhaWxhYmxlIHJlc291cmNlcy4NCg0KICAgCS0gIEFsbG93
aW5nIGxvY2FsIGxhYmVsIGdlbmVyYXRpb24gaGVscHMgZWxpbWluYXRlIHNpZ25hbGluZyBmb3IN
CiAgIGRpc3RyaWJ1dGluZyBsYWJlbHMgYW5kIHNhdmUgbmV0d29yayByZXNvdXJjZXMuDQoNCiAg
IAktICBGbGV4aWJsZSBsYWJlbGluZyBpcyBlZmZpY2llbnQgYmVjYXVzZSBpdCBlbGltaW5hdGVz
IGxvd2VyIGxheWVyDQogICBwZWVyaW5nIGFuZCBhbGxvd3MgcGVlcmluZyBiZXR3ZWVuIG5ldHdv
cmsgbm9kZXMgaW4gbGF5ZXIgMy4gRmxvdw0KICAgTGFiZWwgY29udHJvbCBwbGFuZSBtZWNoYW5p
c21zIGNhbiBiZSB0aWVkIHRvIG9uZSBvciBtb3JlIGxheWVyIDMNCiAgIGNvbnRyb2wgcGxhbmUg
bWVjaGFuaXNtcyBzdWNoIGFzIGFuIElHUCwgUlNWUCwgZXRjLiwgLSB0aGUgbGF0dGVyDQogICBo
ZWxwcyBhdm9pZCBOMiAobi1zcXVhcmVkKSBwcm9ibGVtcyBvZiBiZWxvdy1sYXllciAzIHZpcnR1
YWwNCiAgIGNpcmN1aXRzLg0KDQoNCg0KDQoNCkJvdW5kLCBldCBhbC4gICAgICAgICAgIEV4cGly
ZXMgQXVndXN0IDIxLCAyMDA1ICAgICAgICAgICAgICAgIFtQYWdlIDExXQ0KDA0KSW50ZXJuZXQt
RHJhZnQgICAgUHJvcG9zYWwgZm9yIGEgTmV3IEZsb3cgTGFiZWwgRGVmaW5pdGlvbiBGZWJydWFy
eSAyMDA1DQoNCg0KICAgCS0gIEluIG1vYmlsZSBhZC1ob2MgbmV0d29ya3Mgd2hlcmUgbGlua3Mg
Z28gdXAgYW5kIGRvd24gcmFuZG9tbHkgYW5kDQogICBmcmVxdWVudGx5LCB0aGUgZW5kLXRvLWVu
ZCBtb2RlbCBvZiBmbG93IGVzdGFibGlzaG1lbnQgYW5kDQogICBtYWludGVuYW5jZSBpcyBub3Qg
cHJhY3RpY2FsIG9yIGFkdmlzYWJsZS4gVGhlIGZsZXhpYmxlIGZsb3cgbGFiZWxpbmcNCiAgIHRo
YXQgYWxsb3dzIHBlciBmbG93IHNldCB1cHMgYW5kIHRlYXIgZG93bnMsIG9yIG9wdGluZyBvdXQg
b2YgZmxvd3MNCiAgIHdoZXJlIGZsb3dzIGFyZSBub3QgbmVlZGVkIGlzIG1vcmUgZGVzaXJhYmxl
IC4NCg0KICAgCS0gIFRoZSBGbG93IExhYmVsIGFzIHNwZWNpZmllZCBoZXJlIGNhbiBwb3RlbnRp
YWxseSBiZSB1c2VkIGZvciBWUE5zDQogICAodGhpcyBpcyB0byBiZSBhZGRyZXNzZWQgaW4gZnV0
dXJlIHdvcmspLg0KDQogICBUbyBzdW1tYXJpemUsIHRoZSBmbGV4aWJsZSBsYWJlbCBhcyBwcmVz
ZW50ZWQgaW4gdGhpcyBuZXcgRmxvdyBMYWJlbA0KICAgc3BlY2lmaWNhdGlvbiBhbGxvd3MgZmxv
dyBsYWJlbGluZyBkeW5hbWljYWxseSBvbiBhbiBhcy1hbmQtd2hlcmUNCiAgIG5lZWRlZCBiYXNp
cy4gIEl0IGlzIG5vdCBkb25lIHN0YXRpY2FsbHkgYW5kIG9uIGFuIGVuZC10by1lbmQgYmFzaXMN
CiAgIGFzIHRoZSBjdXJyZW50IHNwZWNpZmljYXRpb24gZG9lcy4gIEZsb3dzIHNvIGRlZmluaWVk
IGFyZSBub3QgdGllZCB0bw0KICAgdGhlIGZsb3cncyBzb3VyY2UtZGVzdGluYXRpb24gbm9kYWwg
cGFpciBidXQgY2FuIGJlIHNwZWNpZmllZCBmb3IgYW55DQogICBwYWlyIG9mIG5vZGVzIC0gbm9k
ZXMgY29ubmVjdGluZyBieSBhcyBob3J0IGEgbGluayBhcyBvbmUgaG9wLiAgVGhlDQogICBsYWJl
bCBiaW5kaW5nIGNhbiBiZSB0b3RhbGx5IGluZGVwZW5kZW50IGZyb20gb25lIGhvcCB0byBhbm90
aGVyLg0KICAgUGFja2V0cyBjYW4gYmUgZm9yd2FyZGVkIHVzaW5nIG9ubHkgdGhlIGxhYmVsIGlu
IGEgZmxvdyBvbmNlIHRoZSBmbG93DQogICBoYXMgYmVlbiBzZXQgdXAgdXNpbmcgdGhpcyBsYWJl
bC4gIFRoZXJlIGlzIG5vIHJlc3RyaWN0aW9uIGFzIHRvIGhvdw0KICAgYSBsYWJlbCBpcyBib3Vu
ZCB0byBhbiBGRUMuICBJdCBpcyBzaWduaWZpY2FudCB0aGF0IGEgZmxvdyBsYWJlbCBpcw0KICAg
bm90IG9ubHkgdXNlZCBmb3IgcGFja2V0IGNsYXNzaWZpY2F0aW9uIGJ1dCBhbHNvIGZvciBwYWNr
ZXQNCiAgIGZvcndhcmRpbmcuICBQYWNrZXQgZm9yd2FyZGluZyB1c2luZyBvbmx5IHRoZSBsYWJl
bCB0aHVzIGNhbiBwcm92aWRlDQogICBzaWduaWZpY2FudCBzYXZpbmdzIGluIG1lbW9yeSwgcHJv
Y2Vzc2luZyBhbmQgcG90ZW50aWFsbHksIGJhbmR3aWR0aA0KICAgdXNhZ2UgLSBhbGwgb2Ygd2hp
Y2ggYXJlIHZlcnkgaW1wb3J0YW50IGZvciBtb2JpbGUgbmV0d29ya3MgaW4gd2hpY2gNCiAgIHRo
ZSBub2RlcyBhcmUgbGltaXRlZCBieSBzaXplLCB3ZWlnaHQgYW5kIHBvd2VyIGZhY3RvcnMgYW5k
IGxpbmtzIGJ5DQogICBhdmFpbGFibGUgYmFuZHdpZHRoLg0KDQogICBUaGUgZGlmZmVyZW5jZSBi
ZXR3ZWVuIHBhY2tldCBmb3J3YXJkaW5nIGJ5IGZsb3cgbGFiZWwgYW5kIHBhY2tldA0KICAgZm9y
d2FyZGluZyBieSBkZXN0aW5hdGlvbiBhZGRyZXNzIGlzIHRoYXQgdGhlIGxhdHRlciBoYXMgbGl0
dGxlIG9yIG5vDQogICBtYXBwaW5nIHRvIFFvUyBkZWxpdmVyeSBvciBzZWN1cmVkIHBhdGggYmFz
ZWQgZGVsaXZlcnksIGlzIGdlbmVyYWxseQ0KICAgc2hvcnRlc3QgcGF0aCBiYXNlZCwgZ2VuZXJh
bGx5IHJlcXVpcmVzIHJvdXRlIGxvb2sgdXAgKG9mdGVuIGluIHRoZQ0KICAgYmFjayBwbGFuZSks
IGlzIG5vdCBmYXN0IGFuZCBpcyBub3Qgc2Vzc2lvbiBzcGVjaWZpYy4NCg0KICAgVGhlIG5ldyBk
ZWZpbml0aW9uIHByZXNlbnRlZCBoZXJlIGV4dGVuZHMgdGhlIG9yaWdpbmFsIEZsb3cgTGFiZWwN
CiAgIGRlZmluaXRpb24gdG8gb3RoZXIgcHVycG9zZXMgc3VjaCBhcyBWUE5zICh0aGUgc3BlY2lm
aWNhdGlvbiBpcyB3b3JrDQogICBpbiBwcm9ncmVzcykgZW5oYW5jaW5nIGJvdGggdGhlIGVmZmlj
aWVuY3kgYW5kIGZ1bmN0aW9uYWxpdHkgb2YgdGhlDQogICBJUHY2IHByb3RvY29sLg0KDQo3LiAg
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMNCg0KICAgU2luY2UgdGhpcyBpcyByZWxhdGVkIHRvIDZM
U0EsIHRoZSBjb25zaWRlcmF0aW9ucyBoZXJlIGFyZSBpZGVudGljYWwNCiAgIHRvIHRob3NlIGZv
ciA2TFNBIFsyXS4gIFRoZSBmbGV4aWJsZSBGbG93IExhYmVsIGFsbG93cyBzZWN1cml0eQ0KICAg
YXNzb2NpYXRpb24uICBJZiB0aGUgc2VjdXJpdHkgYXNzb2NpYXRpb24gKFNBKSBwYXJ0bmVycyBh
cmUgb3V0c2lkZQ0KICAgdGhlIDZTTEEsIHRoZW4gdGhlcmUgaXMgbm8gZWZmZWN0IG9mIHRoaXMg
c3BlY2lmaWNhdGlvbiBvbiA2TFNBDQogICB3aGV0aGVyIHRoZSBtb2RlIG9mIG9wZXJhdGlvbiBp
cyBpbiB0aGUgdHJhbnNwb3J0IG1vZGUgb3IgaW4gdGhlDQogICB0dW5uZWwgbW9kZS4NCg0KICAg
SW4gdGhlIHRyYW5zcG9ydCBtb2RlIG9mIFNBLCBvbmx5IHRoZSBwYWNrZXQgcGF5bG9hZCBpcyBz
dWJqZWN0IHRvDQogICBlbmNyeXB0aW9uIG9yIGF1dGhlbnRpY2F0aW9uLCBzbyB0aGUgSVB2NiBw
YWNrZXQgaGVhZGVyIGZlYXR1cmVzIGFyZQ0KDQoNCg0KQm91bmQsIGV0IGFsLiAgICAgICAgICAg
RXhwaXJlcyBBdWd1c3QgMjEsIDIwMDUgICAgICAgICAgICAgICAgW1BhZ2UgMTJdDQoMDQpJbnRl
cm5ldC1EcmFmdCAgICBQcm9wb3NhbCBmb3IgYSBOZXcgRmxvdyBMYWJlbCBEZWZpbml0aW9uIEZl
YnJ1YXJ5IDIwMDUNCg0KDQogICBub3QgYWZmZWN0ZWQgYW5kIHRoZSA2TFNBIGJlaW5nIGEgdHJh
bnNwb3J0IG1lY2hhbmlzbSB0aGF0IHNldHMgdXANCiAgIDZMU1BzIGFuZCBwcm92aWRlcyBzcGVj
aWZpYyBGRUMtZHJpdmVuIGZvcndhcmRpbmcgdHJlYXRtZW50LCB0aGVyZSBpcw0KICAgbm8gaW1w
YWN0IG9uIHRoZSA2TFNBIG9yIGltcGFjdCBvbiBTQSBvcGVyYXRpb24gYnkgdGhlIDZTTEEgb3Ig
dGhpcw0KICAgc3BlY2lmaWNhdGlvbiBvZiB0aGUgbGFiZWwuDQoNCiAgIEluIHRoZSB0dW5uZWwg
bW9kZSBvZiBTQSwgdGhlIFNBIHJlcXVpcmVzIGFuIG91dGVyIHdyYXBwZXIgSVB2Ng0KICAgcGFj
a2V0LiAgVGhlIHNlbmRpbmcgZ2F0ZXdheSB3cmFwcyB0aGUgd2hvbGUgSVB2NiBwYWNrZXQgaW5j
bHVkaW5nDQogICB0aGUgY29udGVudC4gIFRoZSByZWNlaXZpbmcgZ2F0ZXdheSBwZXJmb3JtcyB0
aGUgY2hlY2tzdW0gb24gdGhlDQogICBvdXRlciB3cmFwcGVyIHBhY2tldCwgdW53cmFwcyB0aGUg
cGFja2V0IGFuZCB0aGVuIHZlcmlmaWVzIHRoZQ0KICAgY2hlY2tzdW0gb2YgdGhlIGlubmVyIHBh
Y2tldCB0aHJvdWdoIGVuZC10by1lbmQgU0EuICBJZiB0aGUgb3V0ZXINCiAgIHdyYXBwZXIgcGFj
a2V0IGNvbnZleXMgdGhlIEZsb3cgTGFiZWwgdmFsdWUgb2YgdGhlIGlubmVyIHBhY2tldCwgdGhl
bg0KICAgaGVyZSBhbHNvLCB0aGVyZSBpcyBubyBpbXBhY3Qgb24gdGhlIDZMU0EgYmFzZWQgdHJh
bnNwb3J0IG9mIHRoZQ0KICAgc2VjdXJlIHBhY2tldHMgb3IgdmljZSB2ZXJzYS4NCg0KICAgVGhl
IEF1dGhlbnRpY2F0aW9uIEhlYWRlciAoQUgpIGlzIHVzZWQgaW4gSVB2NiBmb3IgYXV0aGVudGlj
YXRpb24gb2YNCiAgIGluZGl2aWR1YWwgcGFja2V0cyB0byBwcmV2ZW50IGNvbW1vbiBJbnRlcm5l
dC1iYXNlZCBhdHRhY2tzIHN1Y2ggYXMNCiAgIElQIGFkZHJlc3Mgc3Bvb2ZpbmcgYW5kIHNlc3Np
b24gaGlqYWNraW5nLiAgVGhlIGNvbXB1dGF0aW9uIG9mDQogICBjcnlwdG9ncmFwaGljYWxseSBz
ZWN1cmUgY2hlY2tzdW0gb3ZlciB0aGUgcGF5bG9hZCBhcyB3ZWxsIGFzIHNvbWUNCiAgIGZpZWxk
cyBvZiB0aGUgSVB2NiBhbmQgZXh0ZW5zaW9uIGhlYWRlcnMgaGFzIHRvIHRha2UgcGxhY2UgYmV0
d2Vlbg0KICAgdGhlIFNBIHBhcnRuZXJzLiAgVGhpcyBjb21wdXRhdGlvbiBkb2VzIG5vdCBpbmNs
dWRlIHRoZSBGbG93IExhYmVsDQogICBmaWVsZCBpbiB0aGUgcGFja2V0IGhlYWRlci4gIFRoaXMg
bWFpbnRhaW5zIGxhYmVsIHRyYW5zcGFyZW5jeSBpbiB0aGUNCiAgIDZTTEEuICBBdXRoZW50aWNh
dGlvbiBjYW4gYmUgZWl0aGVyIGluIHRoZSB0cmFuc3BvcnQgbW9kZSBvciBpbiB0aGUNCiAgIHR1
bm5lbCBtb2RlLg0KDQogICBUaGUgNlNMQSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyB0aGF0IGFw
cGx5IHRvIEVuY3J5cHRlZCBTZWN1cml0eQ0KICAgUGF5bG9hZCAoRVNQKSBoZWFkZXIgY29tcHJp
c2UgZW5jcnlwdGlvbiBtb2RlcyB0aGF0IGFyZSBjYXRlZ29yaXplZA0KICAgYXMgdHJhbnNwb3J0
IG1vZGUgb3IgdHVubmVsIG1vZGUuICBJbiB0aGUgdHJhbnNwb3J0IG1vZGUsIG5vDQogICBlbmNy
eXB0aW9uIG9mIHRoZSBGbG93IExhYmVsIGZpZWxkIGlzIHBlcmZvcm1lZCwgc28gdGhlIHZhbHVl
IGlzDQogICBjYXJyaWVkIHRocm91Z2ggdGhlIDZTTEEuICBJbiB0aGUgdHVubmVsIG1vZGUsIHRo
ZSBpc3N1ZXMgYXJlIHRoZQ0KICAgc2FtZSBhcyBzdGF0ZWQgaGVyZSBhYm92ZS4gIEluIGJvdGgg
Y2FzZXMsIHRoZSBjaGFyYWN0ZXJpc3RpY3Mgb2YgdGhlDQogICBmbGV4aWJsZSBsYWJlbCBpcyBp
ZGVudGljYWwgdG8gZml4ZWQgbGFiZWwsDQoNCjguICBBY2tub3dsZWdlbWVudHMNCg0KICAgVGhl
IGF1dGhvcnMgZGVlcGx5IGFwcHJlY2lhdGUgZ2VuZXJhbCBhZHZpY2UgYW5kIGVuY291cmFnZW1l
bnQNCiAgIHJlY2VpdmVkIGZyb20gaW5zaWRlIGFuZCBvdXRzaWRlIG9mIE1pdHJlLg0KDQo5LiAg
RGlzY2xhaW1lcg0KDQogICBUaGUgYWZmaWxpYXRpb24gb2YgY2VydGFpbiBhdXRob3JzIHdpdGgg
VGhlIE1JVFJFIENvcnBvcmF0aW9uIGlzDQogICBwcm92aWRlZCBmb3IgaWRlbnRpZmljYXRpb24g
cHVycG9zZXMgb25seSwgYW5kIGlzIG5vdCBpbnRlbmRlZCB0bw0KICAgY29udmV5IG9yIGltcGx5
IE1JVFJFknMgY29uY3VycmVuY2Ugd2l0aCwgb3Igc3VwcG9ydCBmb3IsIHRoZQ0KICAgcG9zaXRp
b25zLCBvcGluaW9ucyBvciB2aWV3cG9pbnRzIGV4cHJlc3NlZCBieSB0aGUgYXV0aG9yLg0KDQox
MC4gIFJlZmVyZW5jZXMNCg0KDQoNCg0KDQoNCkJvdW5kLCBldCBhbC4gICAgICAgICAgIEV4cGly
ZXMgQXVndXN0IDIxLCAyMDA1ICAgICAgICAgICAgICAgIFtQYWdlIDEzXQ0KDA0KSW50ZXJuZXQt
RHJhZnQgICAgUHJvcG9zYWwgZm9yIGEgTmV3IEZsb3cgTGFiZWwgRGVmaW5pdGlvbiBGZWJydWFy
eSAyMDA1DQoNCg0KICAgCVsxXSBKLiBSYWphaGFsbWUsIGV0IGFsLiwgSVB2NiBGbG93IExhYmVs
IFNwZWNpZmljYXRpb24sIFJGQyAzNjk3LA0KICAgTWFyY2ggMjAwNC4NCg0KICAgCVsyXSBTLiBD
aGFrcmF2b3J0eSwgSVB2NiBMYWJlbCBTd2l0Y2hpbmcgQXJjaGl0ZWN0dXJlICg2TFNBKSwgSUVU
Rg0KICAgSUQgkWRyYWZ0LWNoYWtyYXZvcnR5LTZsc2EtMDEudHh0kiwgSnVseSAyMDA0Lg0KDQog
ICAJWzNdIFMuIERlZXJpbmcgYW5kIFIuIEhpbmRlbiwgSW50ZXJuZXQgUHJvdG9jb2wsIFZlcnNp
b24gNiAoSVB2NikNCiAgIFNwZWNpZmljYXRpb24sIFJGQyAyNDYwLCBEZWNlbWJlciAxOTk4Lg0K
DQoNCg0KQXV0aG9ycycgQWRkcmVzc2VzDQoNCiAgIEppbSBib3VuZA0KICAgTkF2NlRGDQogICBQ
Lk8uIEJveA0KICAgSG9sbGlzLCBOSCAgMjIxMDINCiAgIFVTQQ0KDQogICBFTWFpbDogSmltLmJv
dW5kQGhwLmNvbQ0KDQoNCiAgIFNoYW0gQ2hha3Jhdm9ydHkNCiAgIFRoZSBNSVRSRSBDb3Jwb3Jh
dGlvbg0KICAgMTU3NSBDb2xzaGlyZSBEci4NCiAgIE1jTGVhbiwgVkEgIDIyMTAyDQogICBVU0EN
Cg0KICAgRU1haWw6IHNjaGFrcmFAbWl0cmUub3JnDQoNCg0KICAgS2V2aW4gWmhhbmcNCiAgIFRo
ZSBNSVRSRSBDb3Jwb3JhdGlvbg0KICAgNzUxNSBDb2xzaGlyZSBEci4NCiAgIE1jTGVhbiwgVkEg
IDIyMTAyDQogICBVU0ENCg0KICAgRU1haWw6IGt6aGFuZ0BtaXRyZS5vcmcNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KQm91bmQsIGV0IGFsLiAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMjEs
IDIwMDUgICAgICAgICAgICAgICAgW1BhZ2UgMTRdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICBQcm9w
b3NhbCBmb3IgYSBOZXcgRmxvdyBMYWJlbCBEZWZpbml0aW9uIEZlYnJ1YXJ5IDIwMDUNCg0KDQpJ
bnRlbGxlY3R1YWwgUHJvcGVydHkgU3RhdGVtZW50DQoNCiAgIFRoZSBJRVRGIHRha2VzIG5vIHBv
c2l0aW9uIHJlZ2FyZGluZyB0aGUgdmFsaWRpdHkgb3Igc2NvcGUgb2YgYW55DQogICBJbnRlbGxl
Y3R1YWwgUHJvcGVydHkgUmlnaHRzIG9yIG90aGVyIHJpZ2h0cyB0aGF0IG1pZ2h0IGJlIGNsYWlt
ZWQgdG8NCiAgIHBlcnRhaW4gdG8gdGhlIGltcGxlbWVudGF0aW9uIG9yIHVzZSBvZiB0aGUgdGVj
aG5vbG9neSBkZXNjcmliZWQgaW4NCiAgIHRoaXMgZG9jdW1lbnQgb3IgdGhlIGV4dGVudCB0byB3
aGljaCBhbnkgbGljZW5zZSB1bmRlciBzdWNoIHJpZ2h0cw0KICAgbWlnaHQgb3IgbWlnaHQgbm90
IGJlIGF2YWlsYWJsZTsgbm9yIGRvZXMgaXQgcmVwcmVzZW50IHRoYXQgaXQgaGFzDQogICBtYWRl
IGFueSBpbmRlcGVuZGVudCBlZmZvcnQgdG8gaWRlbnRpZnkgYW55IHN1Y2ggcmlnaHRzLiAgSW5m
b3JtYXRpb24NCiAgIG9uIHRoZSBwcm9jZWR1cmVzIHdpdGggcmVzcGVjdCB0byByaWdodHMgaW4g
UkZDIGRvY3VtZW50cyBjYW4gYmUNCiAgIGZvdW5kIGluIEJDUCA3OCBhbmQgQkNQIDc5Lg0KDQog
ICBDb3BpZXMgb2YgSVBSIGRpc2Nsb3N1cmVzIG1hZGUgdG8gdGhlIElFVEYgU2VjcmV0YXJpYXQg
YW5kIGFueQ0KICAgYXNzdXJhbmNlcyBvZiBsaWNlbnNlcyB0byBiZSBtYWRlIGF2YWlsYWJsZSwg
b3IgdGhlIHJlc3VsdCBvZiBhbg0KICAgYXR0ZW1wdCBtYWRlIHRvIG9idGFpbiBhIGdlbmVyYWwg
bGljZW5zZSBvciBwZXJtaXNzaW9uIGZvciB0aGUgdXNlIG9mDQogICBzdWNoIHByb3ByaWV0YXJ5
IHJpZ2h0cyBieSBpbXBsZW1lbnRlcnMgb3IgdXNlcnMgb2YgdGhpcw0KICAgc3BlY2lmaWNhdGlv
biBjYW4gYmUgb2J0YWluZWQgZnJvbSB0aGUgSUVURiBvbi1saW5lIElQUiByZXBvc2l0b3J5IGF0
DQogICBodHRwOi8vd3d3LmlldGYub3JnL2lwci4NCg0KICAgVGhlIElFVEYgaW52aXRlcyBhbnkg
aW50ZXJlc3RlZCBwYXJ0eSB0byBicmluZyB0byBpdHMgYXR0ZW50aW9uIGFueQ0KICAgY29weXJp
Z2h0cywgcGF0ZW50cyBvciBwYXRlbnQgYXBwbGljYXRpb25zLCBvciBvdGhlciBwcm9wcmlldGFy
eQ0KICAgcmlnaHRzIHRoYXQgbWF5IGNvdmVyIHRlY2hub2xvZ3kgdGhhdCBtYXkgYmUgcmVxdWly
ZWQgdG8gaW1wbGVtZW50DQogICB0aGlzIHN0YW5kYXJkLiAgUGxlYXNlIGFkZHJlc3MgdGhlIGlu
Zm9ybWF0aW9uIHRvIHRoZSBJRVRGIGF0DQogICBpZXRmLWlwckBpZXRmLm9yZy4NCg0KDQpEaXNj
bGFpbWVyIG9mIFZhbGlkaXR5DQoNCiAgIFRoaXMgZG9jdW1lbnQgYW5kIHRoZSBpbmZvcm1hdGlv
biBjb250YWluZWQgaGVyZWluIGFyZSBwcm92aWRlZCBvbiBhbg0KICAgIkFTIElTIiBiYXNpcyBh
bmQgVEhFIENPTlRSSUJVVE9SLCBUSEUgT1JHQU5JWkFUSU9OIEhFL1NIRSBSRVBSRVNFTlRTDQog
ICBPUiBJUyBTUE9OU09SRUQgQlkgKElGIEFOWSksIFRIRSBJTlRFUk5FVCBTT0NJRVRZIEFORCBU
SEUgSU5URVJORVQNCiAgIEVOR0lORUVSSU5HIFRBU0sgRk9SQ0UgRElTQ0xBSU0gQUxMIFdBUlJB
TlRJRVMsIEVYUFJFU1MgT1IgSU1QTElFRCwNCiAgIElOQ0xVRElORyBCVVQgTk9UIExJTUlURUQg
VE8gQU5ZIFdBUlJBTlRZIFRIQVQgVEhFIFVTRSBPRiBUSEUNCiAgIElORk9STUFUSU9OIEhFUkVJ
TiBXSUxMIE5PVCBJTkZSSU5HRSBBTlkgUklHSFRTIE9SIEFOWSBJTVBMSUVEDQogICBXQVJSQU5U
SUVTIE9GIE1FUkNIQU5UQUJJTElUWSBPUiBGSVRORVNTIEZPUiBBIFBBUlRJQ1VMQVIgUFVSUE9T
RS4NCg0KDQpDb3B5cmlnaHQgU3RhdGVtZW50DQoNCiAgIENvcHlyaWdodCAoQykgVGhlIEludGVy
bmV0IFNvY2lldHkgKDIwMDUpLiAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0DQogICB0byB0aGUg
cmlnaHRzLCBsaWNlbnNlcyBhbmQgcmVzdHJpY3Rpb25zIGNvbnRhaW5lZCBpbiBCQ1AgNzgsIGFu
ZA0KICAgZXhjZXB0IGFzIHNldCBmb3J0aCB0aGVyZWluLCB0aGUgYXV0aG9ycyByZXRhaW4gYWxs
IHRoZWlyIHJpZ2h0cy4NCg0KDQpBY2tub3dsZWRnbWVudA0KDQogICBGdW5kaW5nIGZvciB0aGUg
UkZDIEVkaXRvciBmdW5jdGlvbiBpcyBjdXJyZW50bHkgcHJvdmlkZWQgYnkgdGhlDQogICBJbnRl
cm5ldCBTb2NpZXR5Lg0KDQoNCg0KDQpCb3VuZCwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEF1
Z3VzdCAyMSwgMjAwNSAgICAgICAgICAgICAgICBbUGFnZSAxNV0NCgwNCg==

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

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

------_=_NextPart_001_01C51CFB.03194768--




From rtgwg-bounces@ietf.org Thu Apr 28 08:53:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DR8WO-0007A3-9h; Thu, 28 Apr 2005 08:53:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DR8WI-00079u-Ir
	for rtgwg@megatron.ietf.org; Thu, 28 Apr 2005 08:53:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11194
	for <rtgwg@ietf.org>; Thu, 28 Apr 2005 08:53:29 -0400 (EDT)
Received: from weird-brew.cisco.com ([144.254.15.118]
	helo=av-tac-bru.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DR8j9-0000xc-VI
	for rtgwg@ietf.org; Thu, 28 Apr 2005 09:06:48 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j3SCrA215063; Thu, 28 Apr 2005 14:53:10 +0200 (CEST)
Received: from [194.78.81.66] (ams-clip-vpn-dhcp4436.cisco.com [10.61.81.83])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j3SCr5K15881; Thu, 28 Apr 2005 14:53:05 +0200 (CEST)
In-Reply-To: <5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
References: <5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <078547201246b9df5851c3625cdf92e6@cisco.com>
Content-Transfer-Encoding: 7bit
From: stefano previdi <sprevidi@cisco.com>
Date: Thu, 28 Apr 2005 14:54:46 +0200
To: Alia Atlas <aatlas@avici.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org


On Apr 27, 2005, at 10:52 PM, Alia Atlas wrote:

> Stefano,
>
> At 12:04 PM 4/27/2005, stefano previdi wrote:
>> On Apr 27, 2005, at 5:00 PM, Alia Atlas wrote:
>>
>>> Stefano,
>>>
>>> If I understand correctly, you are suggesting that the advertising 
>>> of the addresses could be a starting address (for the block) and 
>>> then each neighbor sub-TLV could give an index within that block?
>>
>> Not exactly. I was suggesting that each router will
>> advertise a kind of not-via summary address in addition
>> to the host part of it on its neighbor TLVs.
>>
>> Example: Router X advertises 10.1.1/24 as the summary
>> not-via address and then, for each of its neighbor on its
>> LSP, router X will add following subTLVs:
>>
>>         neighbor A, not-via-host-address: 1
>>         neighbor B, not-via-host-address: 5
>>         neighbor C, not-via-host-address: 20
>>         ...
>>
>> so, any other router in the area, when receiving router X
>> LSP, can derive that router X not-via addresses will be:
>>
>>         Neighbor-A: 10.1.1.1/32
>>         Neighbor-B: 10.1.1.5/32
>>         Neighbor-C: 10.1.1.20/32
>>
>> And nothing prevents router Y to advertise the _same_
>> summary but with different host addresses.
>
>
> OK.  This seems like it could be a useful way of reducing the actual 
> bits advertised.  It does seem to me that it might be useful/desirable 
> for a router to be able to advertise multiple summary addresses.

yes, but of course the idea being to reduce the amount
of data each router has to flood, advertising multiple
summary addresses may end up in limiting the gain...

>>>  Of course, that introduces the constraint that the notvia addresses 
>>> given by a particular router have to be contiguous
>>
>> I don't think so.
>>
>>>  - and brings up issues when the block size needs to increase.  It 
>>> sounds a lot like the label distribution mechanism used in RFC 2547.
>>
>> I still believe these addresses will likely be taken from
>> the private address space so the issue is more how to
>> reduce the effective information you advertise rather than
>> the address space you're going to use (10/8 will just work
>> fine).
>
> True, but needing to use 10/8 would dictate the effective information 
> required.  The ability to use multiple summaries could be useful to 
> reduce this further.
>
> I guess a question is whether this is the point of concern with the 
> additional quantity of notvia addresses, such that it deserves 
> substantial optimization.

well, I believe that adding a few thousands of ip address
to the igp may not be a big concern for now but still it's
worth to have an optimized scheme.

>>> Another question (somewhat related) would be how to handle a 
>>> neighbor connected by multiple parallel links.   Logically, one only 
>>> needs a single notvia address for the neighbor - but one doesn't 
>>> want the one used to be dependent on which of the parallel links 
>>> came up first.
>>> This argues that there may be multiple notvia addresses advertised 
>>> for a particular neighbor - for the parallel links case.
>>
>> in this case I believe the router will do ipfrr among ECMP
>> members so we need an address in case both link fails.
>
> I don't think so.  Consider that S is connected to E via a link & E is 
> connected to F via two links.  Now, F will advertise at least one F_!E 
> notvia address that S can use if its link to E fails (for traffic 
> whose next-next-hop is F).  The question is how does F decide what 
> address to use to mean F_!E.  It doesn't seem desirable (to me) to 
> have the specific address used to vary - based on which link to E came 
> up first or such.  Therefore, I'd assume that there could be multiple 
> notvia addresses that mean F_!E.

I know a few implementations that do not advertise parallel
links between routers. So in your example E and F will just
advertise a single adjacency in between themselves (the one
with the lowest metric). So, the rest of the area will just
not know the existence of parallel links.

> Do you see a cleaner way to do this & still ensure consistent use of 
> addresses through reboots, link state changes, etc?

I originally thought that the concern we may have is on the
volume of the additional data the igp has to flood. So my
suggestion was a way to reduce the amount of data that each
router will have to advertise, but I wasn't thinking about
a dynamic/automatic way of assigning addresses.

Having said that, we have also to consider that each router
will have to collect and derive all this information from
its lsdb and store it somewhere for the purpose of the
not-via SPFs computations... but of course this is more an
implementation issue.

s.

> Alia


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Apr 28 09:44:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DR9Jq-0007v3-2c; Thu, 28 Apr 2005 09:44:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DR9Jo-0007uy-Rd
	for rtgwg@megatron.ietf.org; Thu, 28 Apr 2005 09:44:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15003
	for <rtgwg@ietf.org>; Thu, 28 Apr 2005 09:44:39 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DR9Wg-0002x4-Qw
	for rtgwg@ietf.org; Thu, 28 Apr 2005 09:57:59 -0400
Received: from aatlas-lt.avici.com (b2-pc231.avici.com [10.2.100.231])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3SDiA7l028991;
	Thu, 28 Apr 2005 09:44:10 -0400
Message-Id: <5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 28 Apr 2005 09:43:53 -0400
To: stefano previdi <sprevidi@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <078547201246b9df5851c3625cdf92e6@cisco.com>
References: <5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

At 08:54 AM 4/28/2005, stefano previdi wrote:

>>OK.  This seems like it could be a useful way of reducing the actual bits 
>>advertised.  It does seem to me that it might be useful/desirable for a 
>>router to be able to advertise multiple summary addresses.
>
>yes, but of course the idea being to reduce the amount
>of data each router has to flood, advertising multiple
>summary addresses may end up in limiting the gain...

What I was considering was whether the router would need to advertise a 
10/8 - which allows saving of 2 bytes per notvia address (top octet plus 
mask) by using a single summary address or whether the router might be able 
to advertise multiple summary addresses so, say, 10.1.1/24 and then 
10.1.8/24 - which saves 4 bytes per notvia address - but adds the bits for 
identifying the summary address intended.

>>True, but needing to use 10/8 would dictate the effective information 
>>required.  The ability to use multiple summaries could be useful to 
>>reduce this further.
>>
>>I guess a question is whether this is the point of concern with the 
>>additional quantity of notvia addresses, such that it deserves 
>>substantial optimization.
>
>well, I believe that adding a few thousands of ip address
>to the igp may not be a big concern for now but still it's
>worth to have an optimized scheme.

Sure.  It's just a question of how complicated is reasonable.

>>I don't think so.  Consider that S is connected to E via a link & E is 
>>connected to F via two links.  Now, F will advertise at least one F_!E 
>>notvia address that S can use if its link to E fails (for traffic whose 
>>next-next-hop is F).  The question is how does F decide what address to 
>>use to mean F_!E.  It doesn't seem desirable (to me) to have the specific 
>>address used to vary - based on which link to E came up first or 
>>such.  Therefore, I'd assume that there could be multiple notvia 
>>addresses that mean F_!E.
>
>I know a few implementations that do not advertise parallel
>links between routers. So in your example E and F will just
>advertise a single adjacency in between themselves (the one
>with the lowest metric). So, the rest of the area will just
>not know the existence of parallel links.

I assume that you are thinking of ISIS & not OSPF?  Regardless, for 
fast-reroute purposes, it is extremely desirable to know of the existence 
of parallel links.  Otherwise, there may be an alternate path that isn't 
computed simply because it uses a parallel link.   The same issue arises 
with RSVP-TE.  For instance, the parallel links may not share any SRLGs in 
common - which can make for quite a difference.

>>Do you see a cleaner way to do this & still ensure consistent use of 
>>addresses through reboots, link state changes, etc?
>
>I originally thought that the concern we may have is on the
>volume of the additional data the igp has to flood. So my
>suggestion was a way to reduce the amount of data that each
>router will have to advertise, but I wasn't thinking about
>a dynamic/automatic way of assigning addresses.

I believe that it is important to consider a dynamic/automatic way of 
assigning addresses - and at the very least, it is needed to have a 
mechanism so that the same IP address means the same thing 
consistently!  If we don't have the latter, it'll be a bit of a nightmare 
to troubleshoot.

Now, the exact mechanisms for ensuring that consistency don't need to be 
specified, but the implications of such mechanisms into the protocol 
extensions, such that the mechanisms are feasible do.  Thus, the 
possibility of using multiple notvia addresses per neighbor.

>Having said that, we have also to consider that each router
>will have to collect and derive all this information from
>its lsdb and store it somewhere for the purpose of the
>not-via SPFs computations... but of course this is more an
>implementation issue.

Oh yes - and even more than just storing the info from the LSDB for the 
computation is the need to store the data for the incremental SPF 
topologies.  Actually, that one may be worth investigating a bit.  Mike & 
Stewart have said what the computation time is like using incremental SPFs 
to handle the notvia addresses.  What about the memory required?  Is it the 
case that the data on the last "primary topology" SPF is stored & then used 
as the basis for each of the other incremental SPFs so that the amount of 
data stored doesn't grow substantially with the number of notvia addresses?

Alia


>s.
>
>>Alia



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Apr 28 09:53:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DR9Sd-0001Al-Ve; Thu, 28 Apr 2005 09:53:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DR9Sb-0001AU-UD; Thu, 28 Apr 2005 09:53:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16019;
	Thu, 28 Apr 2005 09:53:44 -0400 (EDT)
Received: from relay2.mail.uk.clara.net ([80.168.70.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DR9fT-0003KU-WA; Thu, 28 Apr 2005 10:07:04 -0400
Received: from du-069-0201.access.clara.net ([217.158.132.201] helo=Puppy)
	by relay2.mail.uk.clara.net with smtp (Exim 4.50)
	id 1DR9SW-000OeJ-8y; Thu, 28 Apr 2005 14:53:41 +0100
Message-ID: <04fc01c54bf9$f7083fa0$1c849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Bound, Jim" <jim.bound@hp.com>, <ipv6@ietf.org>
References: <9C422444DE99BC46B3AD3C6EAFC9711B087EE13D@tayexc13.americas.cpqcorp.net>
Date: Thu, 28 Apr 2005 14:52:55 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: rtgwg@ietf.org
Subject: Re: 6LSA IETF Drafts
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

Jim,

Thanks for the heads-up.

Please ensure that any BOF you hold does not conflict with either the MPLS
or CCAMP working group meetins. I predict that many people will wish to
attend all three meetings.

After a preliminary reading of draft-chakravorty-6lsa-01.txt it seems to
me that what you are suggesting has massive overlap with MPLS and GMPLS.
That you are proposing a form of layer 3 switching which is not part of
MPLS or GMPLS (but which has been suggested at several previous IETF
meetings) is a fairly minor fact since the data plane operation of
swapping and switching is unchanged. That is, you are proposing a new form
of labeling.

The bigger difference comes in how the labels are distributed, and in this
context, one might ask what is wrong with existing label distribution
schemes.

But clearly I need to read in more detail.

Cheers,
Adrian

----- Original Message ----- 
From: "Bound, Jim" <jim.bound@hp.com>
To: <ipv6@ietf.org>
Cc: <rtgwg@ietf.org>
Sent: Sunday, February 27, 2005 7:34 PM
Subject: 6LSA IETF Drafts


Folks,

See below draft and two attached that will be available after the IETF.
It provides a solution for IPv6 Label Switch Architecture that does not
compete with MPLS or QOS work in progress in the industry at ITU, etc.

http://ietf.org/internet-drafts/draft-chakravorty-6lsa-01.txt

If some of you would do me a favor and review and send comments to Sham
Chakravorty schakra@mitre.org, Jim.Bound@nav6tf.org, and Kevin Zhang
kzhang@mitre.org I would appreciate it.  We will have a BOF most likely
on 6LSA at the Paris meeting to see if this would be its own working
group.  We will set up industry list for technical persons to work on it
until then if we get enough responses. I am pretty sure we should do
this here in the IETF not go to the ITU.  Also we will be at the
Minneapolis IETF so if you have in person comments that is appreciate
too.

Thanks
/jim





> _______________________________________________
> Rtgwg mailing list
> Rtgwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/rtgwg
>


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Apr 28 10:06:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DR9f2-0003dQ-QM; Thu, 28 Apr 2005 10:06:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DR9f1-0003dL-Pa
	for rtgwg@megatron.ietf.org; Thu, 28 Apr 2005 10:06:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17555
	for <rtgwg@ietf.org>; Thu, 28 Apr 2005 10:06:34 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DR9rt-0003qr-KD
	for rtgwg@ietf.org; Thu, 28 Apr 2005 10:19:54 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 28 Apr 2005 16:06:25 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3SE6M54010960; 
	Thu, 28 Apr 2005 16:06:23 +0200 (MEST)
Received: from mshand-w2k02.cisco.com (ams-clip-vpn-dhcp63.cisco.com
	[10.61.64.63])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA04349;
	Thu, 28 Apr 2005 15:06:21 +0100 (BST)
Message-Id: <4.3.2.7.2.20050428145808.038ac208@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 28 Apr 2005 15:06:15 +0100
To: Alia Atlas <aatlas@avici.com>
From: mike shand <mshand@cisco.com>
In-Reply-To: <5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
References: <078547201246b9df5851c3625cdf92e6@cisco.com>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: stefano previdi <sprevidi@cisco.com>, rtgwg@ietf.org
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

At 09:43 28/04/2005 -0400, Alia Atlas wrote:
>At 08:54 AM 4/28/2005, stefano previdi wrote:
>
>>>OK.  This seems like it could be a useful way of reducing the actual 
>>>bits advertised.  It does seem to me that it might be useful/desirable 
>>>for a router to be able to advertise multiple summary addresses.
>>
>>yes, but of course the idea being to reduce the amount
>>of data each router has to flood, advertising multiple
>>summary addresses may end up in limiting the gain...
>
>What I was considering was whether the router would need to advertise a 
>10/8 - which allows saving of 2 bytes per notvia address (top octet plus 
>mask) by using a single summary address or whether the router might be 
>able to advertise multiple summary addresses so, say, 10.1.1/24 and then 
>10.1.8/24 - which saves 4 bytes per notvia address - but adds the bits for 
>identifying the summary address intended.
>
>>>True, but needing to use 10/8 would dictate the effective information 
>>>required.  The ability to use multiple summaries could be useful to 
>>>reduce this further.
>>>
>>>I guess a question is whether this is the point of concern with the 
>>>additional quantity of notvia addresses, such that it deserves 
>>>substantial optimization.
>>
>>well, I believe that adding a few thousands of ip address
>>to the igp may not be a big concern for now but still it's
>>worth to have an optimized scheme.
>
>Sure.  It's just a question of how complicated is reasonable.
>
>>>I don't think so.  Consider that S is connected to E via a link & E is 
>>>connected to F via two links.  Now, F will advertise at least one F_!E 
>>>notvia address that S can use if its link to E fails (for traffic whose 
>>>next-next-hop is F).  The question is how does F decide what address to 
>>>use to mean F_!E.  It doesn't seem desirable (to me) to have the 
>>>specific address used to vary - based on which link to E came up first 
>>>or such.  Therefore, I'd assume that there could be multiple notvia 
>>>addresses that mean F_!E.
>>
>>I know a few implementations that do not advertise parallel
>>links between routers. So in your example E and F will just
>>advertise a single adjacency in between themselves (the one
>>with the lowest metric). So, the rest of the area will just
>>not know the existence of parallel links.
>
>I assume that you are thinking of ISIS & not OSPF?  Regardless, for 
>fast-reroute purposes, it is extremely desirable to know of the existence 
>of parallel links.  Otherwise, there may be an alternate path that isn't 
>computed simply because it uses a parallel link.   The same issue arises 
>with RSVP-TE.  For instance, the parallel links may not share any SRLGs in 
>common - which can make for quite a difference.


In the absence of SRLG then I don't think it matters because only the node 
local to the parallel link needs to know that it is actually parallel, and 
of course it does. However, in the SRLG case, it is certainly important if 
you have a paralell links which are members of different SRLGs. But I think 
to advertise the SRLG membership we would need to advertise both links 
anyway, which is what TE does (in IS-IS anyway).


>>>Do you see a cleaner way to do this & still ensure consistent use of 
>>>addresses through reboots, link state changes, etc?
>>
>>I originally thought that the concern we may have is on the
>>volume of the additional data the igp has to flood. So my
>>suggestion was a way to reduce the amount of data that each
>>router will have to advertise, but I wasn't thinking about
>>a dynamic/automatic way of assigning addresses.
>
>I believe that it is important to consider a dynamic/automatic way of 
>assigning addresses - and at the very least, it is needed to have a 
>mechanism so that the same IP address means the same thing 
>consistently!  If we don't have the latter, it'll be a bit of a nightmare 
>to troubleshoot.
>
>Now, the exact mechanisms for ensuring that consistency don't need to be 
>specified, but the implications of such mechanisms into the protocol 
>extensions, such that the mechanisms are feasible do.  Thus, the 
>possibility of using multiple notvia addresses per neighbor.
>
>>Having said that, we have also to consider that each router
>>will have to collect and derive all this information from
>>its lsdb and store it somewhere for the purpose of the
>>not-via SPFs computations... but of course this is more an
>>implementation issue.
>
>Oh yes - and even more than just storing the info from the LSDB for the 
>computation is the need to store the data for the incremental SPF 
>topologies.  Actually, that one may be worth investigating a bit.  Mike & 
>Stewart have said what the computation time is like using incremental SPFs 
>to handle the notvia addresses.  What about the memory required?  Is it 
>the case that the data on the last "primary topology" SPF is stored & then 
>used as the basis for each of the other incremental SPFs so that the 
>amount of data stored doesn't grow substantially with the number of notvia 
>addresses?

Yes. You compute the "primary topology", which in its simplest form would 
just be the result of your normal SPF, but for interoperability reasons 
would probably be the normal topology minus any routers which can't do 
not-via. (this could be done as an incremental from the normal SPF topology 
if you like, but the gain is not going to be that great). Then for each 
"object" that you need to disable to compute its notvia addresses, you run 
an incremental from that primary topology. So, apart from some additional 
data structures  to allow you to run the incremental while preserving the 
primary topology for the next incremental, there is no additional memory 
requirement.

There is plenty of scope here for trading off memory against processing of 
course, but that is up to the individual implementation.

         Mike



>Alia
>
>
>>s.
>>
>>>Alia
>
>
>
>_______________________________________________
>Rtgwg mailing list
>Rtgwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/rtgwg

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Apr 28 13:18:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRCei-000647-Mz; Thu, 28 Apr 2005 13:18:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRCeh-000642-B6
	for rtgwg@megatron.ietf.org; Thu, 28 Apr 2005 13:18:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05940
	for <rtgwg@ietf.org>; Thu, 28 Apr 2005 13:18:24 -0400 (EDT)
Received: from weird-brew.cisco.com ([144.254.15.118]
	helo=av-tac-bru.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DRCra-0003zk-VU
	for rtgwg@ietf.org; Thu, 28 Apr 2005 13:31:47 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j3SHIAi04888; Thu, 28 Apr 2005 19:18:10 +0200 (CEST)
Received: from [144.254.14.92] (dhcp-peg2-vl21-144-254-14-92.cisco.com
	[144.254.14.92])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j3SHI9K09173; Thu, 28 Apr 2005 19:18:09 +0200 (CEST)
In-Reply-To: <5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
References: <5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <10b7a9cd811ab666398c45c09345a149@cisco.com>
Content-Transfer-Encoding: 7bit
From: stefano previdi <sprevidi@cisco.com>
Date: Thu, 28 Apr 2005 19:19:51 +0200
To: Alia Atlas <aatlas@avici.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: 7bit
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org


On Apr 28, 2005, at 3:43 PM, Alia Atlas wrote:

> At 08:54 AM 4/28/2005, stefano previdi wrote:
>
>>> OK.  This seems like it could be a useful way of reducing the actual 
>>> bits advertised.  It does seem to me that it might be 
>>> useful/desirable for a router to be able to advertise multiple 
>>> summary addresses.
>>
>> yes, but of course the idea being to reduce the amount
>> of data each router has to flood, advertising multiple
>> summary addresses may end up in limiting the gain...
>
> What I was considering was whether the router would need to advertise 
> a 10/8 - which allows saving of 2 bytes per notvia address (top octet 
> plus mask) by using a single summary address or whether the router 
> might be able to advertise multiple summary addresses so, say, 
> 10.1.1/24 and then 10.1.8/24 - which saves 4 bytes per notvia address 
> - but adds the bits for identifying the summary address intended.

well... at this stage it's more a deployment issue...
but we certainly need to allow multiple summaries.

>>> True, but needing to use 10/8 would dictate the effective 
>>> information required.  The ability to use multiple summaries could 
>>> be useful to reduce this further.
>>>
>>> I guess a question is whether this is the point of concern with the 
>>> additional quantity of notvia addresses, such that it deserves 
>>> substantial optimization.
>>
>> well, I believe that adding a few thousands of ip address
>> to the igp may not be a big concern for now but still it's
>> worth to have an optimized scheme.
>
> Sure.  It's just a question of how complicated is reasonable.
>
>>> I don't think so.  Consider that S is connected to E via a link & E 
>>> is connected to F via two links.  Now, F will advertise at least one 
>>> F_!E notvia address that S can use if its link to E fails (for 
>>> traffic whose next-next-hop is F).  The question is how does F 
>>> decide what address to use to mean F_!E.  It doesn't seem desirable 
>>> (to me) to have the specific address used to vary - based on which 
>>> link to E came up first or such.  Therefore, I'd assume that there 
>>> could be multiple notvia addresses that mean F_!E.
>>
>> I know a few implementations that do not advertise parallel
>> links between routers. So in your example E and F will just
>> advertise a single adjacency in between themselves (the one
>> with the lowest metric). So, the rest of the area will just
>> not know the existence of parallel links.
>
> I assume that you are thinking of ISIS & not OSPF?

as far as I'm concerned... yes.

>  Regardless, for fast-reroute purposes, it is extremely desirable to 
> know of the existence of parallel links.  Otherwise, there may be an 
> alternate path that isn't computed simply because it uses a parallel 
> link.   The same issue arises with RSVP-TE.  For instance, the 
> parallel links may not share any SRLGs in common - which can make for 
> quite a difference.

yes, I was referring to IP-only networks. When TE is deployed
such behavior is not used. Odf course we won't use it for ipfrr
neither. It's maybe worth to mention this in some place...

>>> Do you see a cleaner way to do this & still ensure consistent use of 
>>> addresses through reboots, link state changes, etc?
>>
>> I originally thought that the concern we may have is on the
>> volume of the additional data the igp has to flood. So my
>> suggestion was a way to reduce the amount of data that each
>> router will have to advertise, but I wasn't thinking about
>> a dynamic/automatic way of assigning addresses.
>
> I believe that it is important to consider a dynamic/automatic way of 
> assigning addresses - and at the very least, it is needed to have a 
> mechanism so that the same IP address means the same thing 
> consistently!  If we don't have the latter, it'll be a bit of a 
> nightmare to troubleshoot.

I certainly agree with the last part of your statement but
not the first part. Manual assignment of ip addresses is
something that is being done from day one and I don't
believe we have any strong need to make it dynamic. Of
course, a dynamic assignment method that will be consistent
across re-starts and predictable in its results is always
a plus we can think of but at the current stage of ipfrr
I don't see it as a must.

> Now, the exact mechanisms for ensuring that consistency don't need to 
> be specified, but the implications of such mechanisms into the 
> protocol extensions, such that the mechanisms are feasible do.  Thus, 
> the possibility of using multiple notvia addresses per neighbor.
>
>> Having said that, we have also to consider that each router
>> will have to collect and derive all this information from
>> its lsdb and store it somewhere for the purpose of the
>> not-via SPFs computations... but of course this is more an
>> implementation issue.
>
> Oh yes - and even more than just storing the info from the LSDB for 
> the computation is the need to store the data for the incremental SPF 
> topologies.  Actually, that one may be worth investigating a bit.  
> Mike & Stewart have said what the computation time is like using 
> incremental SPFs to handle the notvia addresses.

yes...

>  What about the memory required?  Is it the case that the data on the 
> last "primary topology" SPF is stored & then used as the basis for 
> each of the other incremental SPFs so that the amount of data stored 
> doesn't grow substantially with the number of notvia addresses?

this is one option. Note that in most of the cases each
router stores anyway the data related to its last SPT so
the not-via overhead may not _that_ significant...

Also, the way you store ip addresses and the way you update
rib/fib will make the difference in terms of scaling and
performance.

s.

>
> Alia
>
>
>> s.
>>
>>> Alia
>


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Apr 28 15:08:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRENS-0008Tw-91; Thu, 28 Apr 2005 15:08:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRENQ-0008Tk-BL
	for rtgwg@megatron.ietf.org; Thu, 28 Apr 2005 15:08:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14873
	for <rtgwg@ietf.org>; Thu, 28 Apr 2005 15:08:42 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DREaJ-0000F0-W9
	for rtgwg@ietf.org; Thu, 28 Apr 2005 15:22:05 -0400
Received: from aatlas-lt.avici.com (aatlas-lt.avici.com [10.2.20.92])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3SJ8G7l027238;
	Thu, 28 Apr 2005 15:08:16 -0400
Message-Id: <5.1.0.14.2.20050428143518.01eeadb0@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 28 Apr 2005 15:08:15 -0400
To: mike shand <mshand@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <4.3.2.7.2.20050428145808.038ac208@jaws.cisco.com>
References: <5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
	<078547201246b9df5851c3625cdf92e6@cisco.com>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: stefano previdi <sprevidi@cisco.com>, rtgwg@ietf.org
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

At 10:06 AM 4/28/2005, mike shand wrote:
>At 09:43 28/04/2005 -0400, Alia Atlas wrote:
>>At 08:54 AM 4/28/2005, stefano previdi wrote:
>>>>I don't think so.  Consider that S is connected to E via a link & E is 
>>>>connected to F via two links.  Now, F will advertise at least one F_!E 
>>>>notvia address that S can use if its link to E fails (for traffic whose 
>>>>next-next-hop is F).  The question is how does F decide what address to 
>>>>use to mean F_!E.  It doesn't seem desirable (to me) to have the 
>>>>specific address used to vary - based on which link to E came up first 
>>>>or such.  Therefore, I'd assume that there could be multiple notvia 
>>>>addresses that mean F_!E.
>>>
>>>I know a few implementations that do not advertise parallel
>>>links between routers. So in your example E and F will just
>>>advertise a single adjacency in between themselves (the one
>>>with the lowest metric). So, the rest of the area will just
>>>not know the existence of parallel links.
>>
>>I assume that you are thinking of ISIS & not OSPF?  Regardless, for 
>>fast-reroute purposes, it is extremely desirable to know of the existence 
>>of parallel links.  Otherwise, there may be an alternate path that isn't 
>>computed simply because it uses a parallel link.   The same issue arises 
>>with RSVP-TE.  For instance, the parallel links may not share any SRLGs 
>>in common - which can make for quite a difference.
>
>In the absence of SRLG then I don't think it matters because only the node 
>local to the parallel link needs to know that it is actually parallel, and 
>of course it does. However, in the SRLG case, it is certainly important if 
>you have a paralell links which are members of different SRLGs. But I 
>think to advertise the SRLG membership we would need to advertise both 
>links anyway, which is what TE does (in IS-IS anyway).

I agree that it doesn't matter except in the SRLG cases.

>>Oh yes - and even more than just storing the info from the LSDB for the 
>>computation is the need to store the data for the incremental SPF 
>>topologies.  Actually, that one may be worth investigating a bit.  Mike & 
>>Stewart have said what the computation time is like using incremental 
>>SPFs to handle the notvia addresses.  What about the memory required?  Is 
>>it the case that the data on the last "primary topology" SPF is stored & 
>>then used as the basis for each of the other incremental SPFs so that the 
>>amount of data stored doesn't grow substantially with the number of 
>>notvia addresses?
>
>Yes. You compute the "primary topology", which in its simplest form would 
>just be the result of your normal SPF, but for interoperability reasons 
>would probably be the normal topology minus any routers which can't do 
>not-via. (this could be done as an incremental from the normal SPF 
>topology if you like, but the gain is not going to be that great). Then 
>for each "object" that you need to disable to compute its notvia 
>addresses, you run an incremental from that primary topology. So, apart 
>from some additional data structures  to allow you to run the incremental 
>while preserving the primary topology for the next incremental, there is 
>no additional memory requirement.
>
>There is plenty of scope here for trading off memory against processing of 
>course, but that is up to the individual implementation.

That's about what I expected and seems quite reasonable.

Alia



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Apr 28 17:31:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRGbT-0000mT-LV; Thu, 28 Apr 2005 17:31:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRGbR-0000mG-I9
	for rtgwg@megatron.ietf.org; Thu, 28 Apr 2005 17:31:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26676
	for <rtgwg@ietf.org>; Thu, 28 Apr 2005 17:31:19 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRGoL-00068b-CZ
	for rtgwg@ietf.org; Thu, 28 Apr 2005 17:44:43 -0400
Received: from aatlas-lt.avici.com (b2-pc215.avici.com [10.2.100.215])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3SLV07l019720;
	Thu, 28 Apr 2005 17:31:01 -0400
Message-Id: <5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 28 Apr 2005 17:30:56 -0400
To: stefano previdi <sprevidi@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <10b7a9cd811ab666398c45c09345a149@cisco.com>
References: <5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: rtgwg@ietf.org, mike shand <mshand@cisco.com>
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

At 01:19 PM 4/28/2005, stefano previdi wrote:
>On Apr 28, 2005, at 3:43 PM, Alia Atlas wrote:
>>What I was considering was whether the router would need to advertise a 
>>10/8 - which allows saving of 2 bytes per notvia address (top octet plus 
>>mask) by using a single summary address or whether the router might be 
>>able to advertise multiple summary addresses so, say, 10.1.1/24 and then 
>>10.1.8/24 - which saves 4 bytes per notvia address - but adds the bits 
>>for identifying the summary address intended.
>
>well... at this stage it's more a deployment issue...
>but we certainly need to allow multiple summaries.

As long as we agree on the need to support multiple summaries (at the very 
least to allow the transition from one summary to another), then what type 
of issue we each think it is doesn't seem to matter much. :-)

>>I assume that you are thinking of ISIS & not OSPF?
>
>as far as I'm concerned... yes.

We do want a solution that works for both, so it's useful to catch the 
different assumptions.

>>  Regardless, for fast-reroute purposes, it is extremely desirable to 
>> know of the existence of parallel links.  Otherwise, there may be an 
>> alternate path that isn't computed simply because it uses a parallel 
>> link.   The same issue arises with RSVP-TE.  For instance, the parallel 
>> links may not share any SRLGs in common - which can make for quite a 
>> difference.
>
>yes, I was referring to IP-only networks. When TE is deployed
>such behavior is not used. Odf course we won't use it for ipfrr
>neither. It's maybe worth to mention this in some place...

As Mike pointed out, not reported parallel links isn't a problem until one 
starts to consider SRLGs (local or general).

>>I believe that it is important to consider a dynamic/automatic way of 
>>assigning addresses - and at the very least, it is needed to have a 
>>mechanism so that the same IP address means the same thing 
>>consistently!  If we don't have the latter, it'll be a bit of a nightmare 
>>to troubleshoot.
>
>I certainly agree with the last part of your statement but
>not the first part. Manual assignment of ip addresses is
>something that is being done from day one and I don't
>believe we have any strong need to make it dynamic. Of
>course, a dynamic assignment method that will be consistent
>across re-starts and predictable in its results is always
>a plus we can think of but at the current stage of ipfrr
>I don't see it as a must.

Consistency is the primary concern.  The next is simplicity of 
configuration, trouble-shooting and operation.  Manual assignment of 
addresses to interfaces could be good enough; perhaps the options are just 
implementation differences as to how the router derives a particular notvia 
address to use per interface.

>>  What about the memory required?  Is it the case that the data on the 
>> last "primary topology" SPF is stored & then used as the basis for each 
>> of the other incremental SPFs so that the amount of data stored doesn't 
>> grow substantially with the number of notvia addresses?
>
>this is one option. Note that in most of the cases each
>router stores anyway the data related to its last SPT so
>the not-via overhead may not _that_ significant...

Depends on the router of course, but also as Mike pointed out, the base 
topology used for the notvia computation also has to toss out those routers 
that aren't capable.

>Also, the way you store ip addresses and the way you update
>rib/fib will make the difference in terms of scaling and
>performance.

Isn't is always so?

Alia



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Thu Apr 28 18:01:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRH54-0006RR-Ci; Thu, 28 Apr 2005 18:01:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRH52-0006RJ-Kr
	for rtgwg@megatron.ietf.org; Thu, 28 Apr 2005 18:01:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29140
	for <rtgwg@ietf.org>; Thu, 28 Apr 2005 18:01:54 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRHHx-0007N9-Kw
	for rtgwg@ietf.org; Thu, 28 Apr 2005 18:15:19 -0400
Received: from aatlas-lt.avici.com (b2-pc215.avici.com [10.2.100.215])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3SM1i7l024924
	for <rtgwg@ietf.org>; Thu, 28 Apr 2005 18:01:44 -0400
Message-Id: <5.1.0.14.2.20050428175014.01ee5758@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 28 Apr 2005 18:01:34 -0400
To: rtgwg@ietf.org
From: Alia Atlas <aatlas@avici.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: LFAs and OSPF applicability & problem reporting
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

As the current draft mentions, the loop-free alternates can only be safely 
used within certain network scenarios for OSPF.  The current version of the 
draft discusses the concept of strict downstream alternates;  I am planning 
on removing those from the draft & instead discussing the abstract concept 
(in an appendix) of being able to guarantee an alternate provides 
protection based upon the correct distance checks.

One concern/suggestion raised by Dave Ward this last IETF was that it would 
be good to have an automatic method to detect that a potential problem 
existed with the network topology for OSPF.

This is challenging for the router computing the LFA to do.  However, it 
seems that an ABR could detect, for a given route when an problematic 
decision-point is observed.  For instance, for an ASE route, the ABR could 
detect that it has the option of intra-area routes from multiple 
areas.   For such detection to work, support would be required on the 
ABR.  Otherwise, LFAs can be incrementally deployed - as their computation 
and use can be a local decision.

If such detection by an ABR is desirable, I think it makes sense to put it 
in an OSPF specific MIB.  Presumably, one could get a count of the number 
of such routes as well as which they were.  One could also have a trap for 
the trigger from 0 to non-zero for that count & vice-versa.

Thoughts?  Does this seem like a reasonable, operator-friendly way of 
handling the applicability requirements for LFAs in OSPF?

I'll be sending out text with the proposed section on those applicability 
requirements relatively shortly.

Alia


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Fri Apr 29 05:14:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRRaH-0001Y3-SM; Fri, 29 Apr 2005 05:14:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRRa9-0001Xy-Dh
	for rtgwg@megatron.ietf.org; Fri, 29 Apr 2005 05:14:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06575
	for <rtgwg@ietf.org>; Fri, 29 Apr 2005 05:14:43 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRRnA-0001Cw-QP
	for rtgwg@ietf.org; Fri, 29 Apr 2005 05:28:14 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 29 Apr 2005 11:14:35 +0200
Received: from cisco.com (ams-clip-vpn-dhcp4314.cisco.com [10.61.80.217])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3T9ES54024275; 
	Fri, 29 Apr 2005 11:14:31 +0200 (MEST)
Message-ID: <4271FAF1.4090500@cisco.com>
Date: Fri, 29 Apr 2005 10:14:25 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alia Atlas <aatlas@avici.com>
References: <5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
	<5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>
In-Reply-To: <5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: mike shand <mshand@cisco.com>, stefano previdi <sprevidi@cisco.com>,
	rtgwg@ietf.org
Subject: Re: thoughts on  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org


>>> I believe that it is important to consider a dynamic/automatic way of 
>>> assigning addresses - and at the very least, it is needed to have a 
>>> mechanism so that the same IP address means the same thing 
>>> consistently!  If we don't have the latter, it'll be a bit of a 
>>> nightmare to troubleshoot.
>>
>>
>> I certainly agree with the last part of your statement but
>> not the first part. Manual assignment of ip addresses is
>> something that is being done from day one and I don't
>> believe we have any strong need to make it dynamic. Of
>> course, a dynamic assignment method that will be consistent
>> across re-starts and predictable in its results is always
>> a plus we can think of but at the current stage of ipfrr
>> I don't see it as a must.
> 
> 
> Consistency is the primary concern.  The next is simplicity of 
> configuration, trouble-shooting and operation.  Manual assignment of 
> addresses to interfaces could be good enough; perhaps the options are 
> just implementation differences as to how the router derives a 
> particular notvia address to use per interface.
> 

I think so. Whilst I think that we need a manual address assignment
mode, I am sure that we will also need a block assignment mode.
The config should then try hard to allocate the same address across
reboots, but I do not think that it needs to be perfect. Any tool
that needs to know which address was allocated to which interface
could look in the link state DB.

Stewart

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Fri Apr 29 13:39:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRZSY-000234-J0; Fri, 29 Apr 2005 13:39:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRZSX-00022z-52
	for rtgwg@megatron.ietf.org; Fri, 29 Apr 2005 13:39:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22606
	for <rtgwg@ietf.org>; Fri, 29 Apr 2005 13:39:22 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRZfd-0007zV-1x
	for rtgwg@ietf.org; Fri, 29 Apr 2005 13:52:58 -0400
Received: from aatlas-lt.avici.com (b2-pc45.avici.com [10.2.100.45])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3THcw7l002781;
	Fri, 29 Apr 2005 13:39:02 -0400
Message-Id: <5.1.0.14.2.20050429133636.0201fb70@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 29 Apr 2005 13:38:52 -0400
To: Stewart Bryant <stbryant@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <4271FAF1.4090500@cisco.com>
References: <5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>
	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
	<5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: mike shand <mshand@cisco.com>, stefano previdi <sprevidi@cisco.com>,
	rtgwg@ietf.org
Subject: Re: thoughts on draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

At 05:14 AM 4/29/2005, Stewart Bryant wrote:
>>Consistency is the primary concern.  The next is simplicity of 
>>configuration, trouble-shooting and operation.  Manual assignment of 
>>addresses to interfaces could be good enough; perhaps the options are 
>>just implementation differences as to how the router derives a particular 
>>notvia address to use per interface.
>
>I think so. Whilst I think that we need a manual address assignment
>mode, I am sure that we will also need a block assignment mode.
>The config should then try hard to allocate the same address across
>reboots, but I do not think that it needs to be perfect. Any tool
>that needs to know which address was allocated to which interface
>could look in the link state DB.

I am more concerned about the notvia addresses changing meaning as 
interfaces go up and down.  That would be an issue.  Tools are fine - but 
would all need to be augmented to do such understanding - and human 
operators may make assumptions - such as that the meaning/presence/use of 
an IP address doesn't dynamically change.

Alia


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Fri Apr 29 17:31:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRd4j-0004Wd-57; Fri, 29 Apr 2005 17:31:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRd4i-0004WX-AN
	for rtgwg@megatron.ietf.org; Fri, 29 Apr 2005 17:31:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16935
	for <rtgwg@ietf.org>; Fri, 29 Apr 2005 17:31:01 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRdHq-0005Se-2J
	for rtgwg@ietf.org; Fri, 29 Apr 2005 17:44:39 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 29 Apr 2005 23:30:53 +0200
Received: from cisco.com (ams-clip-vpn-dhcp215.cisco.com [10.61.64.215])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3TLUg54010728; 
	Fri, 29 Apr 2005 23:30:49 +0200 (MEST)
Message-ID: <4272A77C.1070706@cisco.com>
Date: Fri, 29 Apr 2005 22:30:36 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alia Atlas <aatlas@avici.com>
References: <5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>	<5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>
	<5.1.0.14.2.20050429133636.0201fb70@10.2.0.68>
In-Reply-To: <5.1.0.14.2.20050429133636.0201fb70@10.2.0.68>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: rtgwg@ietf.org, stefano previdi <sprevidi@cisco.com>,
	mike shand <mshand@cisco.com>
Subject: Re: thoughts on draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org



Alia Atlas wrote:

> At 05:14 AM 4/29/2005, Stewart Bryant wrote:
> 
>>> Consistency is the primary concern.  The next is simplicity of 
>>> configuration, trouble-shooting and operation.  Manual assignment of 
>>> addresses to interfaces could be good enough; perhaps the options are 
>>> just implementation differences as to how the router derives a 
>>> particular notvia address to use per interface.
>>
>>
>> I think so. Whilst I think that we need a manual address assignment
>> mode, I am sure that we will also need a block assignment mode.
>> The config should then try hard to allocate the same address across
>> reboots, but I do not think that it needs to be perfect. Any tool
>> that needs to know which address was allocated to which interface
>> could look in the link state DB.
> 
> 
> I am more concerned about the notvia addresses changing meaning as 
> interfaces go up and down.  That would be an issue.  

I agree, we need to find a way to make them sticky.

Stewart


> Tools are fine - 
> but would all need to be augmented to do such understanding - and human 
> operators may make assumptions - such as that the meaning/presence/use 
> of an IP address doesn't dynamically change.
> 
> Alia
> 
> 
> _______________________________________________
> Rtgwg mailing list
> Rtgwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/rtgwg
> 
> 

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From rtgwg-bounces@ietf.org Fri Apr 29 20:20:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRfia-00052z-4G; Fri, 29 Apr 2005 20:20:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRfiY-00052u-DP
	for rtgwg@megatron.ietf.org; Fri, 29 Apr 2005 20:20:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04202
	for <rtgwg@ietf.org>; Fri, 29 Apr 2005 20:20:20 -0400 (EDT)
Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRfvh-00062o-QE
	for rtgwg@ietf.org; Fri, 29 Apr 2005 20:33:59 -0400
Received: from aatlas-lt.avici.com (b2-pc135.avici.com [10.2.100.135])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j3U0Iw7l002473;
	Fri, 29 Apr 2005 20:19:00 -0400
Message-Id: <5.1.0.14.2.20050429201731.01e7eb40@10.2.0.68>
X-Sender: aatlas@10.2.0.68
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 29 Apr 2005 20:18:45 -0400
To: Stewart Bryant <stbryant@cisco.com>
From: Alia Atlas <aatlas@avici.com>
In-Reply-To: <4272A77C.1070706@cisco.com>
References: <5.1.0.14.2.20050429133636.0201fb70@10.2.0.68>
	<5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>
	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050325145408.01fa1378@mailhost.avici.com>
	<5.1.0.14.2.20050426110603.020131f0@10.2.0.68>
	<5.1.0.14.2.20050427104752.01feee90@10.2.0.68>
	<5.1.0.14.2.20050427164229.01f95be0@10.2.0.68>
	<5.1.0.14.2.20050428093141.01e7fea8@10.2.0.68>
	<5.1.0.14.2.20050428172357.01ef6ed0@10.2.0.68>
	<5.1.0.14.2.20050429133636.0201fb70@10.2.0.68>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: rtgwg@ietf.org, stefano previdi <sprevidi@cisco.com>,
	mike shand <mshand@cisco.com>
Subject: Re: thoughts on
  draft-bryant-shand-ipfrr-notvia-addresses-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org

At 05:30 PM 4/29/2005, Stewart Bryant wrote:


>Alia Atlas wrote:
>>I am more concerned about the notvia addresses changing meaning as 
>>interfaces go up and down.  That would be an issue.
>
>I agree, we need to find a way to make them sticky.

I think that an aspect of this is that there can be multiple notvia 
addresses advertised by the same router to avoid the same resource.

Anyhow, I think we've got agreement here.  Want to pick the next issue to 
discuss? :-)

Alia


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



