IETF Logo Mail Archive

Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-03.txt> (Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)) to Internet Standard

Stig Venaas <stig@venaas.com> Tue, 17 March 2015 23:58 UTC

Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 337851A1BD9 for <pim@ietfa.amsl.com>; Tue, 17 Mar 2015 16:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 m4cneOyVOqmn for <pim@ietfa.amsl.com>; Tue, 17 Mar 2015 16:58:31 -0700 (PDT)
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (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 40B561A1B96 for <pim@ietf.org>; Tue, 17 Mar 2015 16:58:31 -0700 (PDT)
Received: by wibdy8 with SMTP id dy8so76327864wib.0 for <pim@ietf.org>; Tue, 17 Mar 2015 16:58:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=QJfyC15jiV9vdh/auAKVHPWXCzrT9rD7IntA1sGQ5NQ=; b=BhAr3M4O2LGccAXdft44DbWzKsUhW6E1SmjNBkhVRqxe/o3o107kZZ3TjnK6DdC66T 1127COb9Zv/JxRqmctnQhN9Q62jeZ8WfEB0h+PO2WeltNUTq88UDdEaceai47mf9Knev An4H0UySGYNlqDxv3+vaLtfeItFaqWms8NFrZNLcQeUVaqISs9vuG9MYOnlOzBpmux/+ D6wF1nE4zPcOUpmkWqFUExqMSwZZg1xhXG0XqRK8gxuRX8OuGVdgFGrEX+T+qpgG/xue H22AcSu54pdrOaJzN923IbPVrKbiqG0tDsAPRyjCVA0is+1/gjfbOzZY2QhfkmLLng3k peJA==
X-Gm-Message-State: ALoCoQmvuEQyY6lZWu7NAZiZ9fD3x2e8UKsQFttQdh+wG4+tAc3amSKVqhvbrl2GHYwEkdJNFrxp
MIME-Version: 1.0
X-Received: by 10.195.12.167 with SMTP id er7mr139538654wjd.54.1426636710019; Tue, 17 Mar 2015 16:58:30 -0700 (PDT)
Received: by 10.194.136.170 with HTTP; Tue, 17 Mar 2015 16:58:29 -0700 (PDT)
X-Originating-IP: [166.177.250.81]
Received: by 10.194.136.170 with HTTP; Tue, 17 Mar 2015 16:58:29 -0700 (PDT)
In-Reply-To: <20150311170332.GE874@cisco.com>
References: <20150213174210.6909.43630.idtracker@ietfa.amsl.com> <54F0BFB1.4090707@concordia.ca> <CAG4d1reOc4Wzkyqmg3YF_VXhUfWumVuSr3gTU8zAog9NC12sNg@mail.gmail.com> <20150311134617.GB874@cisco.com> <CAG4d1rfKE6xSHsJyw9xNf38f0Q+sz5J=pE-Fse-Toj7p9rgq2g@mail.gmail.com> <20150311145348.GD874@cisco.com> <CAG4d1rds32stf7iKpDijfiq-hnaC8Jks+HvO704YW1XdgOb9UA@mail.gmail.com> <20150311170332.GE874@cisco.com>
Date: Tue, 17 Mar 2015 16:58:29 -0700
Message-ID: <CAHANBt+5DiRYvonKDg7YCbjNx27_y-JKNwjLGBCb5oyAPgN84g@mail.gmail.com>
From: Stig Venaas <stig@venaas.com>
To: Toerless Eckert <eckert@cisco.com>
Content-Type: multipart/alternative; boundary="047d7bb04bbe5319bf051184bef4"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/gJRcMBjS-MUIxcrvkPBYs6x4p0c>
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-03.txt> (Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)) to Internet Standard
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2015 23:58:33 -0000

There are no changes that I'm aware of needed for an implementation of 4601
to comply with the current 4601bis. I believe the errata mainly fix issues
that are fairly obvious. There may have been some issues that caused
confusion so an implementer of 4601 may in some cases have misunderstood
something.

I think listing all the errata that got addressed in 4601bis is a bit much.
Both a diff and the errata themselves are available if an implementers of
4601 wants to check.

Stig

v2.23.0 | Report a Bug | By Email