From 56969d652baa6d479545fb1f0fb9bd8e8c854cc3 Mon Sep 17 00:00:00 2001
From: Guy Harris <guy@alum.mit.edu>
Date: Thu, 1 Jul 2004 08:35:49 +0000
Subject: [PATCH] Update the URL of FRF 3.2.

Note that it's been claimed that an address field whose first byte has
the low-order bit not zero indicates Frame Relay fragmentation, FRF.12,
and that we should perhaps handle that.

svn path=/trunk/; revision=11295
---
 packet-fr.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/packet-fr.c b/packet-fr.c
index afbbdadb51..5d2637c0c4 100644
--- a/packet-fr.c
+++ b/packet-fr.c
@@ -3,7 +3,7 @@
  *
  * Copyright 2001, Paul Ionescu	<paul@acorp.ro>
  *
- * $Id: packet-fr.c,v 1.48 2004/05/24 02:25:18 guy Exp $
+ * $Id: packet-fr.c,v 1.49 2004/07/01 08:35:49 guy Exp $
  *
  * Ethereal - Network traffic analyzer
  * By Gerald Combs <gerald@ethereal.com>
@@ -26,7 +26,7 @@
  * References:
  *
  * http://www.protocols.com/pbook/frame.htm
- * http://www.frforum.com/5000/Approved/FRF.3/FRF.3.2.pdf
+ * http://www.mplsforum.org/frame/Approved/FRF.3/FRF.3.2.pdf
  * ITU Recommendations Q.922 and Q.933
  * RFC-1490
  * RFC-2427
@@ -246,6 +246,8 @@ dissect_fr_common(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree,
   if (fr_octet & FRELAY_EA) {
     /*
      * Bogus!  There should be at least 2 octets.
+     * XXX - is this FRF.12 frame relay fragmentation?  If so, we
+     * should dissect it as such, if possible.
      */
     address = 0;
     if (tree) {