From Internet-Drafts@ietf.org Wed Mar 2 19:15:02 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C2713A6927; Wed, 2 Mar 2011 19:15:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.579 X-Spam-Level: X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5V09jWvDIq7Q; Wed, 2 Mar 2011 19:15:01 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A054A3A6403; Wed, 2 Mar 2011 19:15:01 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.12 Message-ID: <20110303031501.31633.57427.idtracker@localhost> Date: Wed, 02 Mar 2011 19:15:01 -0800 Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-threat-scope-04.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2011 03:15:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Address Validation Improvements Working Group of the IETF. Title : SAVI Threat Scope Author(s) : D. McPherson, et al. Filename : draft-ietf-savi-threat-scope-04.txt Pages : 22 Date : 2011-03-02 Source Address Validation Improvement (SAVI) effort aims to complement ingress filtering with finer-grained, standardized IP source address validation. This document describes threats enabled by IP source address spoofing both in the global and finer-grained context, describes currently available solutions and challenges, and provides a starting point analysis for finer-grained (host granularity) anti-spoofing work. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-threat-scope-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-savi-threat-scope-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-03-02190454.I-D@ietf.org> --NextPart-- From jmh@joelhalpern.com Wed Mar 2 19:54:00 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03D6C3A6948 for ; Wed, 2 Mar 2011 19:54:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.383 X-Spam-Level: X-Spam-Status: No, score=-102.383 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6N+tZ2Nylg3 for ; Wed, 2 Mar 2011 19:53:59 -0800 (PST) Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by core3.amsl.com (Postfix) with ESMTP id 1DB0E3A6947 for ; Wed, 2 Mar 2011 19:53:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 718B83245DAA for ; Wed, 2 Mar 2011 19:55:06 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net Received: from [10.10.10.101] (pool-71-161-51-81.clppva.btas.verizon.net [71.161.51.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id ED1713245091 for ; Wed, 2 Mar 2011 19:55:05 -0800 (PST) Message-ID: <4D6F111A.8080500@joelhalpern.com> Date: Wed, 02 Mar 2011 22:55:06 -0500 From: "Joel M. Halpern" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.14) Gecko/20110221 Lightning/1.0b2 Thunderbird/3.1.8 MIME-Version: 1.0 To: SAVI Mailing List Content-Type: multipart/mixed; boundary="------------050101050900050105080702" Subject: [savi] Fwd: I-D Action:draft-ietf-savi-threat-scope-04.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2011 03:54:00 -0000 This is a multi-part message in MIME format. --------------050101050900050105080702 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit As per this announcement that went to the SAVI list, there is a new verison of the threats document. This addresses, to the best of our ability, and within the agreements of the working group, the comments received during the WG last call. Chairs, I believe it is back to you. Joel -------- Original Message -------- Subject: [savi] I-D Action:draft-ietf-savi-threat-scope-04.txt Date: Wed, 02 Mar 2011 19:15:01 -0800 From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org CC: savi@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Address Validation Improvements Working Group of the IETF. Title : SAVI Threat Scope Author(s) : D. McPherson, et al. Filename : draft-ietf-savi-threat-scope-04.txt Pages : 22 Date : 2011-03-02 Source Address Validation Improvement (SAVI) effort aims to complement ingress filtering with finer-grained, standardized IP source address validation. This document describes threats enabled by IP source address spoofing both in the global and finer-grained context, describes currently available solutions and challenges, and provides a starting point analysis for finer-grained (host granularity) anti-spoofing work. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-threat-scope-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --------------050101050900050105080702 Content-Type: Message/External-body; name="draft-ietf-savi-threat-scope-04.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="draft-ietf-savi-threat-scope-04.txt" Content-Type: text/plain Content-ID: <2011-03-02190454.I-D@ietf.org> --------------050101050900050105080702 Content-Type: text/plain; name="Attached Message Part" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Attached Message Part" _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi --------------050101050900050105080702-- From junbi@tsinghua.edu.cn Fri Mar 4 07:21:53 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 907E13A69DA for ; Fri, 4 Mar 2011 07:21:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.104 X-Spam-Level: X-Spam-Status: No, score=-101.104 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_DSN=1.495, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjlP2qckiR9A for ; Fri, 4 Mar 2011 07:21:52 -0800 (PST) Received: from smtp.tsinghua.edu.cn (smtp.tsinghua.edu.cn [166.111.8.81]) by core3.amsl.com (Postfix) with ESMTP id 6BFCF3A69C7 for ; Fri, 4 Mar 2011 07:21:52 -0800 (PST) Received: from th024090.ip.tsinghua.edu.cn ([59.66.24.90] helo=junbiVAIOz138) by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from ) id 1PvWqA-00080T-C2; Fri, 04 Mar 2011 23:22:50 +0800 Message-ID: <6ED684A12916412D8A61C05AAA9CED48@junbiVAIOz138> From: "Jun Bi" To: "Mikael Abrahamsson" , "Jean-Michel Combes" References: In-Reply-To: Date: Fri, 4 Mar 2011 23:22:51 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3502.922 X-MIMEOLE: Produced By Microsoft MimeOLE V15.4.3502.922 Cc: SAVI Mailing List , Christian Vogt Subject: Re: [savi] WGLC: draft-ietf-savi-framework-02 X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 15:21:53 -0000 Hi Mikaeal, Thank you for emphasize it. There is a new section in 02 version about mix scenario. The detail mechanism needs to be fixed in solution documents. thanks, Jun -----原始邮件----- From: Mikael Abrahamsson Sent: Monday, February 28, 2011 10:11 PM To: Jean-Michel Combes Cc: SAVI Mailing List ; Christian Vogt Subject: Re: [savi] WGLC: draft-ietf-savi-framework-02 On Wed, 16 Feb 2011, Jean-Michel Combes wrote: I have read the draft and found it sensible and I would like to voice my support for it. I would be more comfortable if it stated more explicitly that the IP/mac binding is important, but I felt that it was at least implicit that this was the ultimate goal. For instance, I think it's important that on a port where DHCP(v6) is specified to be mandatory, no traffic should be allowed from an IP/mac that doesn't correspond to something that has been handed out by stateful DHCP. I hope this is implicit, but if it's expressly stated in the document, I missed it. > Folks, > > This is a 2 weeks working group last call for the "Source Address > Validation Improvement Framework" document. > Please, don't hesitate to review the draft and to say whether you are > in favor advancing the draft or not. > > Thanks. > > Christian & Jean-Michel. > _______________________________________________ > savi mailing list > savi@ietf.org > https://www.ietf.org/mailman/listinfo/savi > -- Mikael Abrahamsson email: swmike@swm.pp.se _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi From junbi@tsinghua.edu.cn Fri Mar 4 07:22:59 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEB173A69E2 for ; Fri, 4 Mar 2011 07:22:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.103 X-Spam-Level: X-Spam-Status: No, score=-101.103 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, DNS_FROM_RFC_DSN=1.495, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XIM9rIR8LAsd for ; Fri, 4 Mar 2011 07:22:58 -0800 (PST) Received: from smtp.tsinghua.edu.cn (smtp.tsinghua.edu.cn [166.111.8.80]) by core3.amsl.com (Postfix) with ESMTP id C3E163A69DA for ; Fri, 4 Mar 2011 07:22:57 -0800 (PST) Received: from th024090.ip.tsinghua.edu.cn ([59.66.24.90] helo=junbiVAIOz138) by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from ) id 1PvWrL-0007Ju-2n; Fri, 04 Mar 2011 23:24:03 +0800 Message-ID: From: "Jun Bi" To: "Jean-Michel Combes" , "SAVI Mailing List" References: In-Reply-To: Date: Fri, 4 Mar 2011 23:24:04 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3502.922 X-MIMEOLE: Produced By Microsoft MimeOLE V15.4.3502.922 Cc: Christian Vogt Subject: Re: [savi] WGLC: draft-ietf-savi-framework-02 X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 15:22:59 -0000 A new version will be delivered soon by taking comments in WGLC. thanks, Jun -----原始邮件----- From: Jean-Michel Combes Sent: Monday, February 28, 2011 10:13 PM To: SAVI Mailing List Cc: Christian Vogt Subject: Re: [savi] WGLC: draft-ietf-savi-framework-02 Please find my review of this draft below (my comments are mostly minor/editorial ones): Source Address Validation Improvement Framework draft-ietf-savi-framework-02 Abstract The Source Address Validation Improvement method was developed to complement ingress filtering with finer-grained, standardized IP source address validation. This document describes and motivates the design of the SAVI method. [snip] 1. Introduction Since IP source addresses are used by hosts and network entities to determine the origin of a packet and as a destination for return data, spoofing of IP source addresses can enable impersonation, concealment, and malicious traffic redirection. Unfortunately, the Internet architecture does not prevent IP source address spoofing. Maybe, add a reference to the treats doc [draft-ietf-savi-threat-scope] at the end of the sentence. Since the IP source address of a packet generally takes no role in forwarding the packet, it can be selected arbitrarily by the sending host without jeopardizing packet delivery. Extra methods are necessary for IP source address validation, to augment packet forwarding with an explicit check of whether a given packet's IP source address is legitimate. IP source address validation can happen at different granularity: Ingress filtering [BCP38], a widely deployed standard for IP source address validation, functions at the coarse granularity of networks. It verifies that the prefix of an IP source address routes to the network from which the packet was received. An advantage of ingress filtering is simplicity: The decision of whether to accept or to s/"is simplicity: The decision of"/"is simplicity: the decision of" reject an IP source address can be made solely based on the information available from routing protocols. However, the "information available from routing protocols": maybe add a reference to RFC3704 simplicity comes at the cost of not being able to validate IP source addresses at a finer granularity, due to the aggregated nature of the information available from routing protocols. Finer-grained IP source address validation would be helpful to enable IP-source- address-based authentication, authorization, and host localization, as well as to efficiently identify misbehaving hosts. Partial solutions [BA2007] exist for finer-grained IP source address validation, but are proprietary and hence often unsuitable for corporate procurement. [snip] 3.1. IP Address Assignment Methods Since the SAVI method traces IP address assignment packets, it necessarily needs to incorporate logic that is specific to particular IP address assignment methods. However, developing SAVI method variants for each IP address assignment method is alone not sufficient, since multiple IP address assignment methods may co-exist on a given link. The SAVI method hence comes in multiple variants: for links with Stateless Address Autoconfiguration, for links with DHCP, for links with Secure Neighbor Discovery, and for links that use any combination of IP address assignment methods. Maybe add a reference for each IP address assignment method. Maybe, even if this is out of scope from the WG charter, add IKEv2 [RFC5996][RFC5739] as IP address assignment method. I have especially in mind Mobile Node's Home Address assignment based on IKEv2 [RFC5026]. The reason to develop SAVI method variants for each single IP address configuration method, in addition to the variant that handles all IP address assignment methods, is to minimize the complexity of the common case: Many link deployments today either are constrained to a s/"common case: Many link deployments"/"common case: many link deployments" single IP address assignment methods or, equivalently from the perspective of the SAVI method, separate IP address assignment methods into different IP address prefixes. The SAVI method for such links can be simpler than the SAVI method for links with multiple IP address assignment methods per IP address prefix. [snip] 4. Scalability Optimizations The preference to locate a SAVI instance close to hosts implies that multiple SAVI instances must be able to co-exist in order to support large links. Although the model of the SAVI method is independent of the number of SAVI instances per link, co-existence of multiple SAVI instances without further measures can lead to higher-than-necessary memory requirements: Since a SAVI instance creates bindings for the s/"memory requirements: Since a SAVI instance creates"/"memory requirements: since a SAVI instance creates" IP source addresses of all hosts on a link, bindings are replicated if multiple SAVI instances co-exist on the link. High memory requirements, in turn, increase the cost of a SAVI instance. This is problematic in particular for SAVI instances that are located on a switch, since it may significantly increase the cost of such a switch. [snip] In the example of figure Figure 1, the protection perimeter encompasses one of the legacy switches, located in the middle of the depicted link topology. This enables a single, unpartitioned protection perimeter. A single protection perimeter minimizes memory requirements for the SAVI instances because every binding is kept only once, namely, by the SAVI instance that attaches to the host being validated. Excluding the legacy switch from the protection perimeter would result in two smaller protection perimeters to the left and to the right of the depicted link topology. The memory requirements for the SAVI instances would then be higher: Since IP s/"then be higher: Since IP"/"then be higher: since IP" source address validation would be activated on the two ports connecting to the legacy switch, the SAVI instances adjacent to the legacy switch would replicate all bindings from the respectively other protection perimeter. The reason why it is possible to include the legacy switch in the protection perimeter is because the depicted link topology guarantees that packets cannot enter the protection perimeter via this legacy switch. Without this guarantee, the legacy switch would have to be excluded from the protection perimeter in order to ensure that packets entering the protection perimeter undergo IP source address validation. 5. Reliability Optimizations [snip] To limit the disruption that missing bindings for legitimate IP addresses can have, the SAVI method includes a mechanism for reactive binding creation based on regular packets. This mechanism supplements the proactive binding creation based on IP address configuration packets. Reactive binding creation occurs when a SAVI instances recognizes excessive drops of regular packets originating from the same IP address. The SAVI instance then verifies whether said IP address is unique on the link. How the verification is carried out depends on the IP address configuration method that the SAVI instance supports: The SAVI method variant for Stateless s/"SAVI instance supports: The SAVI method variant"/"SAVI instance supports. The SAVI method variant" Address Autoconfiguration and for Secure Neighbor Discovery verifies an IP address through the Duplicate Address Detection procedure. The SAVI method variant for DHCP verifies an IP address through a DHCP Lease Query message exchange with the DHCP server. If verification indicates that the IP address is unique on the link, the SAVI instance creates a binding for the IP address. Otherwise, no binding is created, and packets sent from the IP address continue to be dropped. 6. Mix Scenario While multiple assignment methods can be used on the same link, the SAVI device may have to deal with a mix of binding discovery methods. if the address prefix used for each assignment method is different, s/"if the address prefix used for each assignment method"/"If the address prefix used for each assignment method" mix scenario can handle the same as scenario with only one assignment method. If different address assignment methods are used to assign addresses from the same prefix, additional considerations are needed because one binding mechanism may create a binding violating an existing binding from another binding mechanism, e.g., binding from SAVI-FCFS may violate binding from SAVI-DHCP. Thus, the collision Maybe, add references for SAVI-FCFS and SAVI-DHCP. between different SAVI mechanisms in mix scenario must be handled in case more than one address assignment method is used to assign addresses from the same prefix. [snip] A Security Considerations section is missing. An IANA Considerations section is missing too. [snip] 8. References The References section must be split into an Informative References section and a Normative References section. [BA2007] Baker, F., "Cisco IP Version 4 Source Guard", IETF Internet draft (work in progress), November 2007. [BCP38] Paul, P. and D. Senie, "Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing", RFC 2827, BCP 38, May 2000. [snip] Best regards. JMC. 2011/2/25 Jean-Michel Combes : > Folks, > > only 4 days before the end of this WGLC and no feedback for the moment ... > > This document is important for the WG: > - all solutions will have to be compliant with it > - without feedback, it will be impossible to move forward it (i.e. AD > review, IESG review) > - the consequence is that it will be impossible to move forward the > solutions specs > > So, please, review it (it's a short document, only 12 pages) and send > your opinion on the ML. > > Thanks. > > Christian & Jean-Michel. > > > > 2011/2/16 Jean-Michel Combes : >> Folks, >> >> This is a 2 weeks working group last call for the "Source Address >> Validation Improvement Framework" document. >> Please, don't hesitate to review the draft and to say whether you are >> in favor advancing the draft or not. >> >> Thanks. >> >> Christian & Jean-Michel. >> > _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi From junbi@cernet.edu.cn Fri Mar 4 07:23:09 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D5B93A6A3F for ; Fri, 4 Mar 2011 07:23:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.902 X-Spam-Level: X-Spam-Status: No, score=-99.902 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HAS_XAIMC=2.696, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2ad3XzbP+vS for ; Fri, 4 Mar 2011 07:23:08 -0800 (PST) Received: from cernet.edu.cn (cernet.edu.cn [202.112.39.2]) by core3.amsl.com (Postfix) with SMTP id 8F7F23A69DA for ; Fri, 4 Mar 2011 07:23:07 -0800 (PST) Received: from junbiVAIOz138([59.66.24.90]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm74d714548; Fri, 04 Mar 2011 23:23:45 +0800 Message-ID: <5CEBE349E2B244349EA5282900E9A35D@junbiVAIOz138> From: "Jun Bi" To: "Frank Xia" , "'Jean-Michel Combes'" , "'SAVI Mailing List'" References: <001401cbd547$18b7e3d0$5922c10a@china.huawei.com> In-Reply-To: <001401cbd547$18b7e3d0$5922c10a@china.huawei.com> Date: Fri, 4 Mar 2011 23:23:40 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3502.922 X-MIMEOLE: Produced By Microsoft MimeOLE V15.4.3502.922 X-AIMC-AUTH: junbi X-AIMC-MAILFROM: junbi@cernet.edu.cn X-AIMC-Msg-ID: 7aDr6vZB Cc: 'Christian Vogt' Subject: Re: [savi] WGLC: draft-ietf-savi-framework-02 X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 15:23:09 -0000 Hi Frank, This will be mentioned in the new version. thanks, Jun -----原始邮件----- From: Frank Xia Sent: Saturday, February 26, 2011 7:52 AM To: 'Jean-Michel Combes' ; 'SAVI Mailing List' Cc: 'Christian Vogt' Subject: Re: [savi] WGLC: draft-ietf-savi-framework-02 Hi Guys I support this draft to advance. At the same time, I am not sure if these scenarios are covered : 1)A legacy switch to which hosts are attaching uses two trunked ports to connect to SAVI switch. 2)STP runs among switches, and a link failure happens. BR Frank -----Original Message----- From: savi-bounces@ietf.org [mailto:savi-bounces@ietf.org] On Behalf Of Jean-Michel Combes Sent: Friday, February 25, 2011 9:16 AM To: SAVI Mailing List Cc: Christian Vogt Subject: Re: [savi] WGLC: draft-ietf-savi-framework-02 Folks, only 4 days before the end of this WGLC and no feedback for the moment ... This document is important for the WG: - all solutions will have to be compliant with it - without feedback, it will be impossible to move forward it (i.e. AD review, IESG review) - the consequence is that it will be impossible to move forward the solutions specs So, please, review it (it's a short document, only 12 pages) and send your opinion on the ML. Thanks. Christian & Jean-Michel. 2011/2/16 Jean-Michel Combes : > Folks, > > This is a 2 weeks working group last call for the "Source Address > Validation Improvement Framework" document. > Please, don't hesitate to review the draft and to say whether you are > in favor advancing the draft or not. > > Thanks. > > Christian & Jean-Michel. > _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi From jmh@joelhalpern.com Sat Mar 5 08:45:29 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F0503A6AA1 for ; Sat, 5 Mar 2011 08:45:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.409 X-Spam-Level: X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JWzUmmv5Ewhi for ; Sat, 5 Mar 2011 08:45:28 -0800 (PST) Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by core3.amsl.com (Postfix) with ESMTP id 8EC023A6A8C for ; Sat, 5 Mar 2011 08:45:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 076E23244927; Sat, 5 Mar 2011 08:46:38 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net Received: from [10.10.10.101] (pool-71-161-51-81.clppva.btas.verizon.net [71.161.51.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id EB977324410A; Sat, 5 Mar 2011 08:46:36 -0800 (PST) Message-ID: <4D7268E9.8000202@joelhalpern.com> Date: Sat, 05 Mar 2011 11:46:33 -0500 From: "Joel M. Halpern" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.14) Gecko/20110221 Lightning/1.0b2 Thunderbird/3.1.8 MIME-Version: 1.0 To: draft-ietf-savi-fcfs@tools.ietf.org, SAVI Mailing List References: <4D71CDE6.1000707@joelhalpern.com> <4D71FF5A.8040800@it.uc3m.es> In-Reply-To: <4D71FF5A.8040800@it.uc3m.es> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [savi] SAVI FCFS & Logging X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2011 16:45:29 -0000 I asked the SAVI FCFS the question below. In response they quite reasonably asked that I provide text. Following the note excerpt is the suggestion on placement and text. THe text could include a reference to the savi threats document. I was not sure if that would be helpful, so I left it out. Also, as logging is basically an internal activity, I have written this suggestion as non-normative text. > El 05/03/11 6:45, Joel M. Halpern escribió: >> Looking at the traceability issues we raise in the threats document, >> and looking at the uses I see people wanting to make of SAVI for >> SLAAC, should we put some descriptive (not normative) text into SAVI >> FCFS that talks about loggin? >> >> I wanted to check with you folks directly before raising this on the >> list. >> >> Thank you, >> Joel I would suggest adding a section between 2.4 and 2.5 (i.e., it would be 2.5, and the current 2.5 SAVI enforcement perimeter would become 2.6.) --------- 2.x SAVI Logging While the primary goal of SAVI is simply to prevent improper use of IP addresses, a secondary goal is to assist in traceability for determining who an imp-roper actor is. For example, if a remote site reports that a DoS (or component of a DDoS) is coming from the SAVI site, SAVI enforcement can be a useful component in a response. In order to support these and other similar activities, it is a good idea if SAVI devices perform logging of the creation, modification, or removal of address bindings. Any protocol support, such as SYSLOG support for sending those logs to a common server, would be a topic for a future separate document. ----- If instead we want to make that normative, we could put a SHOULD in and put this in section 3.2.6 instead. In addition, it would seem useful to add a short paragraph in the security considerations section. (If Denial of service attacks and Residual threats were 4.1 and 4.2, then I would would att this as 4.3 Security Logging) ------------- In order to improve the integration of SAVI into an overall security environment, and enable response to additional indirect security issues which SAVI can help ameliorate, it is helpful if SAVI systems log the creation, modification, and deletion of binding entries. --------- I realize this basically duplicates the 2.x text. I think it deserves mention in the security considerations, because it is a security consideration. But I don't think that should be the first occurrence. If the duplication is bothersome, then just use the 2.x text. Thank you, Joel From jeanmichel.combes@gmail.com Mon Mar 7 05:10:51 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71E733A67A8 for ; Mon, 7 Mar 2011 05:10:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.645 X-Spam-Level: X-Spam-Status: No, score=-102.645 tagged_above=-999 required=5 tests=[AWL=0.954, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zyaSQeDNguPN for ; Mon, 7 Mar 2011 05:10:50 -0800 (PST) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 75CC53A67B4 for ; Mon, 7 Mar 2011 05:10:50 -0800 (PST) Received: by wyb42 with SMTP id 42so4520771wyb.31 for ; Mon, 07 Mar 2011 05:12:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=0bTRKsVDmY0o+sbp/6hfknXrNp3I/d/sbnm7lGIKhAY=; b=D3Q0HyqcC/sIe9cCn1bmVEKnbSPMny+CIvjestYHFMgytESSsdEmwAoee4zsqMRFP3 bh6HW8KkO0+9VO1+/pzcfhtrccey2lLpiBDdN0AI0Twk6hyQOWNai41coDeAlbKUAcY8 a7mNDOuqE1i4hZdRb4Z7ftBdNU7h08feq2r2U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=rUSuVS70+d5+WdcLmLKn8KLfxXhglA3O9neiU3Q3pQ95hPjzOD4EGBEBkplk9VPCNK IdzSU81+cRf88nmWBosBI0QVg5q0DD8PID5upss1YxXrf3jromc9V9zaVvYkvcrO4R9q NlcRj7dHqMHH9bD+XkytgDncG4AXe3xlpkwjk= MIME-Version: 1.0 Received: by 10.216.145.90 with SMTP id o68mr2332783wej.77.1299503523176; Mon, 07 Mar 2011 05:12:03 -0800 (PST) Received: by 10.216.64.130 with HTTP; Mon, 7 Mar 2011 05:12:03 -0800 (PST) Date: Mon, 7 Mar 2011 14:12:03 +0100 Message-ID: From: Jean-Michel Combes To: SAVI Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Christian Vogt Subject: [savi] IETF 80: Call for presentations X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2011 13:10:52 -0000 Folks, A SAVI session has been scheduled for the next IETF meeting: THURSDAY, March 31, 2011 1520-1720 =A0Afternoon Session II Congress Hall I =A0 INT savi =A0 =A0 =A0 =A0 Source Address Validation Impr= ovements WG People wishing to have a slot for a presentation, please, send an email to the chairs (please, provide also the title of the presentation and the time you would need) by Wednesday, March 16. Thanks. Christian & JMC. From Internet-Drafts@ietf.org Sat Mar 12 14:00:04 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7492C3A68DA; Sat, 12 Mar 2011 14:00:04 -0800 (PST) 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.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dA0ocWedOAf6; Sat, 12 Mar 2011 14:00:02 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32F843A68AB; Sat, 12 Mar 2011 14:00:02 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.12 Message-ID: <20110312220002.13578.57807.idtracker@localhost> Date: Sat, 12 Mar 2011 14:00:02 -0800 Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-framework-03.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Mar 2011 22:00:04 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Address Validation Improvements Working Group of the IETF. Title : Source Address Validation Improvement Framework Author(s) : J. Wu, et al. Filename : draft-ietf-savi-framework-03.txt Pages : 14 Date : 2011-03-12 The Source Address Validation Improvement method was developed to complement ingress filtering with finer-grained, standardized IP source address validation. This document describes and motivates the design of the SAVI method. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-framework-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-savi-framework-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-03-12135345.I-D@ietf.org> --NextPart-- From junbi@tsinghua.edu.cn Sun Mar 13 00:29:49 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C778C3A6AEF; Sun, 13 Mar 2011 00:29:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.103 X-Spam-Level: X-Spam-Status: No, score=-101.103 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, DNS_FROM_RFC_DSN=1.495, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51XjE6jqGeuA; Sun, 13 Mar 2011 00:29:48 -0800 (PST) Received: from smtp.tsinghua.edu.cn (smtp.tsinghua.edu.cn [166.111.8.81]) by core3.amsl.com (Postfix) with ESMTP id 9BE3A3A6AEE; Sun, 13 Mar 2011 00:29:48 -0800 (PST) Received: from th024190.ip.tsinghua.edu.cn ([59.66.24.190] helo=junbiVAIOz138) by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from ) id 1Pyfqj-0005AG-2c; Sun, 13 Mar 2011 15:36:25 +0800 Message-ID: <0177702DCDF6455B96ECAA78CA1A7AD4@junbiVAIOz138> From: "Jun Bi" To: , References: <20110312220002.13578.57807.idtracker@localhost> In-Reply-To: <20110312220002.13578.57807.idtracker@localhost> Date: Sun, 13 Mar 2011 15:26:43 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 1 X-MSMail-Priority: High Importance: High X-Mailer: Microsoft Windows Live Mail 15.4.3502.922 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922 Cc: savi@ietf.org Subject: Re: [savi] I-D Action:draft-ietf-savi-framework-03.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2011 08:29:49 -0000 Dear WG members, A new version of savi-framework was submitted based on comments received during WGLC Thanks to people who provide valuable comments. thanks, Jun Bi -----原始邮件----- From: Internet-Drafts@ietf.org Sent: Sunday, March 13, 2011 6:00 AM To: i-d-announce@ietf.org Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-framework-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Address Validation Improvements Working Group of the IETF. Title : Source Address Validation Improvement Framework Author(s) : J. Wu, et al. Filename : draft-ietf-savi-framework-03.txt Pages : 14 Date : 2011-03-12 The Source Address Validation Improvement method was developed to complement ingress filtering with finer-grained, standardized IP source address validation. This document describes and motivates the design of the SAVI method. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-framework-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi From elevyabe@cisco.com Mon Mar 14 06:47:33 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5BB23A6D23 for ; Mon, 14 Mar 2011 06:47:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wm-m8ErXzuvX for ; Mon, 14 Mar 2011 06:47:33 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id AED983A68ED for ; Mon, 14 Mar 2011 06:47:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=elevyabe@cisco.com; l=3568; q=dns/txt; s=iport; t=1300110536; x=1301320136; h=message-id:date:from:mime-version:to:cc:subject; bh=U77DsCXRwixOId5eeEfSLv6fs2OecUUgb/cYtInYd+s=; b=LBSfIw/E+4DgFD3Cj1iC3MUYc53QJBfXTlvOepgLQq6AGGQznumjh907 myuACWyUkClaflme7x8QYZXh6nEP9WxqJRuTU+/gRiEYiBDEJpfB5o4Rz T6o8+dWPQsQXVC8TV+JOoZRLvsmUMsCYit4nj8d9Nbv5+v4ya4/jfZKKE 4=; X-Files: None : None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao0EAKq5fU2Q/khNgWdsb2JhbACEPKFJFAEBFiYlo3eLG5A3hGx2BIxSg04G X-IronPort-AV: E=Sophos;i="4.62,316,1297036800"; d="eml'208?scan'208,208";a="79083541" Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 14 Mar 2011 13:48:55 +0000 Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2EDmthX023943; Mon, 14 Mar 2011 13:48:55 GMT Received: from xmb-ams-105.cisco.com ([144.254.74.80]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Mar 2011 14:48:55 +0100 Received: from [144.254.53.230] ([144.254.53.230]) by xmb-ams-105.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Mar 2011 14:48:55 +0100 Message-ID: <4D7E1CCA.8050502@cisco.com> Date: Mon, 14 Mar 2011 14:48:58 +0100 From: Eric Levy-Abegnoli User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: SAVI Mailing List Content-Type: multipart/mixed; boundary="------------060901050100010407070808" X-OriginalArrivalTime: 14 Mar 2011 13:48:55.0222 (UTC) FILETIME=[8F735D60:01CBE24E] Cc: Guang Yao Subject: [savi] [Fwd: New Version Notification for draft-bi-savi-mix-04] X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2011 13:47:33 -0000 This is a multi-part message in MIME format. --------------060901050100010407070808 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi This this an updated version of "SAVI for Mixed Address Assignment Methods Scenario" Besides some text cleanup to reflect the outcome of ieft79, the main change is around savi-switch defending address or address range, to provide alternate (to FCFS) prority scheme, when the address spaces betweeen address asignment methods overlap (which the document does not recommend). Comments welcome Thanks Eric --------------060901050100010407070808 Content-Type: message/rfc822; name="New Version Notification for draft-bi-savi-mix-04.eml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="New Version Notification for draft-bi-savi-mix-04.eml" X-Account-Key: account2 X-Mozilla-Keys: Received: from xbh-ams-201.cisco.com ([144.254.75.7]) by xmb-ams-105.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Mar 2011 11:43:30 +0100 Received: from xbh-rcd-102.cisco.com ([72.163.62.139]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Mar 2011 11:43:30 +0100 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Mar 2011 05:43:25 -0500 Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-4.cisco.com with ESMTP; 14 Mar 2011 10:43:25 +0000 Received: from sj-inbound-b.cisco.com (sj-inbound-b.cisco.com [128.107.234.205]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2EAhOiR031932 for ; Mon, 14 Mar 2011 10:43:25 GMT Authentication-Results: sj-inbound-b.cisco.com; dkim=neutral (message not signed) header.i=none X-from-outside-Cisco: 64.170.98.32 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnUAAE6OfU1AqmIgi2dsb2JhbACEPZRAAQGNCRQBAQEKCwsHEgcgpCiLG5AKgSeDRXYEhSuHJw X-IronPort-AV: E=Sophos;i="4.62,315,1297036800"; d="scan'208";a="227619757" Received: from mail.ietf.org ([64.170.98.32]) by sj-inbound-b.cisco.com with ESMTP; 14 Mar 2011 10:43:24 +0000 Received: by core3.amsl.com (Postfix, from userid 30) id DDA6D3A6953; Mon, 14 Mar 2011 03:42:00 -0700 (PDT) From: IETF I-D Submission Tool To: elevyabe@cisco.com Cc: junbi@cernet.edu.cn, yaoguang.china@gmail.com, jmh@joelhalpern.com Subject: New Version Notification for draft-bi-savi-mix-04 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20110314104200.DDA6D3A6953@core3.amsl.com> Date: Mon, 14 Mar 2011 03:42:00 -0700 (PDT) Return-Path: wwwrun@core3.amsl.com X-OriginalArrivalTime: 14 Mar 2011 10:43:26.0027 (UTC) FILETIME=[A5EEF9B0:01CBE234] A new version of I-D, draft-bi-savi-mix-04.txt has been successfully submitted by Eric Levy-Abegnoli and posted to the IETF repository. Filename: draft-bi-savi-mix Revision: 04 Title: SAVI for Mixed Address Assignment Methods Scenario Creation_date: 2011-03-14 WG ID: Independent Submission Number_of_pages: 10 Abstract: This document reviews how multiple address discovery methods can coexist in a single savi device and collisions are resolved when the same binding entry is discovered by two or more methods. The IETF Secretariat. --------------060901050100010407070808-- From jeanmichel.combes@gmail.com Tue Mar 15 02:56:00 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 830C93A6B9F for ; Tue, 15 Mar 2011 02:56:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.836 X-Spam-Level: X-Spam-Status: No, score=-102.836 tagged_above=-999 required=5 tests=[AWL=0.763, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pRX9joY8Zntr for ; Tue, 15 Mar 2011 02:55:59 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 872C53A69E3 for ; Tue, 15 Mar 2011 02:55:59 -0700 (PDT) Received: by wyb42 with SMTP id 42so389450wyb.31 for ; Tue, 15 Mar 2011 02:57:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=lvoJGGef2aG5L0tp9+Rtl8kT5yCGOvgGRAczRY+1if0=; b=N2Qy7VkztYhUgMwUjsf6FhaFywkt8CjsAYlLR2PghoFknm79LxktU9yeceHUMNaq1e DdYKGHx2XaUSZvLhSGzt6v0xQ0vPyu2Px75eUkEbpInzSVwMkIyVd+3uMk4JOLQ90alk Pme3qXDIrWqcHegvJailY9KoJiVkcRJJKjq4g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SW4aMoulZlf9/NvvlRRKGcrYufUsdaCGLo2lfo/NBcI3oQCZcTdsRnI7QBNJDhNFXv OvADevd+zw9dJOyFdNgSOX3cowib6Hs7FUK87aTTV2ya+s8ZeOy9rqyjuPe0dUQ49v32 I//OVIhmKUyFet/E2cz2dEedjgmQDVj2/3TaI= MIME-Version: 1.0 Received: by 10.216.81.69 with SMTP id l47mr3299295wee.78.1300183043850; Tue, 15 Mar 2011 02:57:23 -0700 (PDT) Received: by 10.216.155.76 with HTTP; Tue, 15 Mar 2011 02:57:23 -0700 (PDT) In-Reply-To: References: Date: Tue, 15 Mar 2011 10:57:23 +0100 Message-ID: From: Jean-Michel Combes To: SAVI Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Christian Vogt Subject: Re: [savi] IETF 80: Call for presentations X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2011 09:56:00 -0000 Folks, only one day before the deadline. Best regards. JMC. 2011/3/7 Jean-Michel Combes : > Folks, > > A SAVI session has been scheduled for the next IETF meeting: > > THURSDAY, March 31, 2011 > 1520-1720 =A0Afternoon Session II > Congress Hall I =A0 INT savi =A0 =A0 =A0 =A0 Source Address Validation Im= provements WG > > > People wishing to have a slot for a presentation, please, send an email t= o > the chairs (please, provide also the title of the presentation and the > time you would need) by Wednesday, March 16. > > Thanks. > > Christian & JMC. > From jeanmichel.combes@gmail.com Wed Mar 23 11:40:03 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EAB93A68BF for ; Wed, 23 Mar 2011 11:40:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.963 X-Spam-Level: X-Spam-Status: No, score=-102.963 tagged_above=-999 required=5 tests=[AWL=0.636, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0lJ+4FUr45c7 for ; Wed, 23 Mar 2011 11:40:02 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 1D16F3A68B8 for ; Wed, 23 Mar 2011 11:40:01 -0700 (PDT) Received: by wyb42 with SMTP id 42so8857805wyb.31 for ; Wed, 23 Mar 2011 11:41:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=4Z97mP9rRN2Y1C3uIs3zhBv9K+LFYpxOCv3gIxYVJt4=; b=rCfGbz+9MVdipIaImE+4ZpeySZtT7dOREs8lqVu9tD2BaBUcR2vXiHClO5Ybw6WOTl 4y3faF3G09TJYaGd+1MUk9lV9IxfBcqvUS+QB2l2luxJhjlH2DaMm5ZF2D4Zuy1fkxLr F11uYmjEXwDgxcrLi1Rzo87LFi7q0n6AlanNI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=gqcxRxLxy2fvlIIoqtBGmxhkcpkkpIHzwp5j7dbw/3odSVXXZAfr+sgc2uLsCLr6kt DwlanlhYux98QMp4vo+5+JCv0qKxOrRdKVNw2+ICW86SxRFywtTXJaiRHFGvFSGfLAWh p98gvfhLRPmVf3rtNQrQG++JWXZ3F9PkXPxmQ= MIME-Version: 1.0 Received: by 10.216.12.146 with SMTP id 18mr145776wez.63.1300905695294; Wed, 23 Mar 2011 11:41:35 -0700 (PDT) Received: by 10.216.181.18 with HTTP; Wed, 23 Mar 2011 11:41:35 -0700 (PDT) Date: Wed, 23 Mar 2011 19:41:35 +0100 Message-ID: From: Jean-Michel Combes To: SAVI Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: [savi] IETF 80: Minutes taker & Jabber scribe needed X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2011 18:40:03 -0000 Folks, during the SAVI WG session, we will need one jabber scribe and one (or more) minutes taker. Thanks a lot in advance for the volunteers! Best regards. JMC. From Internet-Drafts@ietf.org Tue Mar 29 14:15:02 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7EB528C0F0; Tue, 29 Mar 2011 14:15:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.578 X-Spam-Level: X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehoXwJsx9JRV; Tue, 29 Mar 2011 14:15:02 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 143E928C0EB; Tue, 29 Mar 2011 14:15:02 -0700 (PDT) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.14 Message-ID: <20110329211502.31015.79721.idtracker@localhost> Date: Tue, 29 Mar 2011 14:15:02 -0700 Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-framework-04.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2011 21:15:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Address Validation Improvements Working Group of the IETF. Title : Source Address Validation Improvement Framework Author(s) : J. Wu, et al. Filename : draft-ietf-savi-framework-04.txt Pages : 14 Date : 2011-03-28 The Source Address Validation Improvement method was developed to complement ingress filtering with finer-grained, standardized IP source address validation. This document describes and motivates the design of the SAVI method. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-framework-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-savi-framework-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-03-29140936.I-D@ietf.org> --NextPart-- From junbi@tsinghua.edu.cn Wed Mar 30 05:01:26 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95A2D28C165 for ; Wed, 30 Mar 2011 05:01:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.103 X-Spam-Level: X-Spam-Status: No, score=-101.103 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_DSN=1.495, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xd9+82KaVsXu for ; Wed, 30 Mar 2011 05:01:25 -0700 (PDT) Received: from smtp.tsinghua.edu.cn (smtp.tsinghua.edu.cn [166.111.8.80]) by core3.amsl.com (Postfix) with ESMTP id 86CFE28C168 for ; Wed, 30 Mar 2011 05:01:25 -0700 (PDT) Received: from dhcp-4681.meeting.ietf.org ([130.129.70.129] helo=junbiVAIOz138) by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from ) id 1Q4u72-0005kb-PO for savi@ietf.org; Wed, 30 Mar 2011 20:03:01 +0800 Message-ID: <8535A3ABF6D242C786B2A2059B74F5E5@junbiVAIOz138> From: "Jun Bi" To: "SAVI Mailing List" References: <20110329211502.31015.79721.idtracker@localhost> In-Reply-To: <20110329211502.31015.79721.idtracker@localhost> Date: Wed, 30 Mar 2011 14:02:58 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3502.922 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922 Subject: Re: [savi] I-D Action:draft-ietf-savi-framework-04.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2011 12:01:26 -0000 Dear WG members, This is the latest revised version regarding to all comments received during WGLC. Thanks, Jun Bi -----原始邮件----- From: Internet-Drafts@ietf.org Sent: Tuesday, March 29, 2011 11:15 PM To: i-d-announce@ietf.org Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-framework-04.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Address Validation Improvements Working Group of the IETF. Title : Source Address Validation Improvement Framework Author(s) : J. Wu, et al. Filename : draft-ietf-savi-framework-04.txt Pages : 14 Date : 2011-03-28 The Source Address Validation Improvement method was developed to complement ingress filtering with finer-grained, standardized IP source address validation. This document describes and motivates the design of the SAVI method. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-framework-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi From jeanmichel.combes@gmail.com Wed Mar 30 06:34:16 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67EB63A6867; Wed, 30 Mar 2011 06:34:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.054 X-Spam-Level: X-Spam-Status: No, score=-103.054 tagged_above=-999 required=5 tests=[AWL=0.545, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfXKQJu9dqaB; Wed, 30 Mar 2011 06:34:15 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 90DB63A6816; Wed, 30 Mar 2011 06:34:14 -0700 (PDT) Received: by wyb29 with SMTP id 29so1217372wyb.31 for ; Wed, 30 Mar 2011 06:35:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=iUQ+7Cw/f9LJOtW29xPnJjSQmylgJVJ3whb6D3XWpus=; b=veyHYzTjSHKssxXWBrXV27GWi892sEpG0KwlaiOpfbCnII9gU6x7FnVbHWWmvNctu1 zNy5F3MZe7YZ/OFoOoXdmdzpkSYTobUAUgmyQiE6KZrd+5n5SaCN0Y6V1Zgufib8iQYm 2oDzJa2PS/hmCK4kfPq3hmTulKGo/nKumvVa8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=a9/yKLZlYeG5Hi6AD7ji77sbg7dVi3eOpLz1RrYSYWWvPDq85b+PwUyUZSEriPNxFE xQNSUU4dOxR1iIDFquLi8g/A8fK6cyj5uAEz4LaRhknzg5LTrWmLvGcbdxxuL1HPOawS smIpqSKv7QNEUpn04Bx4jktKqMg5NQqIkdMMA= MIME-Version: 1.0 Received: by 10.216.58.207 with SMTP id q57mr1144246wec.63.1301492152870; Wed, 30 Mar 2011 06:35:52 -0700 (PDT) Received: by 10.216.153.200 with HTTP; Wed, 30 Mar 2011 06:35:52 -0700 (PDT) Date: Wed, 30 Mar 2011 15:35:52 +0200 Message-ID: From: Jean-Michel Combes To: iesg-secretary@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Cc: SAVI Mailing List , savi-chairs@tools.ietf.org Subject: [savi] Publication request for "Source Address Validation Improvement Framework" (draft-ietf-savi-framework-04) X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2011 13:34:16 -0000 Dear Secretary, This is a request to publish draft-ietf-savi-framework-04 as a Informational RFC. Please find below the I-D write-up. Best regards. JMC. (1.a) Who is the Document Shepherd for this document? Has the Document Shepherd personally reviewed this version of the document and, in particular, does he or she believe this version is ready for forwarding to the IESG for publication? Jean-Michel Combes (jeanmichel.combes@gmail.com) is the Document Shepherd, savi WG co-chair. He has done a review on the document and believes it is ready to be forwarded to IESG for publication. (1.b) Has the document had adequate review both from key WG members and from key non-WG members? Does the Document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? The document has had adequate reviews by key WG members.The document shepherd does not have any concerns regarding the depth or breadth of the reviews received. (1.c) Does the Document Shepherd have concerns that the document needs more review from a particular or broader perspective, e.g., security, operational complexity, someone familiar with AAA, internationalization or XML? No. (1.d) Does the Document Shepherd have any specific concerns or issues with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the WG has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here. Has an IPR disclosure related to this document been filed? If so, please include a reference to the disclosure and summarize the WG discussion and conclusion on this issue. No. (1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? There is savi WG consensus behind the document. (1.f) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise the areas of conflict in separate email messages to the Responsible Area Director. (It should be in a separate email because this questionnaire is entered into the ID Tracker.) No. (1.g) Has the Document Shepherd personally verified that the document satisfies all ID nits? (See the Internet-Drafts Checklist and http://tools.ietf.org/tools/idnits/). Boilerplate checks are not enough; this check needs to be thorough. Has the document met all formal review criteria it needs to, such as the MIB Doctor, media type and URI type reviews? The document shepherd has personally verified that the document satisfies all ID nits. The document does not need MIB doctor review. The document does not contain any media and URI types. (1.h) Has the document split its references into normative and informative? Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the strategy for their completion? Are there normative references that are downward references, as described in [RFC3967]? If so, list these downward references to support the Area Director in the Last Call procedure for them [RFC3967]. References are split into normative and informative sections. (1.i) Has the Document Shepherd verified that the document IANA consideration section exists and is consistent with the body of the document? If the document specifies protocol extensions, are reservations requested in appropriate IANA registries? Are the IANA registries clearly identified? If the document creates a new registry, does it define the proposed initial contents of the registry and an allocation procedure for future registrations? Does it suggest a reasonable name for the new registry? See [RFC5226]. If the document describes an Expert Review process has Shepherd conferred with the Responsible Area Director so that the IESG can appoint the needed Expert during the IESG Evaluation? This document has an IANA considerations section and no IANA considerations that needs to be taken care of. (1.j) Has the Document Shepherd verified that sections of the document that are written in a formal language, such as XML code, BNF rules, MIB definitions, etc., validate correctly in an automated checker? There are no such sections. (1.k) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Write-Up? Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: Technical Summary The Source Address Validation Improvement method was developed to complement ingress filtering with finer-grained, standardized IP source address validation. This document describes and motivates the design of the SAVI method. Working Group Summary The normal WG process was followed. The document as it is now, reflects WG consensus. Document Quality The document was thoroughly reviewed by Frank Xia, Mikael Abrahamsson and Jean-Michel Combes. From jeanmichel.combes@gmail.com Wed Mar 30 06:39:03 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDD303A6B56 for ; Wed, 30 Mar 2011 06:39:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.122 X-Spam-Level: X-Spam-Status: No, score=-103.122 tagged_above=-999 required=5 tests=[AWL=0.477, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qlSHElpe8hWV for ; Wed, 30 Mar 2011 06:39:03 -0700 (PDT) Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id C76F93A6B51 for ; Wed, 30 Mar 2011 06:39:02 -0700 (PDT) Received: by wwa36 with SMTP id 36so1051893wwa.13 for ; Wed, 30 Mar 2011 06:40:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=BpfP/EQ7XsTzSoT4UJAvwPETfHLpoTEOJA0Xmplyfi4=; b=hCDBL0tnY719S47n6/ppHENvKPHv0KaUjBzJJHFkOy+ErGBnT2UHIQZ/DlZiCHQnDi hyPmYnyeWj9Zdwnk+yrgr3swF/T8N9WRxZ+4dmKDgp/aQZiLYkodni9YvRK3J1a7b1pL CES5dK280jRlCS7H1fwxHFLz+5SYb2PxG0WIo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=wa8yXJGaksdHhdYKsCLI53Ev7O3w4cRhWlKrenPKdeBAmfAROgIIfa2xeGJfCgMMCd BPBd86k9czsV/xu3nggkE0QzEXfpCZVBxURuDFK2ABwKZkZLTerwl24AVi/KvRBMYrdy k7AUxxc7EP3/4jxab3yFppsvaGWHWbZylR6pY= MIME-Version: 1.0 Received: by 10.216.58.207 with SMTP id q57mr1151093wec.63.1301492441128; Wed, 30 Mar 2011 06:40:41 -0700 (PDT) Received: by 10.216.153.200 with HTTP; Wed, 30 Mar 2011 06:40:41 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Mar 2011 15:40:41 +0200 Message-ID: From: Jean-Michel Combes To: SAVI Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [savi] IETF 80: Minutes taker & Jabber scribe needed X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2011 13:39:03 -0000 Hi, the SAVI WG session is tomorrow afternoon and we have no volunteers. Please, we really need ones! Thanks in advance. Best regards. JMC. 2011/3/23 Jean-Michel Combes : > Folks, > > during the SAVI WG session, we will need one jabber scribe and one (or > more) minutes taker. > > Thanks a lot in advance for the volunteers! > > Best regards. > > JMC. > From jeanmichel.combes@gmail.com Wed Mar 30 17:16:27 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A567728C1B7 for ; Wed, 30 Mar 2011 17:16:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.217 X-Spam-Level: X-Spam-Status: No, score=-103.217 tagged_above=-999 required=5 tests=[AWL=0.382, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cXH0-zw-6bT2 for ; Wed, 30 Mar 2011 17:16:26 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 7405528C0FD for ; Wed, 30 Mar 2011 17:16:26 -0700 (PDT) Received: by wyb29 with SMTP id 29so1760458wyb.31 for ; Wed, 30 Mar 2011 17:18:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=jr+ytZT+XlirfskQZwjRpjPdmVczfhwUJte75MrweK4=; b=ueqqXw4yG10Z/BLlXfXdDpyrLsbHE6vS4vXy02N5/PHIOlQliZwrIrgkQ6XEk0aM71 6soyTI1Va7ryQrZdwcZJ3osXvMjVGl0//9NHGbzCSDnZ5s8xvw5gAvczPHnFj0fI0oy7 LdYEObTnX4vYVc+AozBISd89JOXFBjXj5Wzok= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=EXertSYk1UsWPGJpUgYGDgm8h+Mnhayrql3muridgI8XUxcvDZueq4glPpMMNMLTCy sSQbc+q6UZcQq86VP//ulyWd4I067a4xmvHWj+nkY86Tv3mCKAVvI8FqaJkAl4796hEK y8Up52EL8+pCvV2FJHfDsUCAaqbDwQCad8RSQ= MIME-Version: 1.0 Received: by 10.216.245.11 with SMTP id n11mr1308787wer.108.1301530684598; Wed, 30 Mar 2011 17:18:04 -0700 (PDT) Received: by 10.216.153.200 with HTTP; Wed, 30 Mar 2011 17:18:04 -0700 (PDT) In-Reply-To: <4D7268E9.8000202@joelhalpern.com> References: <4D71CDE6.1000707@joelhalpern.com> <4D71FF5A.8040800@it.uc3m.es> <4D7268E9.8000202@joelhalpern.com> Date: Thu, 31 Mar 2011 02:18:04 +0200 Message-ID: From: Jean-Michel Combes To: "Joel M. Halpern" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: draft-ietf-savi-fcfs@tools.ietf.org, SAVI Mailing List Subject: Re: [savi] SAVI FCFS & Logging X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2011 00:16:27 -0000 Hi, I am in favor of the addition of such a text: logging could clearly help. Now, I would like to have feedback from the WG and especially from people implementing SAVI to know if logging could be easily implementing (i.e. with no expensive extra-cost): that would determine whether make that normative or not. Best regards. JMC. 2011/3/5 Joel M. Halpern : > I asked the SAVI FCFS the question below. =A0In response they quite reaso= nably > asked that I provide text. =A0Following the note excerpt is the suggestio= n on > placement and text. =A0THe text could include a reference to the savi thr= eats > document. =A0I was not sure if that would be helpful, so I left it out. = =A0Also, > as logging is basically an internal activity, I have written this suggest= ion > as non-normative text. > >> El 05/03/11 6:45, Joel M. Halpern escribi=F3: >>> >>> Looking at the traceability issues we raise in the threats document, >>> and looking at the uses I see people wanting to make of SAVI for >>> SLAAC, should we put some descriptive (not normative) text into SAVI >>> FCFS that talks about loggin? >>> >>> I wanted to check with you folks directly before raising this on the >>> list. >>> >>> Thank you, >>> Joel > > I would suggest adding a section between 2.4 and 2.5 (i.e., it would be 2= .5, > and the current 2.5 SAVI enforcement perimeter would become 2.6.) > --------- > 2.x SAVI Logging > > While the primary goal of SAVI is simply to prevent improper use of IP > addresses, a secondary goal is to assist in traceability for determining = who > an imp-roper actor is. =A0For example, if a remote site reports that a Do= S (or > component of a DDoS) is coming from the SAVI site, SAVI enforcement can b= e a > useful component in a response. > > In order to support these and other similar activities, it is a good idea= if > SAVI devices perform logging of the creation, modification, or removal of > address bindings. =A0Any protocol support, such as SYSLOG support for sen= ding > those logs to a common server, would be a topic for a future separate > document. > ----- > If instead we want to make that normative, we could put a SHOULD in and p= ut > this in section 3.2.6 instead. > > In addition, it would seem useful to add a short paragraph in the securit= y > considerations section. =A0(If Denial of service attacks and Residual thr= eats > were 4.1 and 4.2, then I would would att this as 4.3 Security Logging) > ------------- > In order to improve the integration of SAVI into an overall security > environment, and enable response to additional indirect security issues > which SAVI can help ameliorate, it is helpful if SAVI systems log the > creation, modification, and deletion of binding entries. > --------- > I realize this basically duplicates the 2.x text. =A0I think it deserves > mention in the security considerations, because it is a security > consideration. =A0But I don't think that should be the first occurrence. > If the duplication is bothersome, then just use the 2.x text. > > Thank you, > Joel > _______________________________________________ > savi mailing list > savi@ietf.org > https://www.ietf.org/mailman/listinfo/savi > From jeanmichel.combes@gmail.com Wed Mar 30 17:24:58 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D53293A6BEB for ; Wed, 30 Mar 2011 17:24:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.252 X-Spam-Level: X-Spam-Status: No, score=-103.252 tagged_above=-999 required=5 tests=[AWL=0.347, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wL1NYOy2eM01 for ; Wed, 30 Mar 2011 17:24:57 -0700 (PDT) Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 838F53A6BEA for ; Wed, 30 Mar 2011 17:24:57 -0700 (PDT) Received: by wwa36 with SMTP id 36so1547436wwa.13 for ; Wed, 30 Mar 2011 17:26:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=bBDD/NhrgaCDaX8SwA4qO1GVcBJGX/2JNCsTKSBZm0w=; b=fdvwwRTm5VhPwb9SOE0Oj23eo0gSyX6U213Q7pdB2TSmyfrb1OI3NMDxqKT+IW7bsp jhVWhdBR7q7vQlvYa24QtDm7uukVUidg+zbuwUrPXaaW6QDrtsqPwB3Vm52ZBL8ay3C7 qyoAe2GN4XtxNOUtcVBMrdNCW5ix1i5h/mv/A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OJRbjpp9LS7N3hyYgMgwpTnK5efMBWF9vFR9FWKixq/Ndn7RjEeEF0BTcjV0DpFLSQ jOXrtkUBFdHNzQx8H91rZlcbg/lU08wgMFzN+yjET3veRx20a5PJft/j4rzqTwSWBqZW uh8bpn4IIdwSLBeU0ApwnNx9DiK83Ws07tb8M= MIME-Version: 1.0 Received: by 10.216.179.196 with SMTP id h46mr1823071wem.78.1301531196256; Wed, 30 Mar 2011 17:26:36 -0700 (PDT) Received: by 10.216.153.200 with HTTP; Wed, 30 Mar 2011 17:26:36 -0700 (PDT) Date: Thu, 31 Mar 2011 02:26:36 +0200 Message-ID: From: Jean-Michel Combes To: SAVI Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: [savi] FCFS: about the last WGLC X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2011 00:24:58 -0000 Hi, Two potential issues have been raised during the last WGLC: "IPv4 static configuration" and "Idle host". As there was no clear consensus during the discussion, the chairs took the following decisions: o IPv4 static configuration IPv4 was included in earlier versions of this document and after was removed. To avoid any delay for the publication of this document, we decided this last one will only focus on IPv6. To reflect this, the name of the document has to be modified. o Idle host We think that if there is an issue with an idle host which cannot defend its address, this is not a SAVI issue but a DAD issue. So, no new text about this scenario is needed in the document. Dear co-authors, please, when you will submit a new version of the document, take account of these decisions. BTW, please, check also that the new version will be compliant with the last version of the Framework document (e.g. terminology, architecture design, etc.). Thanks in advance. Best regards. Christian & JMC. From junbi@tsinghua.edu.cn Thu Mar 31 00:21:39 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 842B628C223 for ; Thu, 31 Mar 2011 00:21:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.103 X-Spam-Level: X-Spam-Status: No, score=-101.103 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_DSN=1.495, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVjse+G82-Hg for ; Thu, 31 Mar 2011 00:21:38 -0700 (PDT) Received: from smtp.tsinghua.edu.cn (smtp.tsinghua.edu.cn [166.111.8.80]) by core3.amsl.com (Postfix) with ESMTP id E987028C226 for ; Thu, 31 Mar 2011 00:21:37 -0700 (PDT) Received: from dhcp-4317.meeting.ietf.org ([130.129.67.23] helo=junbiVAIOz138) by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from ) id 1Q5CDp-0008Ip-KQ; Thu, 31 Mar 2011 15:23:14 +0800 Message-ID: From: "Jun Bi" To: "Jean-Michel Combes" , "SAVI Mailing List" References: In-Reply-To: Date: Thu, 31 Mar 2011 09:23:10 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3508.1109 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3508.1109 Subject: Re: [savi] FCFS: about the last WGLC X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2011 07:21:39 -0000 I believe I was one of the WG members who raised the two questions. To not delay the LC, I am fine with the chair's decision. The problems addressed by the questions will happen in real network deployment. so I think maybe laterly a SAVI experimenal draft to include incussing these questions will be good. Best Regards, Jun Bi -----原始邮件----- From: Jean-Michel Combes Sent: Thursday, March 31, 2011 2:26 AM To: SAVI Mailing List Subject: [savi] FCFS: about the last WGLC Hi, Two potential issues have been raised during the last WGLC: "IPv4 static configuration" and "Idle host". As there was no clear consensus during the discussion, the chairs took the following decisions: o IPv4 static configuration IPv4 was included in earlier versions of this document and after was removed. To avoid any delay for the publication of this document, we decided this last one will only focus on IPv6. To reflect this, the name of the document has to be modified. o Idle host We think that if there is an issue with an idle host which cannot defend its address, this is not a SAVI issue but a DAD issue. So, no new text about this scenario is needed in the document. Dear co-authors, please, when you will submit a new version of the document, take account of these decisions. BTW, please, check also that the new version will be compliant with the last version of the Framework document (e.g. terminology, architecture design, etc.). Thanks in advance. Best regards. Christian & JMC. _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi From elevyabe@cisco.com Thu Mar 31 00:25:13 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCD8D28C23C for ; Thu, 31 Mar 2011 00:25:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J9G4egiGwe2L for ; Thu, 31 Mar 2011 00:25:12 -0700 (PDT) Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 0612728C23A for ; Thu, 31 Mar 2011 00:25:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=elevyabe@cisco.com; l=3656; q=dns/txt; s=iport; t=1301556411; x=1302766011; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=xkdvWxcSEbZWJvqIx9gns7mlPefHX/rvzThjE2PasRc=; b=Gaybz7WQmL/poAu12eqTevpq32UzYA+msfxdI77COE81+O24xjDFeiKQ fnUfJ/WgDLYo73cFNlMjs520eRpM+g7MMHTY5ecym4cXBVECS2JZ7DzGe YJA9O+YC4v3bBto699TMEWssD/avv+XsXpOCeZxJEMeaoRdUe7CnXgEhp Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtoDAI4rlE2Q/khMgWdsb2JhbAClTxQBARYmJaJinAGFawSNEYNVBg X-IronPort-AV: E=Sophos;i="4.63,274,1299456000"; d="scan'208";a="23896778" Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 31 Mar 2011 07:26:50 +0000 Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2V7QoUH017454; Thu, 31 Mar 2011 07:26:50 GMT Received: from xmb-ams-105.cisco.com ([144.254.74.80]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 31 Mar 2011 09:26:50 +0200 Received: from [10.86.243.122] ([10.86.243.122]) by xmb-ams-105.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 31 Mar 2011 09:26:50 +0200 Message-ID: <4D942CB7.4030508@cisco.com> Date: Thu, 31 Mar 2011 09:26:47 +0200 From: Eric Levy-Abegnoli User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Jean-Michel Combes References: <4D71CDE6.1000707@joelhalpern.com> <4D71FF5A.8040800@it.uc3m.es> <4D7268E9.8000202@joelhalpern.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 31 Mar 2011 07:26:50.0303 (UTC) FILETIME=[002814F0:01CBEF75] Cc: draft-ietf-savi-fcfs@tools.ietf.org, SAVI Mailing List Subject: Re: [savi] SAVI FCFS & Logging X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2011 07:25:14 -0000 Le 31/03/2011 02:18, Jean-Michel Combes a écrit : > Hi, > > I am in favor of the addition of such a text: logging could clearly help. > Now, I would like to have feedback from the WG and especially from > people implementing SAVI to know if logging could be easily > implementing (i.e. with no expensive extra-cost): that would determine > whether make that normative or not. I support the addition. That has been #1 requirement from many organizations I dealt with deploying SAVI or IPSG solutions. Not particular issue implementation-wise. Eric > Best regards. > > JMC. > > 2011/3/5 Joel M. Halpern: >> I asked the SAVI FCFS the question below. In response they quite reasonably >> asked that I provide text. Following the note excerpt is the suggestion on >> placement and text. THe text could include a reference to the savi threats >> document. I was not sure if that would be helpful, so I left it out. Also, >> as logging is basically an internal activity, I have written this suggestion >> as non-normative text. >> >>> El 05/03/11 6:45, Joel M. Halpern escribió: >>>> Looking at the traceability issues we raise in the threats document, >>>> and looking at the uses I see people wanting to make of SAVI for >>>> SLAAC, should we put some descriptive (not normative) text into SAVI >>>> FCFS that talks about loggin? >>>> >>>> I wanted to check with you folks directly before raising this on the >>>> list. >>>> >>>> Thank you, >>>> Joel >> I would suggest adding a section between 2.4 and 2.5 (i.e., it would be 2.5, >> and the current 2.5 SAVI enforcement perimeter would become 2.6.) >> --------- >> 2.x SAVI Logging >> >> While the primary goal of SAVI is simply to prevent improper use of IP >> addresses, a secondary goal is to assist in traceability for determining who >> an imp-roper actor is. For example, if a remote site reports that a DoS (or >> component of a DDoS) is coming from the SAVI site, SAVI enforcement can be a >> useful component in a response. >> >> In order to support these and other similar activities, it is a good idea if >> SAVI devices perform logging of the creation, modification, or removal of >> address bindings. Any protocol support, such as SYSLOG support for sending >> those logs to a common server, would be a topic for a future separate >> document. >> ----- >> If instead we want to make that normative, we could put a SHOULD in and put >> this in section 3.2.6 instead. >> >> In addition, it would seem useful to add a short paragraph in the security >> considerations section. (If Denial of service attacks and Residual threats >> were 4.1 and 4.2, then I would would att this as 4.3 Security Logging) >> ------------- >> In order to improve the integration of SAVI into an overall security >> environment, and enable response to additional indirect security issues >> which SAVI can help ameliorate, it is helpful if SAVI systems log the >> creation, modification, and deletion of binding entries. >> --------- >> I realize this basically duplicates the 2.x text. I think it deserves >> mention in the security considerations, because it is a security >> consideration. But I don't think that should be the first occurrence. >> If the duplication is bothersome, then just use the 2.x text. >> >> Thank you, >> Joel >> _______________________________________________ >> savi mailing list >> savi@ietf.org >> https://www.ietf.org/mailman/listinfo/savi >> > _______________________________________________ > savi mailing list > savi@ietf.org > https://www.ietf.org/mailman/listinfo/savi > From jeanmichel.combes@gmail.com Thu Mar 31 05:41:55 2011 Return-Path: X-Original-To: savi@core3.amsl.com Delivered-To: savi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BC3328C121 for ; Thu, 31 Mar 2011 05:41:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.281 X-Spam-Level: X-Spam-Status: No, score=-103.281 tagged_above=-999 required=5 tests=[AWL=0.318, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k224yDuNB2qL for ; Thu, 31 Mar 2011 05:41:53 -0700 (PDT) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id DA16428C0F9 for ; Thu, 31 Mar 2011 05:41:50 -0700 (PDT) Received: by wwk4 with SMTP id 4so5149379wwk.1 for ; Thu, 31 Mar 2011 05:43:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=6D//H+tNmaF1NPhp4BPuKhL1tinA1o59jL/KOsVmu+U=; b=Pi7pNbjIYUqVGr5E5U2UPDsC6V7SySCBIXqF84rWUYat6mo4JHPc439SxyqK4vHI/9 joHktjMkVy68iYIQS26nrb0dPJwZcKbJhRux+Hj+Z4qqcjRnyrSfLVM1816PEpxtxnkp MzBe1GB+kej/AA+TY5XYL/gmdSfoimAcMkj64= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fUPd47uOwzcK28EJX2xb4E6InJxljTeYhQhivfNtqLfzkitTSqzD+YZxZ5/brzcgZj Pb/fbXEXQaqLMAxAfNvh7avZu1zVI+nq5d4esJ8ydKMnrauBti4kgrWzeBRc173kGkDy p3LcbOFPFU8SMqkPIquihXHus4Io4sxW5ggIQ= MIME-Version: 1.0 Received: by 10.216.81.69 with SMTP id l47mr1958399wee.78.1301575409888; Thu, 31 Mar 2011 05:43:29 -0700 (PDT) Received: by 10.216.153.200 with HTTP; Thu, 31 Mar 2011 05:43:29 -0700 (PDT) Date: Thu, 31 Mar 2011 14:43:29 +0200 Message-ID: From: Jean-Michel Combes To: SAVI Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: [savi] IETF80: Slides X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the SAVI working group at IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2011 12:41:55 -0000 Hi, slides regarding this afternoon meeting have been uploaded and can be found here: https://datatracker.ietf.org/meeting/80/materials.html Best regards. JMC.