Re: [savi] Gen-ART review of draft-ietf-savi-threat-scope-06

Joel Halpern <joel.halpern@ericsson.com> Thu, 28 March 2013 03:04 UTC

Return-Path: <joel.halpern@ericsson.com>
X-Original-To: savi@ietfa.amsl.com
Delivered-To: savi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6461721F941D; Wed, 27 Mar 2013 20:04:13 -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 2bIi38BJhxaF; Wed, 27 Mar 2013 20:04:12 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 009CB21F85BF; Wed, 27 Mar 2013 20:04:11 -0700 (PDT)
X-AuditID: c618062d-b7f0d6d00000097e-94-5153b32b381a
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id D8.56.02430.B23B3515; Thu, 28 Mar 2013 04:04:11 +0100 (CET)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0318.004; Wed, 27 Mar 2013 23:04:10 -0400
From: Joel Halpern <joel.halpern@ericsson.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [savi] Gen-ART review of draft-ietf-savi-threat-scope-06
Thread-Index: AcwRKxLMGPOwf18pRUizv8st+VLKC4QxHuTAABCsJwAAH6EicAArjFAAAABtFAAAABnuAAAVVisAAAgnlqA=
Date: Thu, 28 Mar 2013 03:04:09 +0000
Message-ID: <6BCE198E4EAEFC4CAB45D75826EFB0760C4AF5@eusaamb101.ericsson.se>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com> <8D23D4052ABE7A4490E77B1A012B63077511F644@mbx-01.win.nominum.com> <8D3D17ACE214DC429325B2B98F3AE71293D36520@MX15A.corp.emc.com> <51531EA4.4030504@joelhalpern.com> <8D3D17ACE214DC429325B2B98F3AE71293D366C6@MX15A.corp.emc.com> <5153222E.30202@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B6307751243D6@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751243D6@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPLMWRmVeSWpSXmKPExsUyuXSPn6725uBAgzu/1Sy2Hl7LbvHuSzuT xdVXn1ksnm2cz2IxpfUkm8XHU2+YLG7+3spisbU71oHD48iR2SweO2fdZfdYsuQnk8e5Kd8Z PV4fmM/qsWtzA1sAWxSXTUpqTmZZapG+XQJXxsSrH9gLJotUTGudy9zA+I6/i5GTQ0LAROJv 52xGCFtM4sK99WxdjFwcQgJHGCX+939gA0kICSxnlPhynwvEZhPQk1j7/jETiC0ioCrx4+Qn FpAGZoFFTBLXt88BaxAWcJXY8eQEG0SRm8TRrkZ2CDtJYvGd62BxFqDm2V9+AQ3i4OAV8JaY 3C4Esfg2s8TL1qXMIDWcAn4ST/7cB6tnBLru+6k1YIuZBcQlbj2ZzwRxtYDEkj3nmSFsUYmX j/+xQtjKEkue7GeBqNeRWLD7ExuErS2xbOFrsHpeAUGJkzOfsExgFJuFZOwsJC2zkLTMQtKy gJFlFSNHaXFqWW66kcEmRmAkHpNg093BuOel5SFGaQ4WJXHeINcLAUIC6YklqdmpqQWpRfFF pTmpxYcYmTg4pRoYgxR3W9xqjl5bsO5J7OdvrXbW9+/LH82T/Cjy3J2zdPv1EmOWmdVW52+s CeMtkn/sffntn0L70zeLeMLe+j999potyD2cSY5/95lghw1ntVZH1J9NsBObXSXIuuwR9yV5 2df+19e+/hx0ofi45bbOrtqWey+/T9W8cOf8XI351UzrAl7kK/lvV2Ipzkg01GIuKk4EAOwS eKGSAgAA
Cc: "McPherson, Danny" <dmcpherson@verisign.com>, "savi@ietf.org" <savi@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Jean-Michel Combes <jeanmichel.combes@gmail.com>, "Black, David" <david.black@emc.com>
Subject: Re: [savi] Gen-ART review of draft-ietf-savi-threat-scope-06
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mailing list for the SAVI working group at IETF <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/savi>, <mailto:savi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/savi>
List-Post: <mailto:savi@ietf.org>
List-Help: <mailto:savi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2013 03:04:13 -0000

I will try to come up with a way to address the MAC move topic.  The challenge is to word it in such a way that it does not imply a new protocol for communicating such a move (Savi was/is prohibited by charter from doing protocol development.)
Yours,
Joel

> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com] 
> Sent: Wednesday, March 27, 2013 10:57 PM
> To: Joel Halpern Direct
> Cc: Black, David; Joel M. Halpern; McPherson, Danny; 
> savi@ietf.org; ietf@ietf.org; gen-art@ietf.org; Jean-Michel 
> Combes; Joel Halpern
> Subject: Re: [savi] Gen-ART review of draft-ietf-savi-threat-scope-06
> 
> On Mar 27, 2013, at 12:45 PM, Joel Halpern Direct 
> <jmh.direct@joelhalpern.com> wrote:
> 
> > Then it will be done.  I will wait for the AD to decide 
> what other changes are needed, and then will either make this 
> change or include it in an RFC Editor note.
> 
> > Old:
> >   If the bridging topologies which connects the switches changes, or
> >   if LACP [IEEE802.3ad] changes which links are used to deliver
> >   traffic, the switch may need to move the SAVI state to a different
> >   port, are the state may need to be moved or reestablished on a
> >   different switch.
> > New:
> >   If the bridging topologies which connects the switches changes, or
> >   if LACP [IEEE802.3ad], VRRP, or other link management
> >   operations, change which links are used to deliver
> >   traffic, the switch may need to move the SAVI state to a different
> >   port, are the state may need to be moved or reestablished on a
> >   different switch.
> 
> I think you probably meant "or", not "are", in the second 
> word of the second-to-last line of the new text.
> 
> As far as I am concerned, given that David is happy with your 
> recent change, I'm happy with it too.   However, since you 
> are asking, if you were willing to also accommodate David's 
> other request (see below) by adding some text to the document 
> in section 5, that would be an added bonus:
> 
> > A paragraph has been added to 5.2.3 to address all three of 
> the above concerns.   I guess that's ok, but I would have 
> liked to see some text pointing out that a MAC move can be 
> detected by the switches and used to update SAVI state about 
> which port(s) a MAC is accessed through.
> 
> So if you can do this, it would be much appreciated; if you 
> can't do it, I think the document is valuable enough to move 
> forward without this additional work.
> 
>