From melinda.shore@gmail.com Mon Jun 3 23:55:46 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF48621F9931 for ; Mon, 3 Jun 2013 23:55:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lo96KC87IQjI for ; Mon, 3 Jun 2013 23:55:33 -0700 (PDT) Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id C4A1821F9A94 for ; Mon, 3 Jun 2013 22:54:57 -0700 (PDT) Received: by mail-pd0-f172.google.com with SMTP id t10so3199501pdi.3 for ; Mon, 03 Jun 2013 22:54:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-forwarded-message-id:content-type :content-transfer-encoding; bh=gt3UjbcQdE8LItz7RrVPDDQ8ubEL/8WB4BXEHDF0UuU=; b=zh2xi5yHE5cXzgV0HYcxefDjXOMgn95q9LUQrlE2WsA/ztZUM6kYsJJAETkoNSIuxl 2KaAci1KelAZIRxfT3GovAyXpdcjFKPtEqORNO3g+cHG2KaVnQECNWw+RZgyDeCQXIad eGTS+FmuQHPJj20po64U3q3cpooTmwU3FRH9VsbfjNCVvyJ/y18MO5UmUU5Mx++B39Uj Svs+axhf31aiCLIxQ8Q5RATYKbESQVIyaKhuWCE0mLKXadBzjes1MvJOaZPFVOyqmXYr DeofEc+YGyCTJuF5fVckk2peJO89DNav2sK2qKu3fn3kQXUqNP6VbGfk5OIzovRszy4u So1g== X-Received: by 10.68.94.5 with SMTP id cy5mr26781310pbb.62.1370325297499; Mon, 03 Jun 2013 22:54:57 -0700 (PDT) Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id lq4sm66046539pab.19.2013.06.03.22.54.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Jun 2013 22:54:56 -0700 (PDT) Message-ID: <51AD812E.20805@gmail.com> Date: Mon, 03 Jun 2013 21:54:54 -0800 From: Melinda Shore User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "opsawg@ietf.org" References: In-Reply-To: X-Forwarded-Message-Id: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [OPSAWG] Fwd: Volunteering for nomcom and registrations X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 06:55:47 -0000 Please give serious consideration to volunteering for nomcom. I know a lot of you would like to make a contribution to the IETF that has a lasting impact. Ultimately it's all about documents and the technical work, but our processes need to support quality technical work, and nomcom participation is one way to contribute to that. Melinda -------- Original Message -------- Subject: Volunteering for nomcom and registrations Date: Tue, 4 Jun 2013 07:09:10 +0300 From: IETF Chair Reply-To: ietf@ietf.org To: ietf-announce@ietf.org CC: Allison Mankin I wanted to highlight that we have an ongoing call for nominating committee (nomcom) volunteers. Allison Mankin, chair of the 2013-2014 nominating committee, has told us that she would like to see more volunteers. The nomcom appoints people to fill the open slots on the IAOC, the IAB, and the IESG each year. The ten members of the nomcom are randomly selected from the pool of volunteers to perform this important task. It is important that the pool is large enough to ensure that we get a representative sample of people from the IETF. You can volunteer by sending e-mail to Allison before 11:59 pm EDT June 16, 2013. The details are at http://www.ietf.org/mail-archive/web/ietf-announce/current/msg11493.html Also, based on a request from Allison, we have added an option to volunteer while you are registering to the Berlin meeting. You can register at http://www.ietf.org/meeting/register.html If you select to volunteer here, Allison will contact you. Either way, volunteers must have attended three out of the last five meetings (IETF 82-86). Alternatively, please consider serving in the positions that nomcom selects. If you are considering doing this, you should not volunteer for duty on the nomcom itself, however. In any case, please consider helping with some of these tasks. And while you are at it, please also register for IETF-87 in Berlin! Jari Arkko IETF chair From melinda.shore@gmail.com Wed Jun 5 14:22:50 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A38011E80AE for ; Wed, 5 Jun 2013 14:22:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsjiXJatMQ1f for ; Wed, 5 Jun 2013 14:22:47 -0700 (PDT) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A99CE11E80AD for ; Wed, 5 Jun 2013 14:22:47 -0700 (PDT) Received: by mail-pa0-f43.google.com with SMTP id hz11so416626pad.30 for ; Wed, 05 Jun 2013 14:22:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding; bh=iJjlBiwIMcy585HS3KeHqIxS9h2DFFYBKKeuCk6T8bQ=; b=Ft0Tg9Hi07DXlfPuWO2WTtfjxHFyjBWazcsSPAhX6lSrpduMzLXb6mi3PpRkdiGLW/ MIvS4Z7DqQSaRSnQdyYgSbIIvDK1M23zyAKbeUr0tLiRapSgrP8RoCfQP91tS1V1I/7Q 3L27zH3+7mjgr8zaPZUqGwcOi4apW3nRKj3WtlvwPh/EyrZX9MvjncordI+0niPZX2yA UE5xo8v+MSvlLzbpJd290qeuW82sRMAjTwd9tHYUopG6QmZjNn8OM/AcuhEFsfWiJltP plKeZdKT7hQwchmOJWQQTrKvPTEuXnkzVuSSYL+ngKPFOgLwfO9A5nZ47e12hJCFYV/q pcLQ== X-Received: by 10.68.107.225 with SMTP id hf1mr35177952pbb.130.1370467367399; Wed, 05 Jun 2013 14:22:47 -0700 (PDT) Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id ih1sm69555484pbb.44.2013.06.05.14.22.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Jun 2013 14:22:46 -0700 (PDT) Message-ID: <51AFAC20.8040403@gmail.com> Date: Wed, 05 Jun 2013 13:22:40 -0800 From: Melinda Shore User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "opsawg@ietf.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "draft-ietf-opsawg-oam-overview@tools.ietf.org" , "opsawg-chairs@tools.ietf.org" Subject: [OPSAWG] draft-ietf-opsawg-oam-overview returned to working group X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jun 2013 21:22:50 -0000 draft-ietf-opsawg-oam-overview has been returned to the working group by the IESG. There is an unresolved DISCUSS, and the one YES on the document was from an AD who is no longer on the IESG (Ron Bonica). The IESG evaluation record can be found at: http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/. Next steps would include revision of the draft to accommodate the issues raised during IESG review. Melinda From denghui02@gmail.com Thu Jun 6 04:20:09 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD43521F995A for ; Thu, 6 Jun 2013 04:20:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.149 X-Spam-Level: X-Spam-Status: No, score=-100.149 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tg28u06WOafr for ; Thu, 6 Jun 2013 04:20:08 -0700 (PDT) Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 579B121F994F for ; Thu, 6 Jun 2013 04:20:08 -0700 (PDT) Received: by mail-qc0-f171.google.com with SMTP id z1so328851qcx.16 for ; Thu, 06 Jun 2013 04:20:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5JJjEsas0eWc/VUn2KuFmJ3LlBvtLN+o56PVyOLlwnI=; b=CaFFTYxBjVJsgUQjvKRVuv+ZTFHLXr9/oy1Q+g5NFEjyE9qhMJZzCGucM7Lfu4riRK oynqRqUu92HYsfRFgXXxjZI/6zvN2uxAkKjGvmKi761GqU+OBiQfohptLqOLHDDZfr0F os0gyeI3TIKEPf8PHS/5EJ8GMbkyuKwcnHhFvrqAkbeXp91zezC7k7m87v5h9yD+QGI8 UgQE8iAOf50OdnoheX8tkOGp/RlnSB/uamE/QwdnnpbU2QGYUl8W5WCJnmKyT1LeXTil 1upMTDf3Hci0s/zs0JoEbLSazn//CGMmi4VZWZ5bQBoFXtMsH+qnVkVbTAIck3uX+hzO UUpQ== MIME-Version: 1.0 X-Received: by 10.224.71.211 with SMTP id i19mr34393037qaj.27.1370517607790; Thu, 06 Jun 2013 04:20:07 -0700 (PDT) Received: by 10.49.16.42 with HTTP; Thu, 6 Jun 2013 04:20:07 -0700 (PDT) In-Reply-To: <6FBCD28690577C4582AFC9B477428E86300C3BB1@dfweml510-mbx.china.huawei.com> References: <6FBCD28690577C4582AFC9B477428E86300C3BB1@dfweml510-mbx.china.huawei.com> Date: Thu, 6 Jun 2013 12:20:07 +0100 Message-ID: From: Hui Deng To: Behcet Sarikaya , "opsawg@ietf.org" Content-Type: multipart/alternative; boundary=047d7bdca64a2bbb2b04de7a7f56 Cc: =?GB2312?B?wfW088X0?= Subject: Re: [OPSAWG] Review about CAPWAP drafts X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jun 2013 11:20:09 -0000 --047d7bdca64a2bbb2b04de7a7f56 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Hi Behcet, Thanks a lot for your kind support, we will continue to update our document based on comments. Best regards, -Hui 2013/6/3 Behcet Sarikaya > Hi Hui,**** > > ** ** > > My apologies for being so late in my reply.**** > > I am not in opsawg mailing list so I could not follow these drafts.**** > > I am OK with forwarding this mail to opsawg list.**** > > I strongly support Hui=A1=AFs draft. **** > > Regarding technical comments, I have been away from CAPWAP protocol since > CAPWAP WG closed. Because of that currently I am unable to provide any > technical comments on the three drafts listed below.**** > > ** ** > > Regards,**** > > ** ** > > Behcet**** > > ** ** > > *From:* Hui Deng [mailto:denghui02@gmail.com] > *Sent:* Wednesday, May 29, 2013 4:22 AM > *To:* Behcet Sarikaya; joel jaeggli; =C1=F5=B4=F3=C5=F4; Melinda Shore > *Subject:* Review about CAPWAP drafts**** > > ** ** > > Dear Behcet,**** > > **** > > Good to know that you are discussing the capwap in Broadband Forum, just > wondering whether you could kindly help to review below three drafts:**** > > http://tools.ietf.org/html/draft-ietf-opsawg-capwap-hybridmac-00 > http://tools.ietf.org/html/draft-ietf-opsawg-capwap-extension-00**** > > http://tools.ietf.org/html/draft-zhang-opsawg-capwap-eap-00 **** > > **** > > Thanks a lot fo ryour kind help**** > > Best regards,**** > > **** > > -Hui**** > --047d7bdca64a2bbb2b04de7a7f56 Content-Type: text/html; charset=GB2312 Content-Transfer-Encoding: quoted-printable
Hi Behcet,
 
Thanks a lot fo= r your kind support, we will continue to update our document based on comme= nts.
 
Best regards,
 
-H= ui
 


2013/6/= 3 Behcet Sarikaya <behcet.sarikaya@huawei.com>
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">

Hi Hui,

 =

My apologies for bei= ng so late in my reply.

I am not in opsawg m= ailing list so I could not follow these drafts.

I am OK with forward= ing this mail to opsawg list.

I strongly support H= ui’s draft.

Regarding technical = comments, I have been away from CAPWAP protocol since CAPWAP WG closed. Bec= ause of that currently I am unable to provide any technical comments on the three drafts listed below.

 =

Regards,

 =

Behcet=

 =

From: Hui Deng [ma= ilto:denghui02@gma= il.com]
Sent: Wednesday, May 29, 2013 4:22 AM
To: Behcet Sarikaya; joel jaeggli; =C1=F5=B4=F3=C5=F4; Melinda Shore
Subject: Review about CAPWAP drafts

 

Dear Behcet,

 

Good to know that you are discussing the capwap in B= roadband Forum, just wondering whether you could kindly help to review belo= w three drafts:

 

Thanks a lot fo ryour kind help

Best regards,

 

-Hui


--047d7bdca64a2bbb2b04de7a7f56-- From tom.taylor.stds@gmail.com Thu Jun 6 06:05:46 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 700CA21F99A5 for ; Thu, 6 Jun 2013 06:05:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybao2rsi6uW7 for ; Thu, 6 Jun 2013 06:05:46 -0700 (PDT) Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id DBCF121F99A4 for ; Thu, 6 Jun 2013 06:05:45 -0700 (PDT) Received: by mail-ob0-f169.google.com with SMTP id up14so4658896obb.0 for ; Thu, 06 Jun 2013 06:05:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-forwarded-message-id:content-type :content-transfer-encoding; bh=huWkOugUakftTpyrrbp41CphfVS2hRh8xeMtNyE6iLY=; b=qeVAjkFfVVtPPBaIZUPSV8gEPFhbvjumS891nuVQ/PBp7BqXRwsdkvwsZExiJDO47M yPcWqzhAbKrthHnkopXHj8V23G1A/tHU29rh0bwkDE0l14V58lGj100/RNGwJO2M1ayg m9fRU+5XSlxBAFBCsSfNOpGmcX7tbvCjsN8PjC5S2IWyWqYbFXT7s7YVYXRlHyCuIFci Tk/wqnRV9uBREceYj+4/X0mWS+FgZOMa+t1m5wE0Zsz/z7LQuMnR0ztixqaxvaZsmQKP 8cYG0B0zYnL61NorkabbXckqMD3fz+8qNb+830yF/kIHOW+N5+bi7Qrc3lc+Cl7v8rgq EMvQ== X-Received: by 10.182.19.168 with SMTP id g8mr18484942obe.21.1370523945445; Thu, 06 Jun 2013 06:05:45 -0700 (PDT) Received: from [192.168.1.64] ([216.254.162.169]) by mx.google.com with ESMTPSA id oe10sm13691372oeb.6.2013.06.06.06.05.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Jun 2013 06:05:44 -0700 (PDT) Message-ID: <51B08927.4080009@gmail.com> Date: Thu, 06 Jun 2013 09:05:43 -0400 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "opsawg@ietf.org" References: <20130606062642.4649.19133.idtracker@ietfa.amsl.com> In-Reply-To: <20130606062642.4649.19133.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20130606062642.4649.19133.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [OPSAWG] Fwd: New Version Notification for draft-schoenw-opsawg-nm-dhc-04.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jun 2013 13:05:46 -0000 This draft was written as a practical follow-on to draft-ietf-opsawg-automated-network-configuration. One of the gaps noted by the latter was the need for new network nodes to be able to locate servers involved in their management. After a deliberate internal review, the Huawei authors wish to state that they are unaware of any IPR claims against the content of this draft. The other two authors did not participate in the review, but assert that they are unaware of any such IPR. Since new DHCPv6 options in particular require Standards Action, the authors hope that the Working Group can agree to move the draft forward. Tom Taylor -------- Original Message -------- Subject: New Version Notification for draft-schoenw-opsawg-nm-dhc-04.txt ... A new version of I-D, draft-schoenw-opsawg-nm-dhc-04.txt has been successfully submitted by Juergen Schoenwaelder and posted to the IETF repository. Filename: draft-schoenw-opsawg-nm-dhc Revision: 04 Title: Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for Network Management Protocols Creation date: 2013-06-05 Group: Individual Submission Number of pages: 11 URL: http://www.ietf.org/internet-drafts/draft-schoenw-opsawg-nm-dhc-04.txt Status: http://datatracker.ietf.org/doc/draft-schoenw-opsawg-nm-dhc Htmlized: http://tools.ietf.org/html/draft-schoenw-opsawg-nm-dhc-04 Diff: http://www.ietf.org/rfcdiff?url2=draft-schoenw-opsawg-nm-dhc-04 Abstract: This document defines new Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) options providing lists of IP addresses that can be used to locate network management services, specifically for the collection of logs and of Simple Network Management Protocol (SNMP) notifications. The IETF Secretariat From bclaise@cisco.com Fri Jun 7 02:42:58 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40AC721F960D for ; Fri, 7 Jun 2013 02:42:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.399 X-Spam-Level: X-Spam-Status: No, score=-10.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EuIVkAz3qwSc for ; Fri, 7 Jun 2013 02:42:53 -0700 (PDT) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 66AC621F96FB for ; Fri, 7 Jun 2013 02:42:52 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r579gj21002680; Fri, 7 Jun 2013 11:42:45 +0200 (CEST) Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r579g5Pa001788; Fri, 7 Jun 2013 11:42:15 +0200 (CEST) Message-ID: <51B1AAED.2000605@cisco.com> Date: Fri, 07 Jun 2013 11:42:05 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 5.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Melinda Shore References: <51AFAC20.8040403@gmail.com> In-Reply-To: <51AFAC20.8040403@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "opsawg@ietf.org" , "draft-ietf-opsawg-oam-overview@tools.ietf.org" , "opsawg-chairs@tools.ietf.org" Subject: Re: [OPSAWG] draft-ietf-opsawg-oam-overview returned to working group X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2013 09:42:58 -0000 Significant issues have been raised with the document during the IESG review, dated from August 2011. Only 5 ADs are currently active from that period. Therefore, I'm sending the document back to the working group for resolution of those issues, to make sure that the working group fully understands the issues and is in control of managing the resolution. Regards, Benoit > draft-ietf-opsawg-oam-overview has been returned to the working > group by the IESG. There is an unresolved DISCUSS, and the one > YES on the document was from an AD who is no longer on the IESG > (Ron Bonica). > > The IESG evaluation record can be found at: > http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/. > > Next steps would include revision of the draft to accommodate the > issues raised during IESG review. > > Melinda > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg > > From cpignata@cisco.com Fri Jun 7 06:01:59 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4065D21F8BE9 for ; Fri, 7 Jun 2013 06:01:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fax4eFsCIU3h for ; Fri, 7 Jun 2013 06:01:54 -0700 (PDT) Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 0914321F8B64 for ; Fri, 7 Jun 2013 06:01:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1515; q=dns/txt; s=iport; t=1370610114; x=1371819714; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=fF3y6wjGA38zOXEP2J6GrqkrUxWAoRJCanT957rzq4Y=; b=IUnQwIxd39pmVL5BvBuCrWW6NSw25tFChW925Mg/Q/6BMhaEjJG2o33C bVEfotcLMamBVaJI57q/Ofr7L+3/BqYI7jnRCfIs+LHeyVmvAjXfU7iO/ ZajyAU74vKCvQB1qbjqI6qu7cC1surrd3ZfXXGuKmtL7gllNSzxOhuFyF E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhIFAKrYsVGtJXG//2dsb2JhbABZgwkwvnB9FnSCJQEEAQEBNzQLEgEIIhQ3CyUCBAENBQgBiAQMvEqOBoEBMQIFgnthA5hpkBmDD4FxNg X-IronPort-AV: E=Sophos;i="4.87,822,1363132800"; d="scan'208";a="220021804" Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-6.cisco.com with ESMTP; 07 Jun 2013 13:01:53 +0000 Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r57D1rvW015733 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 7 Jun 2013 13:01:53 GMT Received: from xmb-aln-x02.cisco.com ([169.254.5.36]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Fri, 7 Jun 2013 08:01:53 -0500 From: "Carlos Pignataro (cpignata)" To: "Benoit Claise (bclaise)" , Melinda Shore Thread-Topic: [OPSAWG] draft-ietf-opsawg-oam-overview returned to working group Thread-Index: AQHOY38tV8u8xgcR+EunQICOOweoqA== Date: Fri, 7 Jun 2013 13:01:18 +0000 Message-ID: <95067C434CE250468B77282634C96ED322BF71DD@xmb-aln-x02.cisco.com> In-Reply-To: <51B1AAED.2000605@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.4.130416 x-originating-ip: [10.81.8.41] Content-Type: text/plain; charset="us-ascii" Content-ID: <0D2E231ABA25934F989A441D87E22DAF@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "opsawg@ietf.org" , "draft-ietf-opsawg-oam-overview@tools.ietf.org" , "opsawg-chairs@tools.ietf.org" Subject: Re: [OPSAWG] draft-ietf-opsawg-oam-overview returned to working group X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2013 13:01:59 -0000 Benoit, WG, In addition to the datatracker-captured comments and text, please note also a number of IETF LC comments as part of directorate reviews as well, as for example=20 http://www.ietf.org/mail-archive/web/rtg-dir/current/msg01827.html Thanks, -- Carlos. On 6/7/13 5:42 AM, "Benoit Claise (bclaise)" wrote: >Significant issues have been raised with the document during the IESG >review, dated from August 2011. Only 5 ADs are currently active from >that period. >Therefore, I'm sending the document back to the working group for >resolution of those issues, to make sure that the working group fully >understands the issues and is in control of managing the resolution. > >Regards, Benoit >> draft-ietf-opsawg-oam-overview has been returned to the working >> group by the IESG. There is an unresolved DISCUSS, and the one >> YES on the document was from an AD who is no longer on the IESG >> (Ron Bonica). >> >> The IESG evaluation record can be found at: >> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/. >> >> Next steps would include revision of the draft to accommodate the >> issues raised during IESG review. >> >> Melinda >> _______________________________________________ >> OPSAWG mailing list >> OPSAWG@ietf.org >> https://www.ietf.org/mailman/listinfo/opsawg >> >> > >_______________________________________________ >OPSAWG mailing list >OPSAWG@ietf.org >https://www.ietf.org/mailman/listinfo/opsawg > From melinda.shore@gmail.com Thu Jun 13 21:05:27 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C659521F9A69 for ; Thu, 13 Jun 2013 21:05:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQ1OqG-g2YtS for ; Thu, 13 Jun 2013 21:05:27 -0700 (PDT) Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 538F821F9A65 for ; Thu, 13 Jun 2013 21:05:27 -0700 (PDT) Received: by mail-pb0-f51.google.com with SMTP id um15so142463pbc.38 for ; Thu, 13 Jun 2013 21:05:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=LNKo8v1qYqS830dKOvyRBk+gAgIyp7PN3LrD4jO1K14=; b=wDCZjzxH8lwQWff8Jl4M9KP6XXbzhlcRR9g0Ltp9cnjNNuzkdYkwsY7EMYHSLShG/Y q4J19boTR9rxCtcwsyO69ojfOraKFK9JMbpviK46cNIOr9oy5Gf3eOS+Xl4ezSOv8uYE EIe6fUzD78Dp1Ay47HLW/Q46dQecznwNi0myGNAKAqnJJGBAClRZ9m/4ssn50v5WcQ6b 5+KeV7js0H4OZJWbJdimN0ZJTOSDxVj9NNhczxXmG5mRnSM9BZEw7gmU82IfugPWckug LB1kQgsTxpqbIEF/ze84Oi3vL/JU2F1v/FvwvBXFs07fo/5zBs7sXSMQrCfF+e95GsvH XdoA== X-Received: by 10.68.115.131 with SMTP id jo3mr613887pbb.133.1371182727104; Thu, 13 Jun 2013 21:05:27 -0700 (PDT) Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id kv2sm553070pbc.28.2013.06.13.21.05.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Jun 2013 21:05:26 -0700 (PDT) Message-ID: <51BA9683.5060409@gmail.com> Date: Thu, 13 Jun 2013 20:05:23 -0800 From: Melinda Shore User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "opsawg@ietf.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [OPSAWG] Meeting preparation X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 04:05:27 -0000 Hi, folks: It's time to start planning for the Berlin meeting. This would be an excellent time to start going through drafts and identifying problems or questions that need resolution, to then bring those to the mailing list, and determining what would benefit from meeting time. If you're thinking of submitting a draft to opsawg and want it discussed at the meeting, it's time to get it uploaded and a discussion started. Thanks, Melinda From bclaise@cisco.com Fri Jun 14 02:56:41 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58CAC21F9BA9; Fri, 14 Jun 2013 02:56:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.872 X-Spam-Level: X-Spam-Status: No, score=-9.872 tagged_above=-999 required=5 tests=[AWL=-0.566, BAYES_00=-2.599, HTML_MESSAGE=0.001, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTVUapI3+T3T; Fri, 14 Jun 2013 02:56:37 -0700 (PDT) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id D04E021F9B9D; Fri, 14 Jun 2013 02:56:36 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r5E9uYFj005902; Fri, 14 Jun 2013 11:56:34 +0200 (CEST) Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r5E9uD7X022568; Fri, 14 Jun 2013 11:56:23 +0200 (CEST) Message-ID: <51BAE8BD.70802@cisco.com> Date: Fri, 14 Jun 2013 11:56:13 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 5.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------080107010101060802070700" X-Mailman-Approved-At: Sat, 15 Jun 2013 21:34:15 -0700 Cc: "ops-ads@tools.ietf.org" Subject: [OPSAWG] OPS/LMAP chair positions X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 09:56:41 -0000 This is a multi-part message in MIME format. --------------080107010101060802070700 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear all, [bcc'ed a couple mailing lists. You might be receiving duplicates] Joel and I are looking for potential WG chair candidates. 1. Specifically for Large-Scale Measurement of Broadband Performance (LMAP ). At this stage, LMAP is still a proposed WG, but it goes through the process, and might become a WG before the IETF in Berlin. 2. This is also a good opportunity to create a pool of candidates interested in chairing OPS WGs in the future. We might even consider training this group if there is some interest. RFC 2418 might help as background information. Alternatively, if you have questions/comments, don't hesitate to reach out to Joel and I at "ops-ads@tools.ietf.org" Regards, Joel and Benoit --------------080107010101060802070700 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear all,

[bcc'ed a couple mailing lists. You might be receiving duplicates]

Joel and I are looking for potential WG chair candidates.
1. Specifically for Large-Scale Measurement of Broadband Performance (LMAP).
At this stage, LMAP is still a proposed WG, but it goes through the process, and might become a WG before the IETF in Berlin.
2. This is also a good opportunity to create a pool of candidates interested in chairing OPS WGs in the future.
We might even consider training this group if there is some interest.

RFC 2418 might help as background information.
Alternatively, if you have questions/comments, don't hesitate to reach out to Joel and I at "ops-ads@tools.ietf.org" <ops-ads@tools.ietf.org>

Regards, Joel and Benoit
--------------080107010101060802070700-- From tom.taylor.stds@gmail.com Tue Jun 18 08:06:18 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 287D521F9C18 for ; Tue, 18 Jun 2013 08:06:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.556 X-Spam-Level: X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mA3w9msdUw+X for ; Tue, 18 Jun 2013 08:06:17 -0700 (PDT) Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 4850821F95DD for ; Tue, 18 Jun 2013 08:06:17 -0700 (PDT) Received: by mail-oa0-f53.google.com with SMTP id k14so5183375oag.12 for ; Tue, 18 Jun 2013 08:06:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=+/p5oW6qWRXnQ5/2KtcayVOojoGlzAd44E9pPEcBlt8=; b=b/W7jPU3J0euOyKmQzpaal9ldKigp2c5TB4dxEuAbBJ1tvsfZCo+Jl7cEsNrlLRl/F Kf09NdOL8qxX/06jztCA/cT6hpjboyBVNcucbFqAzF8WueaetmCPV4mTQ2kvGZGE0u9/ 7Z9suNbTkRIy7G3ebFE7igHIE3BYuh7y4uAU5ZzhdjJOJcENhUBdhi3ySfezP5GNy/oM VLnQrlk0L9AQYqbHYauW20PEdYsljDsJ47XM5VUnkRz8jWRKtRyEGnDUT0GnnYxuKR2n DlOdinPEv8nHuerUK4XLPCeUhJg4g+TYxI9WqMH8BNT0JpBFjoDpHmt7P9wrDcSN+hDc xo7g== X-Received: by 10.60.142.7 with SMTP id rs7mr12629040oeb.106.1371567976688; Tue, 18 Jun 2013 08:06:16 -0700 (PDT) Received: from [192.168.1.64] ([216.254.161.150]) by mx.google.com with ESMTPSA id c20sm22611398oez.4.2013.06.18.08.06.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Jun 2013 08:06:16 -0700 (PDT) Message-ID: <51C07769.5040609@gmail.com> Date: Tue, 18 Jun 2013 11:06:17 -0400 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "opsawg@ietf.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 15:06:18 -0000 Does anyone object in principle to the use of DHCP to provision routers as opposed to hosts? In particular, is there a problem in principle with the proposed DHCP options for finding log and notification servers in draft-schoenw-opsawg-nm-dhc? Tom Taylor From adrian@olddog.co.uk Tue Jun 18 08:24:09 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3018521F9C3E for ; Tue, 18 Jun 2013 08:24:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.585 X-Spam-Level: X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Am2uvFCgGFAT for ; Tue, 18 Jun 2013 08:23:53 -0700 (PDT) Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id DDEA521F9B99 for ; Tue, 18 Jun 2013 08:23:48 -0700 (PDT) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5IFNkZV019263; Tue, 18 Jun 2013 16:23:46 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5IFNj1d019245 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Jun 2013 16:23:45 +0100 From: "Adrian Farrel" To: "'Tom Taylor'" References: <51C07769.5040609@gmail.com> In-Reply-To: <51C07769.5040609@gmail.com> Date: Tue, 18 Jun 2013 16:23:44 +0100 Message-ID: <048f01ce6c37$d27d4830$7777d890$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQL9gNFzO0Oqdrhf/Us76JzgY4ZU5Jbdag4Q Content-Language: en-gb Cc: opsawg@ietf.org Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 15:24:09 -0000 Tom, "Configure routers" is the name of the thin end of a very large wedge :-) If, for example, you were to suggest dynamically installing routes on routers using DHCP, you might hear some opposition. This may be a question you also want to ask on the routing-discussion list. A > -----Original Message----- > From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf > Of Tom Taylor > Sent: 18 June 2013 16:06 > To: opsawg@ietf.org > Subject: [OPSAWG] Use of DHCP to provision routers > > Does anyone object in principle to the use of DHCP to provision routers > as opposed to hosts? In particular, is there a problem in principle with > the proposed DHCP options for finding log and notification servers in > draft-schoenw-opsawg-nm-dhc? > > Tom Taylor > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg From tom.taylor.stds@gmail.com Tue Jun 18 09:29:32 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26CC611E80F6 for ; Tue, 18 Jun 2013 09:29:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.562 X-Spam-Level: X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JwJLY946LNxs for ; Tue, 18 Jun 2013 09:29:09 -0700 (PDT) Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 2E86A11E80F0 for ; Tue, 18 Jun 2013 09:29:05 -0700 (PDT) Received: by mail-oa0-f45.google.com with SMTP id j1so5369102oag.32 for ; Tue, 18 Jun 2013 09:29:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=HeCqi4OSq4n4tex466N1ALKFG9wM2zZt4kE11HU1bxI=; b=TgZvGhQLgmI/eo4iP2c7mBBWVTtUZJi+LZ219RFVjP7kbw4AR8NTbtKt8eDx99x22M h0AIt8so/gUcME/ZWy1oqasEetczQhushh3Tnm9z0Iw8D1t6fgzeDmvWtyrzsPGCBzq2 j4thAByp8lhVIIBEuuJbBMxqsuKhF0ec75Ro1KMPpYNNYL2kkYG5nZSSehV5QKOKRyZI FpZ2+L8fwoC11rMmcAQiYR4zDwWURnztX6qtr6k18UD2loKz3h7KWGQ0ygQ1LInGZBrN GGHWbaf+3Vy7MJYkhY/TvvaaNJAOGRe5rGDyQz8AAXuDXy+DTah+fSignkzEQ9DVZgZb ADhA== X-Received: by 10.60.56.17 with SMTP id w17mr12322195oep.142.1371572943569; Tue, 18 Jun 2013 09:29:03 -0700 (PDT) Received: from [192.168.1.64] ([216.254.161.150]) by mx.google.com with ESMTPSA id ps5sm22970741oeb.8.2013.06.18.09.29.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Jun 2013 09:29:02 -0700 (PDT) Message-ID: <51C08ACF.4080601@gmail.com> Date: Tue, 18 Jun 2013 12:29:03 -0400 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: adrian@olddog.co.uk References: <51C07769.5040609@gmail.com> <048f01ce6c37$d27d4830$7777d890$@olddog.co.uk> In-Reply-To: <048f01ce6c37$d27d4830$7777d890$@olddog.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: opsawg@ietf.org Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 16:29:38 -0000 Posting to routing-discussion would automatically imply something we don't intend, I think. I suppose I should qualify by saying our intention is *initial* configuration of routers. Tom On 18/06/2013 11:23 AM, Adrian Farrel wrote: > Tom, > > "Configure routers" is the name of the thin end of a very large wedge :-) > > If, for example, you were to suggest dynamically installing routes on routers > using DHCP, you might hear some opposition. > > This may be a question you also want to ask on the routing-discussion list. > > A > >> -----Original Message----- >> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf >> Of Tom Taylor >> Sent: 18 June 2013 16:06 >> To: opsawg@ietf.org >> Subject: [OPSAWG] Use of DHCP to provision routers >> >> Does anyone object in principle to the use of DHCP to provision routers >> as opposed to hosts? In particular, is there a problem in principle with >> the proposed DHCP options for finding log and notification servers in >> draft-schoenw-opsawg-nm-dhc? >> >> Tom Taylor >> _______________________________________________ >> OPSAWG mailing list >> OPSAWG@ietf.org >> https://www.ietf.org/mailman/listinfo/opsawg > > From adrian@olddog.co.uk Tue Jun 18 09:36:19 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C92A911E80E2 for ; Tue, 18 Jun 2013 09:36:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.586 X-Spam-Level: X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4mImI0neBMdZ for ; Tue, 18 Jun 2013 09:35:50 -0700 (PDT) Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id CB9A621F9994 for ; Tue, 18 Jun 2013 09:35:49 -0700 (PDT) Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5IGZlFI006231; Tue, 18 Jun 2013 17:35:47 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5IGZkVu006217 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Jun 2013 17:35:46 +0100 From: "Adrian Farrel" To: "'Tom Taylor'" References: <51C07769.5040609@gmail.com> <048f01ce6c37$d27d4830$7777d890$@olddog.co.uk> <51C08ACF.4080601@gmail.com> In-Reply-To: <51C08ACF.4080601@gmail.com> Date: Tue, 18 Jun 2013 17:35:45 +0100 Message-ID: <04be01ce6c41$e1ee2dc0$a5ca8940$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQL9gNFzO0Oqdrhf/Us76JzgY4ZU5AIFI3SvAcjlaTGWvxD2IA== Content-Language: en-gb Cc: opsawg@ietf.org Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 16:36:20 -0000 :-) In that case your email would say "Don't Panic!" At the point of initial configuration, isn't a router just a host? [Stands back behind blast-proof wall] A > -----Original Message----- > From: Tom Taylor [mailto:tom.taylor.stds@gmail.com] > Sent: 18 June 2013 17:29 > To: adrian@olddog.co.uk > Cc: opsawg@ietf.org > Subject: Re: [OPSAWG] Use of DHCP to provision routers > > Posting to routing-discussion would automatically imply something we > don't intend, I think. I suppose I should qualify by saying our > intention is *initial* configuration of routers. > > Tom > > On 18/06/2013 11:23 AM, Adrian Farrel wrote: > > Tom, > > > > "Configure routers" is the name of the thin end of a very large wedge :-) > > > > If, for example, you were to suggest dynamically installing routes on routers > > using DHCP, you might hear some opposition. > > > > This may be a question you also want to ask on the routing-discussion list. > > > > A > > > >> -----Original Message----- > >> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On > Behalf > >> Of Tom Taylor > >> Sent: 18 June 2013 16:06 > >> To: opsawg@ietf.org > >> Subject: [OPSAWG] Use of DHCP to provision routers > >> > >> Does anyone object in principle to the use of DHCP to provision routers > >> as opposed to hosts? In particular, is there a problem in principle with > >> the proposed DHCP options for finding log and notification servers in > >> draft-schoenw-opsawg-nm-dhc? > >> > >> Tom Taylor > >> _______________________________________________ > >> OPSAWG mailing list > >> OPSAWG@ietf.org > >> https://www.ietf.org/mailman/listinfo/opsawg > > > > From cdl@asgaard.org Tue Jun 18 09:50:39 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9559E21F9A5F for ; Tue, 18 Jun 2013 09:50:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ftmOIaio7IPI for ; Tue, 18 Jun 2013 09:50:33 -0700 (PDT) Received: from smtp1.emailarray.com (smtp1.emailarray.com [65.39.216.14]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7B021F9A34 for ; Tue, 18 Jun 2013 09:50:33 -0700 (PDT) Received: (qmail 55514 invoked by uid 89); 18 Jun 2013 16:50:32 -0000 Received: from unknown (HELO ?204.29.150.161?) (Y2RsQGFzZ2FhcmQub3JnQDUwLjc2LjM0LjE4NQ==) (POLARISLOCAL) by smtp1.emailarray.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 18 Jun 2013 16:50:32 -0000 From: "Christopher LILJENSTOLPE" To: "Adrian Farrel" Date: Tue, 18 Jun 2013 09:50:30 -0700 Message-ID: <9A31B9EC-5265-44C5-95F2-2555047DBFF8@asgaard.org> In-Reply-To: <04be01ce6c41$e1ee2dc0$a5ca8940$@olddog.co.uk> References: <51C07769.5040609@gmail.com> <048f01ce6c37$d27d4830$7777d890$@olddog.co.uk> <51C08ACF.4080601@gmail.com> <04be01ce6c41$e1ee2dc0$a5ca8940$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_4E08F20B-39CE-418A-B28C-E949F731C500_="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Mailer: MailMate (1.5.4r3438) X-PolarisMail-Flags: x Cc: opsawg@ietf.org Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 16:50:39 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_4E08F20B-39CE-418A-B28C-E949F731C500_= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 18 Jun 2013, at 9:35, Adrian Farrel wrote: > :-) > > In that case your email would say "Don't Panic!" > > At the point of initial configuration, isn't a router just a host? [Sta= nds back > behind blast-proof wall] Actually, I would concur with Adrian here IFF we are talking about a rout= er as a host (i.e. configuring the management interface, management infra= structure (such as ntp, syslog, etc). If we are talking about configurin= g "traffic" interfaces, I'd have to think really hard about that=E2=80=A6= Christopher > > A > >> -----Original Message----- >> From: Tom Taylor [mailto:tom.taylor.stds@gmail.com] >> Sent: 18 June 2013 17:29 >> To: adrian@olddog.co.uk >> Cc: opsawg@ietf.org >> Subject: Re: [OPSAWG] Use of DHCP to provision routers >> >> Posting to routing-discussion would automatically imply something we >> don't intend, I think. I suppose I should qualify by saying our >> intention is *initial* configuration of routers. >> >> Tom >> >> On 18/06/2013 11:23 AM, Adrian Farrel wrote: >>> Tom, >>> >>> "Configure routers" is the name of the thin end of a very large wedge= :-) >>> >>> If, for example, you were to suggest dynamically installing routes on= > routers >>> using DHCP, you might hear some opposition. >>> >>> This may be a question you also want to ask on the routing-discussion= list. >>> >>> A >>> >>>> -----Original Message----- >>>> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On >> Behalf >>>> Of Tom Taylor >>>> Sent: 18 June 2013 16:06 >>>> To: opsawg@ietf.org >>>> Subject: [OPSAWG] Use of DHCP to provision routers >>>> >>>> Does anyone object in principle to the use of DHCP to provision rout= ers >>>> as opposed to hosts? In particular, is there a problem in principle = with >>>> the proposed DHCP options for finding log and notification servers i= n >>>> draft-schoenw-opsawg-nm-dhc? >>>> >>>> Tom Taylor >>>> _______________________________________________ >>>> OPSAWG mailing list >>>> OPSAWG@ietf.org >>>> https://www.ietf.org/mailman/listinfo/opsawg >>> >>> > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg -- =E6=9D=8E=E6=9F=AF=E7=9D=BF Check my PGP key here: http://www.asgaard.org/cdl/cdl.asc Current vCard here: http://www.asgaard.org/cdl/cdl.vcf --=_MailMate_4E08F20B-39CE-418A-B28C-E949F731C500_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJRwI/WAAoJEGmx2Mt/+Iw/NEIIAInXwqE959xHoSSlposmyryE h/3WOzSdmqoCRlFtsFIANNZh4ZFWAhUCTFME63cu8O+ZFjrYn836cumPdr2K82oU zN2Anb2GwzTNJl+46FHWMgflA+TX+7PFjMWTpQWIYaXZnn2nHdeCRswyBMoIU9RT SZGGYFSdarfia0LQ2UubPp95Ao6bR+nAADooDyPjvrLfoKnRNi4QOiiei4GR25fS rx5AsbTYtVYrwyWuNzFFuPv1jmHvVAOI4Wj3LxSAbTBcPWjMCTQlvIA3eWEAx70x ZipYnvhq3MXQpGgq998EO+eW2mduF7p5lIqbSr6fvkFiM1Ao/tplId7ZC2Z+20w= =Pv2i -----END PGP SIGNATURE----- --=_MailMate_4E08F20B-39CE-418A-B28C-E949F731C500_=-- From j.schoenwaelder@jacobs-university.de Tue Jun 18 10:40:21 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1133D21F9B20 for ; Tue, 18 Jun 2013 10:40:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.063 X-Spam-Level: X-Spam-Status: No, score=-103.063 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oE8gGPavjhJH for ; Tue, 18 Jun 2013 10:40:16 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id D1AFA21F9B1C for ; Tue, 18 Jun 2013 10:40:15 -0700 (PDT) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0D26B20BF7; Tue, 18 Jun 2013 19:40:15 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id z1lhurHdja-6; Tue, 18 Jun 2013 19:40:14 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 9B5B320BF6; Tue, 18 Jun 2013 19:40:14 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 852C926F492A; Tue, 18 Jun 2013 19:40:13 +0200 (CEST) Date: Tue, 18 Jun 2013 19:40:12 +0200 From: Juergen Schoenwaelder To: Tom Taylor Message-ID: <20130618174012.GA23633@elstar.local> Mail-Followup-To: Tom Taylor , "opsawg@ietf.org" References: <51C07769.5040609@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51C07769.5040609@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "opsawg@ietf.org" Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 17:40:21 -0000 On Tue, Jun 18, 2013 at 11:06:17AM -0400, Tom Taylor wrote: > Does anyone object in principle to the use of DHCP to provision > routers as opposed to hosts? In particular, is there a problem in > principle with the proposed DHCP options for finding log and > notification servers in draft-schoenw-opsawg-nm-dhc? Tom, the term "router" may refer to very different things, such as (a) a backbone network router (b) a router in an access network (c) a router in an enterprise network (d) a router in a remote office location (e) a CPE home router (f) a (virtual) router in a virtual machine environment (g) a routing function embedded in a layer-2 switch (h) a routing function embedded in a good old host (i) a routing function embedded in a middlebox (j) ... and I guess depending on which interpretation you choose of the term 'router', you will get very different answers. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From tom.taylor.stds@gmail.com Tue Jun 18 11:15:48 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4803921F9936 for ; Tue, 18 Jun 2013 11:15:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.566 X-Spam-Level: X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rJ8yKvZCvNFm for ; Tue, 18 Jun 2013 11:15:47 -0700 (PDT) Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDE821F8206 for ; Tue, 18 Jun 2013 11:15:47 -0700 (PDT) Received: by mail-oa0-f43.google.com with SMTP id i7so5453544oag.30 for ; Tue, 18 Jun 2013 11:15:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=upjpLuE4OmZ+wHy9XNWqqEWCLt8qOPvqXK7QwL0lf2g=; b=ZcW+4E6aCa4YHXW5Wdpf3xMPekwJOULrUzRxgUS+ppYOzm605CaG6fTR40ccxYwINx xIk0LUq3JYR1pZIKMtq0CLoLpLH3u3LCkzdFGa8BaDJ8/DI9gEeOF9m87cYvTyR/K+Wv TmjvqXppvkB7anB7sxcQpeN1ssG97Z1SISWPcfNcF2qEzWUiJ7CupXOZ/SbZ0xW9zEXt qeUjmABgMdWzzFEtikmHg0c4RUKOxxezPzUBQSiNFxRnxQnvryen3Zh4v11fCuiMw1rU 4rbYnfhtOmtvdqr/ETf9KFkW9PRbdieWoCI631W9gqE74TEMmH+38WH2JglUTrQeqgcl Yf5g== X-Received: by 10.60.130.137 with SMTP id oe9mr5905154oeb.18.1371579338709; Tue, 18 Jun 2013 11:15:38 -0700 (PDT) Received: from [192.168.1.64] ([216.254.161.150]) by mx.google.com with ESMTPSA id h4sm23526938oel.2.2013.06.18.11.15.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Jun 2013 11:15:37 -0700 (PDT) Message-ID: <51C0A3CA.20501@gmail.com> Date: Tue, 18 Jun 2013 14:15:38 -0400 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Christopher LILJENSTOLPE References: <51C07769.5040609@gmail.com> <048f01ce6c37$d27d4830$7777d890$@olddog.co.uk> <51C08ACF.4080601@gmail.com> <04be01ce6c41$e1ee2dc0$a5ca8940$@olddog.co.uk> <9A31B9EC-5265-44C5-95F2-2555047DBFF8@asgaard.org> In-Reply-To: <9A31B9EC-5265-44C5-95F2-2555047DBFF8@asgaard.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: opsawg@ietf.org Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 18:15:48 -0000 My take-away from this is that there is no objection in principle specifically to draft-schoenw-opsawg-nm-dhc. The next question is whether the WG sees configuration of log and notification servers via DHCP as potentially useful in some networks or totally redundant. Tom On 18/06/2013 12:50 PM, Christopher LILJENSTOLPE wrote: > On 18 Jun 2013, at 9:35, Adrian Farrel wrote: > >> :-) >> >> In that case your email would say "Don't Panic!" >> >> At the point of initial configuration, isn't a router just a host? [Stands back >> behind blast-proof wall] > > > Actually, I would concur with Adrian here IFF we are talking about a router as a host (i.e. configuring the management interface, management infrastructure (such as ntp, syslog, etc). If we are talking about configuring "traffic" interfaces, I'd have to think really hard about that… > > Christopher > > >> >> A >> ... From tom.taylor.stds@gmail.com Tue Jun 18 11:16:32 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF2BC21F9A73 for ; Tue, 18 Jun 2013 11:16:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.569 X-Spam-Level: X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwwQ8tTQrWQz for ; Tue, 18 Jun 2013 11:16:32 -0700 (PDT) Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 31D4521F99E8 for ; Tue, 18 Jun 2013 11:16:32 -0700 (PDT) Received: by mail-oa0-f51.google.com with SMTP id i4so5432510oah.38 for ; Tue, 18 Jun 2013 11:16:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=flwk9NIFVvEfReSISkhVbOynd+vEEHa0l98YbmyPHwo=; b=0+xTcMjpIr0Ld9GAWk+UdfiDR468hny4H8hiyGI3Y81e6ziWGtvVkO0iWkfSkYN9xh cXRfOfOo+IX5T68BMM65f064dEtYEU/xNJ5sDh2Xwn045DPNPq0f8CjDwfLPxVSB4/pU /SEooYxOgcKFun1VBtHp9cEWYKsXuG+FYvR2bpMTo1Nf92WcNVbNkl73YQgNKBgq/dnc RpTIJ6BM6v3WSwdtDSM4KK90CJ/RtnjYoALvxyh+IICJqpOeD2onHi2z3vgTl/P4aKS0 hCEns59YlRQgVf+gKnSyEp3YaqF4gozNijL3mWdB3USH9+ao5flDcRrUk1uWirFanJeG Q2Eg== X-Received: by 10.60.55.10 with SMTP id n10mr7145889oep.45.1371579391652; Tue, 18 Jun 2013 11:16:31 -0700 (PDT) Received: from [192.168.1.64] ([216.254.161.150]) by mx.google.com with ESMTPSA id r4sm23521555oem.3.2013.06.18.11.16.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Jun 2013 11:16:31 -0700 (PDT) Message-ID: <51C0A3FF.4050302@gmail.com> Date: Tue, 18 Jun 2013 14:16:31 -0400 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "opsawg@ietf.org" References: <51C07769.5040609@gmail.com> <20130618174012.GA23633@elstar.local> In-Reply-To: <20130618174012.GA23633@elstar.local> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 18:16:33 -0000 The cases I'm particularly interested in are (a) and (b). On 18/06/2013 1:40 PM, Juergen Schoenwaelder wrote: > On Tue, Jun 18, 2013 at 11:06:17AM -0400, Tom Taylor wrote: >> Does anyone object in principle to the use of DHCP to provision >> routers as opposed to hosts? In particular, is there a problem in >> principle with the proposed DHCP options for finding log and >> notification servers in draft-schoenw-opsawg-nm-dhc? > > Tom, > > the term "router" may refer to very different things, such as > > (a) a backbone network router > (b) a router in an access network > (c) a router in an enterprise network > (d) a router in a remote office location > (e) a CPE home router > (f) a (virtual) router in a virtual machine environment > (g) a routing function embedded in a layer-2 switch > (h) a routing function embedded in a good old host > (i) a routing function embedded in a middlebox > (j) ... > > and I guess depending on which interpretation you choose of the term > 'router', you will get very different answers. > > /js > From adrian@olddog.co.uk Tue Jun 18 11:24:08 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D25B21F9BD9 for ; Tue, 18 Jun 2013 11:24:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.586 X-Spam-Level: X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dwDUUATDf3R for ; Tue, 18 Jun 2013 11:24:01 -0700 (PDT) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 75E2021F9BAD for ; Tue, 18 Jun 2013 11:23:58 -0700 (PDT) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5IINtMG022263; Tue, 18 Jun 2013 19:23:55 +0100 Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5IINnqx022158 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Jun 2013 19:23:53 +0100 From: "Adrian Farrel" To: "'Tom Taylor'" , References: <51C07769.5040609@gmail.com> <20130618174012.GA23633@elstar.local> <51C0A3FF.4050302@gmail.com> In-Reply-To: <51C0A3FF.4050302@gmail.com> Date: Tue, 18 Jun 2013 19:23:48 +0100 Message-ID: <04f101ce6c50$fd5877a0$f80966e0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQL9gNFzO0Oqdrhf/Us76JzgY4ZU5AFVaHVpA1ORDESWuFcvQA== Content-Language: en-gb Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 18:24:08 -0000 I find it a bit surprising that a backbone network router or a router in an access network would benefit from "dynamic" configuration. I have an image of a whole backbone network bootstrapping itself outwards from the DHCP server. At this point, I'd probably like to sit down and think about the problem before jumping to use DHCP. A > -----Original Message----- > From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf > Of Tom Taylor > Sent: 18 June 2013 19:17 > To: opsawg@ietf.org > Subject: Re: [OPSAWG] Use of DHCP to provision routers > > The cases I'm particularly interested in are (a) and (b). > > On 18/06/2013 1:40 PM, Juergen Schoenwaelder wrote: > > On Tue, Jun 18, 2013 at 11:06:17AM -0400, Tom Taylor wrote: > >> Does anyone object in principle to the use of DHCP to provision > >> routers as opposed to hosts? In particular, is there a problem in > >> principle with the proposed DHCP options for finding log and > >> notification servers in draft-schoenw-opsawg-nm-dhc? > > > > Tom, > > > > the term "router" may refer to very different things, such as > > > > (a) a backbone network router > > (b) a router in an access network > > (c) a router in an enterprise network > > (d) a router in a remote office location > > (e) a CPE home router > > (f) a (virtual) router in a virtual machine environment > > (g) a routing function embedded in a layer-2 switch > > (h) a routing function embedded in a good old host > > (i) a routing function embedded in a middlebox > > (j) ... > > > > and I guess depending on which interpretation you choose of the term > > 'router', you will get very different answers. > > > > /js > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg From warren@kumari.net Tue Jun 18 11:47:54 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FA2D11E80F8 for ; Tue, 18 Jun 2013 11:47:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.287 X-Spam-Level: X-Spam-Status: No, score=-102.287 tagged_above=-999 required=5 tests=[AWL=0.312, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o+JqTO75YSG8 for ; Tue, 18 Jun 2013 11:47:49 -0700 (PDT) Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id A146911E80EE for ; Tue, 18 Jun 2013 11:47:47 -0700 (PDT) Received: from [192.168.1.153] (unknown [66.84.81.90]) by vimes.kumari.net (Postfix) with ESMTPSA id B8ED01B4029B; Tue, 18 Jun 2013 14:47:45 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Warren Kumari In-Reply-To: <04f101ce6c50$fd5877a0$f80966e0$@olddog.co.uk> Date: Tue, 18 Jun 2013 14:47:39 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <9FB024BD-2B4C-4523-B82E-CCA73FFAC68E@kumari.net> References: <51C07769.5040609@gmail.com> <20130618174012.GA23633@elstar.local> <51C0A3FF.4050302@gmail.com> <04f101ce6c50$fd5877a0$f80966e0$@olddog.co.uk> To: adrian@olddog.co.uk X-Mailer: Apple Mail (2.1508) Cc: opsawg@ietf.org Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 18:47:54 -0000 On Jun 18, 2013, at 2:23 PM, "Adrian Farrel" = wrote: > I find it a bit surprising that a backbone network router or a router = in an > access network would benefit from "dynamic" configuration. +1. There are folk who use DHCP to configure the IP address on router = interfaces. As an example, Cisco does this ( = http://www.cisco.com/en/US/docs/ios/12_4t/ip_addr/configuration/guide/htdh= cpcl.html ) Most folk avoid this as it is inclined to end poorly -- you really want = your network devices to be stable and not rely on a: some other service = or b: the rest of the network being up. If you have a network with more than a few devices you run into odd = boot-strapping issues -- for example you lose power / have some other = large scale outage and all of the boxes reboot. Some box out at the edge = of the network boots a little faster than other divides towards the DHCP = server. By the time you actually have routability to the DHCP server the = edge devices have gotten annoyed and start sulking. If your network is sufficiently small (a doctor's office is the standard = example) you can make this irk, but honestly, for routers it's usually = much safer to just statically configure them=85 There are a whole bunch of other devices that do get their addresses via = DHCP, such as access-points and phones and camera and such. For example, we use Cisco access points at the IETF meetings. There are = fairly dynamically deployed, and rely on DHCP -- when initially booting = they go off and get a DHCP address, which they use to TFTP an AP = specific config. We specify the SNMP / Syslog / similar in the TFTPed = config, but I could see this being useful for other network type widgets = like other APs, monitoring things, UPSs, camera, etc. > I have an image of a whole backbone network bootstrapping itself = outwards from > the DHCP server. >=20 Yeah, don't do that :-P W > At this point, I'd probably like to sit down and think about the = problem before > jumping to use DHCP. >=20 > A >=20 >> -----Original Message----- >> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On = Behalf >> Of Tom Taylor >> Sent: 18 June 2013 19:17 >> To: opsawg@ietf.org >> Subject: Re: [OPSAWG] Use of DHCP to provision routers >>=20 >> The cases I'm particularly interested in are (a) and (b). >>=20 >> On 18/06/2013 1:40 PM, Juergen Schoenwaelder wrote: >>> On Tue, Jun 18, 2013 at 11:06:17AM -0400, Tom Taylor wrote: >>>> Does anyone object in principle to the use of DHCP to provision >>>> routers as opposed to hosts? In particular, is there a problem in >>>> principle with the proposed DHCP options for finding log and >>>> notification servers in draft-schoenw-opsawg-nm-dhc? >>>=20 >>> Tom, >>>=20 >>> the term "router" may refer to very different things, such as >>>=20 >>> (a) a backbone network router >>> (b) a router in an access network >>> (c) a router in an enterprise network >>> (d) a router in a remote office location >>> (e) a CPE home router >>> (f) a (virtual) router in a virtual machine environment >>> (g) a routing function embedded in a layer-2 switch >>> (h) a routing function embedded in a good old host >>> (i) a routing function embedded in a middlebox >>> (j) ... >>>=20 >>> and I guess depending on which interpretation you choose of the term >>> 'router', you will get very different answers. >>>=20 >>> /js >>>=20 >> _______________________________________________ >> OPSAWG mailing list >> OPSAWG@ietf.org >> https://www.ietf.org/mailman/listinfo/opsawg >=20 > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg >=20 -- "Let's just say that if complete and utter chaos was lightning, he'd be = the sort to stand on a hilltop in a thunderstorm wearing wet copper = armour and shouting 'All gods are bastards'." -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of = Magic) From wesley.george@twcable.com Tue Jun 18 13:57:06 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C8721F9638 for ; Tue, 18 Jun 2013 13:57:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.718 X-Spam-Level: X-Spam-Status: No, score=-0.718 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pgKNvdh7IZX for ; Tue, 18 Jun 2013 13:57:01 -0700 (PDT) Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 640A521F9412 for ; Tue, 18 Jun 2013 13:57:01 -0700 (PDT) X-SENDER-IP: 10.136.163.13 X-SENDER-REPUTATION: None X-IronPort-AV: E=Sophos;i="4.87,891,1363147200"; d="scan'208";a="95523774" Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 18 Jun 2013 16:56:09 -0400 Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Tue, 18 Jun 2013 16:46:23 -0400 From: "George, Wes" To: "adrian@olddog.co.uk" , 'Tom Taylor' , "opsawg@ietf.org" Date: Tue, 18 Jun 2013 16:42:15 -0400 Thread-Topic: [OPSAWG] Use of DHCP to provision routers Thread-Index: AQL9gNFzO0Oqdrhf/Us76JzgY4ZU5AFVaHVpA1ORDESWuFcvQIAAH4YA Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592304348389EC@PRVPEXVS15.corp.twcable.com> References: <51C07769.5040609@gmail.com> <20130618174012.GA23633@elstar.local> <51C0A3FF.4050302@gmail.com> <04f101ce6c50$fd5877a0$f80966e0$@olddog.co.uk> In-Reply-To: <04f101ce6c50$fd5877a0$f80966e0$@olddog.co.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 20:57:06 -0000 > From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf > Of Adrian Farrel > Sent: Tuesday, June 18, 2013 2:24 PM > To: 'Tom Taylor'; opsawg@ietf.org > Subject: Re: [OPSAWG] Use of DHCP to provision routers > > I find it a bit surprising that a backbone network router or a router in > an > access network would benefit from "dynamic" configuration. [WEG] Well, renumbering would be easier in some cases. Instead of talking a= bout it in terms of DHCP, you may want to think of it more in terms of sepa= rating the IP from the miscellaneous subtending configuration that depends = on it in something like a router (neighbor config, ACLs, etc). In other wor= ds, why does the IP config need to be static, what actually breaks? You pro= bably can make a distinction between things like WAN IPs and things like lo= opbacks. To go further, how many of those breakage cases are solved if you = can refer to the device via DNS instead of by IP (yes, this adds a failure = domain, just follow me for a second) or use config that works by pulling th= e assigned IP into the right places elsewhere in the config? Not trying to = minimize the scale and other issues with the bootstrapping problem, just fr= aming the question a little differently. 6renum definitely spent some time = talking about things like parameterized config and inheritance to address t= he fact that many IP addresses in a router affect multiple parts of the con= fig such that you have to change it multiple places. Also things like ILNP = focus on splitting locator and identifier so that one can change without af= fecting the other. Making a network work with dynamically configured addres= ses goes in that general direction. But that sort of digresses from the ori= ginal question... > > At this point, I'd probably like to sit down and think about the problem > before > jumping to use DHCP. > > A [WEG] Generally I agree. In a lot of cases, the problem may be better solve= d by proper element management systems to push the right config to the righ= t places, rather than using DHCP in lieu of such, but depending on the appl= ication, DHCP may be the right level of lightweight where a heavyweight ele= ment management system might not be the right choice, especially for (lots = of ) small devices that are supposed to boot and configure themselves with = little or no human hand-holding or preconfiguration. Wes George This E-mail and any of its attachments may contain Time Warner Cable propri= etary information, which is privileged, confidential, or subject to copyrig= ht belonging to Time Warner Cable. This E-mail is intended solely for the u= se of the individual or entity to which it is addressed. If you are not the= intended recipient of this E-mail, you are hereby notified that any dissem= ination, distribution, copying, or action taken in relation to the contents= of and attachments to this E-mail is strictly prohibited and may be unlawf= ul. If you have received this E-mail in error, please notify the sender imm= ediately and permanently delete the original and any copy of this E-mail an= d any printout. From wesley.george@twcable.com Tue Jun 18 14:14:53 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB68F21E8054 for ; Tue, 18 Jun 2013 14:14:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.591 X-Spam-Level: X-Spam-Status: No, score=-0.591 tagged_above=-999 required=5 tests=[AWL=-0.127, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iinD0Murm5qa for ; Tue, 18 Jun 2013 14:14:48 -0700 (PDT) Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id D3BAD11E8101 for ; Tue, 18 Jun 2013 14:14:47 -0700 (PDT) X-SENDER-IP: 10.136.163.13 X-SENDER-REPUTATION: None X-IronPort-AV: E=Sophos;i="4.87,891,1363147200"; d="scan'208";a="92518206" Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 18 Jun 2013 17:13:52 -0400 Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Tue, 18 Jun 2013 16:46:23 -0400 From: "George, Wes" To: "adrian@olddog.co.uk" , 'Tom Taylor' , "opsawg@ietf.org" Date: Tue, 18 Jun 2013 16:42:15 -0400 Thread-Topic: [OPSAWG] Use of DHCP to provision routers Thread-Index: AQL9gNFzO0Oqdrhf/Us76JzgY4ZU5AFVaHVpA1ORDESWuFcvQIAAH4YA Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592304348389EC@PRVPEXVS15.corp.twcable.com> References: <51C07769.5040609@gmail.com> <20130618174012.GA23633@elstar.local> <51C0A3FF.4050302@gmail.com> <04f101ce6c50$fd5877a0$f80966e0$@olddog.co.uk> In-Reply-To: <04f101ce6c50$fd5877a0$f80966e0$@olddog.co.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [OPSAWG] Use of DHCP to provision routers X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 21:14:53 -0000 > From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf > Of Adrian Farrel > Sent: Tuesday, June 18, 2013 2:24 PM > To: 'Tom Taylor'; opsawg@ietf.org > Subject: Re: [OPSAWG] Use of DHCP to provision routers > > I find it a bit surprising that a backbone network router or a router in > an > access network would benefit from "dynamic" configuration. [WEG] Well, renumbering would be easier in some cases. Instead of talking a= bout it in terms of DHCP, you may want to think of it more in terms of sepa= rating the IP from the miscellaneous subtending configuration that depends = on it in something like a router (neighbor config, ACLs, etc). In other wor= ds, why does the IP config need to be static, what actually breaks? You pro= bably can make a distinction between things like WAN IPs and things like lo= opbacks. To go further, how many of those breakage cases are solved if you = can refer to the device via DNS instead of by IP (yes, this adds a failure = domain, just follow me for a second) or use config that works by pulling th= e assigned IP into the right places elsewhere in the config? Not trying to = minimize the scale and other issues with the bootstrapping problem, just fr= aming the question a little differently. 6renum definitely spent some time = talking about things like parameterized config and inheritance to address t= he fact that many IP addresses in a router affect multiple parts of the con= fig such that you have to change it multiple places. Also things like ILNP = focus on splitting locator and identifier so that one can change without af= fecting the other. Making a network work with dynamically configured addres= ses goes in that general direction. But that sort of digresses from the ori= ginal question... > > At this point, I'd probably like to sit down and think about the problem > before > jumping to use DHCP. > > A [WEG] Generally I agree. In a lot of cases, the problem may be better solve= d by proper element management systems to push the right config to the righ= t places, rather than using DHCP in lieu of such, but depending on the appl= ication, DHCP may be the right level of lightweight where a heavyweight ele= ment management system might not be the right choice, especially for (lots = of ) small devices that are supposed to boot and configure themselves with = little or no human hand-holding or preconfiguration. Wes George This E-mail and any of its attachments may contain Time Warner Cable propri= etary information, which is privileged, confidential, or subject to copyrig= ht belonging to Time Warner Cable. This E-mail is intended solely for the u= se of the individual or entity to which it is addressed. If you are not the= intended recipient of this E-mail, you are hereby notified that any dissem= ination, distribution, copying, or action taken in relation to the contents= of and attachments to this E-mail is strictly prohibited and may be unlawf= ul. If you have received this E-mail in error, please notify the sender imm= ediately and permanently delete the original and any copy of this E-mail an= d any printout. From dromasca@avaya.com Wed Jun 19 04:24:53 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A486921F9A1E for ; Wed, 19 Jun 2013 04:24:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.458 X-Spam-Level: X-Spam-Status: No, score=-103.458 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y+l9JxZG-6yn for ; Wed, 19 Jun 2013 04:24:53 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 15CFA21F9C26 for ; Wed, 19 Jun 2013 04:24:49 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8HAH+UwVHGmAcF/2dsb2JhbABagmgher8YfxZtB4IjAQEBAQMSKEsGAQgNBAQBAQsUCTkUBwEBBQQBBBMIGodsAZpYhECbahePCj6CemEDngSLAIMPgig X-IronPort-AV: E=Sophos;i="4.87,896,1363147200"; d="scan'208";a="16750606" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 19 Jun 2013 07:24:48 -0400 Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 19 Jun 2013 07:22:49 -0400 Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Wed, 19 Jun 2013 07:24:47 -0400 From: "Romascanu, Dan (Dan)" To: "opsawg@ietf.org" Thread-Topic: Approval of IEEE Std 802.3.1-2013 Thread-Index: Ac5sanh13Tny74e2Q5OKO9lJMYqaBQAdRziw Date: Wed, 19 Jun 2013 11:24:46 +0000 Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA1A543C@AZ-FFEXMB04.global.avaya.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.64.58.45] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [OPSAWG] FW: Approval of IEEE Std 802.3.1-2013 X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jun 2013 11:24:53 -0000 -----Original Message----- From: Howard Frazier [mailto:hfrazier@BROADCOM.COM]=20 Sent: Wednesday, June 19, 2013 12:28 AM To: STDS-802-3-MIB@LISTSERV.IEEE.ORG Subject: [802.3.1_MIBS] Approval of IEEE Std 802.3.1-2013 Dear Members of the IEEE 802.3.1 Ethernet MIB modules Task Force, I am pleased to report that the IEEE-SA Standards Board has given final app= roval to our revision of IEEE Std 802.3.1. I am working with the IEEE SA ed= itorial staff to prepare the document for publication, and I will let you k= now as soon as it has been published. Congratulations, and thank you for your contributions to this effort. Howard Frazier Chair, IEEE 802.3.1 Ethernet MIB nodules Task Force From internet-drafts@ietf.org Sun Jun 23 09:38:26 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED91521F9B32; Sun, 23 Jun 2013 09:38:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.561 X-Spam-Level: X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nAxDP7nWjex8; Sun, 23 Jun 2013 09:38:26 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4B321F9D82; Sun, 23 Jun 2013 09:38:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130623163826.13640.64829.idtracker@ietfa.amsl.com> Date: Sun, 23 Jun 2013 09:38:26 -0700 Cc: opsawg@ietf.org Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-01.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2013 16:38:27 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Operations and Management Area Working Gr= oup Working Group of the IETF. Title : Mechanisms for Optimal LAG/ECMP Component Link Utilizati= on in Networks Author(s) : Ram Krishnan Sanjay Khanna Lucy Yong Anoop Ghanwani Ning So Bhumip Khasnabish Filename : draft-ietf-opsawg-large-flow-load-balancing-01.txt Pages : 22 Date : 2013-06-23 Abstract: Demands on networking infrastructure are growing exponentially; the drivers are bandwidth hungry rich media applications, inter-data center communications, etc. In this context, it is important to optimally use the bandwidth in wired networks that extensively use LAG/ECMP techniques for bandwidth scaling. This draft explores some of the mechanisms useful for achieving this. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-opsawg-large-flow-load-balancing-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-opsawg-large-flow-load-balanc= ing-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From ramk@Brocade.com Sun Jun 23 09:51:09 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0295A21F9E8A for ; Sun, 23 Jun 2013 09:51:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.265 X-Spam-Level: X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLEMJjcYA-GQ for ; Sun, 23 Jun 2013 09:51:04 -0700 (PDT) Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by ietfa.amsl.com (Postfix) with ESMTP id 2F74D21F9C96 for ; Sun, 23 Jun 2013 09:51:03 -0700 (PDT) Received: from pps.filterd (m0000700 [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r5NGoqAn017225; Sun, 23 Jun 2013 09:50:52 -0700 Received: from hq1wp-exchub01.corp.brocade.com ([144.49.131.13]) by mx0b-000f0801.pphosted.com with ESMTP id 1d5vmag47c-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 23 Jun 2013 09:50:52 -0700 Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXCHUB01.corp.brocade.com (10.70.36.99) with Microsoft SMTP Server (TLS) id 14.2.309.2; Sun, 23 Jun 2013 09:50:51 -0700 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::8c73:93bf:41b4:1443]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Sun, 23 Jun 2013 09:50:50 -0700 From: ramki Krishnan To: "opsawg@ietf.org" Date: Sun, 23 Jun 2013 09:50:49 -0700 Thread-Topic: [OPSAWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-01.txt Thread-Index: Ac5wMBhrRrxEIkDPSii45zqjSJXNWgAAGbBg Message-ID: References: <20130623163826.13640.64829.idtracker@ietfa.amsl.com> In-Reply-To: <20130623163826.13640.64829.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-06-23_06:2013-06-21, 2013-06-23, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1306230156 Cc: Sanjay Khanna , Bhumip Khasnabish , Ning So Subject: Re: [OPSAWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-01.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2013 16:51:09 -0000 Dear All, We have updated the draft with the following information - Editorial information on flow categorization (section 2) - Differences between LAG and ECMP (section 4.1) - Detailed Information Model (section 5) We are looking forward to your comments. -- Thanks, Ramki -----Original Message----- From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of= internet-drafts@ietf.org Sent: Sunday, June 23, 2013 9:38 AM To: i-d-announce@ietf.org Cc: opsawg@ietf.org Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-0= 1.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Operations and Management Area Working Gr= oup Working Group of the IETF. Title : Mechanisms for Optimal LAG/ECMP Component Link Utilizati= on in Networks Author(s) : Ram Krishnan Sanjay Khanna Lucy Yong Anoop Ghanwani Ning So Bhumip Khasnabish Filename : draft-ietf-opsawg-large-flow-load-balancing-01.txt Pages : 22 Date : 2013-06-23 Abstract: Demands on networking infrastructure are growing exponentially; the drivers are bandwidth hungry rich media applications, inter-data center communications, etc. In this context, it is important to optimally use the bandwidth in wired networks that extensively use LAG/ECMP techniques for bandwidth scaling. This draft explores some of the mechanisms useful for achieving this. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancin= g There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-opsawg-large-flow-load-balancing-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-opsawg-large-flow-load-balanc= ing-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg From internet-drafts@ietf.org Tue Jun 25 01:12:56 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5569721F9F4E; Tue, 25 Jun 2013 01:12:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2BTDmKuquq21; Tue, 25 Jun 2013 01:12:55 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D81AB21F9F08; Tue, 25 Jun 2013 01:12:55 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130625081255.4690.57114.idtracker@ietfa.amsl.com> Date: Tue, 25 Jun 2013 01:12:55 -0700 Cc: opsawg@ietf.org Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-rfc5066bis-03.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 08:12:56 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Operations and Management Area Working Gr= oup Working Group of the IETF. Title : Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Author(s) : Edward Beili Filename : draft-ietf-opsawg-rfc5066bis-03.txt Pages : 7 Date : 2013-06-25 Abstract: This document updates RFC 5066. It amends that specification by informing the internet community about the transition of the EFM-CU- MIB module from the IETF Ethernet Interfaces and Hub MIB Working Group to the Institute of Electrical and Electronics Engineers (IEEE) 802.3 working group. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5066bis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-opsawg-rfc5066bis-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-opsawg-rfc5066bis-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Tue Jun 25 16:01:09 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D3D21F9BFF; Tue, 25 Jun 2013 16:01:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.256 X-Spam-Level: X-Spam-Status: No, score=-102.256 tagged_above=-999 required=5 tests=[AWL=0.344, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1P2lEi8xYRzA; Tue, 25 Jun 2013 16:01:09 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D63C21F99F1; Tue, 25 Jun 2013 16:01:09 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130625230108.4936.17272.idtracker@ietfa.amsl.com> Date: Tue, 25 Jun 2013 16:01:08 -0700 Cc: opsawg@ietf.org Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-02.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 23:01:09 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Operations and Management Area Working Gr= oup Working Group of the IETF. Title : Mechanisms for Optimal LAG/ECMP Component Link Utilizati= on in Networks Author(s) : Ram Krishnan Sanjay Khanna Lucy Yong Anoop Ghanwani Ning So Bhumip Khasnabish Filename : draft-ietf-opsawg-large-flow-load-balancing-02.txt Pages : 22 Date : 2013-06-25 Abstract: Demands on networking infrastructure are growing exponentially; the drivers are bandwidth hungry rich media applications, inter-data center communications, etc. In this context, it is important to optimally use the bandwidth in wired networks that extensively use LAG/ECMP techniques for bandwidth scaling. This draft explores some of the mechanisms useful for achieving this. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-opsawg-large-flow-load-balancing-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-opsawg-large-flow-load-balanc= ing-02 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From ramk@Brocade.com Tue Jun 25 16:07:51 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 920CC11E80FB for ; Tue, 25 Jun 2013 16:07:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.264 X-Spam-Level: X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rwi9r4j9I1sn for ; Tue, 25 Jun 2013 16:07:46 -0700 (PDT) Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [67.231.144.122]) by ietfa.amsl.com (Postfix) with ESMTP id DD6B011E817B for ; Tue, 25 Jun 2013 16:07:45 -0700 (PDT) Received: from pps.filterd (m0000542 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id r5PN7VEp018408; Tue, 25 Jun 2013 16:07:44 -0700 Received: from hq1wp-exchub01.corp.brocade.com ([144.49.131.13]) by mx0a-000f0801.pphosted.com with ESMTP id 1d7ewgg6pq-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 25 Jun 2013 16:07:44 -0700 Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by HQ1WP-EXCHUB01.corp.brocade.com (10.70.36.99) with Microsoft SMTP Server (TLS) id 14.2.309.2; Tue, 25 Jun 2013 16:07:43 -0700 Received: from HQ1-EXCH01.corp.brocade.com ([fe80::8c73:93bf:41b4:1443]) by HQ1WP-EXHUB01.corp.brocade.com ([::1]) with mapi; Tue, 25 Jun 2013 16:07:43 -0700 From: ramki Krishnan To: "opsawg@ietf.org" Date: Tue, 25 Jun 2013 16:07:40 -0700 Thread-Topic: [OPSAWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-02.txt Thread-Index: Ac5x9+OIvzLtZ00dRoqIpR+g71XDAQAAD5xg Message-ID: References: <20130625230108.4936.17272.idtracker@ietfa.amsl.com> In-Reply-To: <20130625230108.4936.17272.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C7634EB63EFD984A978DFB46EA5174F2BFFD988A2BHQ1EXCH01corp_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-06-25_08:2013-06-25, 2013-06-25, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1306250216 Cc: "draft-ietf-opsawg-large-flow-load-balancing@tools.ietf.org" Subject: Re: [OPSAWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-02.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jun 2013 23:07:51 -0000 --_000_C7634EB63EFD984A978DFB46EA5174F2BFFD988A2BHQ1EXCH01corp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear All, We have some updates to the draft which includes minimal changes in the fol= lowing areas - Fixed incorrect section references - Section 5.5 - more information on flow export - Section 5.6 - additional techniques for gathering interface cou= nters Your comments are welcome. Thanks, Ramki -----Original Message----- From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of= internet-drafts@ietf.org Sent: Tuesday, June 25, 2013 4:01 PM To: i-d-announce@ietf.org Cc: opsawg@ietf.org Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-0= 2.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Operations and Management Area Working Gro= up Working Group of the IETF. Title : Mechanisms for Optimal LAG/ECMP Component Lin= k Utilization in Networks Author(s) : Ram Krishnan Sanjay Khanna Lucy Yong Anoop Ghanwani Ning So Bhumip Khasnabish Filename : draft-ietf-opsawg-large-flow-load-balancing-0= 2.txt Pages : 22 Date : 2013-06-25 Abstract: Demands on networking infrastructure are growing exponentially; the drivers are bandwidth hungry rich media applications, inter-data center communications, etc. In this context, it is important to optimally use the bandwidth in wired networks that extensively use LAG/ECMP techniques for bandwidth scaling. This draft explores some of the mechanisms useful for achieving this. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancin= g There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-opsawg-large-flow-load-balancing-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-opsawg-large-flow-load-balanc= ing-02 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg --_000_C7634EB63EFD984A978DFB46EA5174F2BFFD988A2BHQ1EXCH01corp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear All,

 

We have some updates to the draft which includes minimal changes in th= e following areas

-   =         Fixed incorrect section referenc= es

-     &n= bsp;     Section 5.5 – more information on flow e= xport

-     = ;      Section 5.6 – additional techniques f= or gathering interface counters

 

Your comments are welcome.

 

Thanks,

Ramki

 

-----Original = Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.o= rg] On Behalf Of internet-drafts@ietf.org
Sent: Tuesday, June 25, 2013 4= :01 PM
To: i-d-announce@ietf.org
Cc: opsawg@ietf.org
Subject: [OPS= AWG] I-D Action: draft-ietf-opsawg-large-flow-load-balancing-02.txt

 

 

A New Internet-Draft is avail= able from the on-line Internet-Drafts directories.

This draft is a work item of the Operations and Management= Area Working Group Working Group of the IETF.

 

   &n= bsp;        Title    = ;       : Mechanisms for Optimal LAG/ECMP Com= ponent Link Utilization in Networks

&= nbsp;           Author(s)=        : Ram Krishnan

          = ;            &n= bsp;   Sanjay Khanna

 =             &nb= sp;            Lucy = Yong

     &n= bsp;            = ;        Anoop Ghanwani

         = ;            &n= bsp;    Ning So

 =             &nb= sp;            Bhumi= p Khasnabish

    =         Filename    =     : draft-ietf-opsawg-large-flow-load-balancing-02.txt

      &nbs= p;     Pages       &= nbsp;   : 22

  &n= bsp;         Date   =          : 2013-06-25

 

Abstr= act:

   Demands on networki= ng infrastructure are growing exponentially; the

   drivers are bandwidth hungry rich media applicatio= ns, inter-data

   center co= mmunications, etc. In this context, it is important to

   optimally use the bandwidth in wired network= s that extensively use

   L= AG/ECMP techniques for bandwidth scaling. This draft explores some

   of the mechanisms useful for ach= ieving this.

 

 

&nbs= p;

 

The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow= -load-balancing

 = ;

There's also a htmlized version availabl= e at:

http://tools.ietf.org/html/draft-ietf-ops= awg-large-flow-load-balancing-02

 

A diff from the previou= s version is available at:

http://www.i= etf.org/rfcdiff?url2=3Ddraft-ietf-opsawg-large-flow-load-balancing-02

 

 

Internet-Draft= s are also available by anonymous FTP at:

ftp://ftp.ietf.org/internet-drafts/<= /a>

 

_______________________________________________

<= p class=3DMsoPlainText>OPSAWG mailing list

OPSAWG@ietf.org

https://www.ietf.org/mailman/= listinfo/opsawg

= --_000_C7634EB63EFD984A978DFB46EA5174F2BFFD988A2BHQ1EXCH01corp_-- From sdanda@cisco.com Thu Jun 27 04:04:28 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9B1121F9CFE for ; Thu, 27 Jun 2013 04:04:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.598 X-Spam-Level: X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCnxb7IcqXtY for ; Thu, 27 Jun 2013 04:04:23 -0700 (PDT) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 52C5B21F9CF0 for ; Thu, 27 Jun 2013 04:04:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4500; q=dns/txt; s=iport; t=1372331063; x=1373540663; h=from:to:cc:subject:date:message-id:mime-version; bh=zzuj173JlEm1aM+ispsUCWwhCsOeneNXu2aAHW/rQkA=; b=OMye/5IkTDibGn+eA/vuMuQ9y4slRLfBG5u/Lr0XNyyikqE5Rd6a/cSF YGCxPqg+hmUo/VKtMYUFvdBy7YyJuSxMOGOJ3oy1l7MCSrkw4QNHoqq1D IdAhOsK7VJiAe/0CGdK1WfgsebzGtwJZBptkvfD6F8sbxbgYF0oa2neAD I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjMFAGobzFGtJXHB/2dsb2JhbABbgkVEMUm/A30WdIIlAQQtTBIBKlYmAQQODROHc7pAjyQxgwlhA6kKgxGCKA X-IronPort-AV: E=Sophos;i="4.87,951,1363132800"; d="scan'208,217";a="227875879" Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-1.cisco.com with ESMTP; 27 Jun 2013 11:04:22 +0000 Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r5RB4M2A010957 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 27 Jun 2013 11:04:22 GMT Received: from xmb-rcd-x14.cisco.com ([169.254.4.194]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Thu, 27 Jun 2013 06:04:22 -0500 From: "Satyanarayana Danda (sdanda)" To: "opsawg@ietf.org" Thread-Topic: Local Authentication at the network device Thread-Index: Ac5zJhMUcRbed1sNTvi+S5IKfitR9Q== Date: Thu, 27 Jun 2013 11:04:22 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.142.105.254] Content-Type: multipart/alternative; boundary="_000_E06F3B652F60A4409C49D8E840BEEC921D6940DBxmbrcdx14ciscoc_" MIME-Version: 1.0 Subject: [OPSAWG] Local Authentication at the network device X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 11:04:29 -0000 --_000_E06F3B652F60A4409C49D8E840BEEC921D6940DBxmbrcdx14ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, In small enterprise deployment, instead of Remote AAA server based authenti= cation, local authentication at the network device can be performed. The device can have a few user authorization parameters and properties whic= h can be used for local authentication/authorization. This optimization is useful for performance and reducing the OPEX and CAPE= X for the customers. However, for this, there are many proprietary solutions. We are seeking feedback or guidance from the WG on standard based solutions= analogous to standard based AAA authentication schemes. Thanks Satya --_000_E06F3B652F60A4409C49D8E840BEEC921D6940DBxmbrcdx14ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

 

In smal= l enterprise deployment, instead of Remote AAA server based authentication,= local authentication at the network device can be performed. 

The dev= ice can have a few user authorization parameters and properties which can b= e used for local authentication/authorization.

This op= timization  is useful for performance and reducing the OPEX and CAPEX = for the customers.  

&n= bsp;

However= , for this, there are many proprietary solutions.  <= /p>

&n= bsp;

We are = seeking feedback or guidance from the WG on standard based solutions analog= ous to standard based AAA authentication schemes. 

&n= bsp;

Thanks<= o:p>

Satya&n= bsp;

 

--_000_E06F3B652F60A4409C49D8E840BEEC921D6940DBxmbrcdx14ciscoc_-- From internet-drafts@ietf.org Thu Jun 27 12:21:21 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BAF811E80EA; Thu, 27 Jun 2013 12:21:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.173 X-Spam-Level: X-Spam-Status: No, score=-102.173 tagged_above=-999 required=5 tests=[AWL=0.427, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wUWDROZmhhP4; Thu, 27 Jun 2013 12:21:20 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D64A11E80D2; Thu, 27 Jun 2013 12:21:20 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.51.p2 Message-ID: <20130627192119.11177.56159.idtracker@ietfa.amsl.com> Date: Thu, 27 Jun 2013 12:21:20 -0700 Cc: opsawg@ietf.org Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-lsn-deployment-03.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 19:21:21 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Operations and Management Area Working Gr= oup Working Group of the IETF. Title : CGN Deployment with BGP/MPLS IP VPNs Author(s) : Victor Kuarsingh John Cianfarani Filename : draft-ietf-opsawg-lsn-deployment-03.txt Pages : 19 Date : 2013-06-27 Abstract: This document specifies a framework to integrate a Network Address Translation layer into an operator's network to function as a Carrier Grade NAT (also known as CGN or Large Scale NAT). The CGN infrastructure will often form a NAT444 environment as the subscriber home network will likely also maintain a subscriber side NAT function. Exhaustion of the IPv4 address pool is a major driver compelling some operators to implement CGN. Although operators may wish to deploy IPv6 to strategically overcome IPv4 exhaustion, near term needs may not be satisfied with an IPv6 deployment alone. This document provides a practical integration model which allows the CGN platform to be integrated into the network meeting the connectivity needs of the subscriber while being mindful of not disrupting existing services and meeting the technical challenges that CGN brings. The model included in this document utilizes BGP/MPLS IP VPNs which allow for virtual routing separation helping ease the CGNs impact on the network. This document does not intend to defend the merits of CGN. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-lsn-deployment There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-opsawg-lsn-deployment-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-opsawg-lsn-deployment-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From melinda.shore@gmail.com Thu Jun 27 12:26:31 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C365B21F9F0A for ; Thu, 27 Jun 2013 12:26:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yDBs1iEwF2H7 for ; Thu, 27 Jun 2013 12:26:30 -0700 (PDT) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id C425621F9EBE for ; Thu, 27 Jun 2013 12:26:29 -0700 (PDT) Received: by mail-pd0-f174.google.com with SMTP id 10so564099pdc.5 for ; Thu, 27 Jun 2013 12:26:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-forwarded-message-id:content-type :content-transfer-encoding; bh=64UupFKW8ypaNGhDQLUqIeh168RyPsT7TJ3UQtZcCWc=; b=ouLQZowR1AeOTSe72wKadqbE97ajLc7H4fKZeyE4tvvP33z4VCzwHUJrkKWgxtXExt FhW+r13Jfppv5LtVXSdQVFFYZr2yE79z19vW59hjSqAxBZku/xqFn5Dh39nUwX1zUDmL BYZQVNiiSxKRCSgXhxW1kjiE2SoygJ4j7Exc4a9dj7FiNLTfMGUGXvQ7A0KNGb1EfS3X eLGPxDurltGRNf62s7Kd5cKyPOqPXVDLxADJSS8LbiUJRyG1mPwe+FrvQ/KIqmsEPylr S6uEdJ9BFhb0Rri5nb5l9dXEhjOxXwuIwyjLWK3MEB+auLIMdnL43T1BO6S6cxOT/0Wb eklA== X-Received: by 10.66.122.99 with SMTP id lr3mr7695600pab.187.1372361189515; Thu, 27 Jun 2013 12:26:29 -0700 (PDT) Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id fp2sm4367905pbb.36.2013.06.27.12.26.27 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 12:26:28 -0700 (PDT) Message-ID: <51CC91E0.3020002@gmail.com> Date: Thu, 27 Jun 2013 11:26:24 -0800 From: Melinda Shore User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "opsawg@ietf.org" References: <20130627192119.11177.56159.idtracker@ietfa.amsl.com> In-Reply-To: <20130627192119.11177.56159.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20130627192119.11177.56159.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [OPSAWG] Fwd: I-D Action: draft-ietf-opsawg-lsn-deployment-03.txt X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 19:26:32 -0000 As we discussed at the last meeting, we'd like to move this version towards working group last call. Please give this a read with that in mind, and provide feedback to the mailing list. Melinda -------- Original Message -------- Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-lsn-deployment-03.txt Date: Thu, 27 Jun 2013 12:21:20 -0700 From: internet-drafts@ietf.org To: i-d-announce@ietf.org CC: opsawg@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF. Title : CGN Deployment with BGP/MPLS IP VPNs Author(s) : Victor Kuarsingh John Cianfarani Filename : draft-ietf-opsawg-lsn-deployment-03.txt Pages : 19 Date : 2013-06-27 Abstract: This document specifies a framework to integrate a Network Address Translation layer into an operator's network to function as a Carrier Grade NAT (also known as CGN or Large Scale NAT). The CGN infrastructure will often form a NAT444 environment as the subscriber home network will likely also maintain a subscriber side NAT function. Exhaustion of the IPv4 address pool is a major driver compelling some operators to implement CGN. Although operators may wish to deploy IPv6 to strategically overcome IPv4 exhaustion, near term needs may not be satisfied with an IPv6 deployment alone. This document provides a practical integration model which allows the CGN platform to be integrated into the network meeting the connectivity needs of the subscriber while being mindful of not disrupting existing services and meeting the technical challenges that CGN brings. The model included in this document utilizes BGP/MPLS IP VPNs which allow for virtual routing separation helping ease the CGNs impact on the network. This document does not intend to defend the merits of CGN. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-lsn-deployment There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-opsawg-lsn-deployment-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-lsn-deployment-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg From melinda.shore@gmail.com Thu Jun 27 13:10:15 2013 Return-Path: X-Original-To: opsawg@ietfa.amsl.com Delivered-To: opsawg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C99D911E80F2 for ; Thu, 27 Jun 2013 13:10:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KW1b8GK83H31 for ; Thu, 27 Jun 2013 13:10:15 -0700 (PDT) Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 52D1311E810C for ; Thu, 27 Jun 2013 13:10:15 -0700 (PDT) Received: by mail-pa0-f54.google.com with SMTP id kx10so1508090pab.41 for ; Thu, 27 Jun 2013 13:10:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-forwarded-message-id:content-type :content-transfer-encoding; bh=IjLPj7GJ2/BFs1SGugT7J5rReZNOuo5h28znLimR+EE=; b=Vaz65NV9CLf/mgRN+mAlV/8LOtubWJTzVt8DrCbpuFAEC630479EfqfSWVPoZ12eag c9WCPKxP0tZlvSjHFU6NsSOAQcTwsFrdaIhu2tu88/CzvBC0p1HbBAJRlnZIqQZ4hDkc OPl26i7znOIBiSCjqAnHNxvLlDPZWZSzIhUY7pO06HcGTI1pvZgZFQ7Wl0SCTbtHMHrH aXA20wMqMu660+LvoqRhW9cgO5hz5eY5E1YtOoI3MBMN0ka+Zf/PzSrxOueVlzgrEkJo xD9YFT0I7elyS0KfQ/4iJN+aUVCKuA4ljZlxFl9xA9LIXcCgVPUz6mocBDN6tYTFAGc4 ihfw== X-Received: by 10.68.252.162 with SMTP id zt2mr7861806pbc.103.1372363815065; Thu, 27 Jun 2013 13:10:15 -0700 (PDT) Received: from spandex.local (216-67-48-180-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.180]) by mx.google.com with ESMTPSA id pl9sm4550470pbc.5.2013.06.27.13.10.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 13:10:14 -0700 (PDT) Message-ID: <51CC9C1F.3090907@gmail.com> Date: Thu, 27 Jun 2013 12:10:07 -0800 From: Melinda Shore User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "opsawg@ietf.org" References: <20130627200752.2986.57190.idtracker@ietfa.amsl.com> In-Reply-To: <20130627200752.2986.57190.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20130627200752.2986.57190.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [OPSAWG] Fwd: opsawg - Requested session has been scheduled for IETF 87 X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jun 2013 20:10:15 -0000 FYI, we've been scheduled to meet 1300-1500 Wednesday afternoon at IETF 87. As is usually the case, this will be a joint meeting of opsawg and opsarea. Melinda