Interpretation of policy language

Slides:



Advertisements
Similar presentations
LACNIC Policy Update Roque Gagliano LACNIC. Current Policies Proposals - LACNIC As a result of the Open Policy Forum at LACNIC XI four policy proposals.
Advertisements

Experimental Internet Resource Allocations Philip Smith, Geoff Huston September 2002.
Internet Number Resources 1. Internet IPv4 addresses IPv6 addresses Autonomous System number Fully Qualified Domain Name Key Internet resources.
Update about the “SHOULDs Analysing Project” in RIPE Policy Documents “Should” we use the RFC 2119 Defined Language in RIPE Policy Documents? Jan Žorž,
IPv4 Addresses. Internet Protocol: Which version? There are currently two versions of the Internet Protocol in use for the Internet IPv4 (IP Version 4)
December 2013 Internet Number Resource Report. December 2013 Internet Number Resource Report INTERNET NUMBER RESOURCE STATUS REPORT As of 31 December.
March 2014 Internet Number Resource Report. March 2014 Internet Number Resource Report INTERNET NUMBER RESOURCE STATUS REPORT As of 31 March 2014 Prepared.
1 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.
Electronic Submission of Medical Documentation (esMD) Clinical Document Architecture R2 and C-CDA Comparison April 24, 2013.
IPv6 Addressing – Status and Policy Report Paul Wilson Director General, APNIC.
Rose-Hulman Institute of Technology Sriram Mohan 18.September.2008 CSSE 497 Requirements Review.
Draft Policy ARIN : Modification to Criteria for IPv6 Initial End-User Assignments.
5-1 Facilitating Business over the Internet: The XML language CR (2004) Prentice Hall, Inc. The xml goals The main objects of xml: Diagrams: Blocks and.
The Resource Public Key Infrastructure Geoff Huston APNIC.
IPv4 Addresses. Internet Protocol: Which version? There are currently two versions of the Internet Protocol in use for the Internet IPv4 (IP Version 4)
APNIC Policy Update 1 st TWNIC Open Policy Meeting 3 December, 2003 Taipei, Taiwan.
CERTIFICATION EXAM. Page 2 The Certification Exam No books, notes or other aids 30 questions in 30 minutes Each question has 4 alternatives Any number.
Policy Experience Report Leslie Nobile. Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness Identify areas where new or modified.
ICANN Root Name Server System Advisory Committee March 2, 1999 SUNTEC Convention Center Singapore.
Erik Bais, May 13 th 2015 PP – unassigned yet General Transfer Policy Presenter : Erik Bais –
Web Programming Week 2 Old Dominion University Department of Computer Science CS 418/518 Fall 2010 Martin Klein 09/07/10.
CDNI Requirements (draft-lefaucheur-cdni-requirements-02) CDNI Working Group IETF 81 Quebec City, Canada July 28, 2011 Kent Leung Yiu.
Unintended side-effects Amending the transfer policy (soon to be called ) James Blessing, Sandra Brown, Remco van Mook.
Requirements standards (use- case model) A use case is a technique used in software and systems engineering to capture the functional requirements of.
1 Requirements for Internet Routers (Gateways) and Hosts Relates to Lab 3. (Supplement) Covers the compliance requirements of Internet routers and hosts.
1 ipv6-node-02.PPT/ 18 November 2002 / John Loughney IETF 55 IPv6 Working Group IPv6 Node Requirements draft-ietf-ipv6-node-requirements-02.txt John Loughney.
Current Policy Topics Emilio Madaio RIPE NCC RIPE November 2010, Rome.
AFRINIC Update Madhvi Gokool Registration Service Manager RIPE66 meeting, Dublin May 2013.
1 ipv6-node-02.PPT/ 18 November 2002 / John Loughney IETF 55 IPv6 Working Group IPv6 Node Requirements draft-ietf-ipv6-node-requirements-02.txt John Loughney.
1 IANA global IPv6 allocation policy [prop-005-v002] Policy SIG 1 Sept 2004 APNIC18, Nadi, Fiji.
1 IETF 91, 10 Nov 2014draft-behringer-anima-reference-model-00.txt A Reference Model for Autonomic Networking draft-behringer-anima-reference-model-00.txt.
Whois & Data Accuracy Across the RIRs. Terms ISP – An Internet Service Provider is allocated address space by an RIR for the purpose of providing connectivity.
Using the Research by Subject Pages 1. The research by subject link is a shortcut for library users interested in finding key resources associated with.
Contracts Offer and Acceptance Business Law Modified: Jan 2013.
E-Genting Programming Competition 2005
Chapter 5 – Requirements Engineering
Toward Best Practice for Language Resource Conversion
COMPREHENSIVE PLAN 2017 AMENDMENT PROCESS and DOCKET
59 Draft Policy Allocation of IPv4 and IPv6 Address Space to Out-of-region Requestors.
IETF 55 IPv6 Working Group IPv6 Node Requirements
Goals of soBGP Verify the origin of advertisements
2002網際網路趨勢研討會IPv6 Tutorial
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
Measuring Outcomes of GEO and GEOSS: A Proposed Framework for Performance Measurement and Evaluation Ed Washburn, US EPA.
AfriNIC Transition Plan
APNIC Trial of Certification of IP Addresses and ASes
IPv4 Addresses.
What is Cookie? Cookie is small information stored in text file on user’s hard drive by web server. This information is later used by web browser to retrieve.
IPv6 Documentation Address Policy
ARIN Scott Leibrand / David Huberman
APNIC Trial of Certification of IP Addresses and ASes
A Proposal for IPv4 Essential Infrastructure
RIPE Policy Landscape Filiz Yilmaz ESNOG, February 2008.
Requiring aggregation for IPv6 subsequent allocations
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
A view from ARIN, LACNIC & RIPE Communities Laura Cobley
Thursday, 20th of July 2017.
Jane Zhang & Wendy Zhao Wei
Prop-078-V002: IPv6 deployment criteria for IPv4 final /8 delegations
Overview of policy proposals
ARIN Inter-RIR Transfers
Experimental Internet Resource Allocations
Title page with photos and adjectives that describe your year
Private Information Handling at APNIC Database
Interpretative reading
Service Guideline Stands for Common Evaluation Principles
Proposal to Change IPv6 Initial Allocation Criteria
Invited talk to the MPLS WG by Anonymous Chair
Removing aggregation criteria for IPv6 initial allocations
M. Boucadair, J. Touch, P. Levis and R. Penno
Presentation transcript:

Interpretation of policy language Jan Žorž Completely random member of Internet community, no hats 

Sharing the story Afrinic meeting in Zambia this year Address Policy WG meeting The text that provoked this presentation: “The LIR should also plan to announce the allocation as a single aggregated block in the inter-domain routing system within twelve months.”

RFC2119 MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

What is the RFCs practice? The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

There is more Other terms/words aren’t clearly defined as well End User End Site Etc.

Questions: Is this not a problem and we do nothing? Should we interpret “should” as a “must”? Should we adopt the RFC2119 specification in the policy text? Should we include other recurring terms/words?