From jeanmichel.combes@gmail.com Tue Apr 5 08:42:01 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 785A83A6959 for ; Tue, 5 Apr 2011 08:42:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.305 X-Spam-Level: X-Spam-Status: No, score=-103.305 tagged_above=-999 required=5 tests=[AWL=0.294, 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 bvhj+eGxAADI for ; Tue, 5 Apr 2011 08:42:00 -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 B7CEE3A694C for ; Tue, 5 Apr 2011 08:41:59 -0700 (PDT) Received: by wwa36 with SMTP id 36so428664wwa.13 for ; Tue, 05 Apr 2011 08:43:42 -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=0HreFhaoVPtwOWUDlwHtGwpR87yRT/hmGNU68AnKico=; b=Z1BlYaB3QMNJFD68lBrYJt02Rs/6402NQs97Zx0PdNyv6y0cvTpn5yyeNEk/EIBfex AmmtAX0y5bTHnOM3HjkTS4F6muacpJgan+ONkYWzxkqtuq34759GD7FoO4kZzhvv1cax 9nrI/ic/bENc5NC8F/pUVzvid6nuf5aIrewv0= 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=hOVQ7TRiv/cUo4TChpJfm5a0VZawSYbUkPzUXFvU2aw+2y1sql7oQIMDUa0ZVpP0pm EcwJW0+ZKaPIzfy2uySNTUvy6TwMC3StQafJ7CTIppp5CswtuevXZF0CKXA+a26JEz+8 L22D1w78GYfB2Id7T6d8Wx+p1BuoNX5bCG9cQ= MIME-Version: 1.0 Received: by 10.216.191.208 with SMTP id g58mr5697204wen.85.1302018222371; Tue, 05 Apr 2011 08:43:42 -0700 (PDT) Received: by 10.216.122.69 with HTTP; Tue, 5 Apr 2011 08:43:42 -0700 (PDT) In-Reply-To: <4D942CB7.4030508@cisco.com> References: <4D71CDE6.1000707@joelhalpern.com> <4D71FF5A.8040800@it.uc3m.es> <4D7268E9.8000202@joelhalpern.com> <4D942CB7.4030508@cisco.com> Date: Tue, 5 Apr 2011 17:43:42 +0200 Message-ID: From: Jean-Michel Combes To: Eric Levy-Abegnoli 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: Tue, 05 Apr 2011 15:42:01 -0000 Hi, To move forward the document ASAP, any additional comments about this topic must be sent before next Tuesday. Thanks in advance. Best regards. JMC. 2011/3/31 Eric Levy-Abegnoli : > Le 31/03/2011 02:18, Jean-Michel Combes a =E9crit : >> >> 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 organizati= ons > 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. =A0In response they quite >>> reasonably >>> asked that I provide text. =A0Following the note excerpt is the suggest= ion >>> on >>> placement and text. =A0THe text could include a reference to the savi >>> threats >>> 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 >>> suggestion >>> 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 determinin= g >>> who >>> an imp-roper actor is. =A0For 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 id= ea >>> if >>> SAVI devices perform logging of the creation, modification, or removal = of >>> address bindings. =A0Any 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. =A0(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. =A0I think it deserve= s >>> 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 >>> >> _______________________________________________ >> savi mailing list >> savi@ietf.org >> https://www.ietf.org/mailman/listinfo/savi >> > > From jeanmichel.combes@gmail.com Wed Apr 6 03:49:18 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 5E09B3A68C4 for ; Wed, 6 Apr 2011 03:49:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.326 X-Spam-Level: X-Spam-Status: No, score=-103.326 tagged_above=-999 required=5 tests=[AWL=0.273, 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 oFNLgMoxMMgJ for ; Wed, 6 Apr 2011 03:49:17 -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 8F4813A68C8 for ; Wed, 6 Apr 2011 03:49:17 -0700 (PDT) Received: by wyb29 with SMTP id 29so1285019wyb.31 for ; Wed, 06 Apr 2011 03:51:00 -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=NShPUXpmiyfbyOiynDdmcTaRe8pKIlnKEZqKZxuDNfQ=; b=n6YD1bwMkptvOI8Gn46LTPjWDG+0DJwZzJTPq+00sAPdQh2y5ZVA5Eg//qI3CC5ivH TgG2r4GpUQBQ63Oe4BrcgOPtTm9K0WIou2f4ZXkhfMih64P1St92OU8xctvUBeYexRLS k0uDfOyky+h6zaTbh0ueHshwJzQ5nltUdNUgs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=AAcNGIXhNsNvWnM9+IexWMVNHv+/LLbig1h0KR83yxWqzLHu4f8r0Xev6LHaIPkVYH miekVWpLscPuJzoBei+xEZH7x37YGkowud0wPjCQ2kQDlB4RgZnr5LsxWiq0D4m+lfXZ IRvSO4sZ6X46uiltz2+IMeMszlMhgXLLvlsq8= MIME-Version: 1.0 Received: by 10.216.59.129 with SMTP id s1mr6157423wec.85.1302087060818; Wed, 06 Apr 2011 03:51:00 -0700 (PDT) Received: by 10.216.122.69 with HTTP; Wed, 6 Apr 2011 03:51:00 -0700 (PDT) Date: Wed, 6 Apr 2011 12:51:00 +0200 Message-ID: From: Jean-Michel Combes To: SAVI Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: [savi] Adoption of "SAVI for Mixed Address Assignment Methods Scenario" (draft-bi-savi-mix-04) as WG I-D: confirmation? 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, 06 Apr 2011 10:49:18 -0000 Folks, during the last SAVI meeting in Prague, there was a consensus to adopt "SAVI for Mixed Address Assignment Methods Scenario" document (draft-bi-savi-mix-04) as WG document. If you have any concern about this adoption, please send an email on the ML before next Tuesday. Best regards. JMC. From Internet-Drafts@ietf.org Mon Apr 11 05: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 405F13A6B05; Mon, 11 Apr 2011 05:00:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.588 X-Spam-Level: X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 xs9SW8l0VTGJ; Mon, 11 Apr 2011 05:00:02 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 344F63A6A09; Mon, 11 Apr 2011 05:00: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.16 Message-ID: <20110411120002.25515.19138.idtracker@localhost> Date: Mon, 11 Apr 2011 05:00:02 -0700 Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-fcfs-06.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: Mon, 11 Apr 2011 12: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 : FCFS-SAVI: First-Come First-Serve Source-Address Validation for Locally Assigned IPv6 Addresses Author(s) : E. Nordmark, et al. Filename : draft-ietf-savi-fcfs-06.txt Pages : 29 Date : 2011-04-11 This memo describes FCFS SAVI a mechanism to provide source address validation for IPv6 networks using the First-Come First-Serve principle. The proposed mechanism is intended to complement ingress filtering techniques to provide a finer granularity on the control of the source addresses used. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-fcfs-06.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-fcfs-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-04-11044616.I-D@ietf.org> --NextPart-- From marcelo@it.uc3m.es Mon Apr 11 05:08:52 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 BEF7828C0F0 for ; Mon, 11 Apr 2011 05:08:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 e6K-JOL82-AC for ; Mon, 11 Apr 2011 05:08:51 -0700 (PDT) Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id 5D31C28C0F8 for ; Mon, 11 Apr 2011 05:08:51 -0700 (PDT) X-uc3m-safe: yes Received: from marcelo-bagnulos-macbook-pro-2.local (wlap005.it.uc3m.es [163.117.139.108]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id 49056BA0376 for ; Mon, 11 Apr 2011 14:08:48 +0200 (CEST) Message-ID: <4DA2EF4F.2080609@it.uc3m.es> Date: Mon, 11 Apr 2011 14:08:47 +0200 From: marcelo bagnulo braun User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; es-ES; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: savi@ietf.org References: <20110411120002.25515.19138.idtracker@localhost> In-Reply-To: <20110411120002.25515.19138.idtracker@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.5.0.1024-18066.007 Subject: Re: [savi] I-D Action:draft-ietf-savi-fcfs-06.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: Mon, 11 Apr 2011 12:08:53 -0000 Hi, This is a new version of the draft that i believe accommodates all the comments received. In particular, its terminology is aligned to the one in the framework document, it includes the text proposed by Joel on logging and it reflects the IPv6 scope in the title. I understand that this is ready to ship to the iesg. Regards, marcelo El 11/04/11 14:00, Internet-Drafts@ietf.org escribió: > 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 : FCFS-SAVI: First-Come First-Serve Source-Address Validation for Locally Assigned IPv6 Addresses > Author(s) : E. Nordmark, et al. > Filename : draft-ietf-savi-fcfs-06.txt > Pages : 29 > Date : 2011-04-11 > > This memo describes FCFS SAVI a mechanism to provide source address > validation for IPv6 networks using the First-Come First-Serve > principle. The proposed mechanism is intended to complement ingress > filtering techniques to provide a finer granularity on the control of > the source addresses used. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-savi-fcfs-06.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 Internet-Drafts@ietf.org Mon Apr 11 07:45: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 E58983A6A47; Mon, 11 Apr 2011 07:45:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.592 X-Spam-Level: X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 o-PG2uxpQIp0; Mon, 11 Apr 2011 07:45:02 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24C393A69FF; Mon, 11 Apr 2011 07:45: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.16 Message-ID: <20110411144502.8808.49474.idtracker@localhost> Date: Mon, 11 Apr 2011 07:45:02 -0700 Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-threat-scope-05.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: Mon, 11 Apr 2011 14:45:03 -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-05.txt Pages : 22 Date : 2011-04-11 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-05.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-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-04-11073102.I-D@ietf.org> --NextPart-- From jeanmichel.combes@gmail.com Tue Apr 12 08:29:05 2011 Return-Path: X-Original-To: savi@ietfc.amsl.com Delivered-To: savi@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id CD2B0E0806; Tue, 12 Apr 2011 08:29:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7N+yX7FGI-G; Tue, 12 Apr 2011 08:29:04 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfc.amsl.com (Postfix) with ESMTP id 48032E07EA; Tue, 12 Apr 2011 08:29:04 -0700 (PDT) Received: by wyb29 with SMTP id 29so6403562wyb.31 for ; Tue, 12 Apr 2011 08:29:03 -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=3gOE0nEw6PAlUrK0c2u6OqVT0Xfp9+LFw5UbyJOPCmc=; b=okEx3dnl2mogSqzba5Dx9JPpSwr82bdIxeq9vAU0Sz0ljP5OPKqm/6R3IJZNDKxbBM Jr1gIYSz1AjWiSb2gaV14TWP+XC99x/t/Ghkfp5i/9Lp2zn18WZe7uf3HPdwFXM5sohd ld002dRHoyYAYb2mXRUK6COtnjAvIUf1pDjxE= 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=JwFW7dkowLR/A62V2FS1OBXS3tkwRkHbNeGLcdaYly0dYpU8fmZS8Oxu7IJmeuaJbr nIhC640DXr+sUnkUoOvXc2JtbM46MontNrKqWmfW9j7dzSa6RCZ5zKIwoMRTTEcwYfQ/ CB0Hurs49KnvYfeHWPNiZ2Zk0QDLpj1TjKrjQ= MIME-Version: 1.0 Received: by 10.216.172.15 with SMTP id s15mr4079603wel.70.1302622143563; Tue, 12 Apr 2011 08:29:03 -0700 (PDT) Received: by 10.216.122.69 with HTTP; Tue, 12 Apr 2011 08:29:03 -0700 (PDT) Date: Tue, 12 Apr 2011 17:29:03 +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 "SAVI Threat Scope" (draft-ietf-savi-threat-scope-05) X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.12 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, 12 Apr 2011 15:29:06 -0000 Dear Secretary, This is a request to publish draft-ietf-savi-threat-scope-05 as a Informational RFC. Please find below the I-D write-up. Thanks in advance. 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 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. 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 Pekka Savola, Marcelo Bagnulo, Eric Vyncke, Jari Arkko and Jean-Michel Combes. From Internet-Drafts@ietf.org Wed Apr 13 02:45:03 2011 Return-Path: X-Original-To: savi@ietfc.amsl.com Delivered-To: savi@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 0E306E06E7; Wed, 13 Apr 2011 02:45:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.589 X-Spam-Level: X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MF3slGtCb04s; Wed, 13 Apr 2011 02:45:02 -0700 (PDT) Received: from ietfc.amsl.com (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 6A71BE0684; Wed, 13 Apr 2011 02:45: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.50 Message-ID: <20110413094502.26867.42820.idtracker@ietfc.amsl.com> Date: Wed, 13 Apr 2011 02:45:02 -0700 Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-fcfs-07.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.12 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, 13 Apr 2011 09:45:03 -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 : FCFS-SAVI: First-Come First-Serve Source-Address Validation for Locally Assigned IPv6 Addresses Author(s) : E. Nordmark, et al. Filename : draft-ietf-savi-fcfs-07.txt Pages : 29 Date : 2011-04-13 This memo describes FCFS SAVI a mechanism to provide source address validation for IPv6 networks using the First-Come First-Serve principle. The proposed mechanism is intended to complement ingress filtering techniques to provide a finer granularity on the control of the source addresses used. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-fcfs-07.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-fcfs-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-04-13023041.I-D@ietf.org> --NextPart-- From Internet-Drafts@ietf.org Fri Apr 15 06:00:03 2011 Return-Path: X-Original-To: savi@ietfc.amsl.com Delivered-To: savi@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5171AE081B; Fri, 15 Apr 2011 06:00:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZcsWdXpjy4V; Fri, 15 Apr 2011 06:00:02 -0700 (PDT) Received: from ietfc.amsl.com (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A3EB4E081D; Fri, 15 Apr 2011 06:00: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.51 Message-ID: <20110415130002.13131.11250.idtracker@ietfc.amsl.com> Date: Fri, 15 Apr 2011 06:00:02 -0700 Cc: savi@ietf.org Subject: [savi] I-D Action:draft-ietf-savi-send-05.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.12 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, 15 Apr 2011 13:00:03 -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 : SEND-based Source-Address Validation Implementation Author(s) : M. Bagnulo, A. Garcia-Martinez Filename : draft-ietf-savi-send-05.txt Pages : 29 Date : 2011-04-15 This memo describes SEND SAVI, a mechanism to provide source address validation using the SEND protocol. The proposed mechanism is intended to complement ingress filtering techniques to provide a finer granularity on the control of the source addresses used. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-send-05.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-send-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-04-15054638.I-D@ietf.org> --NextPart-- From alberto@it.uc3m.es Fri Apr 15 06:16:42 2011 Return-Path: X-Original-To: savi@ietfc.amsl.com Delivered-To: savi@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4C479E06A9 for ; Fri, 15 Apr 2011 06:16:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.299 X-Spam-Level: X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTpgJ74+nRNd for ; Fri, 15 Apr 2011 06:16:41 -0700 (PDT) Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by ietfc.amsl.com (Postfix) with ESMTP id 87CA4E068E for ; Fri, 15 Apr 2011 06:16:41 -0700 (PDT) X-uc3m-safe: yes Received: from BOMBO (unknown [163.117.139.228]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id CEB27B4865D for ; Fri, 15 Apr 2011 15:16:37 +0200 (CEST) From: =?iso-8859-1?Q?Alberto_Garc=EDa?= To: "'SAVI Mailing List'" References: <20110415130002.13131.11250.idtracker@ietfc.amsl.com> In-Reply-To: <20110415130002.13131.11250.idtracker@ietfc.amsl.com> Date: Fri, 15 Apr 2011 15:16:38 +0200 Message-ID: <005901cbfb6f$5a1fdb90$0e5f92b0$@it.uc3m.es> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGoGrdJjSGxfM5KsYgK6XI8eU79LJSmpopQ Content-Language: es X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.5.0.1024-18074.007 Subject: [savi] RV: I-D Action:draft-ietf-savi-send-05.txt X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.12 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, 15 Apr 2011 13:16:42 -0000 Hi, This is a new version of the SEND SAVI draft which aligns terminology to the framework document, also with some text clean-up I understand that it is ready to be shipped to the IESG. Regards, Alberto -----Mensaje original----- De: savi-bounces@ietf.org [mailto:savi-bounces@ietf.org] En nombre de Internet-Drafts@ietf.org Enviado el: viernes, 15 de abril de 2011 15:00 Para: i-d-announce@ietf.org CC: savi@ietf.org Asunto: [savi] I-D Action:draft-ietf-savi-send-05.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 : SEND-based Source-Address Validation Implementation Author(s) : M. Bagnulo, A. Garcia-Martinez Filename : draft-ietf-savi-send-05.txt Pages : 29 Date : 2011-04-15 This memo describes SEND SAVI, a mechanism to provide source address validation using the SEND protocol. The proposed mechanism is intended to complement ingress filtering techniques to provide a finer granularity on the control of the source addresses used. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-savi-send-05.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. From junbi@tsinghua.edu.cn Thu Apr 28 06:30:03 2011 Return-Path: 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 30902E0717 for ; Thu, 28 Apr 2011 06:30:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -97.641 X-Spam-Level: X-Spam-Status: No, score=-97.641 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_50=0.001, DNS_FROM_RFC_DSN=1.495, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ve38C54u5DAF for ; Thu, 28 Apr 2011 06:30:02 -0700 (PDT) Received: from smtp.tsinghua.edu.cn (smtp.tsinghua.edu.cn [166.111.8.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5785AE06EA for ; Thu, 28 Apr 2011 06:30:02 -0700 (PDT) Received: from th024029.ip.tsinghua.edu.cn ([59.66.24.29] helo=junbiVAIOz138) by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from ) id 1QFQxZ-00067G-Bh for savi@ietf.org; Thu, 28 Apr 2011 21:08:45 +0800 Message-ID: <3D4F1A48B5054377BDCA11070248AE38@junbiVAIOz138> From: "Jun Bi" To: "SAVI Mailing List" Date: Thu, 28 Apr 2011 21:08:53 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01E4_01CC05E8.7AA188E0" 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: [savi] draft-ietf-savi-dhcp-08 X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.12 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, 28 Apr 2011 13:30:03 -0000 ÕâÊÇÒ»·â MIME ¸ñʽµÄ¶à·½Óʼþ¡£ ------=_NextPart_000_01E4_01CC05E8.7AA188E0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Dear WG members, https://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/ This is a new version savi-dhcp-08 revised and is compliant=20 with the savi framework document. The 09 version is planed to be submitted based on the review feedback = form WG chairs. Thanks! Jun Bi ------=_NextPart_000_01E4_01CC05E8.7AA188E0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
Dear WG members,

This is a new version savi-dhcp-08 revised and is compliant =
with=20 the savi framework document.
The 09 version is planed to be submitted based on the review = feedback form=20 WG chairs.

Thanks!
Jun Bi
 
 
------=_NextPart_000_01E4_01CC05E8.7AA188E0-- From jeanmichel.combes@gmail.com Thu Apr 28 07:00:14 2011 Return-Path: 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 5A1C5E0715; Thu, 28 Apr 2011 07:00:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.558 X-Spam-Level: X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.441, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HvF9vzzxKb8s; Thu, 28 Apr 2011 07:00:13 -0700 (PDT) Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5A76AE0708; Thu, 28 Apr 2011 07:00:13 -0700 (PDT) Received: by yic13 with SMTP id 13so1183101yic.31 for ; Thu, 28 Apr 2011 07:00:12 -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=hL693lvCBw1o+3jF9cy+PwTwMJ0xpLVbPpsNGOTHYqQ=; b=xcbCJ8KVHlzNzEdtNHfB+cGUkxRqlaV3cDrko+QehULi9E/Hu+8c9r4z21R+XdWUYA Yd7+b0FCT2CoLnF3ySBJl01JqvxPiI0jqqG4KjbqzftoGeBAQmLC79BN99c0R+qRFrHR uQILUWIScNRtgd2xw00UicJA2ZkE+0sZkZRb8= 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=ujWTt9yAP6fHipXnwqjEylnSHWFqGSDrvePer3bq5whzVhpT8GE4Y+v4Hpkr29/kUd UV54GAnk2O7ZmaaSl0Il4MWkDuvKFFDZMZ0VwVW8GBRKhlwMfSQAFOG6TQfhvYp8TM7s a7IzmIjrmpa0X//eXgxL6sAOEdlScwKuR2aWA= MIME-Version: 1.0 Received: by 10.236.199.205 with SMTP id x53mr4301460yhn.193.1303999212647; Thu, 28 Apr 2011 07:00:12 -0700 (PDT) Received: by 10.147.171.17 with HTTP; Thu, 28 Apr 2011 07:00:12 -0700 (PDT) Date: Thu, 28 Apr 2011 16:00:12 +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 "FCFS SAVI: First-Come First-Serve Source-Address Validation for Locally Assigned IPv6 Addresses" (draft-ietf-savi-fcfs-09) X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.12 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, 28 Apr 2011 14:00:14 -0000 Dear Secretary, This is a request to publish draft-ietf-savi-fcfs-09 as a Standard track RFC. Please find below the I-D write-up. Thanks in advance. 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? As this document specifies a new security mechanism that could impact legitimate traffic, a review from the Security Directorate should be done. As this document specifies a Neighbor Discovery Protocol (NDP) based mechanism, a review from v6ops WG and/or 6man WG members may be done. (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. There are no normative references that are downward references. (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 need 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 This memo describes FCFS SAVI a mechanism to provide source address validation for IPv6 networks using the First-Come First-Serve principle. The proposed mechanism is intended to complement ingress filtering techniques to provide a finer granularity on the control of the source addresses used. 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 the document contributors, Joel Halpern and Jean-Michel Combes. From jeanmichel.combes@gmail.com Fri Apr 29 10:52:05 2011 Return-Path: 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 C0EA7E06CC for ; Fri, 29 Apr 2011 10:52:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mpd7YftaDXNP for ; Fri, 29 Apr 2011 10:52:05 -0700 (PDT) Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB21E06A1 for ; Fri, 29 Apr 2011 10:52:05 -0700 (PDT) Received: by gwb20 with SMTP id 20so1700511gwb.31 for ; Fri, 29 Apr 2011 10:52:04 -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=0m0tAcj9YpO4xA3GIJ0ro+/6w6B+3kIiwz8lezAreZU=; b=ID2OSuIgse9kVYo4Wa1ZroEOqjJkWiSH7RC/fEAEgbzjiISckkKc8WAo4jW+XhDdAh 2kRRii24u8o5Y8dyak6YJxxjvsdUpnD+hMdnAoceKrZKOL1JU3KihiE3sr1wXhjekV4e mUyslN2CPHT6cBAfsrqMgl3Gg8BC7zcyRNRIg= 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=xNzuml7j9VzcDlL7HGR1Ocsq5KDqXF3gFtlgKKsV5N6AMpJPu+hQSBpFulYpTDfqSQ kcyShs7xueQtbbJajp23ncH4kkgRHhlNU7ojUW4QBCbhU4uKzDBE7MWfyuLTfVqY7Z8p sOIM/hcabmV7RLVIGznkDnbE/668wAQ7sEU08= MIME-Version: 1.0 Received: by 10.236.77.5 with SMTP id c5mr6719094yhe.126.1304099524557; Fri, 29 Apr 2011 10:52:04 -0700 (PDT) Received: by 10.147.171.17 with HTTP; Fri, 29 Apr 2011 10:52:04 -0700 (PDT) Date: Fri, 29 Apr 2011 19:52:04 +0200 Message-ID: From: Jean-Michel Combes To: SAVI Mailing List Content-Type: text/plain; charset=ISO-8859-1 Cc: savi-chairs@tools.ietf.org Subject: [savi] [IETF80] SAVI meeting minutes X-BeenThere: savi@ietf.org X-Mailman-Version: 2.1.12 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, 29 Apr 2011 17:52:05 -0000 Folks, You may find now the minutes of the last SAVI meeting here: http://www.ietf.org/proceedings/80/minutes/savi.txt If you have comments/questions/modifications, don't hesitate to send them. Thanks again Jun for the minutes! Best regards. JMC.