Re: [homenet] support for HNCP in IPv6 CE routers

james woodyatt <> Tue, 24 October 2017 18:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A0A871393A1 for <>; Tue, 24 Oct 2017 11:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8x2ljQECdyWA for <>; Tue, 24 Oct 2017 11:50:00 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7EC76137ED6 for <>; Tue, 24 Oct 2017 11:50:00 -0700 (PDT)
Received: by with SMTP id j140so11281919itj.1 for <>; Tue, 24 Oct 2017 11:50:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=jRm5NPZXULfbD99zA0R8agmA9G+ZTIFquoMUdgFtjxY=; b=kLZ578fqPuA17rPuGrs+F7MmOjPD0na+2QiafhR0093VstWDiG87IutdYAFHhL6Amj aOybFMRgBiD9OvnYavS86rgNkHW0RJvMVF7yLYwg20oFXOyv3liAgOS3fWSkvBplLDJl zYDKD/sFnFH5H4jwZv40nDv+eTtcd/zpumjScOdqL4TrP4+CDpWcRmycpsb3W/CnmaQQ J22zpNgfI0IXBJOoOJBYHDjodCj4pQyeag7vz1Z+AXhEhgu0Zggk3NgaiTP41i1GKuvh HBs3AeqDI/ivAO/lCMIMtqHJOmyrGdQmsVSedV9O+Zqm4oPxDx8COoQOlKsfcDsKlO/q nv/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=jRm5NPZXULfbD99zA0R8agmA9G+ZTIFquoMUdgFtjxY=; b=S/PELvMLMT98AGIo7BS+icETYtEa7ZRYlal4E6XDbnpeGmDV/J3G5veOgIvDvT/CGU JQHWpjXgl6vXQRNEQ3WX+oMgAxIS4jlDbgtUkeSvuXFs3Md4YRiUQbFbW7JcxAPcnU1Y QZs7/7P3OYzV5av5Y6Sg7CMoy9q7V04ffzWKneYJ/fBXd+jV4asxgpDDkIm+C8dku5W/ l+1prtZu3JN5XpVycb2WErU6igOHIUHlT6kLjO8nVKnz4hBzCG/D+BajqWymI+g48S9C 6zqnhtx7uNp5DfyE1bGfvi4nwVKhZ8dHMuzItPTlveWiGyi15lShZxxTS+r3l36C7LKY SQzQ==
X-Gm-Message-State: AMCzsaUFXjhY8l90ofE8cEZHhnmE/b/VckhbbpfoQA6PepxgqBALIupE eZwO0tsXXDb9nnhERlU3rwZyFffJd0g=
X-Google-Smtp-Source: ABhQp+QYI4p397KrWvnYuzEknNtPmg+yCP+I181xHcI0ez17pMLjVLem0E89eLJlZe/X6Uoi5e3XpA==
X-Received: by with SMTP id x4mr13263itd.103.1508870999342; Tue, 24 Oct 2017 11:49:59 -0700 (PDT)
Received: from ?IPv6:2620:0:10e7:7:c048:bfa9:aa30:da1d? ([2620:0:10e7:7:c048:bfa9:aa30:da1d]) by with ESMTPSA id t3sm380578ioa.3.2017. for <> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Oct 2017 11:49:58 -0700 (PDT)
References: <> <> <> <>
From: james woodyatt <>
Message-ID: <>
Date: Tue, 24 Oct 2017 11:49:57 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [homenet] support for HNCP in IPv6 CE routers
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Oct 2017 18:50:02 -0000

On 10/24/2017 06:31 AM, STARK, BARBARA H wrote:
> [...] and also what may or may not be good to include in requirements specifically targeting routers at the customer's edge (CE).

I think it's a waste of time for HOMENET to propose requirements for 
routers in service provider networks, event those at the edge that 
connects to subscribers. Those requirements will be neither welcome nor 
observed by the industry.

If the service provider industry wants to provide input on requirements 
for HOMENET routers in the interior of residential networks, then I 
think we should consider them judiciously on balance with input from 
application and home networking device developers.