IETF Logo Mail Archive

Re: [dtn] new BPbis spec reference mistakes

Lucas Kahlert <lucas.kahlert@tu-dresden.de> Wed, 23 August 2017 16:57 UTC

Return-Path: <lucas.kahlert@tu-dresden.de>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A60013208E for <dtn@ietfa.amsl.com>; Wed, 23 Aug 2017 09:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jpTGVATYMwGQ for <dtn@ietfa.amsl.com>; Wed, 23 Aug 2017 09:57:25 -0700 (PDT)
Received: from mailout6.zih.tu-dresden.de (mailout6.zih.tu-dresden.de [141.30.67.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0C3D132025 for <dtn@ietf.org>; Wed, 23 Aug 2017 09:57:24 -0700 (PDT)
Received: from mail.zih.tu-dresden.de ([141.76.14.4]) by mailout6.zih.tu-dresden.de with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <lucas.kahlert@tu-dresden.de>) id 1dkYy2-00025E-BQ for dtn@ietf.org; Wed, 23 Aug 2017 18:57:23 +0200
Received: from 77-64-188-193.dynamic.primacom.net ([77.64.188.193] helo=[192.168.1.12]) by server-50.mailclusterdns.zih.tu-dresden.de with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (envelope-from <lucas.kahlert@tu-dresden.de>) id 1dkYy1-0003h3-Fu for dtn@ietf.org; Wed, 23 Aug 2017 18:57:21 +0200
To: dtn@ietf.org
References: <A5BEAD028815CB40A32A5669CF737C3B8AF03CF0@ap-embx-sp40.RES.AD.JPL> <232a391f-dbae-7c10-cf41-71cb6ca08694@tu-dresden.de>
From: Lucas Kahlert <lucas.kahlert@tu-dresden.de>
Message-ID: <f1a70ce3-1df5-4335-3542-b6521e3de748@tu-dresden.de>
Date: Wed, 23 Aug 2017 18:57:20 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <232a391f-dbae-7c10-cf41-71cb6ca08694@tu-dresden.de>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-TUD-Original-From: lucas.kahlert@tu-dresden.de
X-TUD-Virus-Scanned: mailout6.zih.tu-dresden.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/fnXODxs-WWOpRiKTesjk4bGh5tk>
Subject: Re: [dtn] new BPbis spec reference mistakes
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Aug 2017 16:57:27 -0000

Hello,

I think the reference mistakes are still there in version 
draft-ietf-dtn-bpbis-08.

Regards,
Lucas

On 14.07.2017 13:23, Lucas Kahlert wrote:
> Hi,
> 
> I think I have found some mistakes in the cross-references of the new 
> BPbis:
> 
>   - Section 5.14 Bundle Deletion does not exist, I think it should be 
> "Section 5.10"
>   - 5.4.1 Forwarding Contraindicated: "Proceed from Step 5", I think 
> Step 4 is meant
> 
> Regards,
> Lucas
> 
> On 23.06.2017 00:34, Burleigh, Scott C (312B) wrote:
>> Hi.  I just posted an updated BPbis specification that I think 
>> addresses nearly all of the comments on which we reached consensus, 
>> either over email or at IETF 98.  The one exception I can think of is 
>> the request to add references to formal definitions for CRC-16-ANSI 
>> and CRC-32, which I omitted because on a quick search I wasn’t able to 
>> find any; if anyone knows where those definitions live, please speak up.
>>
>> I think we may have two quite different approaches on the table for 
>> defining custody transfer outside of the BP specification.  I will be 
>> posting one of them in a few minutes and hope to post the other 
>> sometime tomorrow.
>>
>> Scott
>>
>>
>>
>> _______________________________________________
>> dtn mailing list
>> dtn@ietf.org
>> https://www.ietf.org/mailman/listinfo/dtn
>>
> 
> _______________________________________________
> dtn mailing list
> dtn@ietf.org
> https://www.ietf.org/mailman/listinfo/dtn

v2.23.0 | Report a Bug | By Email