Re: [Banana] Use of Existing IETF Protocols

Margaret Wasserman <margaretw42@gmail.com> Wed, 20 September 2017 02:17 UTC

Return-Path: <margaretw42@gmail.com>
X-Original-To: banana@ietfa.amsl.com
Delivered-To: banana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF29132A05 for <banana@ietfa.amsl.com>; Tue, 19 Sep 2017 19:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cFqqPGDIa1P8 for <banana@ietfa.amsl.com>; Tue, 19 Sep 2017 19:17:51 -0700 (PDT)
Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF9AF1321DF for <banana@ietf.org>; Tue, 19 Sep 2017 19:17:51 -0700 (PDT)
Received: by mail-qk0-x243.google.com with SMTP id c69so892741qke.5 for <banana@ietf.org>; Tue, 19 Sep 2017 19:17:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+O2J1+2sGzJNM2FvWX7inRk72OGXGqpaUU4ILP5gpGY=; b=tppwhOe451pEYGLJjmVCjmeugy8SyR3zmPQTo47LyfBO/EXTMG07nTjgMLble/S6eq RRPxucwZl/KiZCRsvMl3B9jgcVR9mKKgO4TrQDj2sycLg6bcc/pi7CNFOBAEykuenJeD KlkGRbGY3xnwg/OzxnD0/wEB468zvOQYd3BVLXSctiewIp+uohCu1AF2lJNa6HrflLi2 5KVOgdcKrKizPLOgi29S2/2ql0otuDtJENgNPEXsOzv1oULTsi7MX0JUR3/1/soxHTjD lOXL5fu+WACAIw16CFziNGDcgw7/rDq3SO64JP6VwGf7Cc9VDeatOD8Sv8eag+XRDhjG qv9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+O2J1+2sGzJNM2FvWX7inRk72OGXGqpaUU4ILP5gpGY=; b=gIBulLc8MHgWLdtUc5w/lDlgIYHN+YZUGCGVPDZzVioY5A0VIcPPSAO1Jk5GTWcrn4 D+FcuDT1jF6RKsIHFytx9ZDvohc3NxhJCZo8X1RIscgk5EVKD1tisdn5br11y+p4AqmM RFc+i4anDiYePl3Iv19FYEtFb+yPTlNSh1TkwrHPfUo8gkB/o5XLjZa3JJ7afGee25m/ 19W3sksWcIBVSpaHogToVRMNDEZnIDHRHRmhX14SQa0DVCyGkR2ENvRRAcqnEsfIIpHv Kc1le9wx03+Ic4lJJx3nnAqPRauYmsX7eqmy/LbXhzaDgwbURQoTIcUJDJJTIb+kKCuv olow==
X-Gm-Message-State: AHPjjUiGnES46DkJ7+TpWxPZfNRerGCIjgfurupTO+BxNxRRN2hvmCfr THAQRJHdP47wxqAaQ3F/7Bk=
X-Google-Smtp-Source: AOwi7QBS0WI2H0JlUroNqU/m8EONDvPdkoA2NBwqhVZ6Pgh2Hh623hOMjsXmOym4Tn2AZh/4he3ekA==
X-Received: by 10.55.75.11 with SMTP id y11mr4878244qka.96.1505873870871; Tue, 19 Sep 2017 19:17:50 -0700 (PDT)
Received: from ?IPv6:2607:fb90:e87:14d:9516:eb6a:f538:89e4? ([2607:fb90:e87:14d:9516:eb6a:f538:89e4]) by smtp.gmail.com with ESMTPSA id f48sm581547qtc.49.2017.09.19.19.17.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Sep 2017 19:17:50 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Margaret Wasserman <margaretw42@gmail.com>
X-Mailer: iPhone Mail (14G60)
In-Reply-To: <3FE47F52-C651-4E88-B25D-153102462402@apple.com>
Date: Tue, 19 Sep 2017 22:17:49 -0400
Cc: Margaret Cullen <mrcullen42@gmail.com>, banana@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <73EFEFB8-6330-46B9-BE94-F85728B74DF2@gmail.com>
References: <DEC78849-1E63-470D-89F5-683CCA115C6F@gmail.com> <3FE47F52-C651-4E88-B25D-153102462402@apple.com>
To: Tommy Pauly <tpauly@apple.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/QpFc-NwpDFVyV6QhSQcObCMCtXc>
Subject: Re: [Banana] Use of Existing IETF Protocols
X-BeenThere: banana@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Bandwidth Aggregation for interNet Access: Discussion of bandwidth aggregation solutions based on IETF technologies." <banana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/banana>, <mailto:banana-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/banana/>
List-Post: <mailto:banana@ietf.org>
List-Help: <mailto:banana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/banana>, <mailto:banana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2017 02:17:53 -0000

At the BOF, when we first wrote extent about the use of existing IETF protocols, there was pushback that we should only use existing IETF protocols if they are the best choice for this application.  I was attempting to find a line between some people's insistence that we should use existing protocols if at all possible, and others' opinion that we should build the best solution, using existing protocols when that makes sense.  Personally, I think we should leave it up to the WG to make those trade-offs.

Margaret

Margaret

Sent from my iPhone

> On Sep 19, 2017, at 7:15 PM, Tommy Pauly <tpauly@apple.com> wrote:
> 
> This approach looks good to me. I think we could be still more explicit that the intention is to use existing protocols, if we'd like to err on that side.
> 
> "When applicable, the BANANA WG will use existing IETF protocols, or extensions to existing IETF protocols, as the basis for the work items listed above.  Whenever an existing protocol is used, the WG deliverable will be a document describing the use of that protocol for Bandwidth Aggregation and/or a set of options or extensions to an existing IETF protocol to make it useful for Bandwidth Aggregation."
> 
> This is just a more extreme version; your proposed text would work quite well as-is.
> 
> Thanks,
> Tommy
> 
>> On Sep 19, 2017, at 5:44 AM, Margaret Cullen <mrcullen42@gmail.com> wrote:
>> 
>> The current text in the charter can be interpreted to say that we intend to produce three new “BANANA protocols" for provisioning, signaling and encapsulation, even if there are existing IETF protocols that would work for that purpose.  I don’t think that was anyone’s intention.  For instance, I think we would all expect to produce a DHCP option or RA record, or something similar, for provisioning, rather than inventing a new provisioning protocol.  To make this more clear in the charter, I would propose the following change:
>> 
>> OLD:
>> 
>> The BANANA WG will consider existing IETF protocols, where applicable, as the basis for the work items listed above.
>> 
>> NEW:
>> 
>> The BANANA WG will consider existing IETF protocols, or extensions to existing IETF protocols, as the basis for the work items listed above.  If an existing protocol is used, the WG deliverable could be a document describing the use of that protocol for Bandwidth Aggregation and/or a set of options or extensions to an existing IETF protocol to make it useful for Bandwidth Aggregation.
>> 
>> Thoughts?
>> 
>> Sri, would this address your concern about the WG intending to produce three new protocols, even if suitable IETF protocols already exist?
>> 
>> Margaret
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Banana mailing list
>> Banana@ietf.org
>> https://www.ietf.org/mailman/listinfo/banana
>