q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
GREENWOOD / BLACK WALL STREET WILMINGTON 1898 LITTLE ROCK NINE TUSKEGEE STUDY ROSEWOOD 1923 THE TUSKEGEE AIRMEN SENECA VILLAGE BLACK TOWNS GREENWOOD / BLACK WALL STREET WILMINGTON 1898 LITTLE ROCK NINE TUSKEGEE STUDY ROSEWOOD 1923 THE TUSKEGEE AIRMEN SENECA VILLAGE BLACK TOWNS
What's New!
THE JOURNEY THROUGH TIME
BHP HOME BEFORE AMERICA 1800–1936 1937–1957 1958–1980 1981–2000 2001–PRESENT

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Ruler of the Mali Empire in the 14th century

Mansa Musa was the ruler of the Mali Empire in West Africa. Details recorded here should be sourced; unknown information is left blank.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

IP in IP

IP in IP is an IP tunneling protocol that encapsulates one IP packet in another IP packet. To encapsulate an IP packet in another IP packet, an outer header is added with Source IP, the entry point of the tunnel, and Destination IP, the exit point of the tunnel. While doing this, the inner packet is unmodified (except the TTL field, which is decremented). The Don't Fragment and the Type Of Service fields should be copied to the outer packet. If the packet size, including the outer header, is greater than the Path MTU, the encapsulator fragments the packet. The decapsulator will reassemble the packet.

IP packet encapsulated in IP packet

[edit]
IP in IP Encapsulation
Outer IPv4 header[1]
Offset Octet 0 1 2 3
Octet Bit 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
0 0 Version (4) IHL DSCP ECN Total length
4 32 Identification Flags Fragment offset
8 64 Time to Live Protocol (4) Header checksum
12 96 Source address
16 128 Destination address
20 160 (Options) (if IHL > 5)
⋮ ⋮
56 448
60 480 Encapsulated IP packet (TTL decremented, but unaltered otherwise)
64 512
⋮ ⋮

Outer IP header has the following fields:

Version: 4 bits
This field is the Internet Protocol version number. Set to 4 to indicate IPv4.
Internet Header Length (IHL): 4 bits
This field is the length of outer IP header.
Differentiated Services Code Point (DSCP): 6 bits
This field is copied from the inner IP header.
Explicit Congestion Notification (ECN): 2 bits
This field is copied from the inner IP header.
Total Length: 16 bits
This field is the length of the encapsulated IP packet (including Outer IP Header, Inner IP Header, IP Payload).
Identification: 16 bits
This field is used to identify the fragments of a datagram which will be helpful while reassembling the datagram as the encapsulator might fragment the datagram. For the Outer IP Header, a new number is generated.
Flags: 3 bits
There are three flags defined within this field.
Reserved (R): 1 bit
Reserved. Should be set to 0.
Don't Fragment (DF): 1 bit
This field specifies whether the datagram can be fragmented or not. If this bit is set to 1 in the inner header, then the outer header also have this bit set to 1 saying that this datagram cannot be fragmented. If this bit is set to 0 in the inner header, then the outer header may set to 0 or 1.
More Fragments (MF): 1 bit
This field is required when the datagram is fragmented saying whether the datagram contains some more fragments. This field is not copied from inner header.
Fragment offset: 13 bits
This field is used while reassembling the fragments.
Time To Live (TTL): 8 bits
This field is used to track the lifetime of the datagram. The inner header TTL is decremented before encapsulation and is not changed in decapsulator. The outer header TTL is set to value such that the datagram is delivered to tunnel end point.
Protocol: 8 bits
This field indicates the transport layer protocol of the datagram following this header. The value is set to 4 for IP in IP. Not to be mistaken with value 4 in the Version field, which indicates IPv4.
Header Checksum: 16 bits
This field is the IP checksum of outer header.
Source IP Address: 32 bits
This field is the IP address of the encapsulator.
Destination IP Address: 32 bits
This field is the IP address of the decapsulator.
Options: 0 - 320 bits, padded to multiples of 32 bits
This field in general is NOT copied from the inner IP header. New options can be added.

See also

[edit]

References

[edit]
  1. ^ C. Perkins (October 1996). IP Encapsulation within IP. Network Working Group. doi:10.17487/RFC2003. RFC 2003. Proposed Standard. Updated by RFC 3168 and 6864.

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

No preview image
Wikipedia

IP in IP

IP in IP is an IP tunneling protocol that encapsulates one IP packet in another IP packet. To encapsulate an IP packet in another IP packet, an outer header is added with Source IP, the entry point of the tunnel, and Destination IP, the exit point of the tunnel. While doing this, the inner packet is unmodified (except the TTL field, which is decremented). The Don't Fragment and the Type Of Service fields should be copied to the outer packet. If the packet size, including the outer header, is greater than the Path MTU, the encapsulator fragments the packet. The decapsulator will reassemble the packet.

MORE →
No preview image
Wikipedia

Field encapsulation

In computer programming, field encapsulation involves providing methods that can be used to read from or write to the field rather than accessing the field directly. Sometimes these accessor methods are called getX and setX (where X is the field's name), which are also known as mutator methods. Usually the accessor methods have public visibility while the field being encapsulated is given private visibility - this allows a programmer to restrict what actions another user of the code can perform. Compare the following Java class in which the name field has not been encapsulated: with the same example using encapsulation: In the first example a user is free to use the public name variable however they see fit - in the second however the writer of the class retains control over how the private _name variable is read and written by only permitting access to the field via its getName and setName methods.

MORE →
No preview image
Wikipedia

Mean-field particle methods

Mean-field particle methods are a broad class of interacting type Monte Carlo algorithms for simulating from a sequence of probability distributions satisfying a nonlinear evolution equation. These flows of probability measures can always be interpreted as the distributions of the random states of a Markov process whose transition probabilities depends on the distributions of the current random states. A natural way to simulate these sophisticated nonlinear Markov processes is to sample a large number of copies of the process, replacing in the evolution equation the unknown distributions of the random states by the sampled empirical measures. In contrast with traditional Monte Carlo and Markov chain Monte Carlo methods these mean-field particle techniques rely on sequential interacting samples. The terminology mean-field reflects the fact that each of the samples (a.k.a. particles, individuals, walkers, agents, creatures, or phenotypes) interacts with the empirical measures of the process. When the size of the system tends to infinity, these random empirical measures converge to the deterministic distribution of the random states of the nonlinear Markov chain, so that the statistical interaction between particles vanishes. In other words, starting with a chaotic configuration based on independent copies of initial state of the nonlinear Markov chain model, the chaos propagates at any time horizon as the size the system tends to infinity; that is, finite blocks of particles reduces to independent copies of the nonlinear Markov process. This result is called the propagation of chaos property. The terminology "propagation of chaos" originated with the work of Mark Kac in 1976 on a colliding mean-field kinetic gas model.

MORE →
Wikipedia

Metonymy

Metonymy () is a figure of speech in which a concept is referred to by the name of something associated with that thing or concept. For example, the word "suit" may refer to a person from groups commonly seen wearing business attire, such as business executives, bankers, or lawyers. Metonyms are common in everyday speech and encapsulate a range of other ideas, such as synecdoche and metalepsis. Metonyms are similar to metaphors but where metaphors rely on analogous characteristics to form a comparison, a metonymy is caused by general association of the two objects of comparison.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

What prosperous Tulsa district became widely known as “Black Wall Street”?

The Greenwood District.