Comments on <draft-ietf-isis-ip-interoperable-00.txt>

David Meyer <dmm@sprint.net> Sun, 16 March 2003 23:40 UTC

Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13289 for <rtg-dir-archive@ietf.org>; Sun, 16 Mar 2003 18:40:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GNv9O02325; Sun, 16 Mar 2003 18:57:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2GNsuO02260 for <rtg-dir@optimus.ietf.org>; Sun, 16 Mar 2003 18:54:56 -0500
Received: from sith.maoz.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13244 for <rtg-dir@ietf.org>; Sun, 16 Mar 2003 18:38:18 -0500 (EST)
Received: (from dmm@localhost) by sith.maoz.com (8.12.8/8.12.8) id h2GNewDE012912; Sun, 16 Mar 2003 15:40:58 -0800
Date: Sun, 16 Mar 2003 15:40:58 -0800
From: David Meyer <dmm@sprint.net>
To: rtg-dir@ietf.org
Cc: jparker@axiowave.com
Subject: Comments on <draft-ietf-isis-ip-interoperable-00.txt>
Message-ID: <20030316154058.A12903@sprint.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Sender: rtg-dir-admin@ietf.org
Errors-To: rtg-dir-admin@ietf.org
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>

        Overall, a well written and informative draft which
	does a good job of classifying where interoperability
	issues arise, and provides solutions to those
	situations. I have only 2 minor comments:


        I.      Section 7, discussion of the Overload Bit:

                "An implementation MAY use the Overload Bit to
                signal that it is not ready to accept transit
                traffic."  

                We might consider making this a little stronger,
                e.g., "SHOULD".  


        II.     Section 17, full copyright:

                "Copyright (C) The Internet Society (1997)."