---
oid: "1.3.6.1.4.1.2636.3.759.1.2.2.1.4"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2636 jnxMibs(3) jnxGdoiMIB(759) jnxGdoiMIBObjects(1) jnxGdoiPeers(2) jnxGdoiGmTable(2) jnxGdoiGmEntry(1) jnxGdoiGmRegKeyServerIdType(4)}"
description: "jnxGdoiGmRegKeyServerIdType OBJECT-TYPE "
last-modified: "2021-11-30"
tags: [oid-repository]
---

## OID: `1.3.6.1.4.1.2636.3.759.1.2.2.1.4` (last updated: 2021-11-30)

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2636 jnxMibs(3) jnxGdoiMIB(759) jnxGdoiMIBObjects(1) jnxGdoiPeers(2) jnxGdoiGmTable(2) jnxGdoiGmEntry(1) jnxGdoiGmRegKeyServerIdType(4)}
```

### Description

```asn1
jnxGdoiGmRegKeyServerIdType OBJECT-TYPE 
SYNTAX JnxGdoiIdentificationType 
MAX-ACCESS read-only 
STATUS current 
DESCRIPTION 
"The Identification Type Value used to parse the identity 
information of this Group Member's registered Key Server. 
RFC 4306 defines all valid types that can be used as an 
identifier. These identification types are sent as the 'SRC 
ID Type' and 'DST ID Type' of the KEK and TEK payloads for 
GDOI GROUPKEY-PULL and GROUPKEY-PUSH exchanges." 
REFERENCE 
"RFC 3547 - Sections: 5.3. SA KEK payload 
5\.4.1. PROTO\_IPSEC\_ESP 
RFC 4306 - Section: 3.5. Identification Payloads"

**Classification**: MIB object for network management

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.