Proposed Charter

The proposed ¡°Source Address Validation Architecture¡± Working Group
is chartered to specify standardization of methods for building
effective source-address validation to ensure that packets forwarded
hold authentic source addresses.

¡°Authentic source address¡± in this case has two meanings: 

1) First, the address must be authorized by Internet address
   authorization organization and not be forged. (i.e. the
   route to the address must have been injected into the
   routing tables by someone authorized to inject such a route,
   and the packet must have been injected into the network by
   an entity authorized to use that source address.)

2) Second, the address, except in cases where global uniqueness is
   specifically excluded, must be globally unique and
   traceable. That is, information about the address¡¯s
   location and ownership should be verifiable and correct.

WG scope

The SAVA WG scope includes:

1)	Framework Architecture

2)	Existing protocols and technologies may be extended, and 

3)	New mechanisms and protocols to support the architecture may be created. 

4)	The deployment policy and network transition mechanisms

5)	Explicit trust models for the verification of source address authenticity.

6)      Focus of the WG is the protection of infrastructure from unsecured
        and/or malicious endpoints.

7)      The WG need not limit itself to a single architectural design or a
        single solution for any given part of the architecture,
        although where there are multiple proposed solutions for a
        given part of the architecture, they should address distinct
        use cases. (As per RFC1958, Section 3)


With this in mind, the goals of the Proposed WG are to complete the
following work items:

1) Document the problem statement for which the work of SAVA is a
   solution, and submit it to the IESG as an Informational
   Standard.

2) Design an architectural framework for SAVA and its component
   solutions, identifying the interactions between them, and submit it
   to the IESG for publication as a Proposed Standard.

3) Develop the protocol specifications to support SAVA and submit them
   to the IESG for publication as Proposed Standards.

The WG Will NOT:

1) Work on end-end verification for applications and hosts, although
   hooks may be provided to allow applications to discover if the
   source address of a packet comes from a ¡°SAVA Compliant¡± Network.

2) Work on mechanisms to solve the problem in IPv4 networks, although
   it is recognized that some mechanisms and protocols may have
   application in IPv4 networks.

Goals and Milestones:

Mar 07	 Hold BoF in Prague, asking for this Charter to be approved

Jul 07 Final version of Charter approved and WG created.

Nov 07 Submit WG Draft-00 on Problem Statement for SAVA

Nov 07 Submit WG Draft 00 on Architectural Framework for SAVA

Mar 08 Submit WG Draft 00 for SAVA components (may happen in other WGs)

Jul 2008 and beyond:  Submit Drafts to IESG as informational RFCs and Proposed Standards.