Re: [Roll] [roll] #167 (admin-local-policy): Not match the requirement for administrative configuration of the admin-local scope

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Tue, 06 January 2015 08:24 UTC

Return-Path: <trac+roll@trac.tools.ietf.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A14AB1A9117 for <roll@ietfa.amsl.com>; Tue, 6 Jan 2015 00:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 FdnT-n_hEj_W for <roll@ietfa.amsl.com>; Tue, 6 Jan 2015 00:24:54 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 A92521A9115 for <roll@ietf.org>; Tue, 6 Jan 2015 00:24:54 -0800 (PST)
Received: from localhost ([::1]:50733 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1Y8PRW-0008PP-Ul; Tue, 06 Jan 2015 00:24:46 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "roll issue tracker" <trac+roll@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-roll-admin-local-policy@tools.ietf.org, consultancy@vanderstok.org
X-Trac-Project: roll
Date: Tue, 06 Jan 2015 08:24:46 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/roll/trac/ticket/167#comment:1
Message-ID: <082.f943a09147fd574dc576c8fa068c4b09@trac.tools.ietf.org>
References: <067.22bdea82d68842ae5ee21d726a5c1591@trac.tools.ietf.org>
X-Trac-Ticket-ID: 167
In-Reply-To: <067.22bdea82d68842ae5ee21d726a5c1591@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-roll-admin-local-policy@tools.ietf.org, consultancy@vanderstok.org, roll@ietf.org
X-SA-Exim-Mail-From: trac+roll@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: consultancy@vanderstok.org, robert.cragie@gridmerge.com
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/UxzsE5scpJlfIGBHUw2t3zM6Rp4
Cc: roll@ietf.org
Subject: Re: [Roll] [roll] #167 (admin-local-policy): Not match the requirement for administrative configuration of the admin-local scope
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: roll@ietf.org
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 08:24:57 -0000

#167: Not match the requirement for administrative configuration of the admin-
local scope


Comment (by consultancy@vanderstok.org):

 - The following text is added in alinea 2 of the introduction to explain
 the meaning of "administratively configured":

 'In this document "administratively configured" does not imply actions by
 a human beyond installing the here specified protocol. "Administratively
 configured" means an automatic derivation as described in this document.'

 In addition the relation between zone and MPL4 zone is clarified. The
 following text is added in section 5:
 'MPL4 messages remain bounded within a zone as defined in <xref
 target="RFC4007"/>. Consequently, MPL4 messages
 cannot be routed between interfaces belonging to different zones. When the
 concept of zone is unknown or disabled in a router, all interfaces belong
 to the same zone.
 For example, consider a router with 5 interfaces where interfaces A and
 B belong to zone 1 and interfaces C,D, and E belong to zone 2.
 MPL4 messages can be routed freely between interfaces A and B, and
 freely between C,D, and E. However, a MPL4 message MUST NOT be routed
 from Interface A to interface D.'

 The text for rules and the MPL4 zone is changed accordingly.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |       Owner:  draft-ietf-roll-admin-
  mariainesrobles@gmail.com          |  local-policy@tools.ietf.org
     Type:  defect                   |      Status:  new
 Priority:  major                    |   Milestone:
Component:  admin-local-policy       |     Version:
 Severity:  In WG Last Call          |  Resolution:
 Keywords:                           |
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/167#comment:1>
roll <http://tools.ietf.org/wg/roll/>