rtg.ripv2.agenda
Gary Scott Malkin <gmalkin@xylogics.com> Sun, 17 July 1994 22:57 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03962; 17 Jul 94 18:57 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03958; 17 Jul 94 18:57 EDT
Received: from atlas.xylogics.com by CNRI.Reston.VA.US id aa11055; 17 Jul 94 18:57 EDT
Received: by atlas.xylogics.com id AA00788 (5.65c/UK-2.1-940401); Sun, 17 Jul 1994 18:55:30 -0400
Received: by atlas.xylogics.com id AA01773 (5.65c/UK-2.1-940401); Sun, 17 Jul 1994 18:55:18 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Gary Scott Malkin <gmalkin@xylogics.com>
Date: Sun, 17 Jul 1994 18:55:18 -0400
Message-Id: <1773.199407172255@atlas.xylogics.com>
To: admin@ds.internic.net, internet-announce-post@CNRI.Reston.VA.US
Cc: ietf-rip@xylogics.com
Subject: rtg.ripv2.agenda
AGENDA RIP Version 2 WG (ripv2) 30th IETF - Toronto Tuesday, July 26, 1994 1930-2200 1 - Review Protocol Analysis The purpose of the review is to ensure that all existing implementations have been included. Also, if any other interoperability testing has been done, it should be included as well. 2 - Review Applicability Statement The purpose of the review is to ensure that all of the major features of the procotol have been covered. 3 - Discussion of Jeff Honig's "infinity=15" problem Is there a fix worth applying? Remember backwards compatibility. 4 - Discussion of Next Hop usage The Applicability Statement mentions an additional use for the Next Hop field. Is it always safe? Can it be expanded further? 5 - Advancing RIP-2 and Demand Circuit RIP Go/No go? Any foreseeable problems? 6 - Any other issues 7 - Summary of decisions and action items
- rtg.ripv2.agenda Gary Scott Malkin