NANC 423

Low Tech Interface (LTI) Transaction Filter

Origination Date :09/11/2007

Originator:Verisign

Description:

PIM 64 – Currently, when a SPID has both LTI & SOA connectivity/usage, LTI generated transactions are broadcast to their respective SOA as well.  This potentially creates more work for the SOA when receiving unwanted LTI data.  This change order requests functionality that filters out or eliminates unwanted LTI transaction data broadcast to the SOA.  Should the need arise to see this data in the SOA it could be obtained via an Audit-in activity.

 Nov ’07 LNPAWG discussion:

Clarification was provided by VeriSign on the specific situation, whereby the LTI is used for a specific SPID that only uses the LTI for half their users, and the SOA for the other half of those users.  The ones initiated from the LTI would use this indicator to determine whether or not to send transactions to the SOA.

Func Backward Compatible:  Yes

The NPAC SMS would add a tunable parameter to the SPID-level customer profile that could be set to allow the suppression of LTI initiated transactions to the respective SOA.

Req 1 – Service Provider SOA LTI Transaction Indicator

NPAC SMS shall provide a Service Provider SOA LTI Transaction Flag Indicator tunable parameter which defines whether a SOA will receive/not-receive LTI-generated transactions over their SOA connection.

Req 2 – Service Provider SOA LTI Transaction Indicator Modification

NPAC SMS shall allow NPAC Personnel, via the NPAC Administrative Interface, to modify the Service Provider SOA LTI Transaction Flag Indicator tunable parameter.

Req 3 – Service Provider SOA LTI Transaction Indicator Usage

NPAC SMS shall send LTI-generated transactions over the SOA connection only when the Service Provider SOA LTI Transaction Flag Indicator tunable parameter is set to TRUE 

Func Backward Compatible:  Yes

The NPAC SMS would add a tunable parameter to the SPID-level customer profile that could be set to allow the suppression of LTI initiated transactions to the respective SOA.

  • Req 1 – Service Provider SOA LTI Transaction Indicator

NPAC SMS shall provide a Service Provider SOA LTI Transaction Flag Indicator tunable parameter which defines whether a SOA will receive/not-receive LTI-generated transactions over their SOA connection.

  • Req 2 – Service Provider SOA LTI Transaction Indicator Modification

NPAC SMS shall allow NPAC Personnel, via the NPAC Administrative Interface, to modify the Service Provider SOA LTI Transaction Flag Indicator tunable parameter.

  • Req 3 – Service Provider SOA LTI Transaction Indicator Usage

NPAC SMS shall send LTI-generated transactions over the SOA connection only when the Service Provider SOA LTI Transaction Flag Indicator tunable parameter is set to TRUE.

Final Resolution:

Moved to closed/no-action.

Related Release:

N/A.

Status: Closed