
From nobody Mon Jan  4 09:53:57 2016
Return-Path: <brian@innovationslab.net>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0F01A9037; Mon,  4 Jan 2016 09:53:55 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Brian Haberman" <brian@innovationslab.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160104175355.14746.46722.idtracker@ietfa.amsl.com>
Date: Mon, 04 Jan 2016 09:53:55 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/YzYSZGOFN_VStQ2LNh-s9HbdxcU>
Cc: draft-ietf-pim-explicit-rpf-vector@ietf.org, mmcbride7@gmail.com, pim-chairs@ietf.org, pim@ietf.org
Subject: [pim] Brian Haberman's No Objection on draft-ietf-pim-explicit-rpf-vector-07: (with COMMENT)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2016 17:53:55 -0000

Brian Haberman has entered the following ballot position for
draft-ietf-pim-explicit-rpf-vector-07: 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-pim-explicit-rpf-vector/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I support the publication of this document, but I do have two points I
would like you to consider...

1. The use of 2119 keywords in the Introduction are inappropriate. They
can easily be changed to non-normative words and the meaning will not be
lost.

2. While this approach is viable, and needed, in a subset of deployment
scenarios, it is also inappropriate for other scenarios. I think some
guidance on when to use, or not use, this option would be useful as an
addendum to the motivation provided in section 3.



From nobody Tue Jan  5 12:04:01 2016
Return-Path: <akatlas@gmail.com>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 394D71B2D64; Tue,  5 Jan 2016 12:03:57 -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.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160105200357.20351.1511.idtracker@ietfa.amsl.com>
Date: Tue, 05 Jan 2016 12:03:57 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/KNU852Yr8lWpIq94o8AcSnORfas>
Cc: draft-ietf-pim-explicit-rpf-vector@ietf.org, mmcbride7@gmail.com, pim-chairs@ietf.org, pim@ietf.org
Subject: [pim] Alia Atlas' Yes on draft-ietf-pim-explicit-rpf-vector-07: (with COMMENT)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2016 20:03:57 -0000

Alia Atlas has entered the following ballot position for
draft-ietf-pim-explicit-rpf-vector-07: Yes

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-pim-explicit-rpf-vector/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree with Brian's comment about clear applicability and with Alissa's
comments on the "we" language.



From nobody Wed Jan  6 09:58:02 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F7C1A0035; Wed,  6 Jan 2016 09:58:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160106175801.20293.56363.idtracker@ietfa.amsl.com>
Date: Wed, 06 Jan 2016 09:58:01 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/dcw9koUmiU5qj-DK8W2ChGJrP88>
Cc: draft-ietf-pim-explicit-rpf-vector@ietf.org, mmcbride7@gmail.com, pim-chairs@ietf.org, pim@ietf.org
Subject: [pim] Stephen Farrell's No Objection on draft-ietf-pim-explicit-rpf-vector-07: (with COMMENT)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 17:58:01 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-pim-explicit-rpf-vector-07: 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-pim-explicit-rpf-vector/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------



Please take the comments below with a pinch of salt - I'm
not sure I understood what this was specifying so I may be
off base below. (Mind you, this caveat is also a comment
of sorts;-)

abstract: "RP" could be interpreted as reverse path or
rendezvous point, suggest expanding this in the abstract.

section 7: I don't understand: "A router processing
'Explicit' or 'Loose' RPF Vectors MUST verify that the
order in which RPF Vectors types appear in the PIM Join
Attribute list received from its downstream PIM neighbors
are equal." Seems like a bad plan to have a MUST in such a
hard to grok sentence. Or is that just me? (Actually, that
entire paragraph is hard to get.)

- section 12: couldn't this allow one node to try DoS
another by including it in the vector? Isn't that worth
noting?

- please also respond the secdir review [1] which raised a
couple more points.

   [1] https://www.ietf.org/mail-archive/web/secdir/current/msg06295.html



From nobody Wed Jan  6 11:09:08 2016
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF711A0103 for <pim@ietfa.amsl.com>; Wed,  6 Jan 2016 11:09:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=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 KyzWvscDjAwa for <pim@ietfa.amsl.com>; Wed,  6 Jan 2016 11:09:05 -0800 (PST)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 D30FD1A00F6 for <pim@ietf.org>; Wed,  6 Jan 2016 11:09:04 -0800 (PST)
Received: by mail-lf0-x232.google.com with SMTP id c192so142576538lfe.2 for <pim@ietf.org>; Wed, 06 Jan 2016 11:09:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=tbsf4PNLsGyFUPqwgfFermLTnITg8XfarsKiN4DuKf4=; b=ADeapyHoXRlkZicsFzqLPOauFd8iKyp5mpO6Y4MhDX+aq+FSdWckqpyfI3Qs0ecB7w I/wpT/W8csdvLxA+HX0FHvYSjIzusLmVb+GcOAluRRM9n9eiJ3rkbpw5aLV+nXIgQkOb EWB5xfnQYr5axJgEHocSqozsMvzv5HjLUdcwqhDPmMePHqoaPxnrifFLTltEX30PtTo1 GAhhzm27PbF/55W6Sa7lpwhqwDtlfADYtuKCTv142MP0h3SNv90SOdkGIHnF514PeSG6 7h0gtINMb7OewmQl02+VDt1ARQP54yhrMeNwEbbYbsQ/2Uk/qdGHJJCM70L6zQPvVq5j 1yXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=tbsf4PNLsGyFUPqwgfFermLTnITg8XfarsKiN4DuKf4=; b=AKZd3FSOAgZeOLKmE8slsfgYaBgomgif67g0ejbwBXQUsDpO0ZoaLHQoQPM7YF1/Lw hEKEHWKD6q6PzFTQVuOYacSjxV6QrJbiABuaUNwZ0ap2V9T7IR2lmUy9KaStmaigGEUq uwKGkGnLLP3vg8FZvHoK/PnHRfLVDygq4k4xBo5OeXZWI+/0GVjg0s/8/XawLYM9K9ta oOtpG9Mh4iUV0x89djbQJcLI6Fv6gc3vKwYnCi5J1rjmO05ooKuY0S5QXs4pkLXR/IOT P9bthpEZ0KCi6ri2qbgp8Fl15jV2r85WbEZzZQRAMrephz5xJj1d1oW/otyGeZb805F7 MJxA==
X-Gm-Message-State: ALoCoQn0m4dzg+JzTEakKzzscZofQPJHuIqT998eYy1OfTM0fOs4i/9fKACvF5j7Qj5+xt718G6mPfRFomXgIFU+/kFJhAWa2Q==
MIME-Version: 1.0
X-Received: by 10.25.21.208 with SMTP id 77mr25653612lfv.96.1452107342949; Wed, 06 Jan 2016 11:09:02 -0800 (PST)
Received: by 10.25.138.84 with HTTP; Wed, 6 Jan 2016 11:09:02 -0800 (PST)
Date: Wed, 6 Jan 2016 11:09:02 -0800
Message-ID: <CAHANBtJBNhCDLSMKXK86eEpkK3B1oB9o3Y=X34tP9QXvuUPWMw@mail.gmail.com>
From: Stig Venaas <stig@venaas.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/Gy6QUReVkAqYgH5_eTFxw6FgNVw>
Cc: "pim-chairs@ietf.org" <pim-chairs@ietf.org>
Subject: [pim] Call for adoption of draft-mcallister-pim-yang-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 19:09:06 -0000

Hi

We discussed https://tools.ietf.org/html/draft-mcallister-pim-yang-01
at the last pim meeting. We did an adoption call in the room and had 6
in favor and none against. We would like to confirm that we indeed
have consensus for adoption.

Please respond whether you support adoption or not, or with any other
comments you might have.

The adoption call ends in 2 weeks, on January 20th.

Note that this draft contains the pim yang models that the pim YANG
design team has been working on.

Stig


From nobody Thu Jan  7 07:57:06 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B9C41A9035; Thu,  7 Jan 2016 07:57:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160107155703.5785.44525.idtracker@ietfa.amsl.com>
Date: Thu, 07 Jan 2016 07:57:03 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/MAw3J9axmKaMOLz0uuDGK4EjgFE>
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-hierarchicaljoinattr-05.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2016 15:57:03 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Protocols for IP Multicast Working Group of the IETF.

        Title           : Hierarchical Join/Prune Attributes
        Authors         : Stig Venaas
                          Jesus Arango
                          Isidor Kouvelas
	Filename        : draft-ietf-pim-hierarchicaljoinattr-05.txt
	Pages           : 7
	Date            : 2016-01-07

Abstract:
   This document defines a hierachical method of encoding Join
   attributes, providing a more efficient encoding when the same
   attribute values need to be specified for multiple sources in a PIM
   Join/Prune message.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-hierarchicaljoinattr/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-pim-hierarchicaljoinattr-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pim-hierarchicaljoinattr-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jan 11 09:05:47 2016
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 675981A8AC9 for <pim@ietfa.amsl.com>; Mon, 11 Jan 2016 09:05:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=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 c7oQX3Te9K9N for <pim@ietfa.amsl.com>; Mon, 11 Jan 2016 09:05:45 -0800 (PST)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 14DD81A8AB5 for <pim@ietf.org>; Mon, 11 Jan 2016 09:05:45 -0800 (PST)
Received: by mail-lf0-x234.google.com with SMTP id m198so70344498lfm.0 for <pim@ietf.org>; Mon, 11 Jan 2016 09:05:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7FXSuOASbn2xVAEKuk5/Zj/NEZXtq7PmHpTRblAhbxU=; b=1+IAStVCBXFolQvcsM1JqesqDZ4g/yB0UFke3kTdPkzXpC59gNC0rHm4Nxa2aS2Gs0 //s2ytltMbYS3DLdH6k6bkqLwFAN4DVvGRDptD1kcxlYLbVtJQMFiqL3onNGMfWW0GOD 2tElWkhUZa/TWHriqeSDsNIqLiJt13QjdHbmEGlFgtUKZw4CtEo+gQl44UtEBbmv8mwZ UR+J3L78SHUKLu3ySQD8mNBcAelO1VFp2HHQapGacAy9bRUdYW4KVV0xsHA5HsQv+G7i 7oWGp+hIBzPoEiNYeEzsXAzAwufqoTMziUlub7Gft1QqV+Eg/HOegG23tZd1N/p25abf 4CJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7FXSuOASbn2xVAEKuk5/Zj/NEZXtq7PmHpTRblAhbxU=; b=T4dTWJnQaPzGAaq/alIk+4fQfiCeLLuDcPQIGjNGY48OVS6xXIAoT2pnvAF+fw1S1v ih9nP51Ts+lwajJthZlImV7qH0lycKJWIeyiZnTFJS0tFtqKdk1KMyWPsC2gNSUDIdT8 0rpksopjiiO6nE0dK/XmL/PEfgYE1R50YH8d1+4wPSL8S6w/SoN1idXYGlIohjEBjY8f Co2Vu2cL5mbwY+J4Gl4avQucS5qFLzu62SYpr5Lh2DoUNGlGN+Pl2+aFw++vsHgyi5Wn CnNdn5CDJnIyigb9BrUHDZU3/Fqr47h9Bbfr4ZWlyGADRIrlX8gcItYZCB7I8GpL2L0c jTRQ==
X-Gm-Message-State: ALoCoQkRMu4hswQIfN4ST/09jsyV+eSq+NYMoCm+uwAHYTqH4SEA7x/AyB9Xk4IhYqA6k8isra/1zlQE54+8Db4+GKTg95vYZw==
MIME-Version: 1.0
X-Received: by 10.25.148.141 with SMTP id w135mr20991124lfd.137.1452531943204;  Mon, 11 Jan 2016 09:05:43 -0800 (PST)
Received: by 10.25.26.211 with HTTP; Mon, 11 Jan 2016 09:05:43 -0800 (PST)
In-Reply-To: <CAHANBtJBNhCDLSMKXK86eEpkK3B1oB9o3Y=X34tP9QXvuUPWMw@mail.gmail.com>
References: <CAHANBtJBNhCDLSMKXK86eEpkK3B1oB9o3Y=X34tP9QXvuUPWMw@mail.gmail.com>
Date: Mon, 11 Jan 2016 09:05:43 -0800
Message-ID: <CAHANBt+g=XpVmS76prm1B8R=TLjOVefURadG2mG-x+eO+Pwdtw@mail.gmail.com>
From: Stig Venaas <stig@venaas.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/b8RdpETACy11UI1u3UYyAvgOOlU>
Cc: "pim-chairs@ietf.org" <pim-chairs@ietf.org>
Subject: Re: [pim] Call for adoption of draft-mcallister-pim-yang-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2016 17:05:46 -0000

I wrote 01 in the adoption call, but please look at 02 that was just submitted.
https://tools.ietf.org/html/draft-mcallister-pim-yang-02

Stig


From nobody Tue Jan 19 11:20:44 2016
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 569E21B34BD for <pim@ietfa.amsl.com>; Tue, 19 Jan 2016 11:20:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.122
X-Spam-Level: 
X-Spam-Status: No, score=0.122 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=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 Jm7C2Iwrn9mq for <pim@ietfa.amsl.com>; Tue, 19 Jan 2016 11:20:42 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (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 AEA6D1B34AE for <pim@ietf.org>; Tue, 19 Jan 2016 11:20:41 -0800 (PST)
Received: by mail-lb0-x233.google.com with SMTP id bc4so368410680lbc.2 for <pim@ietf.org>; Tue, 19 Jan 2016 11:20:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kudw9HeJFGaayRmwH8FQ4gSPDH/K8/nIIs8dRG1k+iU=; b=fCKlUEDSPEALQRfq7TOKTTeb9CsRiHkjIhBa2qwJaT6a+0RmG+wOB60h0vJGKrdE7j RX4RkufMb44fRRnAJLrqie5sX2hZg9Pv0zFrWaSC5mTXoPwmR1M9vnlTkOzHjR+TjCdb /tD9euRNAYJCAT+O0BwblCQANmuv2lL2moOljpbacg8i84Hyblg1b6ozxB0hHgdT+z5O 0PUcQly845rgq/5FjUJJ/wZ/HEhZLMM2c0eQvjgwp4Yf2JQMOV5EXbg5DkvLf2bYEAxi IdNQaUP49SAIJeIXFRDl/s+ukUbk41bBuK1emKZVijbpED4I5MdF2m4TATN/201EMM5J tZNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Kudw9HeJFGaayRmwH8FQ4gSPDH/K8/nIIs8dRG1k+iU=; b=ihR3EgRjqWUjf4Mq2DcmkkcDKJxPRq+f6WscxcHLNrokBHLJQqoOlgtrVdZtHqloFM h67cmpcUDQARR0ofc+2C704LF6FbS/naST71RRZQO23DpM9K8QjZb20rfqQhGJbTXRU3 0KF8yoMSGzqWQy2PWRZ+DC8mLTCriDcNMGUFMnXLbsBHaV/MaDe8WgARzDkG3lvYHeeX IwCE+AA7LarK5WkLMPIqnry+zey1zM/33paRmRuu3YH2XpNvql7Go1lor/RhPzp39qpi 61m6zIdO+saD5Yz+/0UQk+nSNslFpUgpQWS2pbbHWg+zfytDnLfCkGFJ3kZUsY8liq2V l2sQ==
X-Gm-Message-State: AG10YOSngDY+5SmtBLs5R5RNxqcdKx8Oy7PKLur9Fa/y37T7pBQwU7fnG6XDjO3YBnpp6FMg0TmZ2I+avTUYHw==
MIME-Version: 1.0
X-Received: by 10.112.168.227 with SMTP id zz3mr4849033lbb.10.1453231239811; Tue, 19 Jan 2016 11:20:39 -0800 (PST)
Received: by 10.25.26.211 with HTTP; Tue, 19 Jan 2016 11:20:39 -0800 (PST)
In-Reply-To: <CAHANBtJBNhCDLSMKXK86eEpkK3B1oB9o3Y=X34tP9QXvuUPWMw@mail.gmail.com>
References: <CAHANBtJBNhCDLSMKXK86eEpkK3B1oB9o3Y=X34tP9QXvuUPWMw@mail.gmail.com>
Date: Tue, 19 Jan 2016 11:20:39 -0800
Message-ID: <CAHANBtKqp+8+4armgQGK=UMqMjz5QhM=vih0HtquHpJGWbOw6A@mail.gmail.com>
From: Stig Venaas <stig@venaas.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/_nxCZK5f2zLvt5_r4so6ZgHOFhM>
Cc: "pim-chairs@ietf.org" <pim-chairs@ietf.org>
Subject: Re: [pim] Call for adoption of draft-mcallister-pim-yang-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2016 19:20:43 -0000

This adoption call ends tomorrow and we haven't got a single response.
Does that mean that no one in the WG cares about YANG models? It is
difficult for us as chairs to know what the WG wants when we don't get
any responses.

Please have a look at the draft and let us know by end of tomorrow
whether you would like this draft to be adopted or not.

Stig


On Wed, Jan 6, 2016 at 11:09 AM, Stig Venaas <stig@venaas.com> wrote:
> Hi
>
> We discussed https://tools.ietf.org/html/draft-mcallister-pim-yang-01
> at the last pim meeting. We did an adoption call in the room and had 6
> in favor and none against. We would like to confirm that we indeed
> have consensus for adoption.
>
> Please respond whether you support adoption or not, or with any other
> comments you might have.
>
> The adoption call ends in 2 weeks, on January 20th.
>
> Note that this draft contains the pim yang models that the pim YANG
> design team has been working on.
>
> Stig


From nobody Tue Jan 19 20:51:16 2016
Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4D21A1BD4; Tue, 19 Jan 2016 20:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.051
X-Spam-Level: 
X-Spam-Status: No, score=-99.051 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 tl4lgHgrua59; Tue, 19 Jan 2016 20:51:13 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 585611A1B89; Tue, 19 Jan 2016 20:51:12 -0800 (PST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 6BA821CF3F9D1; Wed, 20 Jan 2016 12:51:08 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id u0K4p1xt023711; Wed, 20 Jan 2016 12:51:01 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
In-Reply-To: <CAHANBtKqp+8+4armgQGK=UMqMjz5QhM=vih0HtquHpJGWbOw6A@mail.gmail.com>
To: Stig Venaas <stig@venaas.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFAF4B32BE.6822CB94-ON48257F40.001A03B7-48257F40.001AA55C@zte.com.cn>
From: zhang.zheng@zte.com.cn
Date: Wed, 20 Jan 2016 12:51:06 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2016-01-20 12:50:42, Serialize complete at 2016-01-20 12:50:42
Content-Type: multipart/alternative; boundary="=_alternative 001AA55848257F40_="
X-MAIL: mse01.zte.com.cn u0K4p1xt023711
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/OOxml3QedjogOoHQsvC9OqVnBko>
Cc: "pim-chairs@ietf.org" <pim-chairs@ietf.org>, pim <pim-bounces@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Call for adoption of draft-mcallister-pim-yang-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2016 04:51:15 -0000

This is a multipart message in MIME format.
--=_alternative 001AA55848257F40_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

U3VwcG9ydC4NCg0KDQoNCg0KU3RpZyBWZW5hYXMgPHN0aWdAdmVuYWFzLmNvbT4gDQq3orz+yMs6
ICAicGltIiA8cGltLWJvdW5jZXNAaWV0Zi5vcmc+DQoyMDE2LzAxLzIwIDAzOjIwDQoNCsrVvP7I
yw0KInBpbUBpZXRmLm9yZyIgPHBpbUBpZXRmLm9yZz4NCrOty80NCiJwaW0tY2hhaXJzQGlldGYu
b3JnIiA8cGltLWNoYWlyc0BpZXRmLm9yZz4NCtb3zOINClJlOiBbcGltXSBDYWxsIGZvciBhZG9w
dGlvbiBvZiBkcmFmdC1tY2FsbGlzdGVyLXBpbS15YW5nLTAxDQoNCg0KDQoNCg0KDQpUaGlzIGFk
b3B0aW9uIGNhbGwgZW5kcyB0b21vcnJvdyBhbmQgd2UgaGF2ZW4ndCBnb3QgYSBzaW5nbGUgcmVz
cG9uc2UuDQpEb2VzIHRoYXQgbWVhbiB0aGF0IG5vIG9uZSBpbiB0aGUgV0cgY2FyZXMgYWJvdXQg
WUFORyBtb2RlbHM/IEl0IGlzDQpkaWZmaWN1bHQgZm9yIHVzIGFzIGNoYWlycyB0byBrbm93IHdo
YXQgdGhlIFdHIHdhbnRzIHdoZW4gd2UgZG9uJ3QgZ2V0DQphbnkgcmVzcG9uc2VzLg0KDQpQbGVh
c2UgaGF2ZSBhIGxvb2sgYXQgdGhlIGRyYWZ0IGFuZCBsZXQgdXMga25vdyBieSBlbmQgb2YgdG9t
b3Jyb3cNCndoZXRoZXIgeW91IHdvdWxkIGxpa2UgdGhpcyBkcmFmdCB0byBiZSBhZG9wdGVkIG9y
IG5vdC4NCg0KU3RpZw0KDQoNCk9uIFdlZCwgSmFuIDYsIDIwMTYgYXQgMTE6MDkgQU0sIFN0aWcg
VmVuYWFzIDxzdGlnQHZlbmFhcy5jb20+IHdyb3RlOg0KPiBIaQ0KPg0KPiBXZSBkaXNjdXNzZWQg
aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LW1jYWxsaXN0ZXItcGltLXlhbmctMDEN
Cj4gYXQgdGhlIGxhc3QgcGltIG1lZXRpbmcuIFdlIGRpZCBhbiBhZG9wdGlvbiBjYWxsIGluIHRo
ZSByb29tIGFuZCBoYWQgNg0KPiBpbiBmYXZvciBhbmQgbm9uZSBhZ2FpbnN0LiBXZSB3b3VsZCBs
aWtlIHRvIGNvbmZpcm0gdGhhdCB3ZSBpbmRlZWQNCj4gaGF2ZSBjb25zZW5zdXMgZm9yIGFkb3B0
aW9uLg0KPg0KPiBQbGVhc2UgcmVzcG9uZCB3aGV0aGVyIHlvdSBzdXBwb3J0IGFkb3B0aW9uIG9y
IG5vdCwgb3Igd2l0aCBhbnkgb3RoZXINCj4gY29tbWVudHMgeW91IG1pZ2h0IGhhdmUuDQo+DQo+
IFRoZSBhZG9wdGlvbiBjYWxsIGVuZHMgaW4gMiB3ZWVrcywgb24gSmFudWFyeSAyMHRoLg0KPg0K
PiBOb3RlIHRoYXQgdGhpcyBkcmFmdCBjb250YWlucyB0aGUgcGltIHlhbmcgbW9kZWxzIHRoYXQg
dGhlIHBpbSBZQU5HDQo+IGRlc2lnbiB0ZWFtIGhhcyBiZWVuIHdvcmtpbmcgb24uDQo+DQo+IFN0
aWcNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnBp
bSBtYWlsaW5nIGxpc3QNCnBpbUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9waW0NCg0KDQo=
--=_alternative 001AA55848257F40_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlN1cHBvcnQuPC9mb250Pg0KPGJy
Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4N
Cjx0ZCB3aWR0aD0zNiU+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjxiPlN0aWcgVmVu
YWFzICZsdDtzdGlnQHZlbmFhcy5jb20mZ3Q7PC9iPg0KPC9mb250Pg0KPGJyPjxmb250IHNpemU9
MSBmYWNlPSJzYW5zLXNlcmlmIj63orz+yMs6ICZuYnNwOyZxdW90O3BpbSZxdW90OyAmbHQ7cGlt
LWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7PC9mb250Pg0KPHA+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt
c2VyaWYiPjIwMTYvMDEvMjAgMDM6MjA8L2ZvbnQ+DQo8dGQgd2lkdGg9NjMlPg0KPHRhYmxlIHdp
ZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQg
c2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPsrVvP7IyzwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBz
aXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+JnF1b3Q7cGltQGlldGYub3JnJnF1b3Q7ICZsdDtwaW1A
aWV0Zi5vcmcmZ3Q7PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJp
Z2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj6zrcvNPC9mb250PjwvZGl2Pg0KPHRk
Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4mcXVvdDtwaW0tY2hhaXJzQGlldGYub3Jn
JnF1b3Q7ICZsdDtwaW0tY2hhaXJzQGlldGYub3JnJmd0OzwvZm9udD4NCjx0ciB2YWxpZ249dG9w
Pg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+
1vfM4jwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+UmU6
IFtwaW1dIENhbGwgZm9yIGFkb3B0aW9uIG9mIGRyYWZ0LW1jYWxsaXN0ZXItcGltLXlhbmctMDE8
L2ZvbnQ+PC90YWJsZT4NCjxicj4NCjx0YWJsZT4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPHRk
PjwvdGFibGU+DQo8YnI+PC90YWJsZT4NCjxicj4NCjxicj4NCjxicj48Zm9udCBzaXplPTI+PHR0
PlRoaXMgYWRvcHRpb24gY2FsbCBlbmRzIHRvbW9ycm93IGFuZCB3ZSBoYXZlbid0IGdvdA0KYSBz
aW5nbGUgcmVzcG9uc2UuPGJyPg0KRG9lcyB0aGF0IG1lYW4gdGhhdCBubyBvbmUgaW4gdGhlIFdH
IGNhcmVzIGFib3V0IFlBTkcgbW9kZWxzPyBJdCBpczxicj4NCmRpZmZpY3VsdCBmb3IgdXMgYXMg
Y2hhaXJzIHRvIGtub3cgd2hhdCB0aGUgV0cgd2FudHMgd2hlbiB3ZSBkb24ndCBnZXQ8YnI+DQph
bnkgcmVzcG9uc2VzLjxicj4NCjxicj4NClBsZWFzZSBoYXZlIGEgbG9vayBhdCB0aGUgZHJhZnQg
YW5kIGxldCB1cyBrbm93IGJ5IGVuZCBvZiB0b21vcnJvdzxicj4NCndoZXRoZXIgeW91IHdvdWxk
IGxpa2UgdGhpcyBkcmFmdCB0byBiZSBhZG9wdGVkIG9yIG5vdC48YnI+DQo8YnI+DQpTdGlnPGJy
Pg0KPGJyPg0KPGJyPg0KT24gV2VkLCBKYW4gNiwgMjAxNiBhdCAxMTowOSBBTSwgU3RpZyBWZW5h
YXMgJmx0O3N0aWdAdmVuYWFzLmNvbSZndDsgd3JvdGU6PGJyPg0KJmd0OyBIaTxicj4NCiZndDs8
YnI+DQomZ3Q7IFdlIGRpc2N1c3NlZCBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
bWNhbGxpc3Rlci1waW0teWFuZy0wMTxicj4NCiZndDsgYXQgdGhlIGxhc3QgcGltIG1lZXRpbmcu
IFdlIGRpZCBhbiBhZG9wdGlvbiBjYWxsIGluIHRoZSByb29tIGFuZCBoYWQNCjY8YnI+DQomZ3Q7
IGluIGZhdm9yIGFuZCBub25lIGFnYWluc3QuIFdlIHdvdWxkIGxpa2UgdG8gY29uZmlybSB0aGF0
IHdlIGluZGVlZDxicj4NCiZndDsgaGF2ZSBjb25zZW5zdXMgZm9yIGFkb3B0aW9uLjxicj4NCiZn
dDs8YnI+DQomZ3Q7IFBsZWFzZSByZXNwb25kIHdoZXRoZXIgeW91IHN1cHBvcnQgYWRvcHRpb24g
b3Igbm90LCBvciB3aXRoIGFueSBvdGhlcjxicj4NCiZndDsgY29tbWVudHMgeW91IG1pZ2h0IGhh
dmUuPGJyPg0KJmd0Ozxicj4NCiZndDsgVGhlIGFkb3B0aW9uIGNhbGwgZW5kcyBpbiAyIHdlZWtz
LCBvbiBKYW51YXJ5IDIwdGguPGJyPg0KJmd0Ozxicj4NCiZndDsgTm90ZSB0aGF0IHRoaXMgZHJh
ZnQgY29udGFpbnMgdGhlIHBpbSB5YW5nIG1vZGVscyB0aGF0IHRoZSBwaW0gWUFORzxicj4NCiZn
dDsgZGVzaWduIHRlYW0gaGFzIGJlZW4gd29ya2luZyBvbi48YnI+DQomZ3Q7PGJyPg0KJmd0OyBT
dGlnPGJyPg0KPGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX188YnI+DQpwaW0gbWFpbGluZyBsaXN0PGJyPg0KcGltQGlldGYub3JnPGJyPg0KaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW08YnI+DQo8L3R0PjwvZm9udD4NCjxi
cj4NCg==
--=_alternative 001AA55848257F40_=--


From nobody Wed Jan 20 13:18:34 2016
Return-Path: <sami.biz.email@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 531EA1ACEEB for <pim@ietfa.amsl.com>; Wed, 20 Jan 2016 13:18:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 4rUzfUefsw16 for <pim@ietfa.amsl.com>; Wed, 20 Jan 2016 13:18:32 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 0B5CB1ACED8 for <pim@ietf.org>; Wed, 20 Jan 2016 13:18:32 -0800 (PST)
Received: by mail-wm0-x235.google.com with SMTP id 123so149624197wmz.0 for <pim@ietf.org>; Wed, 20 Jan 2016 13:18:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=NQugOTudpkEer2B1NLxXeiWO30nZ9AlR4BguV1ba7Jo=; b=s0RBloXkHVrCaldBhj2FFxWjB++OunnyNCEhDK5XfXad166iifqNd4uNMl8KbjdYv8 /J8yYwQ7ND126i5KQjBPf9MrAD4QZ5xHthZu9VRSVssFpYoI/MDnLcKelsiHvRxImCVw S1XU4Ev2J282OFnEbCAgsibjpSE6W5jC1luKCZuDwkgDxKksEfbdb/4vXlY6ZTDo2R99 Khq5IoJiaCbg4dvvTcIdgDCv8u8gIAW9MDVuV2dqeO2HvnfeedF9BrLd4VSsCF5t1U2d EesQHEVLJ9LbFeq8aSk6yt0nR8ORsTxU4f9T/RqI+QQ5o00L/XReCFC+84/sGTTzcbZw w5jA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=NQugOTudpkEer2B1NLxXeiWO30nZ9AlR4BguV1ba7Jo=; b=TPNeSQh5qQByft/ef0xzjrsneIRydXbO6MIAQzuinf0xB8JawKmml/7aw6NLJas0g2 ASUo7Ut4opL3ZZpSyzpVdoazX3kwc6RKsVePplbehAfuS05RZJxJ8jLZetRv6vmFQL7q xL7mffYQaFxf/K4e+C1WucNGN/bOaD3eAjS/+fVlfi3nYyJSqiF8WexacxbhvSDXW1Bb ch8NAjEjcuWjCltxN3422AeZvK2cVoGXkx53oVP5S+hs+tm3jKGwAQ+5/MH6ry7Otmtb U2ahI+yva9yAmDEtUYQe6M3aehQ/eaboWvNn2Ef74CvqfebJRX4RbzS71YtrKj7TQuOx OHow==
X-Gm-Message-State: ALoCoQlOvRQY47BIk0ylmie2yJW6DnXJTEWJwws90KdOEBhP0NsqXtgxlSafOdBUWLChijIrm0sPWXM/bZW4bFp8373DsJ2dUg==
X-Received: by 10.194.243.6 with SMTP id wu6mr37269104wjc.14.1453324710584; Wed, 20 Jan 2016 13:18:30 -0800 (PST)
Received: from [192.168.1.2] ([5.238.215.36]) by smtp.gmail.com with ESMTPSA id u4sm34799002wjz.4.2016.01.20.13.18.29 for <pim@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Jan 2016 13:18:30 -0800 (PST)
To: pim@ietf.org
References: <mailman.119.1453320022.19183.pim@ietf.org>
From: "S.Sami" <sami.biz.email@gmail.com>
Message-ID: <569FF9A9.7050900@gmail.com>
Date: Thu, 21 Jan 2016 00:48:33 +0330
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <mailman.119.1453320022.19183.pim@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/lNwKv5kTDfiIkQTsxLwCQYz-lZk>
Subject: Re: [pim] Call for adoption of draft-mcallister-pim-yang-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2016 21:18:33 -0000

Hello.
I do support its adoption.

On 20/01/2016 11:30 ب.ظ, pim-request@ietf.org wrote:
> Re: Call for adoption of draft-mcallister-pim-yang-01


From nobody Wed Jan 20 17:50:12 2016
Return-Path: <hu.fangwei@zte.com.cn>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52D81B2CC5 for <pim@ietfa.amsl.com>; Wed, 20 Jan 2016 17:50:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level: 
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 xOWOCw7VKpNL for <pim@ietfa.amsl.com>; Wed, 20 Jan 2016 17:50:09 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 9902B1ACDF1 for <pim@ietf.org>; Wed, 20 Jan 2016 17:50:09 -0800 (PST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 8EE8B365280E6 for <pim@ietf.org>; Thu, 21 Jan 2016 09:49:58 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id u0L1nRSc036643 for <pim@ietf.org>; Thu, 21 Jan 2016 09:49:27 +0800 (GMT-8) (envelope-from hu.fangwei@zte.com.cn)
In-Reply-To: <569FF9A9.7050900@gmail.com>
To: pim@ietf.org
MIME-Version: 1.0
X-KeepSent: EADD17FE:A00BC03E-48257F41:0009CF1D; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFEADD17FE.A00BC03E-ON48257F41.0009CF1D-48257F41.000A06DF@zte.com.cn>
From: hu.fangwei@zte.com.cn
Date: Thu, 21 Jan 2016 09:47:41 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2016-01-21 09:49:27, Serialize complete at 2016-01-21 09:49:27
Content-Type: multipart/alternative; boundary="=_alternative 000A06DE48257F41_="
X-MAIL: mse01.zte.com.cn u0L1nRSc036643
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/EmPpnq5iA_ny1HehPlWk_SjzXBI>
Subject: Re: [pim] Call for adoption of draft-mcallister-pim-yang-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2016 01:50:11 -0000

This is a multipart message in MIME format.
--=_alternative 000A06DE48257F41_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

U3VwcG9ydC4NCg0KDQoNCg0KIlMuU2FtaSIgPHNhbWkuYml6LmVtYWlsQGdtYWlsLmNvbT4gDQrl
j5Hku7bkuro6ICAicGltIiA8cGltLWJvdW5jZXNAaWV0Zi5vcmc+DQoyMDE2LTAxLTIxIDA1OjE4
DQoNCuaUtuS7tuS6ug0KDQrmioTpgIENCg0K5Li76aKYDQpSZTogW3BpbV0gQ2FsbCBmb3IgYWRv
cHRpb24gb2YgZHJhZnQtbWNhbGxpc3Rlci1waW0teWFuZy0wMQ0KDQoNCg0KDQoNCg0KSGVsbG8u
DQpJIGRvIHN1cHBvcnQgaXRzIGFkb3B0aW9uLg0KDQpPbiAyMC8wMS8yMDE2IDExOjMwINioLti4
LCBwaW0tcmVxdWVzdEBpZXRmLm9yZyB3cm90ZToNCj4gUmU6IENhbGwgZm9yIGFkb3B0aW9uIG9m
IGRyYWZ0LW1jYWxsaXN0ZXItcGltLXlhbmctMDENCg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCnBpbSBtYWlsaW5nIGxpc3QNCnBpbUBpZXRmLm9yZw0K
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW0NCg0KDQo=
--=_alternative 000A06DE48257F41_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlN1cHBvcnQuPGJyPg0KPC9mb250
Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4N
Cjx0ZCB3aWR0aD0zNiU+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjxiPiZxdW90O1Mu
U2FtaSZxdW90OyAmbHQ7c2FtaS5iaXouZW1haWxAZ21haWwuY29tJmd0OzwvYj4NCjwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+5Y+R5Lu25Lq6OiAmbmJzcDsmcXVv
dDtwaW0mcXVvdDsgJmx0O3BpbS1ib3VuY2VzQGlldGYub3JnJmd0OzwvZm9udD4NCjxwPjxmb250
IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4yMDE2LTAxLTIxIDA1OjE4PC9mb250Pg0KPHRkIHdp
ZHRoPTYzJT4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2
IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7mlLbku7bkuro8L2Zv
bnQ+PC9kaXY+DQo8dGQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+
PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPuaKhOmAgTwvZm9udD48L2Rpdj4NCjx0ZD4N
Cjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFj
ZT0ic2Fucy1zZXJpZiI+5Li76aKYPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNl
PSJzYW5zLXNlcmlmIj5SZTogW3BpbV0gQ2FsbCBmb3IgYWRvcHRpb24gb2YgZHJhZnQtbWNhbGxp
c3Rlci1waW0teWFuZy0wMTwvZm9udD48L3RhYmxlPg0KPGJyPg0KPHRhYmxlPg0KPHRyIHZhbGln
bj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxlPg0KPGJyPg0KPGJyPg0KPGJy
Pjx0dD48Zm9udCBzaXplPTI+SGVsbG8uPGJyPg0KSSBkbyBzdXBwb3J0IGl0cyBhZG9wdGlvbi48
YnI+DQo8YnI+DQpPbiAyMC8wMS8yMDE2IDExOjMwINioLti4LCBwaW0tcmVxdWVzdEBpZXRmLm9y
ZyB3cm90ZTo8YnI+DQomZ3Q7IFJlOiBDYWxsIGZvciBhZG9wdGlvbiBvZiBkcmFmdC1tY2FsbGlz
dGVyLXBpbS15YW5nLTAxPGJyPg0KPGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX188YnI+DQpwaW0gbWFpbGluZyBsaXN0PGJyPg0KcGltQGlldGYub3Jn
PGJyPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW08YnI+DQo8L2Zv
bnQ+PC90dD4NCjxicj4NCg==
--=_alternative 000A06DE48257F41_=--


From nobody Wed Jan 20 18:18:29 2016
Return-Path: <william.atwood@concordia.ca>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD1A1B2D27 for <pim@ietfa.amsl.com>; Wed, 20 Jan 2016 18:18:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.536
X-Spam-Level: 
X-Spam-Status: No, score=-3.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] 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 ldPfmCNg6-zl for <pim@ietfa.amsl.com>; Wed, 20 Jan 2016 18:18:25 -0800 (PST)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.92]) by ietfa.amsl.com (Postfix) with ESMTP id B7ED11B2D10 for <pim@ietf.org>; Wed, 20 Jan 2016 18:18:25 -0800 (PST)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id u0L2ILso028226 for <pim@ietf.org>; Wed, 20 Jan 2016 21:18:21 -0500
To: pim@ietf.org
References: <CAHANBtJBNhCDLSMKXK86eEpkK3B1oB9o3Y=X34tP9QXvuUPWMw@mail.gmail.com> <CAHANBtKqp+8+4armgQGK=UMqMjz5QhM=vih0HtquHpJGWbOw6A@mail.gmail.com>
From: William Atwood <william.atwood@concordia.ca>
Organization: Concordia University, Montreal
Message-ID: <56A03FEE.6070008@concordia.ca>
Date: Wed, 20 Jan 2016 21:18:22 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAHANBtKqp+8+4armgQGK=UMqMjz5QhM=vih0HtquHpJGWbOw6A@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2016-01-20 21:18:22 EST
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/E2zUqxyGny7vJdeXLHhyNL-B2Lc>
Subject: Re: [pim] Call for adoption of draft-mcallister-pim-yang-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2016 02:18:28 -0000

I support the adoption of this draft as a working group document.

  Bill

On 19/01/2016 2:20 PM, Stig Venaas wrote:
> This adoption call ends tomorrow and we haven't got a single response.
> Does that mean that no one in the WG cares about YANG models? It is
> difficult for us as chairs to know what the WG wants when we don't get
> any responses.
> 
> Please have a look at the draft and let us know by end of tomorrow
> whether you would like this draft to be adopted or not.
> 
> Stig
> 
> 
> On Wed, Jan 6, 2016 at 11:09 AM, Stig Venaas <stig@venaas.com> wrote:
>> Hi
>>
>> We discussed https://tools.ietf.org/html/draft-mcallister-pim-yang-01
>> at the last pim meeting. We did an adoption call in the room and had 6
>> in favor and none against. We would like to confirm that we indeed
>> have consensus for adoption.
>>
>> Please respond whether you support adoption or not, or with any other
>> comments you might have.
>>
>> The adoption call ends in 2 weeks, on January 20th.
>>
>> Note that this draft contains the pim yang models that the pim YANG
>> design team has been working on.
>>
>> Stig
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
> 

-- 

Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email:william.atwood@concordia.ca
1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8


From nobody Thu Jan 21 10:00:56 2016
Return-Path: <aretana@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F37B1A8905; Thu, 21 Jan 2016 10:00:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 b_QQQ7S13U_O; Thu, 21 Jan 2016 10:00:52 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC5CB1A890C; Thu, 21 Jan 2016 10:00:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20304; q=dns/txt; s=iport; t=1453399251; x=1454608851; h=from:to:cc:subject:date:message-id:mime-version; bh=VUdTdqDdMSMa/tO2O/Pi+1KEete668FB9sOGO2UpcDY=; b=FBZAUeyisT9W8gYimYqiECOZJR/J8GzcHNnvhTk3K0Ku1b7T6eLRACS4 nGoYKL6wwc/uxE5bdMIKiknYzALPsMlFRBD+lFx0qAMMqDZzwh9bKSsPU op305OptKcgCZePHkx0gDpi0Lvgexq4zgiGgHRm8No3DkA/8KTozs8CYg E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAgB2HKFW/4MNJK1egm5MUnOIUbIfA?= =?us-ascii?q?Q2BYiaFaYFAOBQBAQEBAQEBfwuENwR5EgGBACcEDoggDrsngl8BAQEBAQEEAQE?= =?us-ascii?q?BAQEBAQEUBIY4AY17BY0phUmEAwGNVoFehESIV4VriFABHgEBQoNmhxF8AQEB?=
X-IronPort-AV: E=Sophos; i="5.22,326,1449532800"; d="scan'208,217"; a="63918018"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Jan 2016 18:00:24 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u0LI0OHm029717 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 21 Jan 2016 18:00:24 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 21 Jan 2016 12:00:23 -0600
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1104.009; Thu, 21 Jan 2016 12:00:23 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "draft-ietf-pim-hierarchicaljoinattr@ietf.org" <draft-ietf-pim-hierarchicaljoinattr@ietf.org>
Thread-Topic: AD Review of draft-ietf-pim-hierarchicaljoinattr-05
Thread-Index: AQHRVHWZCAxn7Bn8W0OMjQBI9BgeOg==
Date: Thu, 21 Jan 2016 18:00:23 +0000
Message-ID: <D2C42460.109697%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.5]
Content-Type: multipart/alternative; boundary="_000_D2C42460109697aretanaciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/fU5CBBemNB_ycSZlQ10oshuaMRc>
Cc: Mike McBride <mmcbride7@gmail.com>, "pim-chairs@ietf.org" <pim-chairs@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: [pim] AD Review of draft-ietf-pim-hierarchicaljoinattr-05
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2016 18:00:55 -0000

--_000_D2C42460109697aretanaciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi!

I just finished reading this document.  I think that the description of the=
 general idea and of the operation when attributes are in fact included at =
different levels should be made a lot clearer than what it is now.  The doc=
ument only presents an idea of how to include attributes at different level=
s, but not what to do with them once they're in.  I would have liked to see=
 sections with more details about how to process attributes to be sent and/=
or received (similar to RFC5384 and 5496..).

Clarifying the text, including the IANA Considerations, and updating the RF=
C4601 reference are all improvements that I would like to see in the docume=
nt before starting the IETF Last Call.  Please see my detailed comments bel=
ow.

Thanks!

Alvaro.


Major:

  1.  Replace the RFC4601 references for draft-ietf-pim-rfc4601bis.
  2.  General Idea.  After reading the text a couple of times, I think I go=
t it! :-)  If the new "Hierarchical Join/Prune Attribute Hello Option" is i=
ncluded in the PIM Hello, then it means that the PIM Attribute from RFC5384=
 can now also be encoded in the Upstream Neighbor Address and the Group Add=
ress.  Right?  [Note that some of the comments below are really minor on th=
eir own, but add up to not clearly explaining what is intended, so includin=
g a succinct explanation would go a long way.]
     *   "This document provides a hierarchical way of encoding attributes =
and their values in a Join/Prune message=85"  This document doesn't define =
a new encoding, the encoding from RFC5384 is still used.  This document doe=
s define a mechanism to include attributes in a hierarchical may=85
     *   "This document extends this by specifying the same encoding type a=
lso for Encoded-Unicast and Encoded-Group formats."  "This" what?   This do=
cument allows the use of type 1=85so that Encoded-=85may contain a sequence=
 of attributes=85  The last paragraph in the Introduction is somewhat redun=
dant, but it does a much better job at explaining what is going on.
     *   Section 4. (PIM Address Encoding Types)
        *   I'm not sure what the purpose of this section is (not to mentio=
n some of the speculative language: "it is possible", "one could have").  I=
t seems to rehash information that is already in RFC5384 and draft-ietf-pim=
-rfc4601bis (BTW, it wouldn't hurt to put a reference related to type 0).  =
The only conclusion seems to be the renaming of the registry.  Is that the =
purpose, to justify the renaming of the registry?
        *
        *   Section 3. (Hierarchical Join/Prune Attribute Definition) "In t=
his document we make use of this to allow Join/Prune attributes in each of =
these addresses, using the encoding in Section 4."  What is "this"?  I don'=
t see any encoding defined in Section 4 (or anywhere else).
  3.  Operation when multiple attributes are present in the hierarchy.
     *   The hierarchy seems straight forward: attributes in the Upstream N=
eighbor Address take precedence over ones in the Group Address (maybe use "=
Multicast Group Address n" to be consistent with the packet), which then ta=
ke precedence over the source ones (Encoded-Source Address).  That is fine,=
 but this sentence in the last paragraph seems to imply that the attributes=
 in the source are always applied (regardless of the hierarchy): "Note that=
 Join/Prune attributes are still applied to sources as specified in [RFC538=
4]."
     *   I'm assuming that the rules specified in RFC5384 for the Encoded-S=
ource Address apply to the Upstream and Group addresses in this document.  =
For example, RFC5384 says that a "type 1 Encoded-Source Address MUST contai=
n at least one Join Attribute.  The way to specify that there are no Join A=
ttributes for a particular tree is to use the type 0 Encoded-Source Address=
."  Please explicitly indicate whether the procedures in RFC5384 apply here=
 or not...or if some do and others don't=85or if some of the rules change.
     *   Should the behavior for higher level attributes affect the lower l=
evels?  One of the reasons I'm asking is because RFC5496 (The RPF Vector TL=
V) says in Section 3.3.2. (Processing a Received Vector Attribute) that "a =
received PIM Join that contains a Vector Attribute, a router MUST first che=
ck to see if the Vector IP address is one of its own IP addresses.  If so, =
the Vector Attribute is discarded, and not passed further upstream."  If th=
is attribute is included so that it affects all sources, should all other V=
ector Attributes be discarded from the lower levels?
        *   Disclaimer: I haven't looked at the other attribute RFCs, but I=
 think that other similar issues may come up.
        *   Related question:  are there cases where it doesn't make sense =
to include a specific attribute at a specific level?  What happens then?
  4.  IANA Considerations
     *   The Introduction says that this "document defines a new IANA regis=
try for PIM encoding types", but the IANA Considerations Section seems to j=
ust be renaming the existing registry.  So it is not a new registry, just a=
 new name.
     *   "the more correct name Join/Prune attributes"  Shouldn't this resu=
lt in renaming the "PIM Join Attribute Types" registry too?
  5.  Security Considerations.  Can including an attribute at a specific le=
vel (maybe where it doesn't make sense =97 think not just of current attrib=
utes) cause an unintended consequence?  Knowing that the attributes can be =
changed (from RFC5384), what are the risks?  You should at least point to t=
he security considerations in RFC5384, even though that doesn't say much.

Minor:

  1.  The Abstract should have a sentence about the update to RFC5384.  Som=
ething simple: "This document updates RFC5384 by=85"  Also, similar text sh=
ould also appear in the Introduction (with maybe some more details).  The 3=
rd paragraph in the Introduction tries, but it is not crisp enough (see abo=
ve).
     *   I think that the update is just related to the registries.
     *   The hierarchical construct is just an extension, not an update.
  2.  Section 1. (Introduction):  Please add a reference to draft-ietf-pim-=
rfc4601bis when mentioning "Encoded-Unicast and Encoded-Group".
  3.  Hello Option.  The use of this term is not consistent.  Sometimes it =
is referred to as just "Hello Option", but the full name seems to be "Hiera=
rchical Join/Prune Attribute Hello Option".  This is specially important in=
 Section 7. (IANA Considerations), where the registry should be specificall=
y called out too.

Nits:

  1.  Section 3 uses "we" several times.  3rd person would be better.
  2.  I'm a little surprised that only one RFC2119 keyword is used.  I'm no=
t suggesting that you add more, as the text can be made clear without them.=
  Just an observation..
  3.  I am also surprised at the minimal changes between draft-venaas-pim-h=
ierarchicaljoinattr-00 and the current version [1] and how little discussio=
n happened on the list.  Again, just an observation.

[1] https://www.ietf.org/rfcdiff?url1=3Ddraft-venaas-pim-hierarchicaljoinat=
tr-00&url2=3Ddraft-ietf-pim-hierarchicaljoinattr-05

--_000_D2C42460109697aretanaciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <FA7BEF056292F540BEB17A54AA2805A4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Hi!</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
I just finished reading this document. &nbsp;I think that the description o=
f the general idea and of the operation when attributes are in fact include=
d at different levels should be made a lot clearer than what it is now. &nb=
sp;The document only presents an idea of how
 to include attributes at different levels, but not what to do with them on=
ce they're in. &nbsp;I would have liked to see sections with more details a=
bout how to process attributes to be sent and/or received (similar to RFC53=
84 and 5496..).</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Clarifying the text, including the IANA Considerations, and updating the RF=
C4601 reference are all improvements that I would like to see in the docume=
nt before starting the IETF Last Call. &nbsp;Please see my detailed comment=
s below.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Thanks!</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Alvaro.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Major:</div>
<ol>
<li style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
Replace the RFC4601 references for&nbsp;draft-ietf-pim-rfc4601bis.</li><li>=
<font face=3D"Calibri,sans-serif" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">General Idea. &nbsp;</font><font f=
ace=3D"Calibri,sans-serif">After reading the text a couple of times, I thin=
k I got it! :-) &nbsp;If the new &quot;Hierarchical
 Join/Prune Attribute Hello Option&quot; is included in the PIM Hello, then=
 it means that the PIM Attribute from RFC5384 can now also be encoded in th=
e&nbsp;Upstream Neighbor Address and the&nbsp;Group Address. &nbsp;Right? &=
nbsp;[Note that some of the comments below are really minor
 on their own, but add up to not clearly explaining what is intended, so in=
cluding a&nbsp;succinct explanation would go a long way.]</font>
<ul style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
<li>&quot;This document provides a hierarchical way of encoding attributes =
and their values in a Join/Prune message=85&quot; &nbsp;This document doesn=
't define a new encoding, the encoding from RFC5384 is still used. &nbsp;Th=
is document does define a mechanism to include attributes
 in a hierarchical may=85</li><li>&quot;This document extends this by speci=
fying the same encoding type also for Encoded-Unicast and Encoded-Group for=
mats.&quot; &nbsp;&quot;This&quot; what? &nbsp; This document allows the us=
e of type 1=85so that Encoded-=85may contain a sequence of attributes=85 &n=
bsp;The last paragraph in the
 Introduction is somewhat redundant, but it does a much better job at expla=
ining what is going on.</li><li>Section 4. (PIM Address Encoding Types) &nb=
sp;
<ul>
<li>I'm not sure what the purpose of this section is (not to mention some o=
f the speculative language: &quot;it is possible&quot;, &quot;one could hav=
e&quot;). &nbsp;It seems to rehash information that is already in RFC5384 a=
nd draft-ietf-pim-rfc4601bis (BTW, it wouldn't hurt to put
 a reference related to type 0). &nbsp;The only conclusion seems to be the =
renaming of the registry. &nbsp;Is that the purpose, to justify the renamin=
g of the registry?</li></ul>
<ul>
<li></li><li>Section 3. (Hierarchical Join/Prune Attribute Definition) &quo=
t;In this document we make use of this to allow Join/Prune attributes in ea=
ch of these addresses, using the encoding in Section 4.&quot; &nbsp;What is=
 &quot;this&quot;? &nbsp;I don't see any encoding defined in Section 4
 (or anywhere else).</li></ul>
</li></ul>
</li><li style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; fo=
nt-size: 14px;">
<font face=3D"Calibri,sans-serif">Operation when multiple attributes are pr=
esent in the hierarchy.</font>
<ul>
<li style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
<font face=3D"Calibri,sans-serif">The hierarchy seems straight forward: att=
ributes in the Upstream Neighbor Address take precedence over ones in the G=
roup Address (maybe use &quot;Multicast Group Address n&quot; to be consist=
ent with the packet), which then take&nbsp;precedence
 over the source ones (Encoded-Source Address). &nbsp;That is fine, but thi=
s sentence in the last paragraph seems to imply that the attributes in the =
source are&nbsp;always applied (regardless of the hierarchy): &quot;</font>=
<font face=3D"Calibri,sans-serif">Note that Join/Prune
 attributes are still applied to sources as&nbsp;</font><span style=3D"font=
-family: Calibri, sans-serif;">specified in [RFC5384].&quot;</span></li><li=
><font face=3D"Calibri,sans-serif" style=3D"color: rgb(0, 0, 0); font-famil=
y: Calibri, sans-serif; font-size: 14px;">I'm assuming that the rules speci=
fied in RFC5384 for the Encoded-Source Address apply to the Upstream and Gr=
oup addresses in this document. &nbsp;For
 example, RFC5384 says that a &quot;</font><span style=3D"color: rgb(0, 0, =
0); font-family: Calibri, sans-serif; font-size: 14px;">type 1 Encoded-Sour=
ce Address MUST contain at least one Join&nbsp;</span><span style=3D"color:=
 rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">Attribut=
e.
 &nbsp;The way to specify that there are no Join Attributes for&nbsp;</span=
><span style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font=
-size: 14px;">a particular tree is to use the type 0 Encoded-Source Address=
.&quot; &nbsp;Please explicitly indicate whether the procedures
 in RFC5384 apply here or not...or if some do and others don't</span><font =
face=3D"Calibri,sans-serif">=85or if some of the rules change.</font></li><=
li style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-siz=
e: 14px;">
<font face=3D"Calibri,sans-serif" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">Should the behavior for higher lev=
el attributes affect the lower levels? &nbsp;One of the reasons I'm asking =
is because RFC5496 (</font><font face=3D"Calibri,sans-serif">The
 RPF Vector TLV) says in Section&nbsp;</font><font face=3D"Calibri,sans-ser=
if">3.3.2. (Processing a Received Vector Attribute) that &quot;</font><span=
 style=3D"font-family: Calibri, sans-serif;">a received PIM Join that conta=
ins a Vector Attribute,&nbsp;</span><span style=3D"font-family: Calibri, sa=
ns-serif;">a
 router MUST first check to see if the Vector IP address is one of&nbsp;</s=
pan><span style=3D"font-family: Calibri, sans-serif;">its own IP addresses.=
 &nbsp;If so, the Vector Attribute is discarded, and&nbsp;</span><span styl=
e=3D"font-family: Calibri, sans-serif;">not passed
 further upstream.&quot; &nbsp;If this attribute is included so that it aff=
ects all sources, should all other Vector Attributes be discarded from the =
lower levels?</span>
<ul style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
<li>Disclaimer: I haven't looked at the other attribute RFCs, but I think t=
hat other similar issues may come up.</li><li>Related question: &nbsp;are t=
here cases where it doesn't make sense to include a specific attribute at a=
 specific level? &nbsp;What happens then?</li></ul>
</li></ul>
</li><li style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; fo=
nt-size: 14px;">
<font face=3D"Calibri,sans-serif">IANA Considerations</font>
<ul style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
<li><font face=3D"Calibri,sans-serif">The Introduction says that this &quot=
;document defines a new IANA registry for PIM encoding types&quot;, but the=
 IANA Considerations Section seems to just be renaming the existing registr=
y. &nbsp;So it is not a new registry, just a new
 name.</font></li><li><font face=3D"Calibri,sans-serif">&quot;</font><font =
face=3D"Calibri,sans-serif">the more correct name Join/Prune attributes&quo=
t; &nbsp;Shouldn't this result in renaming the &quot;</font><font face=3D"C=
alibri,sans-serif">PIM Join Attribute Types&quot; registry too?</font></li>=
</ul>
</li><li style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; fo=
nt-size: 14px;">
<font face=3D"Calibri,sans-serif">Security Considerations. &nbsp;Can includ=
ing an attribute at a specific level (maybe where it doesn't make sense&nbs=
p;=97&nbsp;think not just of current attributes) cause an unintended conseq=
uence? &nbsp;Knowing that the attributes can be changed
 (from RFC5384), what are the risks? &nbsp;You should at least point to the=
 security considerations in RFC5384, even though that doesn't say much.</fo=
nt></li></ol>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Minor:</div>
<ol style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
<li>The Abstract should have a sentence about the update to RFC5384. &nbsp;=
Something simple: &quot;This document updates RFC5384 by=85&quot; &nbsp;Als=
o, similar text should also appear in the Introduction (with maybe some mor=
e details). &nbsp;The 3rd paragraph in the Introduction tries,
 but it is not crisp enough (see above).
<ul>
<li>I think that the update is just related to the registries.</li><li>The =
hierarchical construct is just an extension, not an update.</li></ul>
</li><li style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; fo=
nt-size: 14px;">
Section&nbsp;1. (Introduction): &nbsp;Please add a reference to draft-ietf-=
pim-rfc4601bis when mentioning &quot;Encoded-Unicast and Encoded-Group&quot=
;.</li><li><font face=3D"Calibri,sans-serif">Hello Option. &nbsp;The use of=
 this term is not consistent. &nbsp;Sometimes it is&nbsp;referred to as jus=
t &quot;Hello Option&quot;, but the full name seems to be &quot;</font><fon=
t face=3D"Calibri,sans-serif">Hierarchical Join/Prune Attribute Hello Optio=
n&quot;.
 &nbsp;This is specially important in Section&nbsp;</font><font face=3D"Cal=
ibri,sans-serif">7. (IANA Considerations), where the registry should be spe=
cifically called out too.</font></li></ol>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Nits:</div>
<ol style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
<li style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
Section 3 uses &quot;we&quot; several times. &nbsp;3rd person would be bett=
er.</li><li>I'm a little surprised that only one RFC2119 keyword is used. &=
nbsp;I'm not suggesting that you add more, as the text can be made clear wi=
thout them. &nbsp;Just an observation..</li><li>I am also surprised at the =
minimal changes between&nbsp;draft-venaas-pim-hierarchicaljoinattr-00 and t=
he current version [1] and how little discussion happened on the list. &nbs=
p;Again, just an observation.</li></ol>
<div>[1]&nbsp;https://www.ietf.org/rfcdiff?url1=3Ddraft-venaas-pim-hierarch=
icaljoinattr-00&amp;url2=3Ddraft-ietf-pim-hierarchicaljoinattr-05</div>
</body>
</html>

--_000_D2C42460109697aretanaciscocom_--


From nobody Thu Jan 28 07:43:09 2016
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFA811A8A6B for <pim@ietfa.amsl.com>; Thu, 28 Jan 2016 07:43:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=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 w6XBku7JR4UD for <pim@ietfa.amsl.com>; Thu, 28 Jan 2016 07:43:06 -0800 (PST)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 893BA1A8A47 for <pim@ietf.org>; Thu, 28 Jan 2016 07:43:06 -0800 (PST)
Received: by mail-lf0-x22d.google.com with SMTP id 17so29417843lfz.1 for <pim@ietf.org>; Thu, 28 Jan 2016 07:43:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=88BbTe+YMToK/J2sFm1MuSbz+AUL1q/SByrsbSUISCM=; b=OXkm0/ceA/yMg3AOpZPSMIGfVIPpp0lkhy0sucsut1AZcdKeCoLpMjCLm/6zu8A2HD JdoJDS/EI96TUbL+R5rxqVCcVjJCBhRKn/7zpAEIRYPYg/QgynRV3oRfDf7u6HkVsz7j WcW0cOUer61w6Z+D5crJSnzX1IVp9rILXjeC+fPK+AYXKSKa8ESVwrviUHSPgnTQAF3Q eCnt7y6uvcLwbZZHQDMA5u6bU0h745rmgAnIcmr5jyZjupVKgi8X3whN8POdIVoOtqyW swh6DA1gaafloQtvg3hZKq13SyORgfkUiH3ipXxQhtMpg7y9vxUuYnCp+UzIMLw16wHO 7g3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=88BbTe+YMToK/J2sFm1MuSbz+AUL1q/SByrsbSUISCM=; b=Ck5z8Q/egj7Fr/XkSWMT18LDh66J/JMfR8QwGhPat7pE9mJsmXMp2/Xslq6mu0Nif6 UKnlAsX+KvgNgqzTWcUAGJSk+TnrvRZHdCo7cgyHvho2HVcQbsFBmGnQ266g8PvLtTaS gjfcHqyVzNRXXsstaL571DmftMQ7h4n7x7tJaq4W/6pjMUuHjTuQ0ekuOdptflberKNX 4koT+o5e+ikfaQvhVpf6rLo3uGeohvkaCUzbHKTm9kgUH4Et6MTIVQuah7m6RnjTCMfj gXHvXiaI7tndSsE/ZeSwlp8GdwbFaRgbRht6rWeCgAwT05zv9S/tOH28q4WCSs5JpuDH wD6A==
X-Gm-Message-State: AG10YOS7X6iq4i/YvT29Z+a2kp7OGHU2dRfHQaXkmRI7hEDU6bFVL6t67s3RLl+0DnSYXMDL4r0IZyM3cNJJ+g==
MIME-Version: 1.0
X-Received: by 10.25.162.202 with SMTP id l193mr1431074lfe.138.1453995784777;  Thu, 28 Jan 2016 07:43:04 -0800 (PST)
Received: by 10.25.26.211 with HTTP; Thu, 28 Jan 2016 07:43:04 -0800 (PST)
Received: by 10.25.26.211 with HTTP; Thu, 28 Jan 2016 07:43:04 -0800 (PST)
In-Reply-To: <D2C42460.109697%aretana@cisco.com>
References: <D2C42460.109697%aretana@cisco.com>
Date: Thu, 28 Jan 2016 07:43:04 -0800
Message-ID: <CAHANBtLRouhugeXYXvjspLwQ8Bh3bBEp11ZH5-iZPOmNkMPssQ@mail.gmail.com>
From: Stig Venaas <stig@venaas.com>
To: Alvaro Retana <aretana@cisco.com>
Content-Type: multipart/alternative; boundary=001a114119ec41c851052a66c61d
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/bN-MTE4tSc2rNvHBirSN-dnpzpU>
Cc: Mike McBride <mmcbride7@gmail.com>, "pim-chairs@ietf.org" <pim-chairs@ietf.org>, "draft-ietf-pim-hierarchicaljoinattr@ietf.org" <draft-ietf-pim-hierarchicaljoinattr@ietf.org>, pim@ietf.org
Subject: Re: [pim] AD Review of draft-ietf-pim-hierarchicaljoinattr-05
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 15:43:07 -0000

--001a114119ec41c851052a66c61d
Content-Type: text/plain; charset=UTF-8

Thanks for the review. I'll address the comments. I'm hopefully able to get
back to you next week.

Stig

--001a114119ec41c851052a66c61d
Content-Type: text/html; charset=UTF-8

<p dir="ltr">Thanks for the review. I&#39;ll address the comments. I&#39;m hopefully able to get back to you next week.</p>
<p dir="ltr">Stig<br>
</p>

--001a114119ec41c851052a66c61d--


From nobody Thu Jan 28 15:52:10 2016
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 131321B2AD7 for <pim@ietfa.amsl.com>; Thu, 28 Jan 2016 15:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=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 sC0vD05RsT1N for <pim@ietfa.amsl.com>; Thu, 28 Jan 2016 15:52:07 -0800 (PST)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (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 667CC1B2ACF for <pim@ietf.org>; Thu, 28 Jan 2016 15:52:07 -0800 (PST)
Received: by mail-lb0-x22a.google.com with SMTP id bc4so32422669lbc.2 for <pim@ietf.org>; Thu, 28 Jan 2016 15:52:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3i5JfjJu4eePsiFx8ECvdiy980dQmypBYr6HmQokI68=; b=xz50kLRvQjPv7lG11neSwkpv0lWosALMyhJbYZu3bFoNowVvKeTUvPejTw4p95Q9aC DOFb8qGwUwYgdACYyCpjUYa45PDgogtrIMDFuu2Q7+NWkiZKKT4T/2FTm1bM02DjdfeG BgFgShBec1MXJe/ZoRYDq2ri9ahpvVkeEldB9ULd9NmLc1APdob/8Su4CLfB/ztqYpNK bflnU/1Ma69gUYJfMmC7ZlS7zk2PhO+TyCNy9VBwOdnv5TJ9RWQOPZY2olPnSRQ1zel/ XGwph6UepUYXAc+Tg8+H07D7kmmn7DVePOSR2nmGLwN4r0bdo7oyKxQUWvXumfl5nG1d XOmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=3i5JfjJu4eePsiFx8ECvdiy980dQmypBYr6HmQokI68=; b=iuDB5MaDwypwuv7GDbPileyfyKH3cIgSbuUxXe/AFYWcjyVlejOzJ8GiXMuf0UOuz9 TleuOkrhsHC4hYxARRA6BudmVTntPbdNHJx9eZBoQgavGDLM7dPP/98C5lmkqrN6qTTM 20Fi3d87aY1rffGBBO4x+BLJQaK8ognn+1NgEWA1zqMd21z8inN8vNixJewPvnluFg5U ZbGqyAzMNHwXFic0HWOQR8ABdbolBe9ZgIgu9cChvh0ZBXKFO2Yr5nOwiL/6BbSNXyIR mCe5tkT4hSBEfFcjCL2HPiJ1cjtn9Z3KcM9lTNq+vzGpOGnnCMU1mD/4JlLcX+ygxmO/ yeSA==
X-Gm-Message-State: AG10YORiYcQ5cd7r0dU7XHtAYvOSgJ7JwvqVhtwIF4xMDUgaum5fD+WGhxdPZsB2CLdJVyLYdP0Ed8CFpXejNg==
MIME-Version: 1.0
X-Received: by 10.112.133.68 with SMTP id pa4mr2096896lbb.83.1454025125617; Thu, 28 Jan 2016 15:52:05 -0800 (PST)
Received: by 10.25.26.211 with HTTP; Thu, 28 Jan 2016 15:52:05 -0800 (PST)
In-Reply-To: <56A03FEE.6070008@concordia.ca>
References: <CAHANBtJBNhCDLSMKXK86eEpkK3B1oB9o3Y=X34tP9QXvuUPWMw@mail.gmail.com> <CAHANBtKqp+8+4armgQGK=UMqMjz5QhM=vih0HtquHpJGWbOw6A@mail.gmail.com> <56A03FEE.6070008@concordia.ca>
Date: Thu, 28 Jan 2016 15:52:05 -0800
Message-ID: <CAHANBtLoKn3c9SDSAWa9g+8V7vnZUHqovxz142ako0R1ExKO=g@mail.gmail.com>
From: Stig Venaas <stig@venaas.com>
To: draft-mcallister-pim-yang@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/8BhvaqtWR2JY_rGDTk-zNhPHAtg>
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Call for adoption of draft-mcallister-pim-yang-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 23:52:09 -0000

Thanks to all that responded. We're adopting the draft.

Authors, please submit your draft as draft-ietf-pim-yang-00.

Stig


On Wed, Jan 20, 2016 at 6:18 PM, William Atwood
<william.atwood@concordia.ca> wrote:
> I support the adoption of this draft as a working group document.
>
>   Bill
>
> On 19/01/2016 2:20 PM, Stig Venaas wrote:
>> This adoption call ends tomorrow and we haven't got a single response.
>> Does that mean that no one in the WG cares about YANG models? It is
>> difficult for us as chairs to know what the WG wants when we don't get
>> any responses.
>>
>> Please have a look at the draft and let us know by end of tomorrow
>> whether you would like this draft to be adopted or not.
>>
>> Stig
>>
>>
>> On Wed, Jan 6, 2016 at 11:09 AM, Stig Venaas <stig@venaas.com> wrote:
>>> Hi
>>>
>>> We discussed https://tools.ietf.org/html/draft-mcallister-pim-yang-01
>>> at the last pim meeting. We did an adoption call in the room and had 6
>>> in favor and none against. We would like to confirm that we indeed
>>> have consensus for adoption.
>>>
>>> Please respond whether you support adoption or not, or with any other
>>> comments you might have.
>>>
>>> The adoption call ends in 2 weeks, on January 20th.
>>>
>>> Note that this draft contains the pim yang models that the pim YANG
>>> design team has been working on.
>>>
>>> Stig
>>
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim
>>
>
> --
>
> Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
> Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
> Department of Computer Science
>    and Software Engineering
> Concordia University EV 3.185     email:william.atwood@concordia.ca
> 1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
> Montreal, Quebec Canada H3G 1M8
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

