[6lo] Alia Atlas' No Objection on draft-ietf-6lo-6lobac-06: (with COMMENT)
"Alia Atlas" <akatlas@gmail.com> Tue, 29 November 2016 23:32 UTC
Return-Path: <akatlas@gmail.com>
X-Original-To: 6lo@ietf.org
Delivered-To: 6lo@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3334B127A91; Tue, 29 Nov 2016 15:32:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alia Atlas <akatlas@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.38.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148046235620.11752.2233031007089619864.idtracker@ietfa.amsl.com>
Date: Tue, 29 Nov 2016 15:32:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/Rf0vzd2DOxPOddU-SznUm8COVEY>
Cc: 6lo-chairs@ietf.org, samitac.ietf@gmail.com, draft-ietf-6lo-6lobac@ietf.org, 6lo@ietf.org
Subject: [6lo] Alia Atlas' No Objection on draft-ietf-6lo-6lobac-06: (with COMMENT)
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2016 23:32:36 -0000
Alia Atlas has entered the following ballot position for draft-ietf-6lo-6lobac-06: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-6lo-6lobac/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- In Appendix B, given that there is code, it would be good to specifically mark it as such. As I recall, there are different copyright aspects to the code fragments in an RFC than to the text. I believe that https://www.ietf.org/iesg/statement/copyright.html provides pointers to the implications and encourages marking the code segments with <CODE_BEGINS> and <CODE_ENDS>.