Initial setup of repo
This commit is contained in:
1
.gitignore
vendored
Normal file
1
.gitignore
vendored
Normal file
@@ -0,0 +1 @@
|
||||
.refcache
|
||||
21
Makefile
Normal file
21
Makefile
Normal file
@@ -0,0 +1,21 @@
|
||||
|
||||
DRAFTS = in-tree-hints
|
||||
OUTPUTS = $(foreach draft,$(DRAFTS),draft-${draft}.html draft-${draft}.xml draft-${draft}.txt)
|
||||
STAGING = staging.xml
|
||||
|
||||
all: $(OUTPUTS)
|
||||
|
||||
clean:
|
||||
rm -f $(OUTPUTS) *.$(STAGING)
|
||||
|
||||
draft-%.html: draft-%.xml
|
||||
xml2rfc $< --html
|
||||
|
||||
draft-%.xml: draft-%.md
|
||||
kramdown-rfc2629 $< > $*.$(STAGING)
|
||||
mv $*.$(STAGING) $@
|
||||
|
||||
draft-%.txt: draft-%.xml
|
||||
xml2rfc $< --text
|
||||
|
||||
.PHONY: all clean
|
||||
139
draft-in-tree-hints.md
Normal file
139
draft-in-tree-hints.md
Normal file
@@ -0,0 +1,139 @@
|
||||
---
|
||||
title: In Tree Hints for Resilliency
|
||||
abbrev: in-tree-hints
|
||||
docname: draft-kolkman-in-tree-hints
|
||||
category: info
|
||||
|
||||
ipr: trust200902
|
||||
area: ops
|
||||
workgroup: dnsop
|
||||
keyword: Internet-Draft
|
||||
stand_alone: yes
|
||||
pi:
|
||||
RFCedstyle: yes
|
||||
toc: yes
|
||||
tocindent: yes
|
||||
sortrefs: yes
|
||||
symrefs: yes
|
||||
strict: yes
|
||||
comments: yes
|
||||
inline: yes
|
||||
text-list-symbols: -o*+
|
||||
|
||||
author:
|
||||
-
|
||||
ins: O. Kolkman
|
||||
name: Olaf Kolkman
|
||||
organization: Internet Society
|
||||
email: kolkman@isoc.org
|
||||
|
||||
|
||||
|
||||
normative:
|
||||
RFC5011:
|
||||
|
||||
informative:
|
||||
|
||||
RFC1958:
|
||||
|
||||
|
||||
saltzer:
|
||||
title: "End-to-end arguments in system design"
|
||||
date: 1984
|
||||
author:
|
||||
- ins: J. H. Saltzer, et al
|
||||
target: https://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf
|
||||
|
||||
dkg:
|
||||
title: "Human Rights Protocol Considerations Glossary"
|
||||
date: 2015
|
||||
author:
|
||||
- ins: D. Gillmor
|
||||
target: https://tools.ietf.org/html/draft-dkg-hrpc-glossary-00
|
||||
|
||||
mls:
|
||||
title: "Messaging Layer Security"
|
||||
date: 2018
|
||||
author:
|
||||
- ins: IETF
|
||||
target: https://datatracker.ietf.org/doc/charter-ietf-mls
|
||||
|
||||
openpgp:
|
||||
title: "Open Specification for Pretty Good Privacy"
|
||||
date: 2020
|
||||
author:
|
||||
- ins: IETF
|
||||
target: https://datatracker.ietf.org/doc/charter-ietf-openpgp
|
||||
|
||||
GEC-EU:
|
||||
title: "Breaking encryption myths: What the European Commission’s leaked report got wrong about online security"
|
||||
date: 2020
|
||||
author:
|
||||
- ins: Global Encryption Coaliation
|
||||
target: https://www.globalencryption.org/2020/11/breaking-encryption-myths/
|
||||
|
||||
hale:
|
||||
title: "On End-to-End Encryption"
|
||||
date: 2021
|
||||
|
||||
--- abstract
|
||||
|
||||
Lorem ipsum dolor sit amet, mea et probo aeque honestatis. Ne mel modus audiam quaeque, velit tamquam prodesset ei sea. Putent definitiones interpretaris te nec, ei eos cibo indoctum. Vide quodsi sensibus pri et, nisl dissentias ne qui. Facer inciderint vim in, has mandamus cotidieque ea. Eos quaeque honestatis cu, detraxit postulant concludaturque in eum.
|
||||
|
||||
|
||||
--- middle
|
||||
|
||||
Introduction
|
||||
============
|
||||
|
||||
The Domain Name System (DNS) is a remarkably stable and resilient system. However, in many environments people are looking on how they can remain in control over their own environments under systemic stress.
|
||||
|
||||
In this document we design an operational approach that, with minor support of recursive nameserver can offer one of the elements towards greater autonomy of infrastructure dependent on a specific domain.
|
||||
|
||||
Our approach is designed to be consistent with the design and operation of the DNS. We avoid namespace fragmentation or fundamental protocol changes, in particular we avoid the need for alternative roots.
|
||||
|
||||
The approach describes what the parties that are critically dependent on a specific domain and those that serve zones within that domain will need to do in order to guarantee continuous operation in the case that there is breakage in its ancestral (parent, grandparent etc) domain such as for instance un-reachability of their nameservers or a de-delegation.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
An saepe adversarium nec
|
||||
==========================================
|
||||
|
||||
Est ea homero platonem. An saepe adversarium nec, nec graecis adipiscing instructior ad, no vix velit nullam dolorum. Ex eam quod soleat eloquentiam. Nam ad illud viderer, per id facilis maiorum. Eum amet audire ut.
|
||||
|
||||
eugiat vituperata
|
||||
---------
|
||||
His eu utamur feugiat vituperata. Eu duo consulatu consequuntur, eligendi argumentum reprehendunt his ex, pro insolens periculis te. Ex suas probo debitis usu. Vel nulla singulis te. Eu vis aliquid reprehendunt, cum cetero voluptua no.
|
||||
|
||||
atomorum salutandi definiebas.
|
||||
--------------------
|
||||
Ne mea prompta equidem, duo ut atomorum salutandi definiebas. Clita ponderum molestiae in nam. Veniam discere pri ex, an vix ornatus omittam ponderum. Assum delicata nam no, at natum delectus volutpat vim. Has summo commodo at. Mei in habeo nominavi.
|
||||
|
||||
Conclusions
|
||||
===========
|
||||
|
||||
Alii purto periculis at eum. Mei at simul qualisque, persius consetetur deterruisset nec an. Quot viderer reprimique ei eos, te pro quaeque perpetua. Has ex malis sensibus, et nec dico eligendi. Periculis aliquando eu sit.
|
||||
|
||||
His eu utamur feugiat vituperata. Eu duo consulatu consequuntur, eligendi argumentum reprehendunt his ex, pro insolens periculis te. Ex suas probo debitis usu. Vel nulla singulis te. Eu vis aliquid reprehendunt, cum cetero voluptua no.
|
||||
|
||||
Ne sea porro iuvaret, augue graeco phaedrum ut ius, solet intellegebat id cum. Aperiam nusquam eu vel. Te sed mazim vivendum definitionem, ad has nonumy mucius eirmod. Vel te meis doctus expetendis, tacimates interesset quo an. Dicta discere veritus no eum, cu habeo soluta definitionem qui. Antiopam democritum te cum.
|
||||
|
||||
Acknowledgements
|
||||
================
|
||||
|
||||
His eu utamur feugiat vituperata. Eu duo consulatu consequuntur, eligendi argumentum reprehendunt his ex, pro insolens periculis te. Ex suas probo debitis usu. Vel nulla singulis te. Eu vis aliquid reprehendunt, cum cetero voluptua no.
|
||||
|
||||
|
||||
Security Considerations
|
||||
=======================
|
||||
|
||||
Nam no paulo temporibus, ne eos homero facete quaerendum. Petentium contentiones ne pri. Enim maluisset liberavisse ius in, qui in putent debitis. Cu menandri pertinax mei. Mutat velit maiestatis mei et, option maluisset pri ea.
|
||||
|
||||
|
||||
IANA Considerations
|
||||
===================
|
||||
|
||||
This document has no actions for IANA.
|
||||
Reference in New Issue
Block a user