[sidr] Proposal for next steps - chartering sidrops?

joel jaeggli <joelja@bogus.com> Wed, 17 August 2016 16:46 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 174E612DA17 for <sidr@ietfa.amsl.com>; Wed, 17 Aug 2016 09:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.147
X-Spam-Level:
X-Spam-Status: No, score=-8.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.247] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id APIB0hBOQc0L for <sidr@ietfa.amsl.com>; Wed, 17 Aug 2016 09:46:34 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDD8B12DBFC for <sidr@ietf.org>; Wed, 17 Aug 2016 09:46:32 -0700 (PDT)
Received: from mbp.local ([IPv6:2620:11a:c081:20:602a:5e74:b376:17ff]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u7HGkTKG081260 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 17 Aug 2016 16:46:30 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2620:11a:c081:20:602a:5e74:b376:17ff] claimed to be mbp.local
To: sidr wg list <sidr@ietf.org>, routing-ads@ietf.org, sdir-chairs@ietf.org
From: joel jaeggli <joelja@bogus.com>
Message-ID: <dd98327d-4487-d9dc-af63-82ed5ed2f5aa@bogus.com>
Date: Wed, 17 Aug 2016 09:46:28 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:47.0) Gecko/20100101 Thunderbird/47.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/zIzq66KpUYOLItg58mJoaQnqge0>
Cc: "Benoit Claise \(bclaise\)" <bclaise@cisco.com>
Subject: [sidr] Proposal for next steps - chartering sidrops?
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2016 16:46:36 -0000

Folks,

Some discussion prior to the recent IETF led us to ask the ask the
question about what to do now that SIDR is close to having achieved it's
major milestones. One possible approach we have been looking at is to
Charter a new activity associated with the deployment and operation of
SIDR systems within networks. Here is an initial stab at a sidrops
charter with the milestones drawn from existing SIDR discussion.

https://datatracker.ietf.org/doc/charter-ietf-sidrops/


  The global deployment of RPKI, Origin Validation of BGP announcements
  and BGPSEC, collectively called SIDR, is underway, creating an Internet
  Routing System consisting of SIDR-aware and non-SIDR-aware networks.
  This deployment must be properly handled to avoid the division of
  the Internet into separate networks, ensuring as secure a routing
  system as possible, through encouraged deployment of the SIDR technologies.

  The SIDR Operations Working Group (sidr-ops) develops guidelines for
  the operation of SIDR-aware networks, and provides operational guidance
  on how to deploy and operate SIDR technologies in new and existing networks.

  The main focuaess of the SIDR Operations Working Group are to:
    o discuss deployment and operational issues related to SIDR technologies
      in networks which are part of the global routing system.
    o gather and discuss deployment experiences with the SIDR technologies in
      networks which are part of the global routing system.

  The goals of the sidr-ops working group are:

  1.  Solicit input from network operators to identify
  operational issues with a SIDR-aware Internet, and determine solutions
  or workarounds to those issues.

  2.  Solicit input from network operators to identify
  operational interaction issues with the non-SIDR-aware Internet,
  and determine solutions or workarounds to those issues.

  3.  Operational solutions for identified issues should be developed
  in sidr-ops and documented in informational or BCP documents.

  These documents should document SIDR operational experience, including
  interactions with non-SIDR-aware networks, the interfaces between SIDR-aware
  and non-SIDR-aware networks, and the continued operational/security impacts
  from non-SIDR-aware networks.

  SIDR operational and deployment issues with Interdomain Routing Protocols
  are the primary responsibility of the IDR working gruop.  However, the
  sidr-ops Working Group may provide input to that group, as needed, and
  cooperate with that group in reviewing solutions to SIDR operational and
  deployment problems.

  Future work items within this scope will be adopted by the Working
  Group only if there is a substantial expression of interest from
  the community and if the work clearly does not fit elsewhere in the
  IETF.

  There must be a continuous expression of interest for the Working
  Group to work on a particular work item.  If there is no longer
  sufficient interest in the Working Group in a work item, the item
  may be removed from the list of Working Group items.


Feedback on this proposal and possible milestones above and beyond those
currently present is appreciated before we circulate this for wider review.