Re: [Idr] draft-dickson-idr-second-best-backup-02

Brian Dickson <briand@ca.afilias.info> Tue, 18 March 2008 16:38 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12A3228C6B6; Tue, 18 Mar 2008 09:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.68
X-Spam-Level:
X-Spam-Status: No, score=-100.68 tagged_above=-999 required=5 tests=[AWL=-0.243, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QIOvRwEgoOLM; Tue, 18 Mar 2008 09:38:08 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C090F28C52E; Tue, 18 Mar 2008 09:38:08 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC40B28C21A for <idr@core3.amsl.com>; Tue, 18 Mar 2008 09:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YeyWSPE+CsAZ for <idr@core3.amsl.com>; Tue, 18 Mar 2008 09:38:04 -0700 (PDT)
Received: from mx4.ca.afilias.info (vgateway.libertyrms.info [207.219.45.62]) by core3.amsl.com (Postfix) with ESMTP id D515E28C52E for <idr@ietf.org>; Tue, 18 Mar 2008 09:38:03 -0700 (PDT)
Received: from briand-vpn.int.libertyrms.com ([10.1.7.90]) by mx4.ca.afilias.info with esmtp (Exim 4.22) id 1Jbemw-0004Vs-T8; Tue, 18 Mar 2008 12:35:46 -0400
Message-ID: <47DFEF5C.6000803@ca.afilias.info>
Date: Tue, 18 Mar 2008 12:35:40 -0400
From: Brian Dickson <briand@ca.afilias.info>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Enke Chen <enkechen@cisco.com>
References: <20080218113944.DD87728C0F4@core3.amsl.com> <9E974148-E332-45AB-AB80-283A244182D9@muada.com> <47C3277E.5060502@ca.afilias.info> <47CE34D6.9080600@ca.afilias.info> <47DF8466.8090203@cs.uni-bonn.de> <47DFE2B6.1030409@ca.afilias.info> <47DFE76A.9080507@cisco.com>
In-Reply-To: <47DFE76A.9080507@cisco.com>
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
Cc: idr <idr@ietf.org>
Subject: Re: [Idr] draft-dickson-idr-second-best-backup-02
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Enke Chen wrote:
> Hi, Brian:
>
> I have several questions below.
>
> Brian Dickson wrote:
>
> [snip]
>>
>> I will definitely be modifying the draft, to incorporate N rather 
>> than just 2 for the additional paths.
>>
>> I'll be using most of the walton-draft, as it covers the N-path 
>> codification quite well.
>>   
>
> Have you asked for permission from the walton-draft authors to "use 
> most of the walton-draft", and have you been granted such a permission?
>

As I haven't made the changes yet, I haven't asked yet.

I will be asking permissions from all of the authors, including the 
authors of the referenced incorporated work.

However, technically, I would note that such permission is not required. 
See section 7.3 of BCP78.

Please don't jump to any conclusions about my intentions, simply because 
I haven't yet asked. I only just got back from the IETF on the weekend! :-)

I plan on using language very similar to that found in the walton-draft, 
where it acknowledges that it itself was making use of earlier work by 
Chen et al.

This is consistent with IETF WG documents and procedures.

> I must be missing something here.  You will be "using most of the 
> walton-draft" in your draft to solve a subset of the problem that the 
> walton-draft has already covered?
No, I am adding in only the elements of the walton-draft to encode N-way 
rather than 2-way additional paths.
And, I will be modifying those substantively, since they do not encode 
order on the multiple paths.

What my draft covers, is strictly a superset, not a subset, of what 
walton-draft covered.

And notably, there are corner cases that walton-draft does not handle, 
that my draft does.
Specifically, the modified step (c) handles cases which the walton-draft 
would not handle, or where it would select infeasible paths.
(This happens to be a critical part of ensuring that the propagation on 
inter-as additional paths is valid and correct. The walton-draft didn't 
explicitly cover inter-as at all.)

Brian
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr