Return-Path: X-Original-To: dnsop@ietfa.amsl.com Delivered-To: dnsop@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB4B8120D15 for ; Mon, 23 Dec 2019 15:16:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 F4ATTlpIKEkR for ; Mon, 23 Dec 2019 15:16:30 -0800 (PST) Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0344E1200C5 for ; Mon, 23 Dec 2019 15:16:29 -0800 (PST) Received: by mail-oi1-x230.google.com with SMTP id d62so7284220oia.11 for ; Mon, 23 Dec 2019 15:16:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gP/RdKEJLpovQmSEY0+lnLEzl1ElOAjt5HJTzDPLFnU=; b=XtmO7mLEs6RzFqurFPLsr94hxauJZpZToZqBkkLesalA85lgb7SIFeEV5PlGAIrS+6 Gh0cw00qUPewK/KyKolguNqT2AlzCjgc8+UuZeT+5P3nZvJ9OWrNtMdB1t3j1HD0a6K4 03mIjmgBZF+DQHJ6OU3zSM4hY3Ks6XKD5RmORW11lieZZ1whVAJpu+6AAacMN2vVshcA CnP1Je8n2MSmsafsTFx9qfiuvDCtqCHB+yR8kq/QTjgtcHgpQkWe0rq+eip6njcrgB87 5iWR5vf8O89aMUBTu9ZAUl13toiMkosruTbpdH9tDP983n0Na8wNQjfsOYkxb5DFxODp YiuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gP/RdKEJLpovQmSEY0+lnLEzl1ElOAjt5HJTzDPLFnU=; b=UE+yq0VA4a1YgtnRUewsRroXnJPD9tleJGNKzsGF29E1W5UxO9dXnzUAqoOVer1Jbi T9u1DOWAp4c/mPqjfmuFPBOVezqzAet4DL2ME0s5gfPWC6iwXkAnPLmu235WuiJasl7G 6D0fQfzQFQhbd7u04sOC6tJ5al9c3Bx+8cKiNsdYlRo75FRBgQXpzL9MbpE5AbmbWNNH AobtUyet87LJZ+3uhOHBoY//X9TKHsFSX3LFd22aVaHtSyUg3iRXxwpcJjE3+8PVuUew Us2jjUszsrk0x80yDZcDOjOV9YWYQYnd5Vh2cXzmdvHY6lWEbzMTcaVHS0x2M6YvwDtV 0ugw== X-Gm-Message-State: APjAAAX/UHEMpQT4cmHoz8I5RXNE4JFbtkSnmSU5Y9ceVBA4KOIsjg4b jDsaf4HfelprVUFXDkf7rTGLtHJRpFBHGFuhTtGmxQ== X-Google-Smtp-Source: APXvYqwD4TpdP6USCr1N0Bo2oQcsvsFkDr1Y5cLsl9zQI62/miwZFtChiI/SKfD8qdRvtu0i0BblEEr/NdZhdPFKi2k= X-Received: by 2002:aca:5bd6:: with SMTP id p205mr430364oib.132.1577142989169; Mon, 23 Dec 2019 15:16:29 -0800 (PST) MIME-Version: 1.0 References: <20191122000302.3D09AF40709@rfc-editor.org> In-Reply-To: From: Tim Wicinski Date: Mon, 23 Dec 2019 18:16:18 -0500 Message-ID: To: Ray Bellis Cc: IETF DNSOP WG Content-Type: multipart/alternative; boundary="000000000000a12843059a673726" Archived-At: Subject: Re: [DNSOP] Fwd: [Editorial Errata Reported] RFC1035 (5915) X-BeenThere: dnsop@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF DNSOP WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2019 23:16:32 -0000 --000000000000a12843059a673726 Content-Type: text/plain; charset="UTF-8" +1 on "Complete" Tim (no hats this time) On Mon, Dec 23, 2019 at 5:01 PM Ray Bellis wrote: > > > On 20/12/2019 15:08, Bob Harold wrote: > > > But if we are updating it, could we consider a better word than > > "forward" ? Actually "backward" would be correct, although I prefer > > "from the back to the front" as used elsewhere. > > It's not possible to traverse the RRs in a raw DNS packet "backwards". > You have to start at the beginning and remember the offset of each RR > found. > > Ray > > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop > --000000000000a12843059a673726 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
+1 on "Complete"

Tim
(no hats this time)


On Mon, Dec 23, 2019 at 5:01 = PM Ray Bellis <ray@bellis.me.uk&= gt; wrote:


On 20/12/2019 15:08, Bob Harold wrote:

> But if we are updating it, could we consider a better word than
> "forward" ?=C2=A0 Actually "backward" would be cor= rect, although I prefer
> "from the back to the front" as used elsewhere.

It's not possible to traverse the RRs in a raw DNS packet "backwar= ds".
=C2=A0You have to start at the beginning and remember the offset of each RR=
found.

Ray


_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
--000000000000a12843059a673726--