Docs on Miek Gieben

LaTeX cheat sheet

Mon, 08 Oct 2018 10:23:00 +0000

This is a small LaTeX cheat sheet:

Section:

Use: \section{name}

Subsection:

Use: \subsection{name}

List (unumered):

Use:

\begin{itemize}
\item{My first list item}
\item{My second list item}
\end{itemize}

List (numbered):

Use:

\begin{enumerate}
\item{My first list item}
\item{My second list item}
\end{enumerate}

Emphesis:

\emph{text}

Bold:

\textbf{text} Citation: \cite{reference} (actually managing your bibliography is left out). Citing with parens is done with \citep{reference}, and with a page ref you need: \cite[p. 145]{reference} (or citep).

Mmark Updates

Mon, 09 May 2016 18:54:21 +0100

Recent bug reports prompted some Mmark development (guess I am into bug-driven development). New releases can be found on Github. Anyway Mmark saw some bug fixes and new features:

A feature/pull request from blackfriday got merged, meaning that two different lists are not merged into one:

* A
* B

1. One
2. Two

Is now correctly seen as two different lists.

Further more a <br/> is converted to a <vspace/> in the XML output. This is especially useful when you want a vertical space after a definition term. See rfc/rfc7511.md for an example on how to use this.

Mmark Syntax Document

Sat, 05 Mar 2016 11:13:21 +0000

The canonical version of this document is the version in the Github Wiki.

Mmark Syntax

All syntax elements should be described. Please open an issue or PR if there is something you want to improve here, or even better, edit the doc!

This document describes all the syntax elements that can be used in Mmark. Mmark’s syntax is based on the “standard” Markdown syntax.

It adds numerous enhancements to make it suitable for writing (IETF) Internet Drafts and even complete books. It ~~steals~~ borrows syntax elements from pandoc, kramdown, leanpub, asciidoc, PHP markdown extra and Scholarly markdown.

Inline Attribute Lists

Tue, 01 Mar 2016 14:14:24 +0000

Mmark is a powerful markdown parser.

With Inline Attribute Lists (IALs) you can add extra information to block elements, think of extra classes, attributes or an ID. In Mmark these have the syntax: {#id .class attr="key"}. And should be specified before a block level element.

These will mostly be backend specific, i.e. a {color="blue"} might do something in HTML5 output, but does nothing in the XML v2 output. Worse yet; the XML might not validate anymore. Mmark try to help here by white listing the allowed attributes for an element (this happens in each renderer and is currently a work in progress).

Subfigures in mmark

Sat, 03 Oct 2015 13:24:00 +0000

For XML2RFC version 3 there is a new extended figure element, namely: it can contain multiple <artwork> or <sourcecode> (new in v3) elements. This in turn meant that mmark needed some way to signal “these artworks belong together”. Now Scholarly markdown has a syntax for this. It uses a special section syntax and all images in that section become subfigures of a larger figure. Disadvantage of this syntax is that it can not be used in lists. Hence mmark uses a quote like solution, just like asides (A>), but for figures: we prefix the entire paragraph with F> .

Callouts in Figures in Mmark

Sun, 27 Sep 2015 14:02:00 +0000

The use of callouts in Mmark came from Asciidoc, they are “… a mechanism for annotating verbatim text”. In mmark they work like this.

In a codeblocks you can use <1>, or <2>, etc. to create a callout. After the codeblock/figure you can reference it. An example:

    Code  <1>
    More  <1>
    Not a callout \<3>

As you can see in <1> but not in \<1>. There is no <3>.

This will be rendered as:

Lists in lists with style

Thu, 24 Sep 2015 11:56:00 +0000

Mmark is a markdown dialect for writing RFCs (or books!). The main reason it exists is because the IETF is developing a new XML format (version 3) for writing RFCs. This new format is way more powerful, so sadly Pandoc2rfc does not cut it anymore.

Right now mmark fully supports writing RFCs in XML2RFC version 2, but anything written can also be converted to the (work-in-progress) XML2RFC version 3 format. In a series of blog posts I will detail some of the features, such as list styling while remaining upwards compatible.

Markdown for XML2RFC v3 - Update

Thu, 18 Dec 2014 22:46:00 +0000

And another update (2015-01-12)

This is a follow up the previous article about using markdown for XML2RFC. The syntax has been changed and more features have been implement. And my blackfriday fork has been renamed mmark.

See this document for an up to date syntax of mmark. A short summery will be given here.

New features are:

Include raw XML references
Allow HTML comments to be converted to crefs
Abbreviations (https://michelf.ca/projects/php-markdown/extra/#abbr), this is not used in XML2RFC but seems a relatively standard markdown extension
Example lists (http://johnmacfarlane.net/pandoc/README.html#numbered-example-lists)
Quote attribution

Also the possibility to convert pandoc2rfc documents to mmark has been added (as a quick and dirty perl script + pandoc!):

Markdown for XML2RFC v3

Thu, 27 Nov 2014 22:50:00 +0000

Or… how to write Markdown to generate XML that is valid XML2RFC v3. These are some assorted notes and ideas

Goal:

Self contained file with all information to generate a complete I-D;
CommonMarkdown, with some extension.

I’m working on implementing these ideas in blackfriday. The following has already been implemented:

Abstract;
Citation;
Document divisions;
Index;
File inclusion;
Extra attributes (kramdown’s IAL.) (work-in-progress).

Document meta data

In TOML - much easier than YAML for instance, lines are starting with %. We don’t need to specify the citations here because:

Learning Go

Sun, 01 Jun 2014 08:33:00 +0000

“Learning Go” is a book that gives an introduction into the Go language of Google. It is licensed under a copy-left license. The book currently consists out +/- 120 (A4 sized) pages and the following chapters:

Introduction
Show how to install Go and details the lineage of the language Go.
Basics
Types, variables and control structures.
Functions
How to make and use functions.
Packages
Functions and data is grouped together in packages. Here you will see how to make your own package. How to unit test your package is also described.
Beyond the basics
Learn how to create your own data types and define function on them (called methods in Go).
Interfaces
Go does not support Object Orientation in the traditional sense. In Go the central concept is interfaces.
Concurrency
With the go keyword function can be started in separate routines (called goroutines). Communication with those goroutines is done via channels.
Communication
How to create/read/write from and to files. And how to do networking.

Each chapter concludes with a number of exercises (and answers) to may help you to get some hands on experience. Currently it has more than 30 exercises.

New Site Based on Pelican

Sun, 19 Jan 2014 12:50:00 +0000

I’ve revamped http://miek.nl it is now using Pelican, instead of nanoblogger. The old miek.nl site is available via http://archive.miek.nl.

I’m in the progress of migration articles over. I still need to think what I want to do with my project pages, because most stuff lives on on https://github.com/miekg.

Project page for Learning Go

Thu, 11 Aug 2011 11:15:00 +0000

I added a shiny project page for the “Learning Go” book I’m writing.

Errata, new releases and other stuff will get a place there.

For good measure I even added a “Donate” button - we’ll see how to that plays out.

Older (DNSSEC) presentations

Wed, 27 Aug 2008 13:18:00 +0000

Some older presentations I have given can be found here.

The all deal with DNSSEC - note that most of them have been written a few years ago.

Cisco DNSSEC paper

Sun, 27 Jul 2008 14:14:00 +0000

Just came by this, an article I wrote for Cisco (Internet Protocol Journal) back in 2004.

The article

RFC4641

Sun, 17 Feb 2008 10:33:00 +0000

Co-author of RFC 4641 a BCP (Best Current Practice) for DNSSEC operations. This was written together with Olaf Kolkman.

At the time I was employed at NLnet Labs

This RFC gives guidelines on how to setup secure zones in a world with DNSSEC. It also gives pointers for public and private key handling and deals with the key lengths and how to handle key rollovers.

DNSSEC: problemen en beloftes

Sun, 10 Feb 2008 16:50:00 +0000

older publication: 2001

Door

R. Gieben, miek@nlnetlabs.nl or miek@miek.nl

Voorwoord In dit introductie artikel behandel ik DNSSEC en de beloftes en problemen die het met zich mee brengt. Daarbij wil ik uit leggen wat de bijdrage van NLnet Labs is geweest in het analyseren en oplossen van enkele van die problemen. Verder ga ik in op de plannen voor de uitrol van DNSSEC in Nederland in de nabije toekomst.

NLnet Labs is opgericht door [Stichting NLnet] 1 om nieuwe protocollen en applicaties te promoten en te ontwikkelen voor het Internet. Er is een budget voor 15 jaar ontwikkeling door 6 developers.

DNSSEC in the .nl zone mini HOWTO. The .nl.nl-experiment.

Sun, 10 Feb 2008 14:53:00 +0000

published in 2003

DNSSEC mini HOWTO

By Paul Wouters (paul@xtdnet.nl)

Introduction

This article is a translation of the article “Secure DNS, Het beveiligingen van DNS in de praktijk that appeared in C’T magazine on March 14 2003.

DNSSEC in the .nl zone

The Dutch NIC (SIDN [http://www.domain-registry.nl/]>), The European Regional Internet Registry (RIPE), and NLnetLabs have created the first toplevel secure DNS. The experiment is running its own set of nameservers to guarantee that the experiment will not interfere with the production nameservers. The project started in November of 2002 with the goal of gaining experience in running DNSSEC for a TLD Registry.

DNSSEC in NL or the .nl.nl experiment

Sun, 10 Feb 2008 12:22:00 +0000

This is an older publication (from 2004).

This report gives an outline of the current status of SECREG, the Dutch experiment for introducing DNSSEC in NL.

It is written for SIDN (the people who take care of .nl) and it tries to explain what DNSSEC will mean for a registry.

Downloads are here:

Master's Thesis: Chain of Trust

Sun, 23 Dec 2007 00:17:00 +0000

master’s thesis

For future reference. My master’s thesis can be found here. It details the development of the DNSSEC protocol, a supposed successor of the DNS on the Internet.

It was officially publiced as a research document by my university (University of Nijmegen).

You can find the thesis (pdf|ps) here:
CSI-report.pdf.
CSI-report.ps.

.my talk

Sat, 22 Dec 2007 19:40:00 +0000

.my

I was recently invited to give a talk in KL (Malaysia) about DNSSEC. They are running a three year program after which .my should be signed.

You can find the talk (pdf) here:
dot-my-pres.pdf.