Subject: RE: [SUA Issue] Hop Counter

From: "Gradischnig, Klaus" <[email-masked]>
Date: Thu, 30 Aug 2001 08:46:22 -0500

Gery,

I fully support your position. The hop counter and its use as described by
you has to be made mandatory in SUA. Anything else defeats its purpose.

Klaus

> -----Original Message-----
> From: Verwimp Gery [mailto:[email-masked]]
> Sent: August 28, 2001 9:32 AM
> To: sigtran
> Subject: RE: [SUA Issue] Hop Counter
> 
> 
> John,
> 
> Hop counter is mandatory for CLDT, CLDR and CORE (all that 
> can be routed on
> GT).  Procedures apply to decrement the hop counter whenever 
> GTT/AMF is
> invoked to prevent loops.
> 
> There's also no reason why the hop counter value can't be 
> transparently
> passed between SCCP and SUA at the SG. The perceived 
> "impossibility" again
> comes from an incorrect view of the NIF as "SCCP or 
> SUA-user", which doesn't
> have the hop counter in the "user interface". But the NIF is 
> any possible
> interworking between SCCP and SUA at the SG.
> 
> Regards,
> 
> ____________________________
> 
> Gery Verwimp
> > SIEMENS ATEA
> > ICN D CS D5
> > 
> > Tel. : +32 14 25 3424
> Fax : +32 14 25 3212
> mailto:[email-masked]
> ____________________________________
> 
> 
> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: dinsdag 28 augustus 2001 14:18
> To: sigtran
> Subject: [SUA Issue] Hop Counter
> 
> 
> Hi all,
> 
> Currently, Hop Counter has no home.  It has been removed from the 
> Flags/QoS Parameter.
> 
> I will entertain discussion on this for the next few days.
> 
> The issue is: 
> 
> Is a Hop Counter needed.  If so, what messages (mandatory/option) is
> it present in & when is it decremented.
> 
> John
> 
> 
> > -----Original Message-----
> > From: ext Brian F. G. Bidulock [mailto:[email-masked]]
> > Sent: 24 August, 2001 07:52
> > To: [email-masked]
> > Subject: Re: SUAv7: Usage of Flag Parameters
> > 
> > 
> > Sandeep,
> > 
> > [email-masked] wrote: (Fri, 24 Aug 2001 09:53:24)
> > > 
> > > 
> > > Hi ,
> > > 
> > > I suggest following two text changes.
> > > 
> > > 1. Hop counter should be decremented at each relay node , 
> > GTT may and may not be
> > > performed at all relay nodes. To reflect this text in 
> > section 3.9.1 be changed
> > > to say
> > 
> > Relay nodes perform GTT by definition.
> > 
> > > 
> > > 3.9.1 Flags
> > > Hop counter is decremented each time the relay function is 
> > invoked within an
> > > intermediate (relay) node. The value of the hop counter is 
> > in the range 15 to 1.
> > 
> > This is already stated in Section 1.5.3
> > 
> > > 2. Hop counter parameter can not be passed across IP and 
> > SS7 networks, hence
> > > SCCP hop counter parameter looses meaning once a SCCP/SUA 
> > user message crosses
> > > network boundary.  So in the following text originating 
> > node can only be IP
> > > node.
> > > 
> > > Section 1.5.3
> > > To prevent looping, a hop counter is used. The originating 
> > end node (be it an
> > > SS7 or an IP node) sets the value of the hop counter to the 
> > maximum value (15 or
> > > less)
> > 
> > This is already stated in Section 1.5.3.  An SS7 node (SG) 
> > can set the value
> > if the implementation wants to.
> > 
> > --brian
> > 
> > -- 
> > Brian F. G. Bidulock
> > [email-masked]
> > http://www.openss7.org/
> > 
> > 
> > ---
> > You are currently subscribed to sigtran as: [email-masked]
> > To unsubscribe send a blank email to 
> > [email-masked]
> > 
> 
> 
> ---
> You are currently subscribed to sigtran as: 
> [email-masked]
> To unsubscribe send a blank email to
> [email-masked]
> 
> 
> ---
> You are currently subscribed to sigtran as: 
> [email-masked]
> To unsubscribe send a blank email to 
> [email-masked]
> 

---
You are currently subscribed to sigtran as: [email-masked]
To unsubscribe send a blank email to [email-masked]