Re: [Roll-bier-dt] Fwd: Bier interim in January

Alvaro Retana <> Wed, 28 November 2018 20:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 34559131059 for <>; Wed, 28 Nov 2018 12:00:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.737
X-Spam-Status: No, score=-1.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Udd1W9tT64Ih for <>; Wed, 28 Nov 2018 12:00:12 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5C34D130FE4 for <>; Wed, 28 Nov 2018 12:00:12 -0800 (PST)
Received: by with SMTP id v6so23716228oif.2 for <>; Wed, 28 Nov 2018 12:00:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=sIu6wAUvGQ76zyZ/HOCnF/RIBefqFfRKWhlvtB4sGAg=; b=LOkvHLEawhex1yrmsUGqf+24T4TmtGt6Vmf/iqH3xvqjz6kLhEXP/k5b6aphJ46YlY chjILyd6cBvRizLCV/D2SaDgCTCY9jEEdky5JnwDbLB/zn7XW1NGERRVVPKR9RIunWVI lvyrI/gkOmr+HLRdanNq6sZ5chMcZC/T6c43a8gkUtLK2NmUqgfe5UBhSsz28+PEmVTP n+zzHhVPjFyEW7uLvnrdWMYNpVjYmQn71h5WFBAkMjVTRRk/tBDOmJ/zMhYp37YzrUcI sX/fvQccr/FcKdDhb8lyl7e8WdIDhlh49azb3EV8uOHlSuR3wyblKityUg3z93GV1M9q oO3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=sIu6wAUvGQ76zyZ/HOCnF/RIBefqFfRKWhlvtB4sGAg=; b=MFSLjeZtnd+h1DtRV+Cgb47pTR3XQgP5cktk8JNYaO6wiVXRdnVfuWGNyholYufXZv /mcF67aqFym+oVzA6ccH99dvM0Nq2AKarNA1fhUoz2Qw6jkP/vtoKYUnEUvCHOPyiArM 66dMNQGmpMx7Ms+lhPQ1K+Rgpfk24j2UlHzYcRHXGQKxU8GVbQYprQ7/MisDmsx7U7KQ O+Wq1d/OvTPgB+TERdUzV9CTnCyxk0VZ2tlUPR/s9wDLGn6793wcjFB3C44viJAlWMUj qltQF5s5qr5VntC6lG7/tdz+clTHumnvo+UMhACUTF4YQmcVdBDN//bRdI8wXuGhHq3a ddtA==
X-Gm-Message-State: AA+aEWagoEtfiPvNzezmYQMxxtIAJoVBT/uQms2pCpKFxzKK0rJ1uZsI kLFOxYUBytPaQC5XE2Tg2pwMrLvx2REqVWH+g2taXw==
X-Google-Smtp-Source: AFSGD/XjcTxFixVEd5XcwfGTUXbMDbBOikDFHkkfCQ3xV+6xYv3NxH32t7ZHZy0zBFgIk38nFOGcgYu/tYf5sDCr+BE=
X-Received: by 2002:a54:4698:: with SMTP id k24mr6338185oic.37.1543435211496; Wed, 28 Nov 2018 12:00:11 -0800 (PST)
Received: from 1058052472880 named unknown by with HTTPREST; Wed, 28 Nov 2018 12:00:10 -0800
From: Alvaro Retana <>
In-Reply-To: <>
References: <> <> <> <> <> <> <>
X-Mailer: Airmail (528)
MIME-Version: 1.0
Date: Wed, 28 Nov 2018 12:00:10 -0800
Message-ID: <>
To: "" <>
Cc: "Pascal Thubert (pthubert)" <>, Toerless Eckert <>, "" <>, IJsbrand Wijnands <>, Peter van der Stok <>
Content-Type: multipart/alternative; boundary="00000000000083e2e4057bbf0311"
Archived-At: <>
Subject: Re: [Roll-bier-dt] Fwd: Bier interim in January
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "ROLL WG Design Team for bitstring addressing. See" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Nov 2018 20:00:22 -0000

Just a high-level comment/question…. Off topic...

I’m hoping that "to set the stage for the set of required followup
documents specifying the solution” means that the informational document(s)
will most likely serve their purpose as inspiration for the solution
only…and not be published as RFCs.  Is that the intent?  Or is the intent
to publish that as requirements, framework, or whatever-else RFCs…and
*later* work on solutions?

I realize that without knowing the specific content of those document it
may be hard to provide a definite answer…so I’m just looking for intent at
this point.



On November 28, 2018 at 11:25:19 AM, Toerless Eckert ( wrote:

a) Lets first determine what the next step is in the documents for
roll-bier that we want to achieve by IETF104.

Ines was suggesting that we should consider a high-level overview
draft, for example reformatting into draft form what we had worked
out in slides and the etherpad in the design team. Primarily goal
would be to set the stage for the set of required followup documents
specifying the solution.

I could take a stab at that, but maybe good parts of this should come
fro pascals document, e.g.: splitting up the informational parts from
the normative parts and extending on the informational ones .. ?

And then fesible next steps for the drafts specifying the solution.
Right now the primary documents existing are the one from pascal
and carsten, so i would like their input for how they could see
those documents evolve until 104.

Please chime in if this is the right goal, and if so, what it should